#ATProtocol

You want to leave the instance your account lives on. There are various reasons why you could make such a decision.

Maybe the admin made a call you disagree with or maybe the instance is shutting down.

What happens to your followers, your handle, and your posts then?

On the Fediverse, leaving is a move: followers transfer through the Move activity, your follows/lists/blocks export as CSV and JSON to re-import, and your posts stay behind (Mastodon can export an archive but can't import it into a new account). LOLA, the SWICG data-portability draft, is the effort to close that last gap.

In the ATmosphere, the four things an instance fuses together are split into separate layers, so most "switching" isn't a move at all - only relocating your data server is, and even then your DID keeps your handle and followers intact.

Neither is strictly better. They trade off identity continuity, content portability, and self-governance in different ways.

→ https://federatedmind.com/account-portability-fediverse-vs-atmosphere/?utm_source=mastodon&utm_medium=social&utm_campaign=account-portability

#Fediverse #ActivityPub #Mastodon #ATProtocol #Bluesky #OpenWeb #AccountMigration

You want to leave the instance your account lives on. There are various reasons why you could make such a decision.

Maybe the admin made a call you disagree with or maybe the instance is shutting down.

What happens to your followers, your handle, and your posts then?

On the Fediverse, leaving is a move: followers transfer through the Move activity, your follows/lists/blocks export as CSV and JSON to re-import, and your posts stay behind (Mastodon can export an archive but can't import it into a new account). LOLA, the SWICG data-portability draft, is the effort to close that last gap.

In the ATmosphere, the four things an instance fuses together are split into separate layers, so most "switching" isn't a move at all - only relocating your data server is, and even then your DID keeps your handle and followers intact.

Neither is strictly better. They trade off identity continuity, content portability, and self-governance in different ways.

→ https://federatedmind.com/account-portability-fediverse-vs-atmosphere/?utm_source=mastodon&utm_medium=social&utm_campaign=account-portability

#Fediverse #ActivityPub #Mastodon #ATProtocol #Bluesky #OpenWeb #AccountMigration

Bluesky, the self-proclaimed savior of open ecosystems, just trademarked AT Protocol to ensure it can be used "widely"—which naturally means locking it up tighter than Fort Knox. 🏰🔒 Because nothing says "open ecosystem" like slapping a #trademark on every possible variant of your precious protocol. 🤦‍♂️📜
https://atproto.com/blog/at-protocol-trademark #Bluesky #ATProtocol #openEcosystem #techNews #digitalRights #HackerNews #ngated

Bluesky Trademarks AT Protocol

Interesting approach to 'participating' in an "open, decentralized" network system...

#Bluesky #ATProtocol

Bluesky, the self-proclaimed savior of open ecosystems, just trademarked AT Protocol to ensure it can be used "widely"—which naturally means locking it up tighter than Fort Knox. 🏰🔒 Because nothing says "open ecosystem" like slapping a #trademark on every possible variant of your precious protocol. 🤦‍♂️📜
https://atproto.com/blog/at-protocol-trademark #Bluesky #ATProtocol #openEcosystem #techNews #digitalRights #HackerNews #ngated

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

Building on Bluesky or the AT Protocol with Swift? ATProtoKit wraps the complex xrpc and API logic into something that feels native. Still unstable, but it's the quickest way to get a bot or client running without fighting the protocol.

🔗: https://github.com/MasterJ93/ATProtoKit by Christopher Jr Riley

#Swift #Bluesky #ATProtocol

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

Building on Bluesky or the AT Protocol with Swift? ATProtoKit wraps the complex xrpc and API logic into something that feels native. Still unstable, but it's the quickest way to get a bot or client running without fighting the protocol.

🔗: https://github.com/MasterJ93/ATProtoKit by Christopher Jr Riley

#Swift #Bluesky #ATProtocol

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

@brewsterkahle @internetarchiveeurope @dweb #DWebCamp #DWeb #ATProtocol #ActivityPub #Fediverse

3/3 Participants will take part in talks, workshops, and hands-on collaboration exploring what a more resilient, open, and decentralised web could look like in practice.

DWeb Camp is a space for building, not just talking about, the web we want.

@brewsterkahle @internetarchiveeurope @dweb #DWebCamp #DWeb #ATProtocol #ActivityPub #Fediverse

3/3 Participants will take part in talks, workshops, and hands-on collaboration exploring what a more resilient, open, and decentralised web could look like in practice.

DWeb Camp is a space for building, not just talking about, the web we want.

@brewsterkahle @internetarchiveeurope @dweb #DWebCamp #DWeb #ATProtocol #ActivityPub #Fediverse

Artikel door @Marloezovic over #Mastodon en #Bluesky in @nrc_nl.

„Je zult beleidsdiscussies krijgen die je nooit eerder had”, voorspelt hij... „Maar dat is ook goed. In plaats van die beslissingen in de handen leggen van een paar miljardairs, moeten mensen erover nadenken.”

https://www.nrc.nl/nieuws/2026/06/10/de-technologie-achter-mastodon-versus-bluesky-welke-past-beter-bij-het-sociale-medium-van-nrc-a4929641?utm_source=clipboard&utm_medium=clipboard&utm_campaign=share&utm_term=share-modal&gift_token=4929641~1781727324~bJWrFJ0IEeKfgABQVoV_mg~4Z4JkjS4j6v3htFz1xPaCMDuf3ogsUnnV6XPDxR_xhQ

#GiftLink

Zie ook deze eerdere thread:

https://mastodon.nl/@Marloezovic/116635382316202759

#socialmedia #fediverse #activitypub #ATprotocol

Artikel door @Marloezovic over #Mastodon en #Bluesky in @nrc_nl.

„Je zult beleidsdiscussies krijgen die je nooit eerder had”, voorspelt hij... „Maar dat is ook goed. In plaats van die beslissingen in de handen leggen van een paar miljardairs, moeten mensen erover nadenken.”

https://www.nrc.nl/nieuws/2026/06/10/de-technologie-achter-mastodon-versus-bluesky-welke-past-beter-bij-het-sociale-medium-van-nrc-a4929641?utm_source=clipboard&utm_medium=clipboard&utm_campaign=share&utm_term=share-modal&gift_token=4929641~1781727324~bJWrFJ0IEeKfgABQVoV_mg~4Z4JkjS4j6v3htFz1xPaCMDuf3ogsUnnV6XPDxR_xhQ

#GiftLink

Zie ook deze eerdere thread:

https://mastodon.nl/@Marloezovic/116635382316202759

#socialmedia #fediverse #activitypub #ATprotocol

Servers currently using Starling:
https://starling.fediverse.observer/list

#Starling #PHP #fediverse #ActivityPub #ATProtocol

Servers currently using Starling:
https://starling.fediverse.observer/list

#Starling #PHP #fediverse #ActivityPub #ATProtocol

(3/3)

Negativ:

- technokratischer Top-Down-Ansatz, VC Vibes

- will dezentrale Alternativen ("die nicht mit Leadern reden") gerne überholen

- liberal bis neoliberal bis elitär (s. Board Members)

- zentralisiert und auf schnelle Skalierung fokussiert

- Dialog bis zur Schmerzgrenze (auch rechtsradikale Akteur*innen erst mal willkommen)

#atProtocol & #wSocial vs. #ActivityPub & #Mastodon

(2/3)

Positiv:

- europäisch, demokratisch, rechtsstaatlich orientiert

- Fokus auf Privacy, dennoch Schutz gegen KI und Bots

- klare Kommunikationsregeln, Moderation mit Haltung

- transparente Algorithmen

#atProtocol & #wSocial vs. #ActivityPub & #Mastodon

(1/3)

#atProtocol & #wSocial vs. #ActivityPub & #Mastodon

Was haltet ihr denn so von Anna Zeiter und ihrem neuen #SocialMedia - Projekt?

https://www.swr.de/swr1/leute/neue-social-media-plattform-w-social-das-steckt-dahinter-100.html

Das hier wäre mein erster Take. Die Einschätzung basiert auf dem verlinkten Interview.

#Starling is a lightweight #PHP #fediverse server you can install by just copying files over FTP to a shared host. No PostgreSQL, no workers, no DevOps. Owning your data with #ActivityPub can be much simpler than with #ATProtocol. Have you tried it?
https://github.com/dfaria-eu/Starling

#Starling is a lightweight #PHP #fediverse server you can install by just copying files over FTP to a shared host. No PostgreSQL, no workers, no DevOps. Owning your data with #ActivityPub can be much simpler than with #ATProtocol. Have you tried it?
https://github.com/dfaria-eu/Starling

#Starling is a lightweight #PHP #fediverse server you can install by just copying files over FTP to a shared host. No PostgreSQL, no workers, no DevOps. Owning your data with #ActivityPub can be much simpler than with #ATProtocol. Have you tried it?
https://github.com/dfaria-eu/Starling

So #Vine is coming back, this time as #DiVine!
Does anyone know anyone who can get me an invite code? I want in!
The App is coming back with no #AI allowed, and will allow people to own their own content.

For the geeks: it's built on the #OpenSocial protocol #Nostr, and apparently they're experimenting with integrating the #ATProtocol, future integration with #ActivityPub, the protocol behind #Mastodon and #Flipboard.
https://www.youtube.com/watch?v=zUGnNIh60-0

Daniel Holmgren, head of protocol at Bluesky, will give a talk at FediForum on Tuesday, April 28, titled:

"Atproto: A Technical Introduction"

Have you ever wondered how #ATProtocol actually works? Come join us to find out, online! https://fediforum.org

/cc @dholms.at@bsky.brid.gy

Bridgy Fed is one of the underappreciated but load-bearing parts of the open social web: you don't need to choose any more whether to create an account in the #ActivityPub-based #Fediverse (like #Mastodon) or the #ATProtocol-based #ATmosphere (like #Bluesky).

Daniel Holmgren, head of protocol at Bluesky, will give a talk at FediForum on Tuesday, April 28, titled:

"Atproto: A Technical Introduction"

Have you ever wondered how #ATProtocol actually works? Come join us to find out, online! https://fediforum.org

/cc @dholms.at@bsky.brid.gy

Bridgy Fed is one of the underappreciated but load-bearing parts of the open social web: you don't need to choose any more whether to create an account in the #ActivityPub-based #Fediverse (like #Mastodon) or the #ATProtocol-based #ATmosphere (like #Bluesky).

I want to applaud @rose.bsky.team and @mellifluousbox for appearing on stage together and expressing a desire to cooperate. As I've said for a long time, #Bluesky and #Mastodon, #ActivityPub and #ATProtocol should not be fighting each other. The real opposition are the oligarch-controlled, enshittified, manipulating major commercial platforms. We have no chance of making a dent into their dominance if the revolution fights itself instead.

I want to applaud @rose.bsky.team and @mellifluousbox for appearing on stage together and expressing a desire to cooperate. As I've said for a long time, #Bluesky and #Mastodon, #ActivityPub and #ATProtocol should not be fighting each other. The real opposition are the oligarch-controlled, enshittified, manipulating major commercial platforms. We have no chance of making a dent into their dominance if the revolution fights itself instead.

I want to applaud @rose.bsky.team and @mellifluousbox for appearing on stage together and expressing a desire to cooperate. As I've said for a long time, #Bluesky and #Mastodon, #ActivityPub and #ATProtocol should not be fighting each other. The real opposition are the oligarch-controlled, enshittified, manipulating major commercial platforms. We have no chance of making a dent into their dominance if the revolution fights itself instead.

ATmosphereConf 2026: Great Energy, But We Need to See the Money

https://limeleaf.coop/blog/atmosphere-2026-great-energy-but-we-need-to-see-the-money/

#ATmosphereConf #ATmosphere #ATProtocol

🦫 alert!

We published the second episode of "Teach the Web new Tricks", featuring
native support for ATProto ! Learn more how we improve user agency and privacy at https://webbeef.org/atproto.html :

- Native at:// protocol support.
- Log in your PDS and forget OAuth !
- Authorize 3rd parties

Since we're on Mastodon, please help us figure out what we can do to add native ActivityPub support!

#atproto #ATProtocol #useragent #activitypub

🦫 alert!

We published the second episode of "Teach the Web new Tricks", featuring
native support for ATProto ! Learn more how we improve user agency and privacy at https://webbeef.org/atproto.html :

- Native at:// protocol support.
- Log in your PDS and forget OAuth !
- Authorize 3rd parties

Since we're on Mastodon, please help us figure out what we can do to add native ActivityPub support!

#atproto #ATProtocol #useragent #activitypub

🦫 alert!

We published the second episode of "Teach the Web new Tricks", featuring
native support for ATProto ! Learn more how we improve user agency and privacy at https://webbeef.org/atproto.html :

- Native at:// protocol support.
- Log in your PDS and forget OAuth !
- Authorize 3rd parties

Since we're on Mastodon, please help us figure out what we can do to add native ActivityPub support!

#atproto #ATProtocol #useragent #activitypub

Alternatives to watch out to #ditchDiscord

https://flotilla.social #nostr
https://a.roomy.space by @zicklag and @erlend (of @Bonfire) #ATprotocol
@commetchat based on @matrix
https://stoat.chat (ex @revoltchat)
https://spacebar.chat
https://fluxer.app
@movim #xmpp

#FLOSS

What does a Discord replacement look like, and how might the open social web play a part?
@laurenshof
looks at what needs to happen — different apps built on the same protocols, active collaboration to make sure it all fits together — and how that's already fundamental to the Atmosphere and fediverse.

flip.it/QdL.F…

#ActivityPub #Mastodon #ATProtocol #Bluesky #Blacksky #Discord #Technology #Tech

What does a Discord replacement look like, and how might the open social web play a part?
@laurenshof
looks at what needs to happen — different apps built on the same protocols, active collaboration to make sure it all fits together — and how that's already fundamental to the Atmosphere and fediverse.

flip.it/QdL.F…

#ActivityPub #Mastodon #ATProtocol #Bluesky #Blacksky #Discord #Technology #Tech

This is such an interesting thread as it exposes the friction between ATProtocol/ActivityPub. Clearly, there are some cultural issues.

It's important to understand and I say this often to our own desktop projects - we are always stronger together than apart.

We are not competitors. We are allies.

Understandably we might compete on investment and volunteers but those sort themselves.

#gnome #kde #linuxapps #activitypub #atprotocol

At #ATmosphereConf

https://atprotocol.dev/atmosphereconf/

https://atprotocol.dev/atmosphereconf-2025-talks/

@boris (one of the organizers) is talking in front of the audience. (Boris and I are both from Vancouver.)

I see Fediverse people here. For example, @damon (of We Distribute fame) is sitting next to me.

#ATProto #ATProtocol #DeSo #Bluesky #bsky

Will Mastodon, the platform that keeps the #Fediverse alive, miss a strategic opportunity to bring official institutions on board at scale?

By watching how #EuroSky is being marketed compared to #Mastodon, it certainly seems that way.

I wish the folks at Mastodon would invest in more professional marketing, similar to what we're seeing from its rival, Bluesky.

There was a major meeting in the EU Parliament focused on this topic, yet there was no announcement or microblog post from Mastodon. Zero engagement.

Compare these two approaches:

https://fed.brid.gy/r/https://bsky.app/profile/did:plc:ituoear7k6qx3smjfoxhufm4/post/3me7pxwrgerri

#ActivityPub #ATProtocol #EU #lobby

It does feel like #activitypub has been frozen in amber, maybe this will help. I'm hoping #mastodon developers get involved or its very hard to see how things will change.

Especially the Live Online Account Portability stuff which #atprotocol just has from the get go.

New Blog post: I go over decentralized social media protocols like #nostr #ATProtocol and #ActivityPub and compare the tradeoffs between them.

https://blog.mauve.moe/posts/decentralized-social-media

New Blog post: I go over decentralized social media protocols like #nostr #ATProtocol and #ActivityPub and compare the tradeoffs between them.

https://blog.mauve.moe/posts/decentralized-social-media

New Blog post: I go over decentralized social media protocols like #nostr #ATProtocol and #ActivityPub and compare the tradeoffs between them.

https://blog.mauve.moe/posts/decentralized-social-media

https://arewedecentralizedyet.online/ has been switched over to new datasources for the social networks, coming from my own #fediverse crawler and #atprotocol observer. Improvements include better heuristics for fediverse user counts and real monthly active user stats for #bluesky/#atproto . I'm also making more raw data available, both for the most recent counts and historical data at https://arewedecentralizedyet.online/data/

Overall, doesn't change the conclusions much, but I'm very happy with these new datasources.

It does feel like #activitypub has been frozen in amber, maybe this will help. I'm hoping #mastodon developers get involved or its very hard to see how things will change.

Especially the Live Online Account Portability stuff which #atprotocol just has from the get go.

It does feel like #activitypub has been frozen in amber, maybe this will help. I'm hoping #mastodon developers get involved or its very hard to see how things will change.

Especially the Live Online Account Portability stuff which #atprotocol just has from the get go.

W っていう新しい SNS、 X 対抗という意味なんだろうけどネーミングからして X カウンター感を感じるな。 #ATProtocol 対応らしい

https://cybernews.com/tech/europe-social-media-w/

W っていう新しい SNS、 X 対抗という意味なんだろうけどネーミングからして X カウンター感を感じるな。 #ATProtocol 対応らしい

https://cybernews.com/tech/europe-social-media-w/

https://arewedecentralizedyet.online/ has been switched over to new datasources for the social networks, coming from my own #fediverse crawler and #atprotocol observer. Improvements include better heuristics for fediverse user counts and real monthly active user stats for #bluesky/#atproto . I'm also making more raw data available, both for the most recent counts and historical data at https://arewedecentralizedyet.online/data/

Overall, doesn't change the conclusions much, but I'm very happy with these new datasources.

https://arewedecentralizedyet.online/ has been switched over to new datasources for the social networks, coming from my own #fediverse crawler and #atprotocol observer. Improvements include better heuristics for fediverse user counts and real monthly active user stats for #bluesky/#atproto . I'm also making more raw data available, both for the most recent counts and historical data at https://arewedecentralizedyet.online/data/

Overall, doesn't change the conclusions much, but I'm very happy with these new datasources.

Bluesky "weakened" their age gate in their mobile app.

I can now see posts in the Bluesky app again.

#ATProto #ATProtocol #Bluesky #bsky #Privacy

If I try to view a post on Bluesky web-based app, while being logged in, I see the following age-gate (in the attached screen-shots) — and am prevented from seeing the post.

If I try to view the post without being logged in, I don't get the age-gate, and can just see the post.

#ATProto #ATProtocol #Bluesky #bsky #Privacy

The Bluesky Android mobile app is telling me I cannot use Bluesky unless I provide my date of birth.

(I haven't looked at Bluesky in a while — so, this might not be a new thing.)

I wonder if you can get around this by just installing an alternative (3rd party) Bluesky mobile app.

#ATProto #ATProtocol #Bluesky #bsky #Privacy

Eurosky dawns: Building Infrastructure for Sovereign Social Media – Open Future

Not sure how to take this: Mastodon already exists, it’s a European project and it’s struggling to take off.

I don’t think that the problem with Mastodon’s lack of adoption is the ActivityPub protocol. What advantages does the ATProtocol have that will lead to wider adoption?

developing alternative social media infrastructure that is not controlled by Big Tech or venture capital-backed US corporations, anchored within EU jurisdiction, and designed to foster a more pluralistic information ecosystem.

Source: Eurosky dawns: Building Infrastructure for Sovereign Social Media – Open Future

Eurosky dawns: Building Infrastructure for Sovereign Social Media – Open Future

Not sure how to take this: Mastodon already exists, it’s a European project and it’s struggling to take off.

I don’t think that the problem with Mastodon’s lack of adoption is the ActivityPub protocol. What advantages does the ATProtocol have that will lead to wider adoption?

developing alternative social media infrastructure that is not controlled by Big Tech or venture capital-backed US corporations, anchored within EU jurisdiction, and designed to foster a more pluralistic information ecosystem.

Source: Eurosky dawns: Building Infrastructure for Sovereign Social Media – Open Future

Eurosky dawns: Building Infrastructure for Sovereign Social Media – Open Future

Not sure how to take this: Mastodon already exists, it’s a European project and it’s struggling to take off.

I don’t think that the problem with Mastodon’s lack of adoption is the ActivityPub protocol. What advantages does the ATProtocol have that will lead to wider adoption?

developing alternative social media infrastructure that is not controlled by Big Tech or venture capital-backed US corporations, anchored within EU jurisdiction, and designed to foster a more pluralistic information ecosystem.

Source: Eurosky dawns: Building Infrastructure for Sovereign Social Media – Open Future

🛰️ 왜 사람들은 X·Facebook을 떠나 Bluesky로 모일까?
데이터 소유권과 서비스 다양성을 기반으로 한 차세대 SNS

🌐AT-protocol과 Bluesky, 탈중앙 SNS를 향한 새로운 접근
👤이성민 (boltless)

티켓 https://event-us.kr/fossforall/event/110400
세션 https://2025.fossforall.org/sessions/

#FOSSforAll #Bluesky #ATProtocol #탈중앙SNS #커뮤니티

🛰️ 왜 사람들은 X·Facebook을 떠나 Bluesky로 모일까?
데이터 소유권과 서비스 다양성을 기반으로 한 차세대 SNS

🌐AT-protocol과 Bluesky, 탈중앙 SNS를 향한 새로운 접근
👤이성민 (boltless)

티켓 https://event-us.kr/fossforall/event/110400
세션 https://2025.fossforall.org/sessions/

#FOSSforAll #Bluesky #ATProtocol #탈중앙SNS #커뮤니티

What will happen to the actual #Fediverse if Bluesky really succeeds as the mainstream federated social media platform with other interoperable apps?

#ATProtocol #ActivityPub #SocialMedia #BlueSky

What will happen to the actual #Fediverse if Bluesky really succeeds as the mainstream federated social media platform with other interoperable apps?

#ATProtocol #ActivityPub #SocialMedia #BlueSky

🛰️ 왜 사람들은 X·Facebook을 떠나 Bluesky로 모일까?
데이터 소유권과 서비스 다양성을 기반으로 한 차세대 SNS

🌐AT-protocol과 Bluesky, 탈중앙 SNS를 향한 새로운 접근
👤나사공 (boltless)

세션 https://2025.fossforall.org/sessions/
티켓 https://event-us.kr/fossforall/event/110400

#FOSSforAll #Bluesky #ATProtocol #탈중앙SNS #커뮤니티

🛰️ 왜 사람들은 X·Facebook을 떠나 Bluesky로 모일까?
데이터 소유권과 서비스 다양성을 기반으로 한 차세대 SNS

🌐AT-protocol과 Bluesky, 탈중앙 SNS를 향한 새로운 접근
👤나사공 (boltless)

세션 https://2025.fossforall.org/sessions/
티켓 https://event-us.kr/fossforall/event/110400

#FOSSforAll #Bluesky #ATProtocol #탈중앙SNS #커뮤니티

🛰️ 왜 사람들은 X·Facebook을 떠나 Bluesky로 모일까?
데이터 소유권과 서비스 다양성을 기반으로 한 차세대 SNS

🌐AT-protocol과 Bluesky, 탈중앙 SNS를 향한 새로운 접근
👤나사공 (boltless)

세션 https://2025.fossforall.org/sessions/
티켓 https://event-us.kr/fossforall/event/110400

#FOSSforAll #Bluesky #ATProtocol #탈중앙SNS #커뮤니티

ICYMI: https://arewedecentralizedyet.online/ now has some features that show trends over time so you can watch user data get spread out more as #bluesky goes through some moderation upheaval and credible #atprotocol alternatives ramp up

ICYMI: https://arewedecentralizedyet.online/ now has some features that show trends over time so you can watch user data get spread out more as #bluesky goes through some moderation upheaval and credible #atprotocol alternatives ramp up

ICYMI: https://arewedecentralizedyet.online/ now has some features that show trends over time so you can watch user data get spread out more as #bluesky goes through some moderation upheaval and credible #atprotocol alternatives ramp up

ICYMI: https://arewedecentralizedyet.online/ now has some features that show trends over time so you can watch user data get spread out more as #bluesky goes through some moderation upheaval and credible #atprotocol alternatives ramp up

@FinchHaven "...standardizing parts of #ATProtocol in an effort to establish long-term governance for the protocol."

"parts"?

OSI failed because every vendor wanted their existing, non-interoperable implementations to all somehow magically work by having a non-functional subset of all those vendors' implementations as required but anything they didn't want to change as option. result. the same non-interoperability.

the IETF and TCP/IP are ubiquitous now because they didn't try to avoid actual interoperability in the name of some useless "protocol compliance" of a subset.

color me skeptical that this will be a useful exercise.

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

Recently there has been a lot of discourse about ActivityPub and AT Protocol which has been quite dividing and heated.

Yesterday at the Social Web CG meeting (the group that maintains the ActivityPub and related specifications), I proposed releasing a statement that counters the narrative that one of these protocols must win, when both protocols can co-exist and have a lot to learn from each other.

The statement has been co-signed by various members of both Social Web CG, SocialCG, and the AT Protocol community.

“We do not win by tearing each other down, which only emboldens and empowers those who do not want either protocol to succeed.”

“Arguing between us only emboldens those that seek to derail and destroy efforts to build an open social web.”

You can read the full statement here:
https://writings.thisismissem.social/statement-on-discourse-about-activitypub-and-at-protocol/

This was originally in the swicg/general repository, and you can learn about that here:
https://github.com/swicg/general/blob/master/statements/2025-09-05-activitypub-and-atproto-discourse.md

#activitypub #atprotocol #atproto #SocialWeb

@rysiek #BlueSky isn't decentralized, in the same sense mastodon.social isn't decentralized. It's just one service on the #ATprotocol, just like mastodon.social is just one service on the #ActivityPub protocol.

Social Web Conferences

https://reiver.codeberg.page/social-web-conferences/

…

I am working on creating a list of upcoming Social Web Conferences.

Using a broad definition of "Social Web" that includes the ActivityPub, AT-Protocol, ATmosphere, Bluesky, Farcaster, Fediverse, Matrix, and Nostr.

…

These are conferences that I might want to attend. (And, perhaps you may, too.)

…

Is there anything else I should add to this?

#ActivityPub #ATProto #ATProtocol #bluesky #bsky #farcaster #fediverse #matrix #nostr #SocialWeb

Social Web Conferences

https://reiver.codeberg.page/social-web-conferences/

…

I am working on creating a list of upcoming Social Web Conferences.

Using a broad definition of "Social Web" that includes the ActivityPub, AT-Protocol, ATmosphere, Bluesky, Farcaster, Fediverse, Matrix, and Nostr.

…

These are conferences that I might want to attend. (And, perhaps you may, too.)

…

Is there anything else I should add to this?

#ActivityPub #ATProto #ATProtocol #bluesky #bsky #farcaster #fediverse #matrix #nostr #SocialWeb

Social Web Conferences

https://reiver.codeberg.page/social-web-conferences/

…

I am working on creating a list of upcoming Social Web Conferences.

Using a broad definition of "Social Web" that includes the ActivityPub, AT-Protocol, ATmosphere, Bluesky, Farcaster, Fediverse, Matrix, and Nostr.

…

These are conferences that I might want to attend. (And, perhaps you may, too.)

…

Is there anything else I should add to this?

#ActivityPub #ATProto #ATProtocol #bluesky #bsky #farcaster #fediverse #matrix #nostr #SocialWeb

Social Web Conferences

https://reiver.codeberg.page/social-web-conferences/

…

I am working on creating a list of upcoming Social Web Conferences.

Using a broad definition of "Social Web" that includes the ActivityPub, AT-Protocol, ATmosphere, Bluesky, Farcaster, Fediverse, Matrix, and Nostr.

…

These are conferences that I might want to attend. (And, perhaps you may, too.)

…

Is there anything else I should add to this?

#ActivityPub #ATProto #ATProtocol #bluesky #bsky #farcaster #fediverse #matrix #nostr #SocialWeb

Social Web Conferences

https://reiver.codeberg.page/social-web-conferences/

…

I am working on creating a list of upcoming Social Web Conferences.

Using a broad definition of "Social Web" that includes the ActivityPub, AT-Protocol, ATmosphere, Bluesky, Farcaster, Fediverse, Matrix, and Nostr.

…

These are conferences that I might want to attend. (And, perhaps you may, too.)

…

Is there anything else I should add to this?

#ActivityPub #ATProto #ATProtocol #bluesky #bsky #farcaster #fediverse #matrix #nostr #SocialWeb

Social Web Conferences

https://reiver.codeberg.page/social-web-conferences/

…

I am working on creating a list of upcoming Social Web Conferences.

Using a broad definition of "Social Web" that includes the ActivityPub, AT-Protocol, ATmosphere, Bluesky, Farcaster, Fediverse, Matrix, and Nostr.

…

These are conferences that I might want to attend. (And, perhaps you may, too.)

…

Is there anything else I should add to this?

#ActivityPub #ATProto #ATProtocol #bluesky #bsky #farcaster #fediverse #matrix #nostr #SocialWeb

We've got a first "normal" independent #Bluesky community PDS with >100 users, from Rudy Fraser's Blacksky :) Rudy has officially launched the PDS this weekend and has been helping people from his community migrate there from Bluesky PBC hosted servers whole day.

(There's also a new third party migration tool that was launched this week, which has been very helpful in this: https://pdsmoover.com 🐮)

Stats at: https://blue.mackuba.eu/directory/pdses

#atproto #ATProtocol

We've got a first "normal" independent #Bluesky community PDS with >100 users, from Rudy Fraser's Blacksky :) Rudy has officially launched the PDS this weekend and has been helping people from his community migrate there from Bluesky PBC hosted servers whole day.

(There's also a new third party migration tool that was launched this week, which has been very helpful in this: https://pdsmoover.com 🐮)

Stats at: https://blue.mackuba.eu/directory/pdses

#atproto #ATProtocol

We've got a first "normal" independent #Bluesky community PDS with >100 users, from Rudy Fraser's Blacksky :) Rudy has officially launched the PDS this weekend and has been helping people from his community migrate there from Bluesky PBC hosted servers whole day.

(There's also a new third party migration tool that was launched this week, which has been very helpful in this: https://pdsmoover.com 🐮)

Stats at: https://blue.mackuba.eu/directory/pdses

#atproto #ATProtocol

Beyond Microblogging: AT Protocol for Building Unique Social Apps (FediCon 2025)

by Boris Mann @boris

https://spectra.video/w/1FRNBf5MZ23NGFh5knt1fh

#FediCon #FediCon2025 #Bluesky #ATProtocol #ATProto

I uploaded the fifth FediCon 2025 video:

https://techhub.social/@fedicon/114983843422856184

#FediCon #FediCon2025 #Bluesky #ATProtocol #ATProto

Beyond Microblogging: AT Protocol for Building Unique Social Apps (FediCon 2025)

by Boris Mann @boris

https://spectra.video/w/1FRNBf5MZ23NGFh5knt1fh

#FediCon #FediCon2025 #Bluesky #ATProtocol #ATProto

Beyond Microblogging: AT Protocol for Building Unique Social Apps (FediCon 2025)

by Boris Mann @boris

https://spectra.video/w/1FRNBf5MZ23NGFh5knt1fh

#FediCon #FediCon2025 #Bluesky #ATProtocol #ATProto

I’ve thought about starting my own #ATProtocol PDS.

But the thing is, I’d just be re-posting everything from atomicpoet.org.

I wish #Akkoma worked better with @fed.brid.gy@fed.brid.gy. And actually, I’m going to be talking to @anujahooja about that.

#Fedicon

Okay, really interesting that rich text and out-of-band hashtags are supported in #ATProtocol but not the #Bluesky client.

Haha. I guess it’s not so different from #ActivityPub in some aspects.

#Fedicon

Neat to hear @boris talk about #ATProtocol (which is not #Bluesky), and building apps for it.

#Fedicon

I’ve thought about starting my own #ATProtocol PDS.

But the thing is, I’d just be re-posting everything from atomicpoet.org.

I wish #Akkoma worked better with @fed.brid.gy@fed.brid.gy. And actually, I’m going to be talking to @anujahooja about that.

#Fedicon

Okay, really interesting that rich text and out-of-band hashtags are supported in #ATProtocol but not the #Bluesky client.

Haha. I guess it’s not so different from #ActivityPub in some aspects.

#Fedicon

Neat to hear @boris talk about #ATProtocol (which is not #Bluesky), and building apps for it.

#Fedicon

Okay, really interesting that rich text and out-of-band hashtags are supported in #ATProtocol but not the #Bluesky client.

Haha. I guess it’s not so different from #ActivityPub in some aspects.

#Fedicon

Neat to hear @boris talk about #ATProtocol (which is not #Bluesky), and building apps for it.

#Fedicon

For anyone that can't come to my talk at #ForwardJS in #Ottawa tonight, check out my slides and run the speaker notes through the shittiest text to speech you can find to get a similar experience.

#ActivityPub #ATProtocol #Nostr

https://blog.mauve.moe/slides/decentralized-social-media/

We're really excited to be attending ATProto London this evening!

@FreddieJ and @saskia will both be there to chat decentralised social media, learn more about AT protocol, and enjoy the drinks very kindly provided by graze.social 🥂

We hope to see some of you there too!

#Decentralised #SocialMedia #Fediverse #Bluesky #Mastodon #MeetUp #ATProtocol #ATProto #London

We're really excited to be attending ATProto London this evening!

@FreddieJ and @saskia will both be there to chat decentralised social media, learn more about AT protocol, and enjoy the drinks very kindly provided by graze.social 🥂

We hope to see some of you there too!

#Decentralised #SocialMedia #Fediverse #Bluesky #Mastodon #MeetUp #ATProtocol #ATProto #London

@toddalstrom

Could someone explain a hypothetical.

If Vance were to join mastodon by comparison, assuming a similar desire to block from so many users, how differently might this play out based on the way that federation works within an Activity Pub context.

Just trying to understand the practical nature of the two protocols as applied to this case.

From what I understand of ATProrocol all that folks blocking achieves is it filters that account off for that user but otherwise the account can roll along just fine to other users. Correct me if I’m wrong here also. Keen to know more.

#jdvance #ActivityPub #atprotocol #Mastodon #Federation #Bluesky

Has anyone coined a colloquial term for #Bluesky's flavor of decentralization? #ActivityPub is often associated with the “federation" flavor, but that term doesn't feel applicable to Bsky/ #ATProtocol

At SXSW's Fediverse House, it didn't matter which platform or protocol you preferred — everyone was focused on the singular goal of building a better internet. We've uploaded videos and highlights of key conversations from the event and rounded them up in one post. Here you go:

https://about.flipboard.com/fediverse/fediverse-house-2025-roundup/

#SXSW #FediverseHouse #ATProtocol #ActivityPub #Fediverse #Federation #Flipboard #OpenSocial #OpenSocialWeb

At SXSW's Fediverse House, it didn't matter which platform or protocol you preferred — everyone was focused on the singular goal of building a better internet. We've uploaded videos and highlights of key conversations from the event and rounded them up in one post. Here you go:

https://about.flipboard.com/fediverse/fediverse-house-2025-roundup/

#SXSW #FediverseHouse #ATProtocol #ActivityPub #Fediverse #Federation #Flipboard #OpenSocial #OpenSocialWeb

At SXSW's Fediverse House, it didn't matter which platform or protocol you preferred — everyone was focused on the singular goal of building a better internet. We've uploaded videos and highlights of key conversations from the event and rounded them up in one post. Here you go:

https://about.flipboard.com/fediverse/fediverse-house-2025-roundup/

#SXSW #FediverseHouse #ATProtocol #ActivityPub #Fediverse #Federation #Flipboard #OpenSocial #OpenSocialWeb

If you use Bluesky, you may be interested in today’s news that now you can publish Surf feeds to Bluesky. 🦋

We’d love for you to test with us if you want! Here's more details:

https://bsky.app/profile/surf.social/post/3lnnpyqge5c2p

#bluesky #ATProtocol #customfeeds

If you use Bluesky, you may be interested in today’s news that now you can publish Surf feeds to Bluesky. 🦋

We’d love for you to test with us if you want! Here's more details:

https://bsky.app/profile/surf.social/post/3lnnpyqge5c2p

#bluesky #ATProtocol #customfeeds

If you use Bluesky, you may be interested in today’s news that now you can publish Surf feeds to Bluesky. 🦋

We’d love for you to test with us if you want! Here's more details:

https://bsky.app/profile/surf.social/post/3lnnpyqge5c2p

#bluesky #ATProtocol #customfeeds

そもそも、分散化という意味では #BlueSky と #Mastodon を比べるんじゃなくて、 #BlueSky と #Fediverse をくらべるべきなのではという気もする。 #ATProtocol と #ActivityPub の比較といったほうが良いかも。

#Mastodon の半分が最もメジャーなサーバー以外のサーバーに分散しているということは、#Fediverse という単位でみたらもっと多くの割合が分散しているということになるはず

If you're at #IJF25 next week, I'd love to say hi!

Particularly excited to chat about:

- Building a high-functioning technology culture
- #opensource for newsrooms
- Maintaining source anonymity
- The #fediverse / #atprotocol
- Collab with open source projects

But also, I'd love to hang out!

If you're at #IJF25 next week, I'd love to say hi!

Particularly excited to chat about:

- Building a high-functioning technology culture
- #opensource for newsrooms
- Maintaining source anonymity
- The #fediverse / #atprotocol
- Collab with open source projects

But also, I'd love to hang out!

🌐 Beyond Bluesky: The Rise of Decentralized Social Apps

The AT Protocol (ATProto), the open foundation behind Bluesky, is becoming a launchpad for next-gen social apps.

Some standout innovations:
・Flashes: A photo/video-sharing platform reminiscent of classic Instagram
・Spark: A video-first app with livestreaming on the way
・Streamplace: Livestreaming built with cryptographic creator protections
・Graze: Build, customize, and monetize your own social feeds

This signals a shift toward user-owned, open social ecosystems—a strong contrast to walled-garden platforms. Developers, creators, and users alike are embracing interoperability, privacy, and creative freedom.

👉 https://techcrunch.com/2025/03/30/beyond-bluesky-these-are-the-apps-building-social-experiences-on-the-at-protocol/

#DecentralizedWeb #ATProtocol #Bluesky #Web3 #SocialMediaInnovation #OpenSource

One of a number of take-aways from #ATmosphereConf —

The Bluesky team had a whole session (IndieSky) set up so that others could set up their own parallel Bluesky infrastructure.

The Bluesky team even wanted to make it less expensive for people to do it.

BUT — most the people in the room didn't seem interested in that per se.

Most the people in the room wanted their own ATProto infrastructure for their own applications / platforms built on ATProto.

#ATProto #ATProtocol #Bluesky #bsky #DeSo

This was also shared with me today, too, for the API (NSID) end-points for a Bluesky PDS.

https://github.com/snarfed/bridgy-fed/issues/1046#issuecomment-2174591566

#ATProto #ATProtocol #Bluesky #bsky #BlueskyPDS #PDS

I was looking into how a Bluesky PDS works from a programming point-of-view.

I came across this document the first time I looked around. (And then someone shared it with me again.)

https://github.com/bluesky-social/atproto/discussions/2350

It gives you an overview, but not a list of API (NSID) end-points to implement.

The only resource I could find for that is this:

https://github.com/blacksky-algorithms/rsky/tree/main/rsky-pds%2Fsrc%2Fapis

(You can infer it from the directory names and file names.)

#ATProto #ATProtocol #Bluesky #bsky #BlueskyPDS #PDS

One of a number of take-aways from #ATmosphereConf —

I felt like Paul Frazee (from Bluesky Org) was encouraging people deploy their own relays.

And, to think of the Bluesky Firehose Relay of everything — as a temporary thing to use, when first developing your app or platform. And then later, to deploy your own relay.

#ATProto #ATProtocol #Bluesky #bsky #DeSo

One of a number of take-aways from #ATmosphereConf —

Although there is only one Bluesky Firehose Relay of everything —

There are definitely other relays on the Bluesky ATmosphere.

I talked to more than one person who has their own relay on the Bluesky ATmosphere.

...

Although none of these alt-relays seemed to be meant to be broadly used by others. But, instead meant to be used for the platform they created using ATProto.

#ATProto #ATProtocol #Bluesky #bsky #DeSo

One of a number of take-aways from #ATmosphereConf —

Bluesky might deal with their relay-problem by introducing an architecture that looks a lot like the Fediverse.

Rather than applications getting everything from the Firehose Relay — applications would get data directly from the PDSes.

Although, it wasn't quite clear when whether this would be 'pull' or 'push'.

But still, it is looking a lot more like the Fediverse's architecture at that point.

#ATProto #ATProtocol #Bluesky #bsky #DeSo

RE: https://bsky.app/profile/did:plc:dy62mdx64e6i32pcuzfkekmk/post/3ll2zf7thf22v

#ATProto #ATProtocol #Censorship #bsky #Bluesky #DeSo #Moderation

Really awesome session at #ATmosphereConf talking about @lexicon.community. Such great discussion. #atdev #atprotocol

Really awesome session at #ATmosphereConf talking about @lexicon.community. Such great discussion. #atdev #atprotocol

Blaine Cook ( @blaine ) ( https://bsky.app/profile/blaine.bsky.social ) top priorities:

• moderation tools
• fixing the relay problem
• lexicons
• plus A LOT more

(This was a ATproto specific answer.)

#ATmosphereConf #ATProto #ATProtocol #Bluesky #bsky

At #ATmosphereConf

https://atprotocol.dev/atmosphereconf/

https://atprotocol.dev/atmosphereconf-2025-talks/

@boris (one of the organizers) is talking in front of the audience. (Boris and I are both from Vancouver.)

I see Fediverse people here. For example, @damon (of We Distribute fame) is sitting next to me.

#ATProto #ATProtocol #DeSo #Bluesky #bsky

I will be at ATmosphere Conference this weekend — March 22nd & 23rd.

https://atprotocol.dev/atmosphereconf/

#ATmosphereConf #ATProto #ATProtocol #Bluesky #bsky #DeSo #XRPC

Well, it’s a lucky day 🍀. Our latest update contains a pot o’ gold for the Bluesky community especially. Take a look at what’s in this release, including linking your Bluesky account to Surf, a new Home Timeline that unifies your Bluesky and Mastodon, and Bluesky notifications in our app. 🦋

#bluesky #mastodon #ATProtocol #activitypub #customfeeds #timeline

Well, it’s a lucky day 🍀. Our latest update contains a pot o’ gold for the Bluesky community especially. Take a look at what’s in this release, including linking your Bluesky account to Surf, a new Home Timeline that unifies your Bluesky and Mastodon, and Bluesky notifications in our app. 🦋

#bluesky #mastodon #ATProtocol #activitypub #customfeeds #timeline

Well, it’s a lucky day 🍀. Our latest update contains a pot o’ gold for the Bluesky community especially. Take a look at what’s in this release, including linking your Bluesky account to Surf, a new Home Timeline that unifies your Bluesky and Mastodon, and Bluesky notifications in our app. 🦋

#bluesky #mastodon #ATProtocol #activitypub #customfeeds #timeline

Well, it’s a lucky day 🍀. Our latest update contains a pot o’ gold for the Bluesky community especially. Take a look at what’s in this release, including linking your Bluesky account to Surf, a new Home Timeline that unifies your Bluesky and Mastodon, and Bluesky notifications in our app. 🦋

#bluesky #mastodon #ATProtocol #activitypub #customfeeds #timeline

Bluesky has tried to set up the corporate structure to be sellout resistant. But these measures have yet to be tested. Backed by venture capital, it will still be pressured to make a profit quickly - and discontinuing #ATProtocol would be a quick way to make a buck.

Meanwhile, over 15000 active sites run #ActivityPub compatible code, including Mastodon, Misskey, GotoSocial and more (see https://instances.social/list/old ). Even if Mastodon.social goes down, the network stays on. https://phillipjreese.com/the-social-network-that-cant-sell-out-understanding-mastodon-vs-bluesky/

Bluesky has tried to set up the corporate structure to be sellout resistant. But these measures have yet to be tested. Backed by venture capital, it will still be pressured to make a profit quickly - and discontinuing #ATProtocol would be a quick way to make a buck.

Meanwhile, over 15000 active sites run #ActivityPub compatible code, including Mastodon, Misskey, GotoSocial and more (see https://instances.social/list/old ). Even if Mastodon.social goes down, the network stays on. https://phillipjreese.com/the-social-network-that-cant-sell-out-understanding-mastodon-vs-bluesky/

My argument for #ActivityPub over #ATProtocol is simple: if ATProtocol rules supreme, what will compete against #Bluesky’s firehose?

How many nodes are there on AT Protocol?

How many unique services that don’t resemble Twitter run on AT Protocol?

But above all, what happens if Bluesky gets bought by Musk or Zuckerberg?

With the Fediverse, we got established decentralization. Not theoretical—something that exists in the far off future—but decentralization that is here and now.

My argument for #ActivityPub over #ATProtocol is simple: if ATProtocol rules supreme, what will compete against #Bluesky’s firehose?

How many nodes are there on AT Protocol?

How many unique services that don’t resemble Twitter run on AT Protocol?

But above all, what happens if Bluesky gets bought by Musk or Zuckerberg?

With the Fediverse, we got established decentralization. Not theoretical—something that exists in the far off future—but decentralization that is here and now.

My argument for #ActivityPub over #ATProtocol is simple: if ATProtocol rules supreme, what will compete against #Bluesky’s firehose?

How many nodes are there on AT Protocol?

How many unique services that don’t resemble Twitter run on AT Protocol?

But above all, what happens if Bluesky gets bought by Musk or Zuckerberg?

With the Fediverse, we got established decentralization. Not theoretical—something that exists in the far off future—but decentralization that is here and now.

Investor Mark Cuban shared on TikTok that he's ready to fund a TikTok alternative built on the AT Protocol. "If you’ve got that ability, let me know in the comments. If you create an MVP — a minimum viable product — so I can see it, that’s all the better, because obviously, I think you’d have a whole lot of support,” Cuban said in the video where he also explained the advantage of building on an open protocol. "It’s extensible, so that means nobody can just buy it, nobody can just close it,” he said. Here's more from @Techcrunch's @Sarahp.

https://flip.it/HXI-O7

#ATProtocol #Bluesky #TikTok #MarkCuban

Investor Mark Cuban shared on TikTok that he's ready to fund a TikTok alternative built on the AT Protocol. "If you’ve got that ability, let me know in the comments. If you create an MVP — a minimum viable product — so I can see it, that’s all the better, because obviously, I think you’d have a whole lot of support,” Cuban said in the video where he also explained the advantage of building on an open protocol. "It’s extensible, so that means nobody can just buy it, nobody can just close it,” he said. Here's more from @Techcrunch's @Sarahp.

https://flip.it/HXI-O7

#ATProtocol #Bluesky #TikTok #MarkCuban

#AtivityPub ではなく #ATProtocol をプロトコルとして推す理由についても知りたい（個人的には既に標準化されてる を推してほしい）けど、全体的な方向性として応援したい

https://p2ptk.org/freedom-of-speech/5174

#FreeOurFeeds

I saw this about Free Our Feeds today. I'm genuinely surprised they decided to go down the AT protocol route when the Fediverse seems like a much better & battle tested protocol. Seems to tick all of their boxes, including app development by third parties. Why are people so afraid of the Fediverse as an alternative? #fediverse #atprotocol #freeourfeeds https://www.theverge.com/2025/1/13/24342799/free-our-feeds-social-media-ecosystem-at-protocol-bluesky

I saw this about Free Our Feeds today. I'm genuinely surprised they decided to go down the AT protocol route when the Fediverse seems like a much better & battle tested protocol. Seems to tick all of their boxes, including app development by third parties. Why are people so afraid of the Fediverse as an alternative? #fediverse #atprotocol #freeourfeeds https://www.theverge.com/2025/1/13/24342799/free-our-feeds-social-media-ecosystem-at-protocol-bluesky

Save Social Media From Billionaire Capture: freeourfeeds.com?

"But it will take independent funding and governance to turn Bluesky’s underlying tech—the AT Protocol—into something more powerful than a single app."

I see the executive director and president of Mozilla Foundation as their technical advisors, no surprise. But it surprises me to have the executive director of the Social Web Foundation (@swf) there.

Any thoughts, @evan ?

It also surprised me to see Jimmy Wales, Founder of Wikipedia, involved.

#ActivityPub #ATProtocol #BlueSky #SocialWebFoundation #Mozilla #Wikipedia #VentureCapital #SocialMedia

I didn't like the idea of a HARD-CODED "/xrpc" path for Bluesky's API.

I also don't like the idea of HARD-CODED "/api/v1" path for the Fediverse, due to Mastodon's API.

Actually, I probably dislike the latter ("/api/v1") even more than the former ("/xrpc") since "/api/v1" is so common for web-based APIs in general.

#ATProto #ATProtocol #DeSo #Bluesky #bsky #FediDevs #Fediverse #Mastodon

the @bsky.brid.gy guy has a new non-profit (anew.social) focused on open source social networking tools, largely around ATProtocol and ActivityPub

https://www.theverge.com/2024/12/17/24322908/a-new-social-non-profit-bridge-platforms

#activitypub #atproto #atprotocol