Recent searches
Search options
Reminder: AS/AP-based suffers from #BallOfMud based ad-hoc expansion unless we find common practices and stick to them. Collaboration across a commons is essential here. Just coding your app with custom #ActivityPub protocol extension is contributing to #ProtocolDecay and increasing complexity to facilitate broad #interoperability.
The #FEP process and #SocialCG are where collective effort and proactive participation can improve #fedi for all. We need a bottom up standardization process.
@smallcircles the only question is what we do with the existing applications that are based on mastodon.
with #rdfpub i'm at the very beginning of federation and have been surprised countless times.
i'm very excited to see what else i come across.
the only question is what we do with the existing applications that are based on mastodon.
They will simply get a degraded experience over time, as they don't support many of the features being developed by other platforms.
We already have this issue with Hubzilla vs. Mastodon, and Nomad/Zot Protocol vs. ActivityPub. Mastodon and ActivityPub simply don't support a lot of the features we have. It will eventually be the same when other platforms implement a common way of serving threaded conversations in ActivityPub, but Mastodon sticks with non-threaded conversations. There will be a feature gap.
in calmness @smallcircles@social.coop@scott indeed. As it should be. Ditch that post-facto interoperability laziness, if you care about fedi.