Ryan Barrett

Breakthrough! https://github.com/bluesky-social/atproto/issues/2806#issuecomment-2427494656 led me to try deactivating with `#account` instead of `#tombstone`, which works, and can be undone! Specifically with `active: false, status: deactivated` and then `active: true`. Exciting!

Right. I'll probably be able to do it manually, eventually, but probably by creating a new bridged account, not reviving your old one.

Shipped this, it's live! Tested with https://bsky.app/profile/snarfed.mas.to.ap.brid.gy , blocking deactivated it, and then unblocking and re-following brought it back again, including its posts.

Started figuring out how to bring back old tombstoned Bluesky repos by recreating them as new repos. Recreating the repos works fine, but oddly I can't get them to emit...

Right, no display name or bio is what I mentioned in https://github.com/snarfed/bridgy-fed/issues/1130#issuecomment-2430525165 . @derspyy I'm trying something else. Could you unfollow @[email protected] and then follow again?

@derspyy sorry about that, my fault. Try again now? (And thanks for your patience!)

Thanks for trying @derspyy. Looks like this is still https://github.com/snarfed/arroba/issues/34. Argh. I'll need to work on that soon.

> It is, but Misskey incorrectly requires activity `@id`s to be on the same domain as the signing user. > I believe Bridgy Fed currently places `Follow`-`Accept` activities on `fed.brid.gy`...

Good question, I don't know, it's a UX design judgment call. Probably in general, for all URLs over 27 chars, for readability; I'm guessing that's what bsky.app does. But I...

Yup, your instincts are spot on, we just need to refresh our locally stored DID docs regularly. Should be straightforward!