this post was submitted on 24 Oct 2024
37 points (100.0% liked)

Technology

37686 readers
326 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] FurtiveFugitive@lemm.ee 3 points 5 days ago (2 children)

How would you say it's a turd? I assume because it's still chromium based, but I don't want to put words in your mouth.

It's my browser of choice for my work computer but I do run Firefox at home and on mobile.

[–] Corgana@startrek.website 3 points 5 days ago (1 children)

Yeah, chromium based means adblockers cannot work as effectively.

[–] azdalen@beehaw.org 4 points 5 days ago* (last edited 5 days ago) (1 children)

which is why vivaldi purposefully added a blocker engine into the browser to side-step the extension limitations. It includes some default lists, as well as allows you to add your own with support for ublock, adguard, and ABP syntax and scriptlets. then all you need to do is goto https://github.com/uBlockOrigin/uAssets and add whatever offical asset lists you want... is it as good as FF + uBO, no, but it is something.

[–] Corgana@startrek.website 1 points 5 days ago

I found a Vivaldi blog post on this topic from 2022: https://vivaldi.com/blog/manifest-v3-webrequest-and-ad-blockers/

Will the Vivaldi Ad Blocker be affected by the Manifest V3 changes?

I made some architectural choices early on that I believe should keep it functional, regardless of the Manifest V3 changes. Of course, there is always a possibility that the underlying Chromium architecture will change now or in the future, forcing us to do some extra work to keep this working. ​> Hopefully, a more in-depth description of the architecture and some of the facts surrounding the Manifest V3 changes should help to show why I believe that our implementation is safe for the time being.

[–] fine_sandy_bottom@lemmy.federate.cc 2 points 5 days ago (1 children)

There's a popular phrase "you can't polish a turd". The meaning in this case being that if you put a nice UI on chromium it's still chromium.

[–] FurtiveFugitive@lemm.ee 2 points 5 days ago (1 children)

I am familiar with the phrase. And I was correct assuming you were referring to chromium as the culprit.

In case anyone didn't know, you actually can polish a turd.

https://youtu.be/yiJ9fy1qSFI

I'm not going to watch a video about polishing a turd but I assume the turd remains a turd.

You'll not I didn't actually make the claim that its not possible.