4 ms·
How is this still IRC? :) I'd prefer to see more expansion on the IRC protocol side rather than clients adding their own non-standard augmentations. Things li
by GekkePrutser 6y ago
How is this still IRC? :)
I'd prefer to see more expansion on the IRC protocol side rather than clients adding their own non-standard augmentations.
Things like server-side scrollback, connection persistence without a bouncer, push notifications for mobile would be great. I currently use Quassel server with QuasselDroid app to achieve these things with works well but again it's a client thing only. IRCCloud does a similar thing though not self-hosted.
I'd love to see IRC make some big strides like it did in the 90s. I don't care about video etc though. It shouldn't become another whatsapp or facebook messenger. Though embedding pictures would be useful.
I know IRCv3 is a thing but development is way too slow and isn't really taking the new requirements of the mobile world into account.
But clients adding proprietary stuff that only works with themselves has nothing to do with the idea of IRC.
- theamk 6y agoDon't new features go against the whole IRC idea? The original protocol is amazingly simple. But if you want to support connection persistence, you will need to pretty much redesign it - and in this case, why not go XMPP or Matrix? Both can already do that, and they are open source as well.
- app4soft 6y ago> How is this still IRC? :) Here is an explanation.[0] [0] https://xkcd.com/1782/ https://xkcd.com/1782/
- dTal 6y ago>I'd prefer to see more expansion on the IRC protocol side rather than clients adding their own non-standard augmentations. Unless there's a Council of IRC who decrees changes in protocol (and if there is, they clearly aren't doing their job), then "proprietary" features is how the protocol expansion happens - provided the features are useful and easy to implement (read: documented), other clients will jump on the bandwagon. An example of this already happening is colors in IRC - mIRC defined some proprietary control codes, and now every client supports them and it's de-facto part of the standard. I agree with your feature list, especially scrollback. All that needs to happen is some very popular IRCd taking a stand and making a trivial extension to the protocol, which reports scrollback given a particular server command. Standards be damned - clients will rush to add support for this feature, and servers will soon be seen as second class if they don't support it. It could happen so easily!
- chrismeller 6y ago> Unless there's a Council of IRC who decrees changes in protocol (and if there is, they clearly aren't doing their job) IRC was established through the normal RFC process at the time, so there is, in a way, a “council” governing it. https://en.m.wikipedia.org/wiki/Internet_Relay_Chat https://en.m.wikipedia.org/wiki/Internet_Relay_Chat
- MaxLeiter 6y agoircv3.net exists and has multiple extensions / new capabilities that most popular servers support some amount of
- jhthorsen 6y agoCTCP messages are widely implemented, and there are no standardised or restrictions to how to format them. Since there are no good way to pass WebRTC signalling through IRC, I made up my own protocol. If a more standard way is available in the future, then Convos will for sure adopt it.