Pretty sure the answer is: Yes, since I believe it’s part of the open source project chromium, it would be under the same open source license.
Pretty sure the answer is: Yes, since I believe it’s part of the open source project chromium, it would be under the same open source license.
There’s a post here saying it’s down but no updates: https://very.bignutty.xyz/notes/9hek2yioxnuw9f15
You can learn how to make a donut: https://youtu.be/nIoXOplUvAw
Using their own new protocol that no one else uses and they probably don’t even implement themselves yet.
lol thanks for the correction
Edit: looks like this is wrong lol, that’s what I get for not verifying. So maybe $ does make more sense!
Original message:
I think I’d go with #.
The non-root user probably doesn’t have permission to run the sudo command as www-data user, but root does.
Unless you previously set permissions for the non-root user to sudo as www-data.
The problem with that is you can’t unblock what your instance blocks/defederates from.
They have an integration with container tabs, I’ve only used it once but imagine it could be handy: https://support.mozilla.org/en-US/kb/use-multi-account-containers-mozilla-vpn
You wouldn’t download a car, would you?
I don’t think this blocks all cookies, but instead disables all non-essential cookies in those cookie consent dialogs
I don’t have any prior knowledge about it but it looks pretty invasive, I found this interesting article about it:
And this Firefox extension to block sites from scanning local ports:
That’s a fair point but it looks like it is in chromium.