Skip to content

Update bit.site to bit.ink #2106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update bit.site to bit.ink #2106

wants to merge 1 commit into from

Conversation

bit-ink
Copy link
Contributor

@bit-ink bit-ink commented Aug 11, 2025

Describe your changes

Update bit.ink Peer ID and Address.

Last merged related PR: #1767

Files changed

  • docs/how-to/peering-with-content-providers.md

What issue(s) does this address?

Does this update depend on any other PRs?

Checklist before requesting a review

  • Passing the beta version of the Check Markdown links for modified files check. Action results can be viewed here.

Checklist before merging

  • Passing all required checks (The beta Check Markdown links for modified files check is not required)

Copy link
Contributor

🚀 Build Preview on IPFS ready

@2color
Copy link
Member

2color commented Aug 24, 2025

None of the multiaddrs advertised by this peer are publicly reachable.

https://delegated-ipfs.dev/routing/v1/peers/12D3KooWRgfueeG1Re92hdxsEqsxW3pNmxnZmsbGUA4oSRRQyhbw

{
  "Peers": [
    {
      "Addrs": [
        "/dns4/72-201-76-39.k51qzi5uqu5dgvylknxzn6yrx1pujksg9ljqavx412q9fwx361t3ebu0vf6wja.libp2p.direct/tcp/32851/tls/ws/p2p/12D3KooWBikGjEd7K8WAwPBXBz8XRXyw3vtxDXige2heu1kZ8RuP/p2p-circuit",
        "/ip4/108.61.205.36/udp/4001/quic-v1/p2p/12D3KooWJWBiZcHU2zs74RDTsJpruEzKfWrQBfgjcoTN99AC2GWk/p2p-circuit",
        "/ip4/72.201.76.39/udp/32851/quic-v1/p2p/12D3KooWBikGjEd7K8WAwPBXBz8XRXyw3vtxDXige2heu1kZ8RuP/p2p-circuit",
        "/ip4/108.61.205.36/udp/4001/quic/p2p/12D3KooWJWBiZcHU2zs74RDTsJpruEzKfWrQBfgjcoTN99AC2GWk/p2p-circuit",
        "/ip4/72.201.76.39/udp/32851/webrtc-direct/certhash/uEiDoUGqPTQufKJQ2YGFCwktQomLyjSBAMPbp7m8Rcz8EqA/p2p/12D3KooWBikGjEd7K8WAwPBXBz8XRXyw3vtxDXige2heu1kZ8RuP/p2p-circuit",
        "/ip4/72.201.76.39/tcp/32851/p2p/12D3KooWBikGjEd7K8WAwPBXBz8XRXyw3vtxDXige2heu1kZ8RuP/p2p-circuit",
        "/ip4/108.61.205.36/tcp/4001/p2p/12D3KooWJWBiZcHU2zs74RDTsJpruEzKfWrQBfgjcoTN99AC2GWk/p2p-circuit",
        "/ip4/72.201.76.39/udp/32851/quic-v1/webtransport/certhash/uEiAM3Jy14wQwAyhmRQQbPwjB9FvfICfz4V7Sek9RJ7z7Xg/certhash/uEiDDysJOBFtPSb9OYuGgCoESReQRkgU9FqPFUCPTedoLVA/p2p/12D3KooWBikGjEd7K8WAwPBXBz8XRXyw3vtxDXige2heu1kZ8RuP/p2p-circuit"
      ],
      "ID": "12D3KooWRgfueeG1Re92hdxsEqsxW3pNmxnZmsbGUA4oSRRQyhbw",
      "Schema": "peer"
    }
  ]
}

Nor do they correlate with the A Record of node-1.ipfs.bit.ink which is 183.233.190.90.

Either way, we are considering removing this section, as it often falls out of date, and reflects problems with content routing which should be fixed.

@bit-ink bit-ink closed this Aug 25, 2025
@bit-ink bit-ink reopened this Aug 25, 2025
@bit-ink
Copy link
Contributor Author

bit-ink commented Aug 25, 2025

It was found that the IPFS server configuration was incorrect, and it has been updated.

@2color
Copy link
Member

2color commented Aug 25, 2025

Why does the peer record only support TCP (no quick or web friendly transports)

@2color
Copy link
Member

2color commented Aug 25, 2025

Closing this as we decided to remove this section, given that many of the peers on the list were offline, and we don't want the burden of maintenance of this list in a public IPFS resource.

@2color 2color closed this Aug 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants