Thread

1. Conlectus · 1790598456 · focus · HN ↗

   There’s a specific downside to LLM-based development that people can get neck deep in a new project without interfacing with the existing work in the field.

   In this case, this is basically a poorly specified implementation of half of XMPP. Of course, I half expect the LLM would have mentioned that at some point, but the repository does not.

   1. dale_glass · 1790601737 · focus · HN ↗

      Unfortunately XMPP is an absolutely terrible protocol. IRC's not much good either, but at least it has the excuse of being ancient and limited in what it wanted to achieve.

      I don't know how it just happens that sending text messages to people can manage to result in specs that are painful to implement.

      1. monkeywork · 1790605151 · focus · HN ↗

         >Unfortunately XMPP is an absolutely terrible protocol

         Can you provide more details here? I've never seen an issue with the protocol at all, more issues with feature difference between servers depending on what they have decided to implement or not.

         1. rtpg · 1790645787 · focus · HN ↗

            I will say that the middle layer is not great. I have an XMPP bot and the "interaction with the network" stuff really is ugly and unfun.

            I think the protocol itself is... I mean it's fine, I guess? Protocols are tricky because a lot of stuff is bolted on and it's not really super stateless as a protocol. But like all the Python XMPP client libs (for example) are all real janky.

            The protocol is complex enough to where the "simple and easy" client libs require way more up front design.

Unofficial Hacker News client; not affiliated with Y Combinator.