User page UI: show when Bluesky repo is deactivated/tombstoned

[comodoropet4]

Greetings!

I've followed the Bridgy Fed for Bluesky account with my uwu.social profile on Mastodon, and allowed it to follow me back to engage the federation process with Bluesky.

However, when I look up my profile over there, it doesn't exist. I search it up, no dice. I click on the link to it from the confirmation DM I got from the Bridgy Fed account, and the Bluesky app tells me the account doesn't exist.

My user page on bridgy fed shows that the federation has been made, and it even has a log of my public activity from Mastodon that should be federated on Bluesky.

I hope it's not a big ask to request help on getting this issue solved.

Thanks!

[snarfed]

Hey, sorry for the trouble! Have you looked at https://fed.brid.gy/docs#troubleshooting ?

[comodoropet4]

Hey, sorry for the trouble! Have you looked at https://fed.brid.gy/docs#troubleshooting ?

It's alright! I know it's a one-man effort, per the same information at the bottom of the docs, so I hope it's all good 😊

I've indeed gone through all the steps and nothing has helped me.

• My Mastodon account is more than two weeks old and has a profile picture.
• I contacted the uwu.social admin and he told me that neither bsky.brid.gy nor brid.gy were being moderated at all. I checked the Moderated Servers section myself and indeed they don't appear over there.

Other than that, and the obvious considerations of not blocking bridgy fed and stuff, I have nothing else I can try from my end.

[qazmlp]

Interestingly, trying to view the account in ATProto Browser results in an internal server error: https://atproto-browser.vercel.app/at/katakislives.uwu.social.ap.brid.gy
(as opposed to not finding the account at all when I try to look up an account that really doesn't exist).

The lookup for my own bridged account works fine (but notably shows an empty TODO collection).

[snarfed]

Aha, @comodoropet4 looks like you blocked @bsky.brid.gy@bsky.brid.gy at 2024-09-07 23:14:13 UTC, activity id https://uwu.social/112a55b8-b158-4680-826a-3c2cd1c50bc9 . That disables the bridge for your account, and sadly we can't yet undo that for fediverse => Bluesky, even if you unblock and refollow. https://fed.brid.gy/docs#opt-out

Sorry for the bad news. Hopefully this will be undoable eventually, feel free to follow #1130 .

Ideally we'd show this on your Bridgy Fed user page! I'll track that UI update in this issue.

[comodoropet4]

Aha, @comodoropet4 looks like you blocked @bsky.brid.gy@bsky.brid.gy at 2024-09-07 23:14:13 UTC, activity id https://uwu.social/112a55b8-b158-4680-826a-3c2cd1c50bc9 . That disables the bridge for your account, and sadly we can't yet undo that for fediverse => Bluesky, even if you unblock and refollow. https://fed.brid.gy/docs#opt-out

Sorry for the bad news. Hopefully this will be undoable eventually, feel free to follow #1130 .

Ideally we'd show this on your Bridgy Fed user page! I'll track that UI update in this issue.

Well, that's unfortunate 😢

Indeed I blocked the Bridgy Fed account once in an attempt to make it work, since I tried to engage the federation process back when my account was less than two weeks old.

Alas, I'll follow the suggested issue to stay up on whether it'll be fixed.

Thanks for letting me know! 😊

[Tamschi]

The original cause of this problem (tombstoning the DID) is now fixed, but stuck accounts aren't generally reactivated yet.
There's been some progress on that starting at #1130 (comment), but it's likely this requires fixing snarfed/arroba#34 first.

Solving that in general may obsolete this issue.

[snarfed]

Yes! Right now, if you don't have a specific protocol like Bluesky enabled, we don't show the visible link to it on your user page. That's probably enough for this.

I'm going to go ahead and close this and file a new issue for fixing tombstoned accounts that tried (unsuccessfully) to re-enable themselves.

[Tamschi]

I'm going to go ahead and close this and file a new issue for fixing tombstoned accounts that tried (unsuccessfully) to re-enable themselves.

(For future reference, that's now #1446.)