this post was submitted on 11 Jul 2023
6 points (100.0% liked)
Fediverse
19 readers
2 users here now
This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Is ActivityPub not open to arbitrary extensions? I thought it was a very loose spec and the only concrete spec is an agreement between instance types. But i've not looked at the protocol closely yet, despite developing around it hah.
You mean... embrace and extend?
Yes it can be extended but apps would need to be upgraded to make use of the new data flowing around. If they see an activity type they don't understand they'll just ignore it.
Expecting every different platform to all move in lockstep is not feasible so a situation where some support downvotes but some do not is going to have to be part of the process. Even if it was just kbin to kbin initially, that'd still be an improvement.
Yea, that is what i was thinking. I myself am working on some ActivityPub stuff and while compat is important to me, i also plan on potentially exposing new features in this manner. If other software wants to federate with it, cool, if not, whatevs. It's data propagation, as with everything in ActivityPub it's optional that consumers use it as desired.