Natanael

Catnip

Client software (browsers, etc) would need to resolve it, just like mailto:

It certainly should happen, but it’s not likely because it takes too much momentum

https://www.timesofisrael.com/for-years-netanyahu-propped-up-hamas-now-its-blown-up-in-our-faces/

Strange how their attempts to establish peace through other groups was undermined by Netanyahu, who literally helped Hamas get cash

Local NAS, local security cameras, in-house streaming, LAN multiplayer, local torrent-like data sharing (FYI, Windows Update and more uses the local network to share update between computers by default, so it gets downloaded once and then shared internally)

Atproto is better at global views thanks to stuff like content addressing than activitypub is. That’s better to reduce fragmentation.

Tell that to the people running their own PDS servers and the people running whitewind and all the other services built on the protocol

There’s already others running other relays. The appview is the most difficult, but in theory indexes on top of the data could be shared too which would reduce the need for each appview to have everything saved in advance

You don’t have to deal with being sent links to other people’s mail servers’ public mail lists, and then figuring out how to get your own mail server to figure out how to join that conversation. Mailto links open in your mail client which already knows what your server is.

Mastodon don’t have a mailto: equivalent, pages can’t identify themselves in a way your browser recognize as a Mastodon host, your browser won’t remember your Mastodon account(s) specifically. And federation sync issues aren’t even dealt with here…

That’s what bluesky’s DID based account identity does. Unless you make that key the sole authority (no key rotation, like nostr) then you need a registry as authority (like bluesky’s PLC registry)

Bluesky specifically lets the account hosting server handle your auth, the directory points to where your account server is as in when you enter your handle, every 3rd party service and federated peer can do OAuth seamlessly to your account host. Then you can log into every compatible site with your handle, instead of having to get redirected “home” before you can interact. Your account server’s repository keeps records of all your posts and your social network, and you can even migrate seamlessly across hosts.

They’re actively working on making it easier to fork the entire platform.

There’s already 3rd party account hosts, moderation labelers, feed generators, and alternative implementations like whitewind (blogging system on top of the same account repo & lexicon architecture) were you can use the exact same account. All of these works together independently of which hosts / providers you use.

Relays and microblogging appviews (a fully functional bluesky mirror) are technically possible but more expensive to duplicate but there’s work on making that practical too.

You can already bypass PLC by using DID:Web for account identity.

The single most important thing if you want to be able to recover from bluesky going bad is to just back up your account recover signing key, and to keep a recent backup of the repo to preserve your post history and social network (follows, etc).

All the rest can be rebuilt if you have your account hey and backup. The content addressing will make it seamless!

It’s open source and designed to literally not be reliant on the company running it. Start a community appview and plc and you can bring your entire account history with you

This time he bailed early though. He’s got no control of the site

And then there’s 20 apps at $15/month each which collectively costs like $2 to run

They got funding from Twitter and Jack was on the board for a bit, but he bailed and formally quit (funny enough he bailed because they did more moderation than he wanted)

The atproto architecture is technology though. Open source and all

Spamhaus, spamcop