Google is trying hard to kill sideloading so probably not.

We had a vote on that. Your proposal lost. Deal with it.

"Jailbreak" definitely implied something illicit in 1974 when AC/DC performed the song, but in 2026?! No. Jailbreaking is totally legit 99 times out of a hundred.

Jails were once respected because they were a product of society's consensus. When DRM appeared, jails became anyone's restrictions, with no societal inputs and no claims to legitimacy.

If you break out of the county jail or federal prison, that's a whole other thing than breaking out of your neighbor's sex dungeon. And almost all the time we talk about "jailbreaking" now, it's analogous to the neighbor's sex dungeon. Nearly everyone would agree it's legit to leave, and any illicitness is on the part of the captor!

[I]t's important to note that jailbreaking a Kindle might violate Amazon's terms of service.

Isn't the context here, that there is no service? I suspect that whatever terms the two parties came to agree upon, Amazon is the one who has initiated the violation of those terms, by ceasing to provide service!

Slashdot is a website for the elderly.

"I had some issues where I forgot how to implement a Laravel API"

As long as you still know how to read the documentation, it will likely come back to you fairly quickly.
I guess it is like when you switch away to a different framework / API / etc, stuff like that will leave your short-term memory after a while, and you have to re-learn it, but you will re-learn it a lot quicker than how long it took you to originally learn it.

Do you really mean that if your git repo were corrupted, restoring a snapshot of the repo from backups wouldn't work? If that's true, then it sounds like your backup system is broken. The hashes after restoring ought to be identical to what they were before the backup.

If git used the files' iNode numbers for its hashes, then I could understand how a filesystem-based backup/restore might not really work; you'd have to backup at the block level instead. But git doesn't use the iNode numbers.

git isn't magical. It only knows files. It doesn't know if you moved the repo, copied the the repo, or restored the repo from a ten year old backup. I have moved git repos around plenty of times, `cp -a`ed directories with repos, tared and un-tared directories that contain repos, and the copies have always Just Worked without any hash mismatches.

mkdir ~/test. cd ~/test. git init, touch test.txt, git add test.txt and git commit. cp -a ~/test ~/test2. cd ~/test2 and check out the backup repo. The backup is valid. Then simulate a disaster with rm -rf ~/test. Then recover from the disaster with cp -a ~/test2 ~/test and you've just restored a repo from filesystem-level backup. The resulting repo works perfectly and its hashes aren't off. git has no idea you deleted and restored under its nose. Try it yourself.

What am I missing? I'm not surprised to be called idiotic, and the shoe often fits. But I'm surprised to be called that over this.

My router's hardware's parts were made in China. Its software was made as a worldwide effort but the team seems to be officially based in the Netherlands. And I'm not asking my government's permission for updating either one. Trumptards and their micromanaging far-left centralized-economic-planners can go fuck themselves. Keep your damn dirty ape hands off my computers, comrade.

>>If you bothered to read, they are not blaming the victim, they fixed the problem and just point to where it came from.

They fixed one manifestation of the problem. The real source of the problem is that the AI can't seem to evaluate the status of it's training data; even at the most basic level of fiction vs non-fiction, to say nothing of more subtle differences like plausible vs implausible, joking vs serious, fact vs opinion, etc.

It's a fun house mirror that exaggerates some aspects and minimizes others (and you don't know which it will do until you try it).

What needs to be controlled are the firms and people working on AI (just like we regulate research on viruses, genetics, atomic energy, etc).

Is there room for consciousness to manifest in a brain?

>> Prof Dawkins said he had let Claude read a draft of the novel he was writing and was astounded by its insights. "He took a few seconds to read it and then showed, in subsequent conversation, a level of understanding so subtle, so sensitive, so intelligent that I was moved to expostulate: 'You may not know you are conscious, but you bloody well are!'" Prof Dawkins said.

Translation: The bot told him that it loved his book (as the overly-agreeable bots are programmed to) and the noted egotist declared that the bot was not just sentient but also brilliant.

If the data center is primarily intended for use by (exclusively or nearly exclusively) the people in the neighborhood, sure, it could make sense. I know this is quaint and out-of-date but one can imagine a neighborhood squid cache, NNTP server, modern Netflix cache, etc for the neighborhood. Have it be connectable by a high-speed neighborhood LAN, to share the 'hood's WAN.

Just a classic neighborhood network coop, but with some added caching services, which is what would cause it to be called a "datacenter" instead of a "router." ;-)

As if that would really happen. And that's sure not what this is.

Once again, I'm not shocked by the percentage laid off, but I'm shocked by the number of individuals. If 700 people was 14% of their workforce, then this company had about a hundred times as many employees as I would have guessed. Not that my guesses are particularly well-informed, but when I look at what this company's product appears to be and compare it to my own experiences, I can't help but make guesses that are apparently 99% off! (I'm that dumb!?)

What do employees at these large companies do all day? Why were they hired in the first place, or why weren't they laid off many years ago? I just don't get it.

I don't mean it as a put-down of their products, but on the surface it just doesn't look like their thousands of employees do anything bigger or more complicated than my dozen-developers-sized team (which is, itself, much larger than the teams I've been on in previous decades). Is everyone's productivity just .. eaten up by labor-not-scaling problems? Do I need to really read the Mythical Man Month instead of treating it as distant folklore that I'll some day get to?

Or is the answer in some other direction? Part of me thinks I should just drop it, and accept that I really don't know jack shit about the profession I've had for the last 40 years.