•••••
> Instead, Google did what Google does in 2026 and gave me an AI overview. These used to bother me but at this point I'm mostly ok with them, they're sometimes helpful I never found them helpful. I always have to block them via extensions. Google is really an annoying company these days. I am hardly the only one who wishes that company were to cease to exist altogether. In the past I did not understand, on reddit, the de-google movement. Now I completely understand it, but I think it is the reverse as problem here - people abandoning Google. I think Google needs to abandon mankind and this planet. Let them go far away where they no longer cause any issues here. > Google, a search engine which does not have human emotions, assumed that I had been spurned by a man in my life named Dario and decided what I wanted was an empathetic digital friend. What I wanted was some links, but that's not what Google does in 2026. Expanding the AI overview to see the full answer gave me this: Poor guy ^^^ has not yet realised that AI slop steals his time. I realised this the first time I notice the AI slop generated text spam Google pushes onto people. A few lost souls may find this useful - I find it utter trash. No quality. Just steals my time. > What in the fucking hell? I think this was the moment I, the frog, noticed the pot had been boiling for a while. In what universe is it Google's job to console me and be an empathetic listener rather than just find what I am looking for on the internet? Good that he finally realised it. Million people noticed this before already. I noticed this when Google started to ruin its search engine. First time I remember was via AMP-ification. AMP mostly failed, but Google kept on pushing towards less quality and more suckage. AI is just the final nail in the coffin, but Google search started to suck way before that. One of these days some scientists should determine when Google really started to suck, because in, say, 2006 or so, Google search did not suck as much. > Regardless of what you think of AI or chatbots, I think it's pretty obvious this is just plain weird. Not if you think Google is not doing this on purpose. They are trying to kill off the search engine so they can present you an AI slop spam world. The other AI slop companies do this too. Slop suckage everywhere now. > Is it so hard to imagine that some parts of search were just fine before LLMs? That is how YOU think - but not Google. They deliberately crippled their search engine. The adCompany that Google is today, has nothing to do with the original Google. The billionaires running the show just want to suck in more money and dish out more slop. > I'm not sure how to feel about all of this. Maybe I should go talk to my friend Google, it's always so nice to me. Some people realise things more slowly. I am glad he finally understands why so many people are pissed at Google. Same for youtube by the way - about 80% of the shorts are AI slop generated or AI slop modified. I noticed this when I watched Brent Spiner on that podcast show; in the video itself, he had white hair but not totally white. In the short, both he and Jonathan Frakes had much whiter hair. I then realised that AI spam filter slop lies to me. I hate AI slop. Youtube is now infected with that, in particular the shorts. Poor guys looking at their smartphones being spammed down via lying slopness.
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
That's why we have different criminal statutes for homicide. If you're at a gun range looking down a scope and someone crosses right in front of your gun as you fire, you would probably be fine since you were shooting responsibly and had no way to see them until it was too late. If you're at a gun range and that backstop is deficient such that a bullet passes through and hits someone, again, probably not liable but the gun range may be since they built a bad backstop and let people use it. If you are at a gun range and lose control of an automatic weapon and kill someone, you may be liable for negligence because you were using a gun you couldn't control. If you are cleaning your gun and it goes off because you forgot to check if it was loaded, again, criminal negligence. If you threaten someone with a gun and they get shot while trying to wrestle it away from you, that may be some form of manslaughter. You had no intention of shooting them but the act of threatening them with it created a situation where the other person died. Same with killing someone while drunk driving, you didn't mean to crash your car but you did something to create the risk. If you plan to kill someone, it might be the top tier of homicide charges but it depends on how much planning went into it. If you walked in on your spouse cheating and went to grab a gun to shoot the affair partner, maybe a lighter form of murder than if you made a plan to track the affair partner to their house and killed them there. Simply put, there are a multitude of ways you can be charged with a crime that takes into account your intentions and forethought. Did someone intend for these agents to escape their sandbox? Did they do their due diligence in building a sandbox such that it would be difficult for agents to escape? Just like with all software, a reasonable person assumes that nothing is bulletproof, spend enough time and money and you can probably find a vulnerability. The question is does a reasonable person think that this sandbox should have kept an agent contained?
•••••••
#!/bin/sh errecho() { >&2 printf '%s\n' "$@" } if [ "$#" != 1 ] || [ -z "$1" ] then errecho 'Requires a single filename as the argument' exit 1 fi ORIGINAL=$1 if [ "${ORIGINAL#./}" == "$ORIGINAL" ] && [ "${ORIGINAL#/}" == "$ORIGINAL" ] then ORIGINAL=./"$ORIGINAL" fi # because of course the output of dirname can't be blindly joined with slash and the basename DIRNAME=$(dirname -- "$ORIGINAL") if [ "$DIRNAME" = / ] then DIRNAME= fi FILENAME=$(basename -- "$ORIGINAL") # because of course extracting the filename's extension is not supported out of the box case "$FILENAME" in .*.* ) EXTENSION=.${FILENAME#.*.} BASENAME=$(printf '%s' "$FILENAME" | cut -c-$((${#FILENAME} - ${#EXTENSION})) ) ;; .* ) EXTENSION= BASENAME=$FILENAME ;; *.[^.]* ) BASENAME=${FILENAME%%.*} EXTENSION=${FILENAME#*.} ;; * ) BASENAME=${FILENAME%%.*} EXTENSION=$(printf '%s' "$FILENAME" | cut -c$((${#BASENAME} + 1))- ) ;; esac if [ "$FILENAME" != "$BASENAME$EXTENSION" ] || [ -z "$BASENAME" ] then errecho 'Failed to properly split the extension from the filename:' "$FILENAME" exit 1 fi TIMESTAMP=$(date --utc --date=@"$(stat --format %Y "$ORIGINAL")" +'_%Y-%m-%d_%H%M%S') if [ -z "$TIMESTAMP" ] then errecho 'Failed to get the timestamp of the file:' "$ORIGINAL" exit 1 fi NEW_FILENAME=$(printf '%s/%s_%s%s' "$DIRNAME" "$BASENAME" "$TIMESTAMP" "$EXTENSION") if [ "$NEW_FILENAME" = "$ORIGINAL" ] then errecho 'Somehow the name for the backup is the same as the original file' exit 1 fi # this preserves the timestamps somewhat better if ! mv --no-clobber --no-copy -- "$ORIGINAL" "$NEW_FILENAME" then errecho 'Failed to backup the file: ' "$ORIGINAL" "$NEW_FILENAME" exit 1 fi if ! cp -- "$NEW_FILENAME" "$ORIGINAL" then errecho 'Failed to backup the file: ' "$ORIGINAL" "$NEW_FILENAME" mv --no-clobber --no-copy -- "$NEW_FILENAME" "$ORIGINAL" fi Actually, nevermind that bullshit, you know what? I think I'd prefer to have an editor with locally persisted edit history instead.
••
 Top