News for hackers. Stuff that matters.
Re:IRCv3 2022 Spec round-up by Gigachad on Sunday November 20, 2022 @06:05PM (#33686500)
This goes back to the previous comment. IRC users and other IM users are in different universes now. Stuff that is considered core functionality like push notifications, embedded images and videos is probably never going to work in IRC.
Re:IRCv3 2022 Spec round-up by superkuh on Sunday November 20, 2022 @08:12PM (#33687490)
People who use IRC see it as the text communication component of the platform that is the internet. When we need to do media we use the appropriate protocol and simply paste an address in chat (or DCC send it). Building everything into one protocol is just asking for problems (both legal and social).
Re:IRCv3 2022 Spec round-up by u801e on Sunday November 20, 2022 @11:01PM (#33688581)
> Building everything into one protocol is just asking for problems (both legal and social).

That's what's been happening with HTTP. Now browsers are bloated and take a lot of system resources to run.

Re:IRCv3 2022 Spec round-up by throwawaylinux on Sunday November 20, 2022 @09:26PM (#33687946)
All incoming IRC messages are like push notifications aren't they? Or do I have my webology terms confused? IRC clients can certainly pop up a notification or make a sound or blink an icon when they encounter certain messages (e.g., your nick is mentioned), if push notification now means a more intrusive type of alert.
Re:IRCv3 2022 Spec round-up by Gigachad on Sunday November 20, 2022 @10:43PM (#33688473)
Push notifications are a specific thing where your OS can briefly wake up, check for notifications for all services, and then sleep again. It’s how you can have 10 IM apps but still be notified of messages on all of them despite none of the apps actually running unless they are actively on the screen.

IRC is unable to do this because it requires a constant active connection which is something that was fine in the desktop era but is not usable on battery powered devices.

Re:IRCv3 2022 Spec round-up by aidenn0 on Monday November 21, 2022 @12:33AM (#33689168)
Constant TCP connections work great on Android as long as there is no traffic.

Conversations.im works this way and has minimal battery impact. iOS doesn't allow this, because it's easy to get wrong.

Re:IRCv3 2022 Spec round-up by throwawaylinux on Monday November 21, 2022 @02:14AM (#33689754)
> Push notifications are a specific thing where your OS can briefly wake up, check for notifications for all services, and then sleep again. It’s how you can have 10 IM apps but still be notified of messages on all of them despite none of the apps actually running unless they are actively on the screen.

Ah, I didn't know that's what push notifications were. Sounds like a regular old pull aka refresh but I have no idea about web stuff.

> IRC is unable to do this because it requires a constant active connection which is something that was fine in the desktop era but is not usable on battery powered devices.

I think at the scale which devices are already waking up to check things, it's unlikely to be a problem for most. Phones don't actually sleep for hours (or probably even minutes.

That said, IRC's heavyweight connection does seem clunky, if your connection drops momentarily it's unlikely you wanted to lose track of conversations you were currently participating in. Although that can be solved with logs / archives pulling what you missed, it seems better solved at a core level (maybe it is, I haven't looked at IRC for a decade or more).

Re:IRCv3 2022 Spec round-up by _flux on Monday November 21, 2022 @03:03AM (#33690049)
In particular frequent disconnect/reconnects seem to cause stress to others in IRC, sometimes even resulting in bans, when it ultimately just shouldn't matter.
Re:IRCv3 2022 Spec round-up by Gigachad on Monday November 21, 2022 @03:41AM (#33690290)
I remember my irc bouncer broke once and I had received a network ban for join/quit spam.
Re:IRCv3 2022 Spec round-up by Springtime on Monday November 21, 2022 @02:41AM (#33689927)
Textual (macOS client) has had both image and video inline embedding since at least 2014 (in fact it was ironically used for the longest time as the main client of the dev behind Hexchat, another IRC client). KiwiIRC (web client) also has embeds IIRC.