New millipds users are not able to federate with bsky appview #3215
-
|
Around the 17th of November, I set up an instance of millipds at https://pds.dev.retr0.id/ Everything worked great (mostly), and the account is visible at https://bsky.app/profile/david.dev.retr0.id Over the past few days, a few other people have set up millipds instances:
Unfortunately, they've not had so much luck. I can't debug very effectively from my vantage point, but the first two accounts in particular appear to be connecting to the relay correctly, just not the appview - none of their profiles or posts are visible in bsky.app. The issue may well be on millipds's end, but it's hard to debug further without knowing what's going on inside the appview - I'm hoping we might be able to get some insight there. Of course, I'm happy to answer questions about "what millipds does", along with my setup for I recently wrote up instructions for setting up a new account on millipds, which they may have been following: https://github.com/DavidBuchanan314/millipds/blob/main/docs/ACCOUNTS.md |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
Possibly related: #3214 "Accounts on federated PDSes sometimes get "stuck" and stop updating in the appview" (although in this case, they never worked in the first place) |
Beta Was this translation helpful? Give feedback.
-
|
Something that may be related - millipds does not yet properly set the |
Beta Was this translation helpful? Give feedback.
-
|
Booting-up millipds to take a look. |
Beta Was this translation helpful? Give feedback.
-
|
As far as I can tell millipds is working just fine (also very fun to hack around with). I think I've narrowed it down to an issue related to backfill behaviors in the Bluesky appview, digging into it! |
Beta Was this translation helpful? Give feedback.
-
|
@DavidBuchanan314 I think we got to the bottom of this, and those profiles linked above appear to be indexed now. My millipds setup is also being indexed again normally. My hunch about "what's different" about millipds that triggered the behavior is that it may have to do with either a. not having a commit event for the repo init (just a commit block), or b. emitting some events prior to the first account/identity events for the repo. Both should have been things that we were recovering from—and I believe have been addressed—but may be why the same thing wasn't happening on the mushroom servers. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for looking into this! So everything millipds currently does wrt account activation is at least "not incorrect"? I definitely plan on automating the account/identity events in the future (so they happen at more correct times), and I can think about emitting a "commit zero" that commits the initial empty MST |
Beta Was this translation helpful? Give feedback.
@DavidBuchanan314 I think we got to the bottom of this, and those profiles linked above appear to be indexed now. My millipds setup is also being indexed again normally. My hunch about "what's different" about millipds that triggered the behavior is that it may have to do with either a. not having a commit event for the repo init (just a commit block), or b. emitting some events prior to the first account/identity events for the repo. Both should have been things that we were recovering from—and I believe have been addressed—but may be why the same thing wasn't happening on the mushroom servers.