“All a ‘true ActivityPub server’ is for is storing data, fanning out subscriptions and collecting incoming data for you to view. #ActivityPub was originally designed so that all of the data presentation layers—Mastodon, PeerTube, Pixelfed—would be specialized clients communicating with the generic server. But the first popular apps cut out the client-to-server part of the protocol, so people think you need a separate identity for every client application. https://news.ycombinator.com/item?id=45396517
Discussion
Loading...
Post
@zoul this is an important point and one I've been thinking about too. In the #XMPP world, we have generic servers and let the clients do whatever they want on top of it, which means the same account can be used for various purposes. I was wondering why this wasn't so in the #ActivityPub world, so it's good to know there's no particular reason for it and it can be that way if we want it to be!
It'd also reduce work for new projects as they "just" have to implement a client, not a server 
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled