PHM was much more ambitious in its scope than either.

I enjoyed Artemis-- can't find too much fault in any book whose main character writes an extended love letter to welding-- but I enjoyed PHM much more.

Just a counterpoint, I loved Project Hail Mary. I wanted my time back after reading Children of time, and it's exceptionally rare that I feel that way about anything scifi. Tastes differ. ::shrugs::

I really loved Children of Time but then he really went back to the same well for the rest of the series

Yeah the sequel ran with it decently. The third one was a slog and that ending ... Ooofff.

Hey, that's not the wallet inspector...

Yeah, in particular, what happens when you install the same amount of ram in both and downclock the N150 to match the rpi performance?

It's a bit of an odd comparison though because I don't think that rpi5 is particularly power efficient among small linux capable SBCs.

Yesterday I linked to an implementation (with complexity quadratic in the number of errors) I helped to create in another comment in this thread.

> constant factor using Chien's search algorithm

Chien's search is only really reasonable for small field sizes... which I think doesn't really make sense in this application, where the list is long and the missing elements are relatively few.

Fortunately in characteristic 2 it's quite straight forward and fast to just factor the polynomial using the berlekamp trace algorithm.

Oh yeah, factoring the polynomial is also a good idea. For a long enough list that ought to be better than AFFT too.

Tables yuck :P, maybe

XOR[0...x] = (x&1^(x&2)>>1)+x*(~x&1)

~Is there a simple proof for this type of identity?~

Actually I found something through Gemini based on the table mod 4 idea in previous post. Thanks.

Generalizing an 'xor accumulator' support set difference of more than one element is interesting: https://github.com/bitcoin-core/minisketch

And let me guess, this rule isn't eliminated if your property is isolated by a reduced pressure zone device?

I assume that in your post "WA" means Western Australia -- as I can't imagine this kind of absurd protectionism law flying in Washington state, even though it's a little more paternalistic than average for the US.

Yeah, Western Australia.

And of course not! As mentioned - the rule has even recently been extended to 'protect' people like us who live semi off-grid, with rainwater capture for drinking and a septic system.

Australians really seem to loooooove rules.

And of course, for the most part, nobody's actually checking this stuff and people pay varying levels of attention to the rules. Seems like a waste of time all round.

Selectively enforcing the rules is another classic Aussie trait.

> Infinite scroll wasn't designed to be taken literally, holy shit

Someone told them online chat was Hyperbolic and they took it literally.

Why does any additional encryption need to be broken? Signal dark patterns users into using insecure few digit 'pins' to protect their data, then waves some SGX hokum around that as an argument as to why very short pins have acceptable security. Of course, no one with physical access / state level resources is meaningfully impaired by SGX, so the security is just a trivial pin crackable by a speak and spell.

Concerns that were all dismissed when the insecure pin system was introduced because only contacts and settings were hosted, not content. ...

It's already known that users can't choose secure passwords even without UI that tries hard to encourage an insecure choice and that the rare ones that are secure are the ones that also get lost/forgotten. As a cryptosystem "user chooses and remembers a key" is known to be broken. So backup to the cloud really just means "hand to NSA with already known broken encryption".