@Zerglingman@tn5421@p@ec670 yeah I think federating over gemini would be tough because most servers are probably going to want to validate the certificate chain. All fedi software would have to start using trust on first use, but only if self signed because when a LE cert is replaced it would break federation. As a client I can make a decision to accept or reject a new certificate, but if puters are talking to each other figuring out that a new cert should be trusted will be more difficult without a signing authority. It would be possible to build a CA that fedi admins could opt into trusting, but you still have to deal with browsers, and you couldn't federate with anyone who didn't trust it.
@thatguyoverthere@tn5421@p@ec670 Again, fediCA doesn't actually solve the problem of too much power in one place. I don't know why this direction keeps appearing, it's obviously strictly worse than current. The thing is that I'm not proposing throwing out cert signing, not at all. I'm offering a self-signed cert because web of trust has to start somewhere. The reason changing certs with a CA doesn't prompt a warning is because you're only trusting the cert due to the authority guaranteeing it in the first place, and *their* cert hasn't changed (iterate as much as necessary).
Of course federating over gemini requires that the server supports it, so differences in SSL needing specific support is... You're already at the point of specific support in the software. Nothing of note after that. Anyway, I'm moving towards "http-based protocols aren't real protocols anyway". Make our own AP with blackjack and hookers and it uses its own dedicated ports.
At least you acknowledge that the UX for FOSS chat services is garbage. But even the protocols themselves are pretty trash. XMPP in particular considering how much “modding” you have to do just to get it to run in a way that is worth a shit, but Matrix’s protocol has its own issues, like for example storing its events in a DAG.
@NEETzsche@tn5421@Zerglingman@p@thatguyoverthere X in XMPP means "extensible", it's built to be a barebones protocol that can be extended with XEPs. That, of course, leads to fragmentation and lack of consensus between software developers, but whether this issue is large enough to be a dealbreaker is debatable. Linux with all its distros is the same.
@NEETzsche@tn5421@Zerglingman@p@mint@thatguyoverthere something to offer like actually having multiple independent implementations (people tend to give up fighting synapse for compatibility) :ablobcatgooglytenor:
Well if we take a “let the market decide” analysis of how much of a dealbreaker it is we find that basically nobody outside of tech spergs and paranoid political dissidents use XMPP. You can attribute some of this to the network effect for sure, but commercial services like Discord, Snapchat, and Telegram don’t janny enough normal people to merit actually using any of this stuff.
I get the theory behind extensibility and XEPs but in practice it’s a pain in the ass. And that absolutely is a dealbreaker to anybody who intends to correspond with someone who doesn’t have a computer science background.
@NEETzsche@tn5421@Zerglingman@p@mint@thatguyoverthere we basically need an easy to use messaging platform without the needs to use a phone number to register and freedom of speech. Currently Matrix is the only one which excels in that.
Matrix isn’t as bad as it was but the flagship client – Element – really is clunky, even now. And it’s routine for Matrix to lag out if you try to join a channel that’s on another homeserver. It’s not like Discord where you click one button and you’re in within a couple seconds.