@ujay68 Plex then still runs some the API (the searches, at least) through Sonos's cloud services, which, no, just no. It's also a paid subscription service that isn't FLOSS.

And Apple is banned in this household, they're even more locked down than Sonos.

If I'm going to rip out thousands of Euros of hardware (and replace them), I'm not going to fall for a future #enshittification yet again :)

Oh my, a 1.6 rating on the Google store and dropping. Seems I'm not the only very annoyed customer.
Did they not do any testing prior to rollout?
They had a great product and the only thing they had to do was not break it and the occasional refresh.
Seriously, #Sonos is a study in "How not to tech".

#enshittification, but to what end?

Normally there's at least a business case.

Like many other technologists, I gave my time and expertise for free to #StackOverflow because the content was licensed CC-BY-SA - meaning that it was a public good. It brought me joy to help people figure out why their #ASR code wasn't working, or assist with a #CUDA bug.

Now that a deal has been struck with #OpenAI to scrape all the questions and answers in Stack Overflow, to train #GenerativeAI models, like #LLMs, without attribution to authors (as required under the CC-BY-SA license under which Stack Overflow content is licensed), to be sold back to us (the SA clause requires derivative works to be shared under the same license), I have issued a Data Deletion request to Stack Overflow to disassociate my username from my Stack Overflow username, and am closing my account, just like I did with Reddit, Inc.

https://policies.stackoverflow.co/data-request/

The data I helped create is going to be bundled in an #LLM and sold back to me.

In a single move, Stack Overflow has alienated its community - which is also its main source of competitive advantage, in exchange for token lucre.

Stack Exchange, Stack Overflow's former instantiation, used to fulfill a psychological contract - help others out when you can, for the expectation that others may in turn assist you in the future. Now it's not an exchange, it's #enshittification.

Programmers now join artists and copywriters, whose works have been snaffled up to create #GenAI solutions.

The silver lining I see is that once OpenAI creates LLMs that generate code - like Microsoft has done with Copilot on GitHub - where will they go to get help with the bugs that the generative AI models introduce, particularly, given the recent GitClear report, of the "downward pressure on code quality" caused by these tools?

While this is just one more example of #enshittification, it's also a salient lesson for #DevRel folks - if your community is your source of advantage, don't upset them.

Neue groß angekündigte #Sonos App ist da und sie ist ein Paradebeispiel an #enshittification

Meine lokal angelegten Icecast/HLS-Streams sind in der App nicht mehr zugreifbar (altes TuneIn-Plugin in dem die konfigurierbar waren ist weg). 🤡
Das neue TuneIn-Radiostreaming-Plugin verlangt einen Cloud-Account bei Tunein.

Ich kann auf meine über Navidrome/Bonob angeschlossenen lokalen Musikserver nicht mehr zugreifen. 🤡

personally, I'll boycott the #Enshittification and refuse to buy a #GPTmouse and anything with a #CopilotKey as a matter of principle!

Just like I refuse to buy stuff without #toolfree remove- and #swappable #batteries...

#WhatYouAllowIsWhatWillContinue

The Man Who Killed #Google #Search.

This guy is taking no prisoners. Even though we all have a good intuitive sense as to why Google has gone to shit, there has been something slippery about it. This article makes it all more concrete.

https://www.wheresyoured.at/the-men-who-killed-google/

#enshittification #SmallWeb #web

The Man Who Killed Google Search

This is the story of how Google Search died, and the people responsible for killing it. The story begins on February 5th 2019, when Ben Gomes, Google’s head of search, had a problem.

^{Edward Zitron (Ed Zitron's Where's Your Ed At)}

• Ja, konstant geblieben (12%, 1 vote)
• Ja, hat zugenommen (37%, 3 votes)
• Ja, hat abgenommen (12%, 1 vote)
• Nein, gar nicht (mehr) (37%, 3 votes)

offf, this story about how Google made google search into a pile of seagull shit hits me hard:

https://www.wheresyoured.at/the-men-who-killed-google/
Around the time of this story, I was living through a similar situation in my work life (on a much smaller scope, of course, WordPress.com first, Tumblr later).

Back in 2019, working on WordPress, I started finding myself, almost weekly, arguing against people who wanted to take the product we were working at and made it worse if that mean they could squeeze 0.1% more revenue from it

The 0.1% figure is not even a random number: I remember this speciffic A/B test on WordPress.com that was declared a success and shipped to 100% of the users because it increased the free-to-paid conversion by 0.1%. Soon after it was released, I found out that as a side effect, it increased the churn of free users by 20 something %,so I called for an urgent rollback and removal of the change. So I was promptly explained that we didn't care about free-users churn, because finance had calculated the average long-term value of the free users to be something like $2 per year, and the increase in conversion was bigger than what we could get from them.

Everything became about growth hacking. Everything became thinly-veiled dark patterns. In our private dev slack channels, we joked that since it was impossible to make it smaller or less conspicuous, the next thing the growth team was going to ask us to do was to make the 'free plan' button flee away from the mouse pointer when the user tried to click it. We kept making our product worse, we kept consciously crippling the cheaper versions so we could force people to move to the more expensive options.

Back then I was the lead of one of the two dev divisions working on WordPress.com, so my job was mainly to discuss what we were going to be doing, when and how. And I was getting drained by a constant state of fight against a constant wave of shit they wanted us to build. So much than by the end of 2020, the CEO quietly told me to follow the growth team plans and shut up or step down.

So I requested to move to tumblr, because I thought the pastures were greener over there. But it was all the same: Adding login walls to what we were pretending to be "the last bastion of the free internet", cramping in embarrasingly obvious money-making schemes disguised as features, and making them silently opt-out instead of opt-in so the less people the possible would deactivate them, having to fend off the pressure from the CEO to make everything algorithmic timelines because, you know, tiktok makes a lot of money and why aren't we, etc etc.

I found myself in a place where building something good that people enjoy using was no longer a priority, but tricking people into generating more money for the company was. And when I looked around me, I could see that happening everywhere else, not only in my company. Experiencing the start of the enshittification years from inside wasn't easy.

And, as in the article, the people who decided to turn the shit-metter up to 200%, have a name, in every case. And these people, no matter if they are called Sundar and Prabhakar or Matt and Mark, are destroying the internet. These people are milllionaires, or billionaries, and are destroying our shared, common spaces to squeeze some extra cash from us.

That's why the fediverse and its principles are important. Because that's how we take back internet from their dirty hands. That's how we make internet resilient against them. That's how we build the commons.

The Man Who Killed Google Search

This is the story of how Google Search died, and the people responsible for killing it. The story begins on February 5th 2019, when Ben Gomes, Google’s head of search, had a problem.

^{Edward Zitron (Ed Zitron's Where's Your Ed At)}

🧠 Boost if you wish investors and marketers would start investing money into HI (Human Intelligence) again.

#HI #HumanIntelligence #AI #ArtificialIntelligence #enshittification

"But SEO is just giving people what they want!"

False.

Patient zero: if I search the web for a phone number, what I *want* is to know whose phone number it is.

The top results should be pages that contain that phone number and information about what person or business it belongs to (including, if it's a business, their own web site).

What I don't want—what NOBODY wants—are spammy, scammy, for-pay reverse phone lookup companies.

#SearchIsDead #enshittification #SEO

1. Find information that already exists for free (or that is extremely cheap to get)*.

2. Either put it behind a paywall or wrap it in ads until it is virtually unusable (or both).

3. Find a way to increase the search ranking of your version.

This is not a business model, this is ruining the web for money.

* ~ Also, some aren't even doing this (e.g., like a reverse phone lookup service that PRETENDS to have data it doesn't).

#SearchIsDead #enshittification #SEO

#Google is turning #GMail from an Email provider into a website.
No more access via standard email protocols such as #IMAP and #POP

The final stage of #enshittification . Locking the users in.

I wonder how they want to get rid of SMTP as stated in the support posting.
I guess this means outgoing SMTP to forward mail to a real email server.

I guess without relaying I won't ever receive any notifications Google services send to me again as I don't use the Gmail website.
I host my own Email server for many years, thank you.

Timeline for transition

Summer of 2024:

If you (or your users) try to connect to a less secure app for the first time, you will not be able to. This restriction includes third-party apps that still use basic authentication, such as CalDAV, CardDAV, IMAP, SMTP, and POP, to access Gmail, Google Calendar, and Contacts. If you’re not trying to connect for the first time, you will be able to continue using the apps until they’re turned off.
In the Google Admin console, you will not be able to access the turn on and off setting for less secure apps.
Users will not be able to turn IMAP on or off in their Gmail settings.

https://support.google.com/a/answer/14114704?hl=en&sjid=8073259250606890309-EU

I admit that I feel salty about the word “enshittification” taking off instead of my phrase for the same thing: “user domestication”. I prefer the latter because it emphasizes the gross disrespect so many platforms show their users, and how the lack of autonomy/mobility naturally leads to enshittification.

Any platform able to get away with enshittification will do so when given the incentive. Enshittification emphasizes the process of a platform’s downfall; we should be taking steps to prevent that from happening in the first place by keeping platforms open. Vigilance against enshittification is misplaced when better spent against user domestication.

Originally posted on https://seirdy.one/notes/2024/01/11/enshittification-and-user-domestication/ (POSSE). #enshittification #UserDomestication

Enshittification and user domestication

I admit that I feel salty about the word “enshittification” taking off instead of my phrase for the same thing: “user domestication”. I prefer the latter

^{Seirdy’s Home}

Youtube's tantrum escalates.

Forced to concede that they cannot outpace ad blocking extensions, parent company Google artificially limits the rate of extension updates in Chrome.

No justification for the user experience is given, and in fact this makes chrome users more vulnerable to attacks injected via ads.

#tech #news #enshittification

https://arstechnica.com/google/2023/12/chromes-next-weapon-in-the-war-on-ad-blockers-slower-extension-updates/

Chrome’s next weapon in the War on Ad Blockers: Slower extension updates

When ad blocking is a cat-and-mouse game, make the mouse slower.

^{Ars Technica}

1. Read this:

“Just as GitHub was founded on Git, today we are re-founded on Copilot.”

https://github.blog/2023-11-08-universe-2023-copilot-transforms-github-into-the-ai-powered-developer-platform/

2. Go here:

https://codeberg.org/

#git #gitHub #codeberg #enshittification #BigTech #cooperative #dev

Universe 2023: Copilot transforms GitHub into the AI-powered developer platform - The GitHub Blog

GitHub is announcing general availability of GitHub Copilot Chat and previews of the new GitHub Copilot Enterprise offering, new AI-powered security features, and the GitHub Copilot Partner Program.

^{Thomas Dohmke (The GitHub Blog)}