this post was submitted on 10 Mar 2025
17 points (79.3% liked)

Fediverse

31253 readers
1224 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)

founded 2 years ago
MODERATORS
 

Bluesky, which uses it, has been opened to federation now, and the standard basically just looks better than ActivityPub. Has anyone heard about a project to make a Lemmy-style "link aggregator" service on it?

you are viewing a single comment's thread
view the rest of the comments
[–] rglullis@communick.news 3 points 3 hours ago (1 children)

We still don't need ATProto for that. ActivityPods solves that.

ActivityPub itself is built around the principle that the server owns your identity: the best you can do is abandon an identity (i.e, your actor URL) and tell everyone else (via the Move Activity) that you are adopting a new identity.

[–] jackalope@lemmy.ml 1 points 2 hours ago* (last edited 2 hours ago) (1 children)

The move activity ain't a great solution. We need federated identity or else ux will continue to lag. When I want to move servers, I can set the move activity but there's no guarantee my followers will subscribe to the new account. It's bad ux. Mass adoption is not going to happen with that kind of flow.

Activity Pods is cool bit not implemented on mastodon.

[–] rglullis@communick.news 2 points 1 hour ago* (last edited 1 hour ago)

We need federated identity or else ux will continue to lag

What I am saying is that the ActivityPub protocol is inherently built towards a server-centric system, where identities are owned by the server. Go read the spec: even the "Client-to-Server" specification assumes that the server owns the keys and dictates that the client (i.e, users) must do everything through the API provided by the server (i.e, the client's outbox).

Anything that is built with a design where the client owns the keys may even be able to interoperate with ActivityPub, but is not ActivityPub.

Activity Pods is cool bit not implemented on mastodon.

It's the other way around. We shouldn't be looking for "Mastodon on ActivityPods", but "ActivityPods applications that can talk with Mastodon servers", and those do exist.