so far my main impression of irc is i don't understand how it can simultaneously be *this* complicated whilst also lacking so many of the features i've come to expect of chat platforms
-
@jacqueline for a very narrow definition of "fine".
@Brett_E_Carlock -
@fedops @Brett_E_Carlock alright, fedops, i'm all ears.
-
i think most of all what sucks is the constant assumption across the whole ecosystem that anyone who might find themselves in a moderator or server operator role is necessarily a veteran of irc's ux. it's a bad assumption, and its effect on irc-based communities is utterly predictable
-
R [email protected] shared this topic
-
Ariadne Conill 🐰:therian:replied to jacquelines 🌟 last edited by
@jacqueline look unless you’re ready to die for irc you’re just not going to understand
-
A [email protected] shared this topic
-
@jacqueline its this complicated and also doesn’t have ‘acks’ so you don’t even know if the server has received that message you sent or not
-
@hailey huh?? so what happens if your connection is flaky?
-
@jacqueline you will find out 60-120 seconds later upon tcp timeout, and you have to reconnect, apologise, and ask people in the channel which the latest message of yours was that they saw and what was said in your absence
-
@hailey cool!
-
@hailey so the mobile clients must all just suck then i assume? nobody is using this on their phone?
-
@jacqueline yeah you just have to use a bouncer
-
@hailey @jacqueline I forgot how painful it is / how many papercuts like "just use a bouncer" exist
-
Captain Ventilationreplied to {Insert Pasta Pun} last edited by
@risottobias @hailey @jacqueline IRC is peer-to-peer because you have to run your own server to use it.
-
{Insert Pasta Pun}replied to Captain Ventilation last edited by
@be @hailey @jacqueline *keels over in pain*
-
@jacqueline @fedops @Brett_E_Carlock I'm curious too
-
@arichtman @jacqueline
@Brett_E_CarlockJust one example: DNS.
DNS is a super lightweight UDP-based application protocol - one packet with a query, one packet with an answer, in 90+% of use cases. Boom you're done.
Now the DNS-over-https (DoH) abomination changes that to a very expensive TCP connection with TCP handshake, connection management, SSL handshake, the actual query/answer, and then tear everything back down.
1/3
-
O [email protected] shared this topic
