Forgot your password?
typodupeerror

Comment Re:Tax is the wrong term (Score 1) 24

One aspect of enshittification that people don't talk about much is that sites do need to make money to continue. They can't be free forever.

Yes they can. If musicians, software companies, and movie producers don't need to be paid for what they produce, these sites don't need to be paid either.

Comment Re:Synthetic (Score 1) 101

An AI has no capability to have feelings

And what is a feeling? Based on Wiki:

According to psychologist Carroll Izard, feelings are best understood as the conscious experience of emotion, arising when an affective state reaches awareness.[4] William James similarly proposed that feelings result from the perception of bodily changes in response to external stimuli, thus forming part of the emotional process.[5] More recently, affective neuroscientist Jaak Panksepp hypothesized the role of subcortical brain systems in generating core affects that underlie both feelings and emotions.[6]

In other words, a feeling is a reaction to an external stimuli. Since reactions are nothing but the neural connections in our brains responding to the external stimuli, there is little reason to say an AI, with its digital connections, can't respond to external stimuli in a similar fashion.

Comment Re:And are permanent? (Score 1) 88

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.

Comment I don't ask FCC to "allow" me anything (Score 3) 75

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.

Slashdot Top Deals

"A child is a person who can't understand why someone would give away a perfectly good kitten." -- Doug Larson

Working...