You just replace that anxiety with a different fear.

I don’t fear oblivion, I fear it will keep me waiting. Not existing is a silent matter, living past your due as a broken, diseased husk or a person is a torture to you and those you cherish.

Death is a promise of rest, there’s no need to fear it. I’m a bit sad that I won’t get to witness most of the things I want to witness, but so be it.

Been using minpac since forever. It has all the minimal functionality and is a perfect dead project one doesn’t have to worry about.

One day I might switch to lazy, but so far I’m too lazy to.

Funny how those articles the useful idiots share never link to the report in question.

https://www.echr.coe.int/documents/d/echr/HUDOC_38263_08_Annexes_ENG

Turns out, report doesn’t claim what the articles claim. What it does do, however, is engage in a useful “both sides are to blame”, “green men didn’t have official patches”, and “think of the children human suffering” sophistry that Russians just fucking love to spin into a disinformation campaign. Oh, and it immediately starts with authors absolving themselves from any responsibility and claims of having discovered truth.

I’m not afraid of retirement, I’m afraid of needing to work on the day of my funeral.

Just reread my wall of text, and I think bits and bytes are in the right places. I do have a tendency to be blind to my own typos, however, so there’s that ._.

Definitely. I’d say the limit should also be calculated over a useful inputs space, which is likely larger than 60 symbols. A good chunk of byte sequences that hash algorithm could accept are nearly guaranteed to never be submitted by a legitimate user.

Depending on an encoding and an alphabet the password manager or user themselves use, up to half of possible bit sequences are impossible to achieve. E.g. 10000001 is not a valid one-character string in UTF-8. And no upper byte in UTF-8 can’t start with 0. So it’s easy to get locked to 7 bits of variability on every byte.

Which would mean that 60 symbols input is not 2^480 variable bytes, but 2^420. That translates into an effective length of about 52 characters. Still a lot and above what’s considered vulnerable, but a few more restrictions or overeager optimizations, and suddenly the problem is shrunk to a space that a bitcoin farm can manage.

In other words, security is a fascinating topic.

PS: “up to half” is definitely optimistic, by the way. I’m definitely unlikely to ever produce a password that has a byte starting with 0 and two follow up bytes starting with 1s. I won’t even know how to type them, and I like my passwords typable.

Considering hash functions used for passwords operate in a range of 32 to 64 bytes, that’s really not a problem. Go above that length, and you’re not ultimately improving your password collision resistance due to pigeonhole principle.

There are caveats. For example, if the only source of feeding the colliding passwords to the system is an endpoint that filters for human readable inputs, then that could double (well, spread) the effective collision search space size. Which is not really a factor on your 480 bits password length.

PS: Newer password hashing algorithms like argon2 can scale into gods defying territory, but in practice they also tend to stay below 128 bytes. Those hashes need to be stored, calculated, and compared - all of which are DoS vectors.

Bullshit. If they wanted to cut ties and protect their image, they could block the channel and wash their hands.

This here is pure profiteering.

Every wave is affected by Doppler effect.

When a car rushes your way, it’s a tiny bit bluer, a little bit hotter, it’s drivers’ phone is operating on a slightly higher frequency and it sounds higher. According to you.

They are as incapable of handling one third of a dollar as binary positional notation is incapable of handling one fifth (0.2).

It’s not really a float problem. It’s a positional notation one. Some perfectly rational numbers refuse to squeeze into that mold.

Do not solve maintenance problems that you don’t face.

They don’t measure emission but body absorption. Body limit is 2 W/kg, limbs limit is 4 W/kg. Apparently only the latter limit is violated.

For meat sacks like us it primarily translates to heat. At frequencies used, this radiation can nudge molecules a bit, which directly translates to heating up. If it was in a hundreds of watts, we’d be approaching microwave ovens territory.

The limits are there because there’s a limit to how much heat a body can efficiently dissipate, and quite a few sources of it. There’s also a concern that localized RF heating can cause cancer, which is not empirically confirmed. I personally care more about a confirmed issue of the nuclear ball in the sky causing one.

https://www.bleepingcomputer.com/news/security/france-demands-apple-pull-iphone-12-due-to-high-rf-radiation-levels/amp/

PS: Totally forgot, just by existing and occasionally eating, you’re generating roughly 1W per kilogram of body mass, probably a bit more.

With free time and some rest I’d move to sourcehut.

And with KDE and Wayland development, dumping games with annoying save mechanics to disk might also become available.

Save scumming ahoy!

Every time someone confidently claims that we can cryptographically verify voting, they are deliberately or ignorantly keeping the complexity and necessity of verifying the verifier runtime, the data source, and the communication channels out of the picture.

Cryptography doesn’t solve voting verification problem, it obscures and shifts it.

By becoming a CTO and having an early retirement. Or not at all.

deleted by creator

It’s your job to prove your assertion that we know enough about cognition to make reasonable comparisons.

This is pretty much all that’s needed. The language in the block is identified via a name that follows the opening triple backtick. E.g.:

```python some carefully indented code ```

“Private” in “virtual private network” means “routed by different rules”. It’s the same “private” that’s in “private Internet Protocol addresses”.

It was never about personal privacy.