RealID is so important to security, it can't be used to prove you are a U.S. citizen. So says DHS, the people administering the RealID program.

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?

And should be treated as such.

No enterprise concerns if you can just tick a policy box.

And for home users, people who don't know what GPO is let alone have access to it? They're just screwed, aren't they?

There was no issue until Israel drug the U.S. by the nose into a war it can't win.

Remind everyone again who it is that keeps attacking its neighbors claiming "self defense" then whines it's the victim? Or who has been saying another country is "two weeks away" from nuclear weapons for the past 40 years?

I don't know who to root against more here. Can they both lose? Is that an option?

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.

You had the opportunity and blew it. Here is what you should have used:

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.

Microsoft pays its employees so well.

Just like all those other programmers people say deserve their rich salaries.

Even if this crazy minimum-age shit weren't happening, it's generally a good idea to give incorrect information. Have one birthday for site x and a different birthday for site y. Use one of your parent's birthdays here, and a celebrity's birthday there. Pollute the public data and cause confusion.

If minimum age laws help to encourage data public data pollution (all of which arguably shouldn't be public at all anyway), then at least one good thing will have come out of it.

Let's get it up to 84% of parents helping their kids bypass age checks.