Bluesky bridged accounts sometimes get "stuck" and stop bridging

[Benniepie]

From bluesky-social/atproto#3214 :

For a while now in Bridgy Fed, we've seen a steady trickle of our ATProto accounts get "stuck" at some point, and records we emit for them stop appearing in bsky.app. Early on, I think one trigger here was emitting records that didn't pass lexicon validation, but I'm pretty confident we squashed that a while back, and this is still happening.

On the technical side, this is probably our top priority ask for the Bluesky team right now, since we don't have any visibility into what's happening or what we can do about it.

@bnewbold nodded to the need for tools here recently in https://bsky.app/profile/bnewbold.net/post/3lcmad4ktkk26 . https://atproto.tools/records (RIP?) was somewhat useful in the past when this was relay related, as was running my own relay locally to debug. I suspect the cases of this now are more appview related, though. (I don't have evidence, just a hunch.) I'd love something sooner, this is one of the common classes of support request I currently get for Bridgy Fed, but I'm open to ideas.

A few users recently have said this happened when they set a custom domain handle on their bridged account. That seems like an unrelated coincidence to me, but I guess it's possible?

Here are a couple examples:

• @makigas.es, https://bsky.app/profile/did:plc:xhyk5f7cpndo4lrlkylf7l4h, stopped updating 2 mos ago
  recent record: at://did:plc:xhyk5f7cpndo4lrlkylf7l4h/app.bsky.actor.profile/self, commit bafyreiekz3uorn2kbz5ynftvhuv66ampfwga27cgr7ikf6xaqihkwxzp5e, atproto.brid.gy subscribeRepos seq 5505770, emitted 2024-12-09 11:03:20 UTC
• @nosgustalinux.es, https://bsky.app/profile/did:plc:b4zgkneq5mcqm3gpmztfbm4w, stopped updating 1w ago
  recent record: at://did:plc:b4zgkneq5mcqm3gpmztfbm4w/app.bsky.feed.post/3lcukk3k5sw32, commit bafyreibgnstiaoknz6xdihalkuyatcjoj2sdl7w3luqhdzczb4nmmsxgqq , atproto.brid.gy subscribeRepos seq 5505071, emitted 2024-12-09 between 10:53:26 and 11:05:38 UTC (not sure when for your relay specifically)

Interestingly, when I try to goat get these two at:// URIs, I get:

error: XRPC ERROR 400: InvalidRequest: in com.atproto.repo.getRecord, string cid with value `''`: is invalid for format cid

...but getRecord on atproto.brid.gy returns them fine, eg https://atproto.brid.gy/xrpc/com.atproto.repo.getRecord?repo=did:plc:b4zgkneq5mcqm3gpmztfbm4w&collection=app.bsky.feed.post&rkey=3lcukk3k5sw32 , and when I paste the records and their lexicons into https://atproto.tools/lexicons , it says they validate ok.

---

Original description:

My bridged web account has stopped posting to Blue Sky since around the time I did the DNS validation (added a txt dns record). Apologies if I've done or not done something! Domain is atpgeo.com could you have a look please?

[snarfed]

Hey, sorry for the trouble! Bridged accounts in Bluesky occasionally get "stuck" like this. Bridgy Fed is happily committing your new posts to its ATProto repo, and emitting them to the Bluesky relay, but they're not making it all the way into the appview. We don't know why yet. Ugh.

[Benniepie]

Thanks for coming back to me. Is there anything I can do at this end to unblock it? Eg change the way my posts are tagged or remove the txt record from the domain dns, would this revert the username? Could either of these help?

[snarfed]

Afaik this is unrelated to your domain handle. You can test that by changing your handle bak and forth if you want though!

Otherwise, no, I don't know of an easy fix yet, sorry. I talk with the Bluesky team about it on and off, hopefully we'll figure something out soon.

[tnonate]

Howdy, I just did this myself (username set to my domain from Mastodon to Bluesky) and also noticed this issue. Bluesky appears to be pulling my website instead of my Mastodon account. (If you want to see what I mean, the domain is thenewoil.org)

1. Any chance you could update the documentation to warn about this issue for people who might be considering it? Or are you hoping to have it resolved so fast that it's not worth mentioning?

2. How can I roll back to the default way of doing things until this is resolved?

Thanks!

[snarfed]

@tnonate hmm, sorry for the trouble! https://bsky.app/profile/thenewoil.org looks like it's correctly bridging https://mastodon.thenewoil.org/@thenewoil to me...?

(I do see https://bsky.app/profile/thenewoil.org.web.brid.gy for your web site too, but that's separate.)

[tnonate]

@snarfed Well, disregard, I guess I just didn't give it enough time.

I was bridging from Mastodon to Bluesky, I followed the instructions here and after a while the existing link (https://bsky.app/profile/thenewoil.mastodon.thenewoil.org.ap.brid.gy) stopped working but the new profile was nowhere to be found. When I checked GitHub I saw this issue and thought it described my issue the same, but I guess it just took longer than expected to populate.

Sorry for the confusion and noise.

[fluffy-critter]

https://bsky.app/profile/sockpuppet.band and https://bsky.app/profile/beesbuzz.biz seem to have also fallen prey to this.