Comment Re:Hahaha (Score 1) 36
"Yes, you did pay to delete the backup... but not the redundant copy."
"Yes, you did pay to delete the backup... but not the redundant copy."
Well, odds are the people in charge at Instructure are relatively stupid themselves. It's like the old Sherlock Holmes quote: "Mediocrity knows nothing higher than itself" - the Instructure leadership probably can't fathom how anyone smarter than them could exist.
Given how people keep stupidly paying these ransoms... maybe it's time to criminalize that act.
GoogleBook never sleeps! It is always watching...
Uh, out for you! Yeah, that's it. It is always watching out for you.
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.
Apple's driving consumer behavior on the exclusive "blue bubble" while fighting the adoption of good standards always seemed like 90's Microsoft behavior to me.
Well, it wasn't just Apple. Google was cynically playing that tune on repeat for marketing purposes - while not letting anyone on Android who wasn't using Google's own apps to encrypt RCS either.
Translation: Guy whose company has made untold billions from AI is telling people to embrace AI because it'll solve everything.
I remember our university had what amounted to a showroom - a place we could go to see all the different varieties of computers which were available to campus people (students, faculty, and staff) with some sort of discount from the manufacturer.
"insidertrading.com"
Right now, it's pretty likely the following would also cover this:
"whitehouse.gov/insidertrading"
That is called a transaction fee. Is this intended to be a deterrent, or just a concern that the government isn't getting their cut?
You've both asked, and answered, your own question.
I think we're also still "two weeks" away from that imaginary beautiful gift Trump claimed the Iranians offered as well...
When the tech firms got involved with creating these sites in the first place, it wasn't out of the goodness of their CEOs' (non-existent) hearts...
They didn't burn the robot's arm with incense because robots are deathly afraid of fire.
Just once, I'd like to see the white hat turn out to be someone like Jisoo...
"If John Madden steps outside on February 2, looks down, and doesn't see his feet, we'll have 6 more weeks of Pro football." -- Chuck Newcombe