Show Navigation
Conversation
Notices
-
Right now if you want to talk to Mastodon or Pleroma or PixelFed or anything else which uses ActivityPub, you need a seperate, different set of code for each. This is not the result of a standard. A standard is ... well, *standard*. A good standard means that any device, or in this case piece of software, which follows that standard, can communicate with any other. That makes ActivityPub a very poor standard. Parts that need tight specification are under-specified. Parts that need looser specification are over-specified. It's not worth implementing.
-
But it's not about what's best, technically speaking. It never is. It's about what's popular, and I have to admit, they definitely got me there.