HN user

scraptor

578 karma
Posts13
Comments82
View on HN

This time it has a major impact on the possible RNG outcomes even for a player who doesn't know about the bug, and it was caught much earlier in development before the permanent stability of existing seeds was guaranteed.

The idea was to transition from coal to natural gas while using solar and wind to reduce fuel consumption, thereby significantly reducing CO2 emissions. Any claims of hydrogen being burned were either lies to the public to get the gas plants built despite the non-green optics or lies to investors as part of a fraud scheme.

I don't hate journald because it's not plaintext, I hate it because it's worse than plaintext. Somehow journald manages to provide a database which is 40x slower to query than running grep on a compressed text file. I'm all in favour of storing logs in an indexed structured format but journald ain't it.

sqlite resolves lock contention between processes with exponential backoff. When the WAL reaches 4MB it stops all writes while it gets compacted into the database. Once the compaction is over all the waiting processes probably have retry intervals in the hundred millisecond range, and as they exit they are immediately replaced with new processes with shorter initial retry intervals. I don't know enough queuing theory to state this nicely or prove it, but I imagine the tail latency for the existing processes goes up quickly as the throughput of new processes approaches the limit of the database.

The client side toggle might be new since 2024 but the volume normalisation has been a thing for a long time.

Hyperspace 1 year ago

The linux tools can't get it wrong, the kernel checks that the files submitted for deduplication are actually identical.

If your nodes disclose their affiliation that's fine but the client will avoid using multiple. If you try to do this in secret the tor project will attempt to catch you by looking for suspicious nodes that use the same isp and update their tor version at the same time and things like that, to questionable success.

It will be incorrect whenever the time changes, so twice a year and maybe once more if you expect your microwave to adjust for leap seconds. Depending on the device it will also lose track of time if it looses power but in that case it should know to resync immediately.