There is a third-party API now: https://doc.fnar.net/ , which collects data through a browser extension that scraps the traffic. This kind of extension is blessed by the devs as long as it does not automate actions.
They most definitely did not solve real time translation yet. The French in the video is barely understandable, both the translation and the pronunciation are the quality of an American who hasn't used French since high-school.
I don't think power use is the issue. I have this cheap CO2 sensor: https://www.domadoo.fr/en/devices/5882-heiman-zigbee-air-qua...
which draws 0.5W. This includes thermometer and humidity sensor, Zigbee transmission, and acting as a Zigbee router, but it gives us an upper bound.
It also measures continuously (picks up someone breathing on it within 10s), which is overkill. A phone could measure CO2 levels once every 10 minutes which would average under 0.01W, so that would work.
However, this assumes the sensor would fit in a smartphone, which is not a given. And these things need air flow. And they also wouldn't work while the phone is in a bag or a pocket.
> Replacing the server-to-server protocol sounds a lot like it's not really IRC protocol any more
There hasn't been a standard server-to-server protocol in like three decades. Even RFC 2813 only specifies one of the protocols in use at the time (IRCnet's). Each implementation has its own (some of them forked from the original)
> The chathistory link says "This specification may change at any time and we do not recommend implementing it in a production environment."
True. Ratification of the final spec is stuck on some details, unfortunately.
It's not inherent to the protocol. https://ergo.chat/ does not have netsplits (from having a single server) and https://github.com/Libera-Chat/sable replaces the server-to-server protocol to eliminate netsplits as well.
And even when not eliminated entirely, they are infrequent and barely visible on well-managed networks like Libera.Chat. Many chat platforms have more (and longer) outages than Libera has netsplits.
Solved decades ago thanks to NickServ and ChanServ (though I'll admit they are ad-hoc additions on top of the protocol). And ~15 years ago we got native support for authentication (https://ircv3.net/specs/extensions/sasl-3.1)
but that's not a violation of the contract, it's just a hash collision. Hash collisions are expected to happen, so HashMap and HashSet won't "misbehave seriously", they'll just be slow (linear-time lookup) and unable to remove entries.
The contract of Hash is that if two values are equal, then they hash to the same value. Which would be violated by doing the opposite of Maxwell: all values equal each other, but their hash differs (you can even make it random so it changes across calls on the same value!)
email: [email protected]