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

Emit requestCrawl automatically? #36

Open
DavidBuchanan314 opened this issue Dec 28, 2024 · 3 comments
Open

Emit requestCrawl automatically? #36

DavidBuchanan314 opened this issue Dec 28, 2024 · 3 comments

Comments

@DavidBuchanan314
Copy link
Owner

At this point several millipds users have set up an instance and had it "not work", and the only issue was a lack of requestCrawl.

An automatic requestCrawl on first startup (or every startup?) would alleviate that sharp edge for new users.

However, I'm a bit reluctant to hardcode "the" bluesky pbc relay address, as a matter of principle.

Maybe the real solution is better docs, and/or a federation troubleshooting guide.

@DavidBuchanan314
Copy link
Owner Author

oh shit I just had an excellent idea.

I'll make millipds itself:

a) record the address of all recent inbound relay connections
b) listen for inbound requestCrawls. when it receives a requestCrawl, it forwards that request to all the relays it knows about

And then, instead of hardcoding bsky.network as the default requestCrawl target, I can hardcode my own PDS url.

@DavidBuchanan314
Copy link
Owner Author

mild problem: we only know the IP of connecting relays (and relay-likes), not necessarily their hostname

@DavidBuchanan314
Copy link
Owner Author

I'm upgrading that problem from "mild" to "significant", there's no reliable way to infer a working hostname from the bare IP

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

No branches or pull requests

1 participant