Whatever else you do, homelabbing and/or coding on private projects on the side will do you well. Try to go small. Holds at literally any level.

Sounds like clients could do a better job in merging cross-posts and making it easier to filter them from the view.

Been digging into the Tor Browser codebase recently and as a consequence now lifting over a few goodies in the privacy and security departments from there to Konform Browser

Maybe you already figured this out but I think it’s a common gotcha:

Wireguard AllowedIPs means just that: IP addresses that are allowed to be routed over the tunnel.

There is nothing that says that you need to have 1-to-1 mapping between that and actual routes. Most of the time it’s what you want but there are situations where you want it different. Some people have a wider subnet for AllowedIPs but only add certain routes specifically.

wg-quick additionally adds corresponding ip routes as a convenience. systemd-networkd did at some point but don’t anymore. I’m not sure what NetworkManager’s Wireguard plugin is even supposed to be doing there these days. Most of the time what looks broken is actually a result of unclear documentation and a mismatch in assumptions between dev and user.

It’s an understandable source of confusion and the tools don’t always help when they try to.

Just to be clear, most of these (think about egrep/fgrep for a moment) are deprecated and “shouldn’t be used” in scripts for distribution. What’s new is that you can’t expect everyone else to have them and having dependency on them in shipped software is considered antipattern.

Nobody gives a shit what aliases and shims you use in your own shell.

On iptables: By now it’s even gone from kernel and the turn tabled with the cli command now actually being a shim calling into its successor nft. IMO nft is much more approachable for beginners to pick up and the rules files become so much more readable and maintainable. If you’re already committed to iptables syntax then cool - but with very few exceptions I don’t think anyone needs to learn iptables today - just go straight to nft and you’ll be happier for it. Similar for ifconfig.

ip -br a, even

Oh actually I wouldn’t know - maybe it’s one of those funny crossovers! Will have to remember asking about it next time I meet my Brazilian friend. If it works for you then why not ^^

master( ͡° ͜ʖ ͡°)main

still pissed the name is not inspired on a canine/lupine

I kind of want to keep that subtle but it is there :p

Follow-up hint: In Japan they sound different than in Norway

Good to know on the crossposting. And thanks for encouragement! If winds are willing we can also land a patch for this in Tor Browser (and I guess consequentially Mullvad). Only feels fair to try contributing back since we are effectively benefiting from their contributions and if we get reviewing eyes on code in process it’s win-win.

The screenshot in the post is from IronFox.

It’s not, though? Let me guess, it’s from some tool or page doing static analysis on the APK and reporting results? Please include a link or reference to actual source when reporting in the future.

So, Firefox contains a library that can be used for reporting telemetry to Mozilla. When you download Firefox from Mozilla, this is enabled and pointing to Mozilla servers. After reading Privacy Notice shouldn’t be a surprise.

When you install one of the fork that disables telemetry (IronFox, LibreWolf, Konform Browser at least do it this way), they will configure the build such that the endpoints are never called. Mozilla are actually reasonable enough that this is supported, documented, and reasonably straightforward for those bothering to build FF from source.

So yes, when you download IronFox it contains a library that could be used for Mozilla Telemetry. It’s just that it’s never used to do so (assuming no bugs).

A util to make it easier to work with large firefox and thunderbird prefs files https://codeberg.org/konform-browser/diffprefs

It’s Thursday as I reply but I guess it’s Wednesday somewhere in the world (:

Find out for yourself!

https://codeberg.org/dialhome-study/browser-network-insights

Usage details for running locally under “Testing procedure” -> “Basic test environment usage”

Previously posted on this community here: https://lemmy.ca/post/59519788

Assuming you mean the Mullvad extension (which is installed by default in MB) and not the Mullvad VPN app (which also exists but never came close to these machines) :)

That will indeed likely make a difference on Mullvad Browser numbers. However for now I’m not changing the “keep addons at stock defaults” invariant or the test matrix might get really out of hand… Should we disable uBlock Origin in LibreWolf? How about uBO or NoSccript in Mullvad then? Konform Browser loads uBO but only if its apt package is installed; should we do that? What happens when we try to explicitly opt out of everything under Preferences in Firefox? I guess the last one is something to actually consider but for now not touching the addons.

(Would be super cool if anyone else tries this out and reports back though! The compose should hopefully be straight forward and easy to get started with if you are on Linux and have podman available. The report mentions it TL;DR we had to work around the oBO install in LW not properly utilizing the proxy (?) like this and I think same approach could be used to Uninstall Mullvad extension from Mullvad Browser and prevent it from even loading)