Careless logging is the one.

At the time Facebook was invented, plaintext passwords had been a joke for years.

PHP extension might be telling. Consider that phpBB had an extention system that didn’t have any kind of hooks. All extensions were installed by modifying the code in place. They did not use any of the diff formats already out there; in a gross case of Not Invented Here, they made their own. Took them a while to make their own patch tool to automatically apply their custom diff, and it was buggy as hell.

So that shop might have just been following the lead of one of the most successful PHP apps.

Someone will be along to say “PHP is good now, actually”, but I don’t care. The community was shit back then, and I don’t see why anyone should care beyond legacy software at this point.

Lol

They want AGI, which would match or exceed human intelligence. Current methods seem to be hitting a wall. It takes exponentially more inputs and more power to see the same level of improvement seen in past years. They’ve already eaten all the content they can, and they’re starting to talk about using entire nuclear reactors just to power it all. Even the more modest promises, like pictures of people with the correct number of fingers, seem out of reach.

Investors are starting to notice that these promises aren’t going to happen. Nvidia’s stock price is probably going to be the bellwether.

It was the night before.

I think the best way forward would be a single board computer that can do an open source equivalent to chromecasting. Plug that in and leave your TV unconnected to the network.

You can’t do chromecast directly, because Google holds encryption keys for it. Unfortunately, this means casting apps need to be modified to support it.

There’s a few projects like this:

• https://github.com/MayaPosch/NymphCast
• https://fcast.org/

Fantasy evolved out of folk tales in the public domain. It was owned by nobody, and everyone could add to the story. It’d be accepted if people thought the story was good enough. Later, new stories were under copyright, but their heritage was clearly public.

SF grew up when a strong copyright regime was already in place. It was owned by either a single person or a corporation, and only they had the legal right to declare what was canon or not.

Short of it is that John Deere is preventing farmers from repairing their own tractors. How much it threatens the food supply, I’m not sure, but there is an obvious connection.

Dry? It was a carribean island, right? Probably humid as fuck.

That’s more of a Japanese company thing than something specific to Nintendo.

Not that it makes it OK, but this is a country that looked at how workers are treated in America and decided the problem was not going hard enough.

Languages don’t die. They have long tails.

That’s a very narrow view of programming.

Guys, I think Marx might have been onto something with the theory of alienation.

I’m not sure it is. Like, yes, it does exist in the Left/Right, Auth/Lib political compass, but that’s just a model. The stance has some inherent contradictions.

And so does Right/Lib, for that matter. “Fiscally conservative/socially liberal” is a nonsense position, and those taking it tend to just be conservative in practice.

BufferedReader cannot accept file name because it makes arbitrary reader… well buffered. It’s not BufferedFileReader, even that would accept something like Path or File, not string, because File can be remote file, should Reader now know all possible local and remote protocols and path formats? What else it must do?

You’re just describing the problem. Yes, I see where they’re going with this. It’s still a usability nightmare. I can’t think of another language that makes you jump through hoops like this on IO, and they get along fine without it.

OK. How do you reconcile that with “Hashing passwords isn’t even the best practice at this point”? Key derivation functions are certainly the recommended approach these days. If they are hashes, then your earlier post is wrong, and if they aren’t hashes, then your next post was wrong.

Lots of older databases had fixed length fields, and you had to pad it if it was smaller. VARCHAR is a relatively new thing. So it’s not just saving space, but that old databases tended to force the issue.

Nobody has an excuse today. Even Cobol has variable length strings.

It matters for bcrypt/scrypt. They have a 72 byte limit. Not characters, bytes.

That said, I also think it doesn’t matter much. Reasonable length passphrases that could be covered by the old Latin-1 charset can easily fit in that. If you’re talking about KJC languages, then each character is actually a whole word, and you’re packing a lot of entropy into one character. 72 bytes is already beyond what’s needed for security; it’s diminishing returns at that point.

Sarah Palin had her Yahoo mail account hacked because of those “security” questions. In 2008. We should be well past the time where they are a thing.