> You should do a breakthrough
This is just as funny and ridiculous as those "make no mistake" prompts.
5,907 karma · joined June 4, 2021
Contact info: Don't.
> You should do a breakthrough
This is just as funny and ridiculous as those "make no mistake" prompts.
String concatenation SQL injection in the year 2026.
I hate those arguments "it has emdash therefore AI", of course humans also write that way.
But poor and excessive usage of them is a pretty strong red flag, also together with other tells.
I assumed some of my coworkers added "replace all em-dashes with semicolons" into their CLAUDE.md as a really crappy attempt at hiding their inability to write a single sentence without assistance.
Is that a new feature? I have over a thousand contributions on StreetComplete (casually using it during walks) and somehow I never noticed that button.
Who cares about AI, I wanted to read about living in Galapagos
You know you can just read the linked articles, right?
Edit: parent has edited their post, it used to say something like "google has never notified anyone about such things".
I've seen many people who are quite competent under close supervision but completely clueless on their own.
We could debate if academia would be better off with different approach though.
This is one option, trading ease of use and low cost for lower picture quality and less light.
It's not extreme interpretation, it's the intent.
Just say it would break your vendor lock-in.
Our github->slack subscription breaks every few months, they never acknowledged it before. At this point we have a doc with the list of repos and settings, whenever someone notices that things are awfully quiet we just go through it and resubscribe.
- Receive a huge vibecoded PR for complicated new feature.
- Complain that this needs some design doc to figure out the right approach first.
- Author says no need for design doc, easier to have vibed implementation and discuss the concrete code instead of abstract document.
- I disagree (obviously), but review the PR with feedback along the lines: this entire approach is flawed, throw this out and start over.
- Author gets defensive, says "but this is already working and ready, let's just merge".
- I tell them there is no chance in hell this is getting merged. They go sulk to their manager that I'm not interested in helping them launch.
They have forums where people post neat cloud photos and if you sign up for membership they will send you an identification chart plus a journal for keeping track of the types you have seen.
Makes for a nice gift for that person you know who always goes "oh look at that cloud!" :)
I wish I had your Spotify.
Over the last few months they have served me multiple slop tracks in the discover weekly playlist. Probably more I didn't notice when just listening without focus, but several had generic artist name without bio and dozens of nearly identical tracks.
It's also on completely different OSI layer.
I don't see the difference between your comment and a statement like "I don't like email so let's stop using TCP".
Garbage Invoker, Garbage Output
> Chrome alone controls roughly 73% of global desktop browser market share.
> More and more, the webdevs of the world test and develop for Chrome only.
> It doesn't need to be this way. https:// is not the only way to connect and interface with the Internet
These are completely unrelated concepts! Google/Chrome doesn't control HTTP nor HTTPS. There is nothing wrong with the protocols, you can just make your website plaintext file if you like.
C2PA is basically a signature that serves to prove it came from certain source.
It's useful in case you want to prove you got an image from AI model to someone who doesn't believe you.
It's trivially removable and not useful against people trying to pass off generated images as real.
No, you are perfectly normal.
The people who in one week decided to replace the whole codebase for a widely used tool with code no human has seen are the crazy ones.
Why? Already getting traffic for free.