D
Deleted member 30996
Guest
Wait till I firewalk you and tell you the LAN designation of every machine on it.Trihexagonal HA! I see you. You're that 192.168.1.1, aren't ya?
Wait till I firewalk you and tell you the LAN designation of every machine on it.Trihexagonal HA! I see you. You're that 192.168.1.1, aren't ya?
I think you just gotta vet your IRC client for those kinds of things. Sure, for stuff like UTF-8 and fonts, you can let your local Konsole take care of that, for authentication - there's OpenSSL, and server-side - If you wanna run your own, RTFM and pay attention to the security. Once all that gets properly set up and compliant with modern security standards - there should be no issues banging away at the keyboard like in the 'good old days' - things will look and work pretty much the same.What's funny is that you can gracefully degrade emojis, reactions, images, avatars, etc into IRC without it turning into MS Comic Chat but still "no." Even for things that aren't GUI oriented: No UTF8, no ZNC standardization, no more secure authentication schemes, no impossible-to-takeover-via-netsplit channels. Just "no."
Uhm: It's indeed a shortcoming of IRC (as a protocol) that it doesn't support encodings of any kind. It will just pass on "octets".I think you just gotta vet your IRC client for those kinds of things. Sure, for stuff like UTF-8 […]
Well, one thing I like about IRC is that it isn't web.
I think that IRC should be treated as a service rather than as a protocol. Back in the early days of Internet, passing straight octets was 'good enough', because it worked. All we needed were rules for creating octets on one end, and processing them on the other. That's why IRC was a protocol. Times have changed, so have rules of the game.Uhm: It's indeed a shortcoming of IRC (as a protocol)
Wasn't meant as criticism against weechat If anyone wants a web interface, fine for me as well, it's just the one thing I personally don't want. Maybe I'll have a look at weechat some day anyways (for exploring the other possibilities), but so far, I'm very happy with good old irc/irssiAs for irc/weechat has some different interfaces to offer, btw.
Well, as soon as US-ASCII (7bit) wasn't a universal standard any more, charset (conversion) support was important. Email added it, Usenet added it, of course HTTP (browsers) as well.I think that IRC should be treated as a service rather than as a protocol. Back in the early days of Internet, passing straight octets was 'good enough', because it worked. All we needed were rules for creating octets on one end, and processing them on the other. That's why IRC was a protocol. Times have changed, so have rules of the game.
Just seen similar admin abuse on Libera. jess (libera.chat staff) just took over the #zfs channel from ptx0 when ptx0 is and always has been the owner of #zfs on Freenode. The problem is not isolated.
… IRC is a dying medium …
Using Glowing Bear can truly level up your IRC experience.
… Matrix? …
over to discord?
Weechat is fine after some customizations, the defaults for me is quite clunky.Wasn't meant as criticism against weechat If anyone wants a web interface, fine for me as well, it's just the one thing I personally don't want. Maybe I'll have a look at weechat some day anyways (for exploring the other possibilities), but so far, I'm very happy with good old irc/irssi
Is there some issue with connecting to more than one ircd of which I've been unaware for years? It's not uncommon that my client is connected to several.As many channels moved from freenode to libera, I now followed. I just hope I won't have to reconnect to freenode as well. The fragmentation is what's really bothering me.
Not a technical one. Well, of course, each connection will allocate resources (a local socket and some bandwith), but with IRC, that's indeed negligible.Is there some issue with connecting to more than one ircd of which I've been unaware for years?