ATProto integration

[erlend-sh]

• Import (archive) Bluesky importer #205
• Login: Login with Bluesky (atproto) #206
• Alias: Alias masto/bsky username #249
• Domains: ATProto integration  #275 (comment)
• Client: myb style: weird theme zeucapua/myb#32
• key rotation / recovery key
• PDS interop
• bespoke PDS on top of Leaf? (late 2025 at best)

Account and Identity

Our answer to the call is that Weird can handle this well:

Account Backups: services and tools to help backup account data and identity control. This could be things like cronjobs which do daily repo CAR file and "blob" backups to an S3-compatible bucket, or Shamir secret sharing between friends to recover PLC rotation keys. Monitoring and alerting for unexpected account changes.

PLC Rotation Key Management: most users in the network today do not have complete control over their network identity, because they have not registered a locally-controlled rotation key. Getting everyday users in control of their identities will take work, but the first steps are to increase accessibility of this to developers, technical users, and high-profile / high-value accounts. This could include command line tools, integrations in password managers and "wallets", support or plugins for hardware enclaves, as well as tutorials and guides to security best practices.

Account Data Exports: the current repo export format is CAR files. These are complete, app-neutral, can be used for account migration, and have a well documented format. They can be processed with tools like 'goat', but are not particularly accessible for many users. More accessible tools to convert and explore CAR exports would be helpful: indexing into sqlite, converting to spreadsheets (CSV) or JSON, displaying and browsing bsky posts, etc.

Privacy

If folks want to implement less-visible content in atproto projects today, we recommend doing what we did for the temporary Bluesky Chat DMs system: implement a [de-]centralized server and talk to it over Lexicon APIs using service proxying (aka, service authentication). In the future, when private data is ready to use, it should be possible to have users migrate their content over.

Weird/Leaf can supplement ATproto with several privacy facilities, largely thanks to Willow and Meadowcap.

[zicklag]

Bluesky Handle Provider

Weird can be an easy way to get custom handles for BlueSky. Already weird gives each user who signs up a handle, like zicklag.weird.one or amy.norml.one. We'll have a small number of suffixes to pick from.

Since Weird is already running its own DNS server it will be very easy to allow you to connect your bluesky account by logging into it from the Weird app and Weird can automatically setup your bluesky account to use your Weird handle.

It'd also be possible to implement something like https://www.skyname.io/ where users are allowed to bring their own domains and contribute them as a public suffix, earning a commission for users that sign up using their suffix.

You can also share your domain with us. If people buy a subdomain that belongs to your domain, we will give you a commission. It's a great way to earn some extra income while helping others get their Bluesky handles.

Handles for community contributed suffixes would obviously come with less guarantees because the contributor has ultimate control over the domain if they ever want to take it back, but we can be transparent about that in Weird, and monitor the domain to notify users if the contributor changes the domain's nameserver to take back control of the domain records.

An advantage to using your Weird handle as your BlueSky handle is that it comes with a customizable links page, so that your BlueSky handle is also a real website.