Post

Post deletes being complete happening soon! Thanks @jay.bsky.team! NOTE regardless of network, scraping happens and can't really be stopped. For years a bot reposted my every tweet. Please be careful. BlueSky is a playground - not a different universe - even if we rejoice in momentary reprieve.

Jay 🦋@jay.bsky.team

yep, we probably need a new user FAQ. But on this issue, the PRs to hard delete blobs and accounts are landing soon, and rebasing to hard delete posts is following. https://github.com/bluesky-social/atproto/pull/963

every user in atproto has a signed data repository, which is quite similar to a git repository. changes get written in commits and each repository maintains a history (commit log) we do that because the network is largely pull-based, and maintaining the history makes catchup sync efficient

Is it ever envisioned that users will control those signing keys? I assume today during signnin with passwords we have an association to a centrally stored signing key used under the covers since we don't have the key ourselves. But is that the longterm vision?

up until august that was the design, but it introduced a ton of complexity. we decided instead to use recovery keys that can override the signing keys for rehoming your repository. you *do* control the recovery key and that way you're protected but not signing every op

I do see the challenges with user held signing keys for portability and recovery at scale. Today's use of simple passwords is temporary? Are you looking at stronger auth methods before the userbase scales up? Tommorow is world password day & it would be great to use modern methods like passkey

0 reposts4 likes

No replies yet.