The repo record itself doesn’t have versioning so you would only see the latest version or in the case of a deleted record nothing at all, iirc.
The relay that puts out the firehose has a retention period of a couple of days, so you could replay recent events but not from the beginning of time.

there's no need to subpoena anything. The government (or anyone else) can subscribe to the event log service aka firehose and get all the events in the network for archival. You should assume they already do.

Familiarity for Substack users seems to me like higher priority than anything else. I wouldn't waste time on a whole new design at the beginning: the time where you have the least amount of information you'll ever have. There's a reason bsky looks just like Twitter.

The short answer is that Bluesky is not in charge of your following list. You are.
You're the only one who can edit the list of accounts you follow and nobody else has permissions to edit it for you; not Bluesky, not the people you follow, only you.

We already have a few bookmark services on atproto but if you're going to build one please use the community lexicon for it so it will be compatible with other good citizens of the ecosystem: community.lexicon.bookmarks.bookmark

What's cardy? Can't find anything about it online.

exactly. The longer we go without private records, the more tempted apps will be to stop seeing the PDS as canonical storage.

At first I thought you were being sarcastic, describing how Bluesky's underlying protocol works, more or less. But it's pretty insightful that you saw it this way without knowing that. Nice!

Personal Data Server, the component that stores your account and content like your posts and images. A separate component is the apps that interact with it like Bluesky and many others.

If the client is going to the app for the optimistic update why not go to the app for the original mutation too? Seems cleaner.

Good to hear! Good luck with the rest of the process recovering your account

Careful, using a script to follow people from an old account can get your account suspended. Ask me how I know.

OAuth scopes are coming soon. In the meantime it's just like any OS app that is not sandboxed: The reputational damage an app would suffer for doing something malicious like that is enough to stop it.

With potentially some exceptions like maybe an app needs to keep an internal record that you agreed to the Terms for legal reasons but deleting everything else.

You would still be "visible" in the sense that you can see Obama's profile on Tangled because it's a Bluesky profile record but that's just a matter of educating the user on what it means.

A reasonable standard would be: there's no difference between a "deactivated" app and an app you've never used. So deactivation would be deleting the collection(s) from your PDS and all your indexed data on that App, including private/internal data.

I'm so happy with how it turned out I'm gonna like my own article.