Technology

59396 readers

2618 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

Let's talk about Google Chrome and ads, and getting around Google's ad enforcing tactics (manifestv3) (lemmy.cafe)

submitted 4 months ago by [email protected] to c/technology

26 comments fedilink hide all child comments

Google has been blocking adblockers, or atleast trying to for some time now. Notably on Youtube.

I barely feel the impact of this because I use Mastodon, Lemmy, Peertube and other services that don't have ads.

Unlike your traditional website, these services federate, with each other over this Fediverse thing we all know about.

What's good about this is if, some severs wants to be greedy against it's users, users can easily just change servers and not have to worry about losing familiarity with the platforms user interfaces that they grew accustomed to.

Legally the largest Mastodon, Peertube servers and other can't do anything to smaller servers as the software used for the Fediverse platforms, generally are open source and federated with each other with help from activity pub which is also open source.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 67 points 4 months ago (1 children)

Just don't use Google Chrome. I only use it for one system at work and I blame Microsoft for that not working well with Firefox.

[–] ConstipatedWatson 4 points 4 months ago* (last edited 4 months ago) (5 children)

Well, you're right in principle, but with my (old, but current) Mac+Intel configuration Firefox is not as sleek as Chrome and also often Firefox turns the fan on while Chrome doesn't (it may just be that Google is bricking Firefox when you're on YouTube, for example)

Anyhow, I'm trying to use Firefox as much as I can (I've always done so), but it's always been true it was a better experience to use Chrome on my setup (and I've never used Safari)

Edit: why the downvotes? To teach me a lesson? I said he's right, but I do have an actual problem and cannot yet make the full move (and am going to check out the suggestions below. Thanks!)

[–] mrvictory1 9 points 4 months ago (1 children)

Firefox turns the fan on while Chrome doesn’t

Does this happen on YT? Enable hw acceleration and install enhanced h264ify.

[–] ConstipatedWatson 1 points 4 months ago (1 children)

I finally had a minute to try it out and unfortunately it does not seem to change anything on my 2020 Mac+Intel (the GPU load skyrockets when I watch videos on YouTube)

[–] mrvictory1 1 points 4 months ago* (last edited 4 months ago)

GPU load should increase when watching videos, even if hardware acceleration is enabled. In about:config, set media.hardware-video-decoding.force-enabled as true and restart firefox. Additional stuff may be needed for Mac which I don't know.

[–] INeedMana 7 points 4 months ago

Firefox turns the fan on while Chrome doesn’t

Does it also happen when you change user-agent to chrome? Google has been worsening the experience of their services on non-Chrome browsers for a solid few years now

[–] [email protected] 6 points 4 months ago

You could try Librewolf or possibly even Floorp, if baseline firefox doesn't do it for you.

[–] [email protected] 4 points 4 months ago* (last edited 4 months ago)

Have you considered Orion? It has the sleekness of Safari (and based on WebKit) but gives you plug-ins from Chrome and Mozilla. I love it because it doesn’t have the non-native clunkiness of other browsers.

[–] [email protected] 2 points 4 months ago

With the fan turning on, unfortunately it's potentially due to Firefox being a little more resource heavy. Could be Chromium is a bit under the threshold and Firefox is a little over.