furry: 
hello, tox protocol is fucked
c-toxcore devs:
we don't intend to do anything about it
well'p.
hello, tox protocol is fuckedc-toxcore devs:
we don't intend to do anything about itwell'p.
+bonifartius 𒂼𒄄
@icedquinn i wonder if there is anything vaguely modern which isn't shit from a protocol perspective.
@icedquinn @bonifartius the most protocols are fine. just people are stupid hiseters sometimes and donàt have enough brain to work with them.
Follow
@iron_bug @icedquinn i'm increasingly disenchanted with many modern protocols, even if the projects are a good idea.
e.g. matrix has some nice parts and good ideas, but the protocol is in reality just a moderately good rest api.
XMPP works fine, but XEP hell killed it.
i think with many protocols there just are too many moving parts so you always end up with unintended side effects or things not working properly across implementations.
@icedquinn @bonifartius I mean normal RFC protocols, designed by serious engineers. not handcraft by amateurs. ActivityPub is also terrible, because is's just raw and undefined for the most critical cases. but tox is fine, it's well designed and works just fine.
@iron_bug @bonifartius
> well designed
it isn't, though https://github.com/TokTok/c-toxcore/issues/426
> well designed
it isn't, though https://github.com/TokTok/c-toxcore/issues/426
@icedquinn @bonifartius in the example user supplied M has A_priv key. but man, if you have stolen somebody's private key it means the account is lost. because the account in Tox is defined by provate key.
@icedquinn @bonifartius I also think that idea of extensions is fine by itself. the hell begins because of incompatibility of different realizations, though. there should be a method to exchange between clients with information about their capacities to avoid failures.
its mostly an issue because the desktop programmers died and all we have now are webshits