EnshittifAIcation
rockstar2001
32 points
5 comments
March 20, 2026
Related Discussions
Found 5 related stories in 42.9ms across 3,471 title embeddings via pgvector HNSW
- A Day in the Life of an Enshittificator [video] leephillips · 11 pts · March 01, 2026 · 58% similar
- A Day in the Life of an Enshittificator [video] doener · 11 pts · March 01, 2026 · 58% similar
- Antienshittification ystrickler · 17 pts · March 30, 2026 · 51% similar
- Things I've Done with AI shepherdjerred · 80 pts · March 09, 2026 · 49% similar
- AI (2014) bjornroberg · 69 pts · March 20, 2026 · 47% similar
Discussion Highlights (4 comments)
eqvinox
Go with EnshittificAItion. Sounds much better.
judgardner
Had a similar experience with a vendor. Marketing team requests we add some DKIM settings for yet another vendor that is gonna spam people on our behalf. The requested record is * TXT test I explain that's gotta be a bug on their UI, we send a screenshot to the support of the vendor. The marketing team has 4 turns with an AI that refuses to escalate to a human and is convinced this is the only entry it needs us to add to our DNS. Dropped the vendor. Someone from their retention team followed up and we linked them the ticket talking to the bot about the obvious bug. Never heard back.
icedchai
I'm seeing an unfortunate pattern where someone wants to write an email, and "asks Claude", producing a needlessly verbose response that the recipient doesn't even want to read. The slop is obvious. This behavior is being pushed down by senior management.
lproven
I wonder if Nexi having LLM bots both originating and receiving emails might be the root cause of the FSFE problem? https://news.ycombinator.com/item?id=47451429 I do not know! Just speculating.