Frankly I don't think that part of the spec was well thought ... • Aaron Parecki

53°F

Gabe Kangas https://social.gabekangas.com/users/gabek • Nov 24
It was a mistake that ActivityPub Client-to-Server never took off and I think we'll pay for it one day.

Right now one person calls the shots for the client APIs of multiple projects because all the projects want to be compatible with the biggest server implementation. This feels wrong, but I don't know what the solution is at this point.

Frankly I don't think that part of the spec was well thought out, and I also disagree with the fundamentals of how it works. I suspect it didn't take off because other people feel the same.

The fact that Mastodon dictates the default posting API isn't good, but also isn't surprising, and it's definitely something I would like to see change! I'm pretty sure the reason that happened was because people were already writing Mastodon clients before Mastodon adopted ActivityPub in the first place.

Portland, Oregon • 48°F

Thu, Nov 24, 2022 4:52pm -08:00

1 reply
Have you written a response to this? Let me know the URL:
- Gabe Kangas social.gabekangas.com/users/gabek
  
  @aaronpk Oh I don't mean the specifics of the spec, just that the concept of it never took off and I've never heard of anybody really having a problem with how things are now.
  
  Thu, Nov 24, 2022 10:56pm -08:00

Posted in /replies using monocle.p3k.io