What is the definition of the #fediverse? Is it services that use #activitypub or anything decentralized? When we motivate people to use the #fediverse or promote it. What are we expecting from them?
@Stark9837 @fediversenews There’s not a precise definition. I think it’s mostly a buzzword. *My* personal definition of the #fediverse includes more than applications using the #activitypub protocol. Federation, to me, implies decentralized applications that are *autonomous and locally controlled*. Web-scale applications like Twitter (for example) are physically decentralized, but not federated since all the servers are controlled by one company.
@fediversenews @steve @Stark9837 Agreed. #IndieWeb is a good example of a federation that doesn’t use #ActivityPub. You could make a case for #RSS, as well. ActivityPub is my absolute LEAST favorite protocol to work with, but it’s the current darling of the “extended” Fediverse. Some day we may have a better protocol to build upon. But to me too, “The Fediverse” is much bigger than ActivityPub.
@benpate @fediversenews @steve Well, the #RSS and #ATOM guys hate #activitypub. There are a few long forum discussions where they go on about how unnecessary it is, and everything can be done with Atom. But I feel that ActivityPub isn't just the format but also how they communicate, and the format is more formalised and standardized, especially for social things.
@fediversenews @Stark9837 @steve I have implemented both, and you can do MOST of ActivityPub in RSS+WebSub for sooooo much less pain. But, ActivityPub can carry MUCH more, and richer information than any RSS format, so it’s the one to build on for now.
@fediversenews @Stark9837 @steve One of my troubles with ActivityPub is that it’s TOO flexible, meaning that every different app can pick and choose how they want to implement it and you have to make mappings for every possible flavor of ActivityPub. There are no flavors of RSS/Atom/JSONFeed. The fields and types are well defined, so everyone implements them the same way.