Notices by Axel Rauschmayer (rauschma@fosstodon.org)

@silverpill That makes sense! Per-server caching significantly lessens the load.

One remaining challenge is replies, profile data etc. being incomplete and/or out of date (you are working on that, IIRC). Thanks to per-server caching that shouldn’t cause too much additional traffic.

Bluesky says that: “Never lose access to your followers or data.”

However, I don’t think that’s true. Can someone confirm?

Even in a scenario where there are multiple Relay/AppView/Labeler services, if you move to a different service:
• You can only follow a user if their PDS is crawled by your service.
• A user can only follow you if your PDS is crawled by their service.

@serapath From what I know about Bluesky’s team, I believe that their intentions are good.

But, eventually, they’ll have to make money.

Upside: People have moved once (from Twitter to Bluesky). Moving again is going to be much easier and the Fediverse isn’t going anywhere.

Only potential downside of ActivityPub that isn’t relatively easy to fix: It *may* not scale as well—no one knows at the moment. I’m curious: Could AP handle (e.g.) Taylor Swift joining the Fediverse?