News for hackers. Stuff that matters.
Re:IRC necromancy by na85 on Saturday November 18, 2017 @06:51PM (#15731382)
Change aversion killed IRC. A lot of the opers on the big networks are extremely conservative and default to poo-pooing ideas because it's simpler.

IRC with good mobile/push support could have taken off, but using it from a mobile device is painful because of the constant drops and the need to have your device responding to ping pongs every few seconds kills your battery.

Re:IRC necromancy by kuschku on Saturday November 18, 2017 @08:47PM (#15731791)
> IRC with good mobile/push support could have taken off, but using it from a mobile device is painful because of the constant drops and the need to have your device responding to ping pongs every few seconds kills your battery.

You mean, something like IRCCloud, or what I’m moving Quasseldroid to right now?

Re:IRC necromancy by metabrew on Sunday November 19, 2017 @06:42AM (#15733475)
Random irccloud/quassel anecdote for you: when I started working on what is now irccloud, I was originally just going to write a (mobile-)web front end for quassel core, since I was using Quassel on KDE at the time (and had been for some time). This predates Quasseldroid I think, at least I don't remember there being a good mobile app for quassel back then.

The protocol between the quassel core and clients looked to be some sort of serialized Qt objects (iirc), so I abandoned that idea and wrote the irc client backend in erlang, with a json protocol.

Re:IRC necromancy by kuschku on Sunday November 19, 2017 @06:53AM (#15733513)
The protocol are serialized Qt objects (I've started documenting it), but compared to Json, this gives a huge performance advantage.

It's planned to be replaced it with protobuf relatively soon, though.

Re:IRC necromancy by na85 on Saturday November 18, 2017 @09:09PM (#15731843)
Yes, except irc cloud is a 3rd party platform and requires payment as far as I'm aware.

"Something like irc cloud" should have been baked into the ircd/protocol so that there's a lower barrier to entry.

Re:IRC necromancy by kuschku on Saturday November 18, 2017 @09:32PM (#15731925)
Well, Quassel is the same, open source, under GPL, self-hosted. (Disclaimer: I contribute to Quassel occasionally)
Re:IRC necromancy by na85 on Saturday November 18, 2017 @11:05PM (#15732190)
Again, it needs to be baked into the server, otherwise it's just another barrier to entry.
Re:IRC necromancy by kuschku on Sunday November 19, 2017 @10:02AM (#15734151)
That’s not really possible, actually.

The push notification systems used by Android and iOS only allow the same person that can authorize updates for an app to send push notifications to this app.

This means either every IRC app would need to operate an open gateway for notifications, or you’d need to give every IRC server the same certificate that you use to sign your app updates on the Apple AppStore.

Push notifications on mobile devices are designed to only work for situations where the same company controls all servers, and apps.

Re:IRC necromancy by na85 on Sunday November 19, 2017 @12:52PM (#15734963)
Okay, well, now we've discovered a big obstacle to irc adoption on mobile.

Things like this are the reason slack and discord ate irc.

Most users simply won't sign up for 3 services just to chat.

Re:IRC necromancy by kuschku on Sunday November 19, 2017 @01:33PM (#15735142)
Well, rather, we've discovered why everything is becoming centralized, not just IRC.