This is the protocol every sane human should use

You mean Signal protocol ?

Attached: lxFDD-4n.png (512x512, 24K)

>kek
aren't you the guy that shills his shitty meme server here every day?

It's like signal, only better and not a honeypot!

> doesn't know kek
how fucking NEW are you to this site, cunt? maybe reddit is more to your liking? and no, i don't shill a fucking thing anywhere, you cancerous new faggot.

>XML
dropped

Name 1 (one) reason it's bad without looking it up on wikiped first

I've been here longer than you mate

literally anything else makes more sense, is simpler and easier to use and work with without being complex and error prone. fuck you

You still haven't named your alternative though, shouldn't be too hard when everything is better, huh?

You asked me to name a reason, not an alternative.

And your reason is an alternative, so name one. You're just talking shit.

I am talking shit about XML, it blows. Try JSON.

Easily debunked, xml is better for this use case
xmpp.org/about/myths.html

>xmpp.org/about/myths.html
The only thing that page cites about JSON is that there's a marginal performance difference. I prefer JSON because the formatting is simpler and easier to work with. If its all generated by code and never touched by a human, I couldn't care less what format the data is in.

I doubt you could take 30 random people off the street, bash their heads with rocks for 10 years and force them to make a language worse than xml.
Only the dumbest of all apes could find redeeming qualities about xml and I think most of them are already webdevs.

No XSL template to convert XML to JSON yet though

So it's just personal preference of yours then, no arguments whatsoever. In my opinion xml is a lot more readable than whatever json garbage scheme people come up with

not how the paper is in the "humorous" section because noone in their right mind would use json for anything that's not based on javascript

>simple
>very light

XMPP example from RFC:

Wherefore art thou, Romeo?

Equivalent IRC example:
PRIVMSG romeo Wherefore art thou, Romeo?

XMPP is retarded. It is not a good protocol.

irc is not a good protocol for complex interactions though. You can't be sure a message is over (unless you set a retarded max message length) and the overall "protocol" is a single hardly maintainable hack

>You can't be sure a message is over
What. Every message ends with CR+LF.

You mean
>Equivalent IRC example:
:[email protected] PRIVMSG romeo :Wherefore art thou, Romeo,
then hope that the message gets to the sender (no ACK, no receipt acknowledgement, netsplits are a thing) and that stuff like Unicode encodings and other such miscellaneous features are handled correctly by the server and all clients?

just use Matrix
it's xmpp: evolved

It sure is, looking at server ram usage

it's the protocol, just implement your own server

>evolved
bloated and in continuous beta you mean

As someone who tried riot again yesterday after about a year, I wholeheartedly agree with you, OP.
I still believe that something like matrix (probably the Grid) will be the future. But currently, nothing really beats xmpp.

I forgot a colon. Sorry.

>no ACK, no receipt acknowledgement
This discussion is about simplicity. IRC works well because there is no parsing of messages, no acknowledgements.

>that stuff like Unicode encodings and other such miscellaneous features are handled correctly by the server and all clients?
How many fucking retarded things do you think is client specific in something as insanely bloated as XMPP? Character encoding not being standardized isn't a huge problem now, and is completely understandable given the age of the protocol.

But it's simplicity also makes it not really applicable for modern messaging, where you have unstable connections and lots of different clients. irc is also not federated, thus requiring an account for each user on every server that user wants to talk on, which is rather cumbersome

>I forgot a colon. Sorry.
I mostly meant the source part of the message, which is pretty much equivalent to the "from" attribute in your XMPP example. IRC server adds that to any message you send.

>there is no parsing of messages
Er, what?

>IRC works well because there is […] no acknowledgements
No, not at all. If any party, server included, disconnects, an unknown number of messages might've not been delivered. That's also a part of the reason why stuff like netsplits exist and there's no catching up to stuff you miss during them. IRC is no more reliable than the underlying TCP session, which is not a lot in the days of mobile connections.

what fucking grid, what is it with these ungoogleable names

*complex parsing, as in XML. Obviously it is parsing stuff.

This discussion is about simplicity, not reliability. The protocol was not designed for this.

>IRC is no more reliable than the underlying TCP session
Nobody is claiming it is. Nobody cares if it is. The purpose of the protocol is to send messages around with minimal overhead and be easy to implement.

gitlab.com/thegridprotocol/home/blob/master/docs/overview.md

thanks. the name still sucks though

>Nobody cares if it is.
You mean except all the people who don't know or can't set up their own bouncer?

IRC's main strength is how common and old it is. It doesn't work well. It *barely* works, but when it does, it is indeed usable for simple text chat.
IRC isn't even the simplest possible implementation of such a chat protocol. There are quite a lot of possible optimizations that could be done if sheer simplicity is desirable.

However, IRC isn't suitable to be the mainstream general-purpose instant messaging protocol. It's way too limited and has too many faults to fill that role. Most people (perhaps not most on Jow Forums, but otherwise) prefer to have a simple solution that works reliably for them with less effort than setting up a complete IRC stack includes.
And while you can be all like "who cares what normalfags do, I'm fine on IRC!" today, more and more relevant groups (including some FOSS projects) are moving to centralized proprietary garbage like Slack or Discord because of these reasons. Eventually, there will be no one left on IRC. If you're satisfied with using it just with some very specific small groups of friends, that's fine. However, if you want to actually use a sensible service with general public (and why wouldn't you want to?), then now is a good time to start pushing for a better, open, federated IM protocol.

I prefer Matrix to XMPP, by the way.

This discussion is in no way about simplicity, it's about what's required to build a good messenger. irc is not suited for that.

>today, more and more relevant groups (including some FOSS projects) are moving to centralized proprietary garbage like Slack or Discord
So, completely unlike when they used AOL Messenger, MSN and ICQ? IRC will not die in favor of proprietary software. IRC will not die in favor of a complex and retarded protocol.

Every network IRC but Rizon and Freenode has been dying for years. More and more communities use proprietary stuff for their hangout place.
IRC will not die completely. However, if you can claim that it hasn't lost a significant amount of ground for these new era open group chat channel services, you're either extremely sheltered or good at deluding yourself.

>I've been here longer than you mate
dumb phoneposter