They had intel on a 6 month old Hamas baby.

That would waste days while there is a danger…

The US is so crazy when it comes to this. In Europe you’d almost always just sue for actual damages, which because of healthcare are pretty low. You could get a small amount in cash but nothing crazy. Suing just to get money is stupid.

Try to do some research like you would do with closed source tools. See if they have a website and if it links to the GitHub you encountered. Also see if there are subreddits or forums and see what they link to.

In the case of this “Pro” version of KeePass; a simple search would have shown that there is no Pro version.

It’s filter bubbles mostly. You always need counter arguments and modern technology is suppressing those. I believe banning algorithms will help a lot.

PSA: The amount of stars on GitHub can be botted and is not a good indicator to know if you are dealing with a legitimate repository. Even the commit history can be faked (although that’s less common).

But not surprising.

“Spaghetti is a great dish so why would spaghetti code be bad?” - Vibe Coder

When using Stremio you are seeding. There’s a cache size that holds a specific size that you will be uploading back. As long as Stremio is running in the background you will be seeding.

There’s tools to normalize audio in a movie. Dynamic range compression or something like the dynaudnorm filter in ffmpeg.

Lmao.

As if my title isn’t almost exactly the same.

bcrypt hashes only the first 72 bytes. 24 characters is the max amount of 4 byte UTF8 characters when using bcrypt. Which is stupid because UTF8 is variable, but still, it’s a possible explanation.

but this in no way indicates clear text password storage.

It does.

No it doesn’t.

What an awful thing to say. Go question your motives.

That’s not true. There’s limits everywhere.

The claim was that a limit on passwords implies plaintext storage. It doesn’t. There is no such thing as unlimited on computers.

Seems reasonable.

There’s some software that hashes the password clientside before sending it, sure. But it still should be hashed serverside too.

The backend should care though. Even if strings can have an unlimited amount of characters, you don’t want to go and hash a gigabyte of data. In lower level languages you don’t have magic strings either so you might do something like char password[64].

There’s many reasons to limit raw password length. Not many good ones to have it as small as 24 (or even 64) though.