Skip to content
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

Lists of all fediverse instances, Bluesky PDSes, Nostr relays #552

Open
snarfed opened this issue Jun 18, 2023 · 9 comments
Open

Lists of all fediverse instances, Bluesky PDSes, Nostr relays #552

snarfed opened this issue Jun 18, 2023 · 9 comments
Labels

Comments

@snarfed
Copy link
Owner

snarfed commented Jun 18, 2023

These would be useful as hints to which protocol a given URL or domain is on. Right now we have to sniff in Protocol.for_id.

These lists are constantly changing, and some are big, eg the fediverse currently has 20-25k instances, so we'd need some mechanism to regularly fetch and update them. Probably just store each list in a single file on Cloud Storage or similar and load it into memory at startup.

@snarfed snarfed changed the title Maintain and use updated lists of all fediverse instances, Bluesky PDSes, Nostr relays Lists of all fediverse instances, Bluesky PDSes, Nostr relays Aug 29, 2023
@snarfed
Copy link
Owner Author

snarfed commented Oct 12, 2023

https://nodes.fediverse.party/ has an easily downloadable list for the fediverse, updated every 6h: https://nodes.fediverse.party/nodes.json

@WisTex
Copy link

WisTex commented Feb 15, 2024

Will you be able to detect that a server is multi-protocol? For example, Friendica and Hubzilla are both multi-protocol (if the admin has enabled multiple protocols).

@WisTex
Copy link

WisTex commented Feb 26, 2024

I didn't see it on your list, but there is also https://fedidb.org/

@snarfed
Copy link
Owner Author

snarfed commented Feb 26, 2024

Yes! FediDB is great. It didn't exist when I originally filed this issue. 😁

@Tamschi
Copy link
Collaborator

Tamschi commented Dec 5, 2024

For most fediverse instances, it should be possible to detect them on demand via NodeInfo for the domain and potentially WebFinger with the URL as parameter.

@snarfed
Copy link
Owner Author

snarfed commented Dec 5, 2024

Oh sure, for a given domain, definitely. The more interesting question is how to detect newly created instances in general, ie domains that we don't know about at all yet.

@Tamschi
Copy link
Collaborator

Tamschi commented Dec 6, 2024

I don't think we should, for ActivityPub. It doesn't seem relevant to the bridge's functions to do this proactively.

@snarfed
Copy link
Owner Author

snarfed commented Dec 6, 2024

It would definitely help internally. We often have to figure out which protocol a given URL belongs to, which often requires making an external HTTP fetch. This would often prevent that.

@Tamschi
Copy link
Collaborator

Tamschi commented Dec 9, 2024

Ah, right, but that's much better served with an on-demand cache than with a global list too.

(Arguably, constructing a global or even reasonably complete list for ActivityPub is not possible in the first place.)

This was referenced Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants