I would make a issue to their guthub if the issue persists: https://github.com/Exodus-Privacy/exodus

Here’s the original article: https://www.svd.se/a/K8nrV4/metas-ai-smart-glasses-and-data-privacy-concerns-workers-say-we-see-everything

Yeah, I would like graphene, if not for the fact that they require me to brimg money into the google echo system…

It’s just the engine, but it’s supposed to be a much more modern and smaller engine, so writing a new browser on top of it would be much easier than using gecko is. But you’re right, it’s not a browser. There is Verso as a prototype browser, but it’s far from functional.

Ublock is added by default to librewolf, unless you installed it in an unconventional way.

When it comes to zen I haven’t really seen a compelling reason for it. I care about privacy more than functionality, but I don’t really want to go about hardening a whole new browser.

I have found that using PWAs with librewolf as the engine is very in lign with my mental image of how to run things.

I don’t know much about ip routing, but userns=keep-id id determined based on what podman is run as. For example, I run podman as user 1000 on the host, so if I do keep-id the user in the container will map to the same id. This often messes with things as the container require it is root inside it’s own context. It seems you are running podman as root, meaning that keep-id will map the container user to the actual root id, givintthe container essentially root access. Normally the container user is mapped to a random id on the host, like 653477, not 0. It’s unsafe to map the containers id to root as they would be unbounded if they managed to escape. I would recommend doing systemctl cat on the different services to see what the .container file expands to.

When it comes to the networking I think that you need to create a podman network with internal set to true. I believe that this restricts internet access. Then you would need to only let these services communicate with gluetun.

I don’t know if this was any help, but it’s all I’ve managed to learn from doing it myself.

Here are some liks I found:
https://lists.podman.io/archives/list/podman@lists.podman.io/thread/NKVFO4JQO5JLYKWXHHODC2WHQRG7A2KO/
https://docs.podman.io/en/v4.6.1/markdown/options/userns.container.html

Blocking a dns request is like removing a phonenumber from a phonebook. You can still call that number, you just need another phonebook to find it.

Why?

This feels way too overkill for me.

Quite the kinky lineup; WiFiAnal, Wetter, QuickDic… 😏

I tried these methods already. It was this stream link that yt-dlp said was drm locked and ffmpeg aaid was malformed. I’ll try the obs method later. Thank you :3

Edit: looking closer I didn’t shorten the url. I might try this later.

Thank you. Screen recording is my next option. I was just hoping for a more efficient method :P

I have no idea, but I would guess that’s Microsoft’s doing.

I feel like that’s way too easy to accidentally flip.

My confusion is more that that quote doesn’t confirm that they are trying to mimic QUIC traffic, only that they use udp with http.

If I understand it correctly, it masks that its vpn traffic by appearing as QUIC traffic (udp under http)?

The only thing I find bad about using blink is that it gives google more power over the consortium. Things are added as a standard when they are widely used, so if google disables jxl functionality, they kill any chance of that becoming the new standard. The bigger the market share of blink is, the more power google has over what other browsers prioritize also.

“Not chrome” … uses blink engine…

Benn is amazing. I’ll need to watch this later.

This is from their site:

We currently sell in European Union, UK, Norway and Switzerland.
Please be welcome to use our products anywhere in the world, however due to our limited resources we can only support the noted regions.