Em Adespoton

The government IS the test run.

Sounds like a new target for timing attacks?

The main point is that with a regular backup regime, it doesn’t matter if SSD will lose your data if unpowered for a long time… because a) they won’t be unpowered for a long time (there’s rotation happening here, not archival), and b) you’ll have already hopefully moved off any specific piece of media before MTBF, and if you haven’t, hopefully all your devices don’t fail at exactly the same time.

So yeah: SSD isn’t for archival purposes. But archival isn’t really what we’re after here, as backup of ALL data is a possibility. It’s not like we have a monk or vellum shortage to worry about.

You missed a few terms… how about “influencer handle” instead of “pen name,” for example?

I have 3 physical backups of all my stuff, one a rotating offsite backup. The backup media gets replaced over time.

I don’t expect media (especially backup media) to last more than 10 years. But it doesn’t matter, as my NVMe backup solution of today looks nothing like my spinning rust backup solution of 20 years ago, despite holding all of that data.

Wouldn’t that be fitting? After all this, Elon comes to Canada and is put away for life for defrauding the Canadian government.

Fails to mention he also was selling the discs online.

But they want to sentence him for 15 years for this, even though his actions likely saved lives during the height of COVID if the allegations are true; if they aren’t true, he harmed nobody because those 10 million people wouldn’t have seen the movies in theaters anyway.

Well, Usk is a Canadian citizen, so is allowed to buy cars in Canada. Even his own.

My lesson in this was way back when LinkedIn came out with an app. I installed it and the first thing it did was ask me for all my contacts and start pinging tracking servers. I uninstalled it immediately and avoided apps for web services after that.

Later that year, I found that if I HAD allowed that app to do what it wanted, it would have grabbed all that data and sent it to the company, who was selling it off to third parties. They got in a big class action lawsuit for it.

Those were the days. Now it’s just expected behavior.

Well, as a lot of us are on instances hosted outside the US, a very long time.

Funny; that’s where my mind went too.

TV equivalent of OpenWRT?

He’s already investigated himself and found that Xitter is a bastion of freedom. Same goes for Truth Social.

In reality, coding is something you can learn on your own… or not. Colleges are good for teaching computing science and architectural design, but the good ones will assume you already know how to code. The problem of course, is that when you graduate you are unlikely to find a job as a computer scientist or software architect, and will most likely need to spend 5+ years as a junior programmer first.

Namanyay, I’m sorry to say, sounds like a relative newbie when it comes to software development. The refrain “junior software developers can’t actually code” has been around as long as software development.

I remember when Stack Exchange first popped up, senior developers complained “junior developers don’t actually LEARN anything anymore; they just copy code off of Stack Exchange without understanding what it does!”

And before SE? We were doing the exact same thing in the comp.* newsgroups. And before that? When you started developing something, a senior dev dropped a bunch of books on your desk and said “when you’ve finished reading those, let’s talk.”

The truth is, ever since libraries have been a thing, the majority of developers have just used the libraries without really understanding what goes on inside them. And that’s not necessarily a bad thing — the entire point of abstraction is so that developers can focus on the stuff they need to get done while ignoring the already solved problems.

The issues arise when you place code monkeys in software architecture or senior development positions, and they’ve never had the curiosity to read through the header files for those libraries they use, but instead just let Claude code complete their way to functionality. Because then most style guides with teeth go out the window, as there’s no intention behind the choices made.

And this results in something that really irks (and always has) senior software developers: instead of writing really clean, performant and novel code, those senior devs have to spend all their time doing code reviews and editing and refactoring codebases that nobody else understands.

Same as it ever was.

Essentially, JS is the new Flash….

JavaScript has its place as a lightweight runtime interpreter.

Rust has its place as a secure and modern way to engineer and produce dependable software.

Expensive large screen displays are better.

Smart TVs are privacy invasive billboards that let you watch some TV on their terms.

Could be… it makes sense to reinvent the wheel if the previous inventors won’t share.

The big question though is: why?

CAPTCHA was implemented because machine learning was worse than people at solving the problems, so they could filter out the bots AND train their algorithms.

Today, the bots are often better than the humans, so both reasons for having CAPTCHAS no longer make sense. Even user verification can be easily faked by AI now.

The president isn’t a teenager, and as a sociopath wouldn’t have been representative of teenagers even when he was one.