191–200 of 446 posts
This remark, topped with the author's piece on "normiefication", is the kind of intellectual elitism that reliably keeps me away from IRC whenever I think of coming back to it.
Earlier quoted context omitted.
let’s rebrand “mosh and a vps” as “irc nitro”, and then everyone will be happy. (ripgrep is a very nice log searching tool, only top tier users will be told about it!)
Or be told about the channels that are not for beginners
> The reliability and lack of bloat that are inherent to IRC ultimately also means that there are a number of fancy modern features that Discord has that IRC lacks, a big one being the inability to view backlogs of conversations that transpired while one was not connected to an IRC server. Although IRC does not itself provide this functionality, the extremely simple nature of IRC allows for a couple of lightweight op…
Not having a backlog is actually the thing I like about it. Discord (and Slack) have this thing where because there’s a backlog, people expect other people to have read everything. I prefer the experience where the assumption is that the people not in the room are assumed to have not seen a message. It makes it more unambiguously a synchronous experience, whereas Discord and Slack chat is pretty ambiguous as to wheth…
Not to mention some IRC channels are really high latency, you leave a message and someone else replies ten hours later. If you miss the reply because you were offline, you couldn't expect anyone to be around to repeat missed conversations back to you.
Due to this I've never really liked IRC, its not good for mobile devices or people who live with DSL or dial-up. Sure you can "just get an account on a bouncer" but that's pretty esoteric knowledge that I never encountered until after university.
I loved the days where I'd be in a couple IRC rooms and a couple slack rooms all in the same IRC client. Slack killing IRC support still bums me out.
Earlier quoted context omitted.
I couldn’t imagine joining a workplace only to be told that I had to maintain a service to participate in essential communication channels.
Exchange servers anyone?
Earlier quoted context omitted.
I would put logging as a bottom tier feature for most chats. The characteristic of chats is in the moment and not some archival function. I am a heavy discord and telegram user but overall I would value the benefit of everything getting deleted after 72hours higher than the few times I actually search for something older than that.
My company uses chats as information stores. Not saying it’s the best idea, but you are an outlier with your preference.
Twitch has been providing a non-TLS and public IRC bridge.
Moreover, IRC chat can be extremely well extented, namely with bells and whistle features if the client supports them, and if not can be ignored and and then displays harmless garbage (you can encode A LOT in a short text string, and now with utf-8... you can encode MASSIVE load of things within a short text string).
From a noscript/basic (x)html, just need a irc:// URL and were good. We can even have pre-authencitated irc connection using a transient TCP port opening with IP[46] locking (ok... you will need a pool of IP[46]s for significantly sized services).
Ofc, the bad thing: most of the time the noscript/basic (x)html browser will fire up an irc client, then you get 2 windows. Or we could have an IRC client integrated into a noscript/basic (x)html browser which will open a "frame"/new tab, well... modularity, and this would still be cosmically less costly from a technical point of view than any Big Tech web engine.
It is like some _LEAN_ p2p protocols (streaming, live or not) directly integrated into noscript/basic (x)html browsers with good and honest default (that's the hard part, it will be abused, and if it is too much, won't actually work). Well, a "private" tracker would do the "trick". Still, it could fire up an external p2p-enabled media player (via with the p2p URL with the private tracker and video hash, or the private tracker infos could be part of a dash file).
Ofc, you have to expect the worst from Big Tech: adamant lobbying against that, sabotage up to shadow-hire hacker teams, etc...
Earlier quoted context omitted.
I would put logging as a bottom tier feature for most chats. The characteristic of chats is in the moment and not some archival function. I am a heavy discord and telegram user but overall I would value the benefit of everything getting deleted after 72hours higher than the few times I actually search for something older than that.
My company uses chats as information stores. Not saying it’s the best idea, but you are an outlier with your preference.
Yes this is a real thing.
Earlier quoted context omitted.
So supplement IRC with a bunch of other services? Realising people didn't want to deal with this shit is why discord is so popular. (Seriously, this response and others like it demonstrate that IRC will continue to remain a niche. I won't fault you if this kind of setup works for you but suggesting this kind of thing is acceptable for the average user is really, truly, genuinely out of touch. I'm among the demographi…
[dead]
You might be comfortable stringing together a bunch of plugins for IRC in order to get the same functionality, but the average Discord user never will be.
Earlier quoted context omitted.
Discord has shitty logging and log-search capabilities. Discord's logging is shitty because: 1 - The logs aren't yours, they're Discord's. If you get banned from the server, your server shuts down, or Discord bans you altogether your access to those logs is gone forever. 2 - Unlike the logs of some IRC channels, Discord's logs aren't available on the web anywhere, so they can't be indexed or searched outside of Disco…
In case anyone is not aware, you can download Discord logs. https://github.com/Tyrrrz/DiscordChatExporter But beware -- it can result in account termination! https://support.discord.com/hc/en-us/articles/115002192352-A...