You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered: