Kagi of course reviews it
They had quite some lag at the beginning. I made reports from the very day they announced it, and none of them were processed last month. But they are now! (Though they rejected half of them)
HN user
[ my public key: https://keybase.io/progval; my proof: https://keybase.io/progval/sigs/iJkfMTZcmOHP3IcHyhl94KHqYHNLDk5z-JbHXnZgvUQ ]
email: progval+hn@progval.net
Kagi of course reviews it
They had quite some lag at the beginning. I made reports from the very day they announced it, and none of them were processed last month. But they are now! (Though they rejected half of them)
1 and 2: I rarely need to do that. When I do, then move or hardlink to a dir with shared read access
3: There is no reason for both my main user account and a dev account to share a credential. Main account either has the login or an API key, and dev account has its own API key with minimal permissions.
Successful sudo from a cgroup still makes you root on the machine. What you want for this is user namespaces, not (just) cgroups.
I meant for CLI tasks. Just "adduser" and "sudo -u <user> bash".
Most programmers and power users install large dependency trees with npm/pip/bundler/... on the same user account as their main browser on a regular basis. Even on Linux where it's easy to create new user accounts. This isn't much different.
Depending on where you live, your employer may be legally required to accommodate your disabilities. Here in France, HR are usually dutiful about it.
It's because the page you posted contains this incorrect tag:
<link rel="canonical" href="https://ec.europa.eu/commission/presscorner/home/en">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 can't find information about this except in a Reddit thread. Is it documented somewhere?
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.
They probably meant 74000m², not 74km².
But it's not even a first draft. There are only pictures and markdown files.
A Mastodon instance used it: https://www.theverge.com/2024/2/12/24071036/queer-af-mastodo...
What does it mean for a DNS resolver to be "integrated with CDNs"? And why does that affect streaming speed negatively?
https://www.scientificamerican.com/article/google-engineer-c...
it was before ChatGPT
There is some recent progress on https://github.com/rust-lang/crates.io/issues/326
It also means Diffusion in the context of images and videos.
The IRCv3 WG was convened near the end of 2016, so 9 or so.
SASL support in IRC predates IRCv3.
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.
This is Pyodide, not Python.
Netsplits
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.
missed messages
Solved by most server implementations using https://ircv3.net/specs/extensions/chathistory
bot wars over channel and nick ownership
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)
Fun, but there is a mistake in https://docs.rs/misfortunate/latest/misfortunate/struct.Maxw... which claims: "yet violates the social contract of these two combined. A Maxwell is not equal to anything (even itself) but all Maxwells hash the same"
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!)
The paper (https://hannesweissteiner.com/pdfs/frost.pdf) cites two earlier papers (from 2014 and 2017) that did the same for HDDs.
The random times don't have to be uniformly distributed. Though it's enough for attackers to know the distribution to de-noisify it.
Nothing in the article says the cameras are inside.
Didn't work last time https://www.theguardian.com/uk-news/2020/nov/06/companies-ho...
Are there estimates of their failure rate?
According to https://bugzilla.mozilla.org/show_bug.cgi?id=1950764#c23 , it is not getting fixed.