• 3 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


  • It’s the ActivityPub API (client to server) where clients supposed to interface with so that you could have one client, for all fedi. But turns out server implementations (Lemmy, mastodon etc) find it not so well designed or performant or adequate (or idk what else) so instead they implement their own client APIs, effectively making clients being specific to the server rather than interoperable (one client that could understand all servers). It’s reasonable though, it’s just … I thought… that this was already done and established… but well…




















  • Not entirely sure on what is the oversight.

    I’ve been reading for AP these days so it’s out of my understanding so far… I might be wrong.

    So from my understanding, the owner is the one that is responsible for holding the master copy. Given that the community is a owned by beehaw, all other places except LW that actually accepted the message(s) shouldn’t see it.

    Otherwise LW would have to ask beehaw every time if the message should be accepted, which would be very problematic and not close to federation but more like replication (“every server using activity pub is an active relay”).

    Imagine sending an email and your server not accepting until it receives a positive answer from the recipients server that your mail was accepted. You wouldn’t see your email at the sent folder up until 4 days. You wouldn’t even know if you actually sent the message after you click the send button.

    Also excuse my lengthy post, I think it’s because understanding AP is recent for me.

    If anyone that has a better understanding than me, please feel free to correct me