Ryan Barrett

OK @ShreyanJain9 I've manually refreshed your DID doc. Mind trying again? If blobs work now, that confirms this hypothesis.

Sadly it's not really solved afaik. Bridgy Fed would need to subscribe to the PLC directory's audit log, https://github.com/did-method-plc/did-method-plc#audit-logs , which it doesn't yet do. Afaik there isn't a websocket...

`#account` etc events are now documented, https://atproto.com/specs/account#pds-account-migration , but I can't tell if PDS migrations or other DID doc updates generate `#account` events on the relay firehose. Hrm.

Aha, https://github.com/bluesky-social/atproto/discussions/3175 has the answer: > Overall, this means that account migration should result in three events coming from the relay: an #identity (from new PDS), an #account (from new...

Done! At least going forward. Existing accounts with stale DID docs can be refreshed by clicking the 🔁 button on their Bridgy Fed user page.

Hey John, thanks for the catch! Out of curiosity, do you know of any Bridgy Fed consumers that do full JSON-LD compaction/expansion and would choke on this as is? Obviously...

Did this a while ago, in snarfed/granary@8ce611b60eadc797b915f023d18f9c22ac72665b!

Thanks for filing! Yeah we started short circuiting out of processing earlier for non-opted-in accounts a while ago; sorry for misleading you here. I'm a little cautious about this for...

Lots more discussion on this in #1535

Here's a rough design for a first pass at this: * Start with read-only, one-way notifications of new, non-bridged replies, and maybe quotes, and maybe @-mentions, but not likes or...