ivn

J'avais pas vu de contrepoints depuis que j'ai quitté reddit, bas ça m'avais pas manqué.

What's the game?

My next phone is definitely going to be a Pixel for this reason. But my current one is not even 6 years old so I'll wait a bit.

It has some deal breaking limitations:

• No filter list that can be updated, you have to update the whole extension to update filters. This adds delay as it has to go through Google verification process, they could even refuse some updates.
• Not every type of rules are available on MV3, so it has to drop some filters.
• No CNAME-uncloacking.

T’as essayé de lire le flux direct ?

Du genre : mpv https://www.france.tv/france-2/direct.html.

Protaigez-vous

While the code being open is good you still have to rely on trust.

I certainly don't have the time to review to code of each extension I use. And even then, we have no garanties that the extension distributed through the browser stores has the same code.

You can see the issue was opened on august 18th but the responsible commit was only made on the 19th. So the code was pushed the extension users before it was made available on the repository. Open code is of no help here.

Here's what the video is based on: https://signal.org/bigbrother/cd-california-grand-jury/

I get not watching the video, I didn't, but why reply then? It's obvious you would be off the mark. Also, sometimes the description is enough to get what a video is about, here it was.

It just showed the developer is not to be trusted.

This seems sketchy : https://github.com/brookhong/Surfingkeys/issues/1796

I agree, there are a bunch of annoying limitations. But it's better than nothing. To me the best vim based browser is qutebrowser, too bad it's using chromium.

I don't think it's the same source code (uBOL vs uBO). And it's definitely not the same logic, that's the whole point, blocking with MV3 must be done in a declarative way.