this post was submitted on 19 Dec 2025
652 points (97.9% liked)

Microblog Memes

9916 readers
2827 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

Rules:

  1. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Senal@programming.dev 1 points 5 hours ago (1 children)
[–] BananaIsABerry@lemmy.zip -2 points 5 hours ago (1 children)

Hard disagree. In no way are you being forced to interact with any of this.

[–] Senal@programming.dev 1 points 2 hours ago (1 children)

TL;DR;

On by default is exactly what forcing interaction looks like.

There are many effects regardless of whether or not you interact with the features directly.


Disagreeing vehemently doesn't make you correct.

Some of these things are on by default, that's the very definition of forcing an interaction, even if it's just to hunt through the settings to turn it off.

Regardless, just don’t interact with the AI stuff and you won’t even know the difference.

It's so close to the same energy it's even parroting the same kind of "make absolute statements without understanding the realities of the subject" mindset.


Let's start with some basics.

  • At least some of these features are on by default so from the get go you are already being affected, even if it's just a minor annoyance.
    • You need go out of your way to turn them all off (and keep on top of new additions, again, some of which are on by default).
    • They are also regularly "reset" during upgrades
  • Assuming you're a regular user and don't religiously go turning all of these features off at the root, some of them will be part of interacting with the daily usage of the browser, incurring a performance cost.
    • Right click context actions are a good example of this, as is AI tab grouping and the planned Link Preview (though the latter currently needs a key press to activate)
    • Even if you never use the tab grouping, the analysis of what's needed to suggest things is still a performance cost, possible a non-trivial one.
  • Any new code or feature added to the browser contributes to bug and maintenance surface area, meaning resources used to develop, test and maintain that code.
    • This is resource not being used on other, non AI, bugs and features.
    • Project management is complicated so it isn't a one-to-one ratio of resources from one thing to another, but it's still a non-zero percentage.

Now for the slightly more esoteric

  • LLM's as a whole are provably bad for the environment, power grids and water supplies , that's both the running and the model generation
    • People might not care about this, but not caring doesn't negate negative impacts in this case.
    • Some might consider the tradeoff to be worth it, that's fine, still affected by it though.

I'm not arguing for or against LLM features (though for the record i'm not a fan of them being auto-included) i'm saying that your statement about not being affected if you don't use them is incorrect.

[–] BananaIsABerry@lemmy.zip 1 points 19 minutes ago

Remember what I said about being over dramatic?