You are right, my bad, last change seems to be a year ago.
You are right, my bad, last change seems to be a year ago.
But uBlock Origin does not set update_url
in it’s manifest.json
so it won’t update automatically. You’d have to do it manually every time.
It’s really standard to leave some time for users to adapt when making a big change. Especially end users. It’s actually a good thing, the “friend showing up” analogy makes no sense.
End of support for users is June 2024.
But it did seem to have changed a year ago or so, my bad.
But if the extension is removed from the store you will not get updates.
I don’t get it, the timeline has been known since 2021 and has not changed. We are in the middle of the phase-out. All of this is really predictable.
https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline
For system wide DNS blocking you only have two options: use a DNS server with blocking (either your own with something like a piHole our a public one) or use the hosts file.
Depends on the country you’re in.
without being pwned
How do you know?
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:
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.
It just showed the developer is not to be trusted.
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.
How does it compare to tridactyl?
You are right that there are underlying causes that needs to be addressed. That’s why it spread so much and so fast. But that doesn’t make racially motivated fake news OK.
But this seems easy to automatically block, no? If a client is querying an unknown domain check for some Matrix related data in /.well-known/
and add it to the block list if there is. And since the servers are publicly advertising the port used you just need to periodically check the list of known matrix domains you are creating in the first step.
Russia is already doing DPI and blocking ESNI so that seems easy. A more widespread usage of ECH would help everyone, as is Signal advocating, but that’s not the case yet.
But no one is saying that a single tweet started all this.
It’s a good thing to be able to communicate without sarcasms when it’s not called for.
But I don’t think it’ll change, feel free to try and make a PR but you’ll also need to setup a server to host the releases and
update.xml
.