@sten0_SE@strypey ah, the pain is definitely going to happen, and probably soon. The fun part is that the part of the left that kept saying "voting is bull, democracy is dead" is still partially guilty of bringing this self-fulfilling prophecy on us all.
"Hey, the system doesn't work well; let's completely disengage and hope for the best, what could possibly go wrong."
@maiyannah@deadsuperhero For one thing, we might finally get a common protocol so that Diaspora, GNU Social, Pump.IO, MediaGoblin, Mastodon, etc all work together. I'm also working on a test suite so there should be less "errors" between implementations.
That was the main goal of the working group (and why we spent so long getting community feedback).
@deadsuperhero The question in my mind would be: what do we get out of adding it that we don't already have? What if anything would we lose?
This is part of why I want to modularize protocol support on postActiv. It lowers the cost of testing things like that, so you can experiment more freely.
It's a nice thought, and hopefully we can do that in the long term. But some part of me is apprehensive about the spec and the leg work it will take to support it.
There are certain unanswered questions, such as "Will ActivityPub support Diaspora's federated privacy controls?"
@maiyannah It's a hard problem. I work with browsers, and interoperability/compatibility is a huge topic of discussion. One project we started too late was a shared test suite (https://github.com/w3c/web-platform-tests). Maybe the federation needs some sort of equivalent to the W3C/WHATWG.
@bottitytto@hakui ostatus doesn't really have a spec so much as "put these 20 protocols in a bowl, blend, put in the oven and hope for the best". is there a test suite somewhere?
@strypey Ahh! I see. I didn't understand the relationship.
I suppose there are more Mastodon instances that may be unaccounted for on the list, but then there's a MUCH BROADER universe that is the general Fediverse.