Each state that gets money in a judgement or settlement, should use that money to make sure their public education system teaches kids how to block ads.

By 2030, I don't think anyone should be able to graduate high school in America, unless they've learned how to be ad-free (on screens under their control; obviously they won't gain superpowers to blank out billboards or the sides of buses).

That was equally true for previous generations, and all those generations had exceptions -- kids that were excited about it, despite the other kids not being interested. (I figure the majority of Slashdot may have been such exceptions.)

Do we have reason to suspect the current generation is a unique special case, the one generation where somehow all of them make an effort to never learn about computers?

I bet some of them are like some of us, a 2026 minority that we would have recognized 40 years ago.

And if that works, then I think the days of pi being irrational will soon be over.

With apologies to Dr "Suse", to the tune of "Green Eggs and Ham".

Linux can. Linux can .Use Linux

That Linux can! That Linux can! I do not like that Linux can!

Do you like open sourcing plan?

I do not like that Linux can. I do not like the open sourcing plan.

Would you like to free source share?

I would not like to free source share. I would not like it anywhere. I do not like open sourcing plan. I do not like that Linux can.

Would you like it very stable? Would you like it to enable?

I do not like it very stable. I do not like it to enable. I do not like to free source share. I do not like it anywhere. I do not like the open sourcing plan. I do not like that Linux can.

Would you use it in a X-Box? Would you use it if it ROCKS?

Not on X-box. Not if it rocks. Not if very stable. Not to enable. I would not let them free source share. I would not let them anywhere. I would not allow open sourcing plan. I do not like that Linux can.

Would you? Could you? In your biz? Use it! Use it! Here it is.

I would not, could not, in our biz.

You may like it. You will see. You may like it if it's free!

I would not, could not if it's free. Not in our biz! It should never be!

I do not like it on the X-box. I do not like it that it rocks. I do not like it amongst our biz. I do not like it that it is. I do not like they free source share. I do not like that anywhere. I do not like that Linux can. I do not like you Linux man!

service! service! service! service! Could you, would you, as a service?

Not as a service! Not if it's free! Not in my biz! Man! Let not it be! I would not, could not, on a X-box. I could not, would not, if it rocks. I will not use it if its stable. I will not use it even to enable. I will not let them free source share. I will not let them anywhere. I do not like open sourcing plan. I do not like that Linux can.

Say! if in copyleft? always free copyleft! Would you, could you, copyleft?

I would not, could not, in copyleft.

Would you, could you, why so nervous?

I would not, could not, I'm NOT nervous. Not as copyleft. Not as a service. Not in my biz. Not if it's free. I do not like that it can, you see. Not if it's stable. Not on X-box. Not to enable. Not if it rocks. I will not let them free source share. I do not like it anywhere!

You do not like open sourcing plan?

I do not like that Linux can.

Could you, would you use what we wrote?

I would not, could not, use what you wrote!

Would you, could you, to avoid your bloat?

I could not, would not, avoid bloat. I will not, will not, use what you wrote. I will not compete with them as a service. I will not because it makes us nervous. Not in our biz! Not if it's free! Not if it is! You let me be! I do not like it on the X-Box. I do not like it that it Rocks. I will not use it if it's stable. I do not like that it does enable. I do not like they free source share. I do not like it ANYWHERE I do not like open sourcing plan!I do not like that, Linux can.

You do not like it. So you say. Try it! Try it! And you may. Try it and you may, I say.

Man! If you will let me be, I will try it. You will see.

Say! I like open sourcing plan! I do! I like that, Linux can! And I would use it because it's stable. And I could use it to enable... And I could charge for providing a service. And I could copyleft without being nervous. And in my biz. And still source free. For you can still charge for a service fee!

So I will use it on the networked X-box. And I will promote it because it ROCKS. And I will use it because it's stable. And I will use it to enable.

And I will use it here and there. Say! I can use it ANYWHERE!

I do so like open sourcing plan! Thank you! Thank you, Linux man!

By The Cat with the Red Hat

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.

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.

Is there room for consciousness to manifest in a brain?

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.

I can't really say it's bad for it to be doing these seemingly-bad things, until I know the answer to this: what is the app's intended purpose? Why would/should a person use it?

If it's intended to inconvenience/expose/punish users for trying to find out things about the White House, then maybe the application is doing the right thing.

Restore the repo from backup at the filesystem level, and the hash will be valid because it was valid at the time you backed up.