While WebTransport is promising, it's limited to client-server communication unlike WebRTC.
WebRTC supports peer-to-peer UDP connections as well. Thus it's better for use cases like low-latency games, video calling, and secure direct communication between devices.
A better push might be to make WebRTC more simple and modern, but I'm not sure if any standards committees are working on this yet.
In a nutshell, ideally `peer.connect(remoteId)`. An API like peer-js/simple-peer. And symmetric negotiation would be great as well.
WebRTC should be the universal networking primitive for the next phase of the web, but the API exposes too many implementation details – its abstractions leak.
This plus the overall weight of integrations limit mass adoption by developers.
You realise the irony right? You say say AI "slop" has a distinctive structure, but at the same time you (and the other poster) say that AI tools can not detect it? For what it's worth I'm an AI sceptic, but one thing that AI tools are good at is pattern matching (that's really all they do). But somehow pattern matching AI writing is so obvious to human's but it completely fails all AI tools (just tried another tool which said 100% human).
It doesn't match up. Moreover it's getting tiring, because every single article has these comments on them, and I've seen enough examples where authors showed up in discussions or texts were from before LLMs were widely available, but posters were still adamant that the text was AI generated.
I highly doubt that people here would reliably pick out (success rate > 60%, i.e. you get 60% of guesses correctly if text was generated by a human or LLM) LLM generated text that completely fools 90% of AI detectors.
Regarding the setup-punchline format, guess what, those were popular way before LLMs (not surprising LLMs must have learned them from somewhere).
What detection tools are you using and why do you have such confidence in them? How reliable are they and how do you know? Why do you think these particular tools are better pattern matchers than actual humans (on HN no less)?
Food for thought, fwiw I think you have some valid points.
You could also use JSON Merge Patch (RFC 7396) for a similar use case.
(The downside of JSON Merge Patch is it doesn't support concatenating string values, so you must send a value like `{"msg": "Hello World"}` as one message, you can't join `{"msg": "Hello"}` with `{"msg": " World")`.)
Should order this list by number of affected rather than alphabetical IMO. The 275K monthly user platform is almost hidden relative to the 49 and 300 user examples.
WebRTC supports peer-to-peer UDP connections as well. Thus it's better for use cases like low-latency games, video calling, and secure direct communication between devices.
A better push might be to make WebRTC more simple and modern, but I'm not sure if any standards committees are working on this yet.