atproto

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.

Thought here … #fediforum, #fedidev, #atproto builders who are deeper in the architecture than I can get…

Trying to better understand ATproto and Activitypub similarities and differences.

Developer perspective on tradeoffs… #ATProto architecture is more centralized. #ActivityPub has JSON-LD. ⚖️ So much pain and confusion, so little benefit and the Fedi Father refuses to consider JSON-LD alternatives because replacing the “feature” that almost no one actually uses with something useful will apparently break the Fediverse.

Just learned from @quillmatiq that @msonnberger is working on #FediSky, a new project "that adds an #ActivityPub instance sidecar to a PDS"