@rysiek @david_ross I was like "why would Signal federate, it's being run by a company after all" then looked it up on the wikipedia, and it turned out OWS is running from donations... but it's not a non-profit, and from what I've seen, it's acting like a for-profit company... dunno what to think about it...
@Wolf480pl @david_ross this is Moxie's reasoning: https://whispersystems.org/blog/the-ecosystem-is-moving/
@Wolf480pl @rysiek @david_ross it's not even five years ago when we had a xmpp deployment within a single company and you couldn't depend on it to deliver messages, not to ever mention luxuries like voice (lol) or sending files (lol^2), because it just didn't ever work properly no matter what you tried, even when you could fix a particular issue on hand, next day, there would be another and then another, neverending stream of broken shit
moxie is right
With whatever "content policies" you're proposing, at least you would see it, before any kind of content policies took care of it.
The harm to you is the same. You saw the spoiler you didn't want to see. Because there was no CW.
@Wolf480pl @rysiek @david_ross sure, but fixable how? there's no way to make xep's non-optional in any sane way, all that xmpp is a very poor text messaging protocol with a lot of optional stuff on top, you can say, so go ahead and use this one good xmpp client and one good server, but thx, we already did this by picking up a different good protocol and client and we just don't care, because, well, why?
1. you agree on which XEPs should be supported by everyone
2. you take some of the funding that goes to Open Whisper Systems and give it to XMPP client and server devs who get no funding whatsoever
3. you make an automatic test suite that checks which clients and servers support which XEPs, and make it generate a public website with a leaderboard of clients and servers with best conformance.