From: Prayank <prayank@tutanota•de>
To: ogunden@phauna•org
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin.org missing bitcoin core version 22.0
Date: Wed, 20 Oct 2021 16:47:17 +0200 (CEST) [thread overview]
Message-ID: <MmT9umZ--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Hi Owen,
> When I search for "download bitcoin core" my top result is bitcoin.org, which is out of date and doesn't have 22.0
This is an issue related to SEO which only website owners can fix or maybe others can help who know better.
> It seems confusing to have two sites that seemingly both represent bitcoin core.
There is only one website which represents Bitcoin Core full node implementation. You can download Bitcoin Core from https://bitcoincore.org
Ensure that you are using the correct domain as some people have registered domains which use punycode, looks similar and spreading malware: https://bitcoin.stackexchange.com/a/107738/
> Maybe the download links could be removed from bitcoin.org and instead it could just link to bitcoincore.org?
You can open an issue in website repository: https://github.com/bitcoin-dot-org/bitcoin.org and tag Cobra who owns the website and domain.
Alternately you could also try a derivative of Bitcoin Core: https://bitcoinknots.org/ maintained by Luke Dashjr.
--
Prayank
A3B1 E430 2298 178F
[-- Attachment #2: Type: text/html, Size: 1744 bytes --]
next reply other threads:[~2021-10-20 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 14:47 Prayank [this message]
2021-10-20 19:20 ` Owen Gunden
2021-10-20 19:37 ` Pieter Wuille
2021-10-20 19:49 ` Owen Gunden
2021-10-20 19:43 ` Charles Hill
2021-10-20 20:18 ` Kate Salazar
2021-11-05 8:17 ` Prayank
2021-11-05 10:52 ` damian
2021-11-05 14:45 ` yanmaani
2021-11-08 3:02 ` ZmnSCPxj
2021-11-09 12:49 ` Prayank
-- strict thread matches above, loose matches on Subject: below --
2021-10-20 21:50 Andrew Chow
2021-10-20 12:54 Owen Gunden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MmT9umZ--3-2@tutanota.de \
--to=prayank@tutanota$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=ogunden@phauna$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox