Ah fair enough, can’t argue with personal preference.
You sure you weren’t using waterfox classic though? That has a more dated UI than the current version.

I personally use librewolf anyway, but waterfox is still a pretty decent step up from Firefox, privacy-wise.

Interesting. What did you dislike about waterfox?

It’s actually a comment on the performance loss incurred from a likely failed branch prediction.

Yes. It’s clearly red.

Keep your magic ways to yourself, wizard

You don’t use butterflies?

Bruh you better watch out or I’m gonna delete your IP address

CrackTonight

We can, but blockchain is old technology.
We should use an LLM to create and verify the tokens.

That’s when you add an extra point of failure validator.
Server 1 generates a token for server 2 to validate.
You send the token to server 2, who validates and generates you a token for server 3. Then finally server 3 validates the token and grants/denies your access.

The more nodes you have across different countries, the harder it is for the last server to discover your identity.

Definitely not without its flaws, but I wonder if a decentralised node setup similar to the tor network could work.

Probably because it’s only four bytes of data, and counting/extracting bits takes more cpu time than one AND operation.
Most CPU’s are optimised to work with whole integers (32/64 bit) rather than individual bits.

If memory was a serious concern you could compress it down to one byte as a ‘number of 1s’ counter at the cost of additional cpu operations, but because 3 extra bytes is such a small amount of data, this memory/time trade off isn’t worth it in most systems.

It’d be useful if you wanted to compress some data logs or something with many subnet masks though.

That dude looks like a Disney character. Even his name sounds like one.