by gopiandcode on 4/23/23, 10:56 AM with 108 comments
by mariusor on 4/23/23, 11:37 AM
The ActivityPub specification needs to be read with a goal similar to an email server in mind. It should do one thing: receive JSON-LD objects in inbox, process them according to the specification, and(maybe) store them on disk.
The idea of "users", "friends", "posts", "feeds" etc, are concepts that belong to the clients on top of this server, not in the server itself.
This separation between clients and server will also allow better interop/graceful degradation of object types that the client/server don't specifically understand.
by dahwolf on 4/24/23, 10:45 PM
https://universeodon.com/@supernovae
He's the admin of universeodon, a mastodon instance with 13K MAU. He recently shared that in a month's time, 3TB of text was transferred just in ActivityPub events. Images a multiple of it. I don't know what the bill is, but I was pretty shocked by the stats...for "just" 13K users.
And the cruel thing is that it still doesn't work properly. Likes/boosts and replies do not properly synchronize.
by erwinh on 4/24/23, 6:17 PM
What are the thoughts on OCaml on HN?
by SideburnsOfDoom on 4/24/23, 7:15 PM
"Try and load it up in a client app" seems suboptimal.
"load it up and see" attitude is part of what made parsing and renderings HTML so hairy, and compliance test suites helped.
by nologic01 on 4/24/23, 10:39 PM
As for the activitypub spec and the currently popular implementations it doesnt take long exposure to the fediverse to realise there are some rough edges and historical accidents (e.g mastodon being actually the defacto interpretation of the standard). Imho now that there is substantial more mindshare devoted to decentralized social it would be opportune to revisit these things and if needed revise before they get backed in.
by mikece on 4/23/23, 11:20 AM
by throwaway290 on 4/24/23, 5:41 PM