Look, I’m extrapolating from the general rule to the specific case of torrenting.

The general rule is that, because the IP protocol requires numerical addresses to connect to a remote machine, if what you have is a site name you have to translate that name into a numerical address before you can actually establish a connection, and a DNS query is how you translate site names into their numerical IP addresses.

Now, if you look at the contents of a tracker, what you see are not numerical addresses but site names, so those must be translated into numerical addresses before your client can connect to those trackers, hence DNS queries are done to do that translation.

Meanwhile, if you look at the “peers” section in an active torrent in your torrenting program, you see that they all have numerical IP addresses, not site names. This makes sense for two reasons:

• Most of those machines are user machines, and usually users don’t just buy a domain to have site names for the machines they used only as clients (i.e. browsing, torrenting and so on) since that is not at all needed. Site names are required for machines which serve stuff (literally, “server machines”, such as machines hosting websites) to arbitrary clients that by their own initiative connect to that machine - they’re meant as a human readable memorable alias for the numerical IP address of a machine, which people can enter in appropriate fields of client applications to connect to that site (i.e. putting “lemmy.dbzer0.com” in your browser rather than having to remember that its IP address is “51.77.203.116”)
• As I said, IP connections require IP numerical addresses to be established. For performance reasons it makes sense that in the torrent protocol the information exchanged about peers and between peers is always and only the machine’s numerical IP address since with those there is no need to do the additional step which is the DNS query before they can be used by the networking layer to open TCP/IP or UDP/IP connections to those peers.

Hence my conclusion is that the torrenting protocol itself will only deal with site names (which require DNS queries before network connections can be made to them) for the entrance into the protocol (i.e. start up and connect to trackers) and then deal with everything else using numerical IP addresses only, both because almost no peer will actually have a site name and because it’s low performance and doesn’t make sense to get site names from peers and have to resolve those into numerical addresses when then peer itself already knows its numerical address and can directly provide it. Certainly that’s how I would design it.

Now, since I didn’t actually read the protocol or logged the network connections in a machine torrenting to see what’s going one, I’m not absolutely certain there are now DNS queries at all after the initial resolution of the trackers of a torrent. I am however confident that it is so because that makes sense from a programming point of view.

Well, if the trackers are specified as names (and a quick peek at some random torrent shows that most if not all all), those do have to be resolved to IP adresses and if that DNS query is happening outside the VPN then your ISP as well as the DNS server being queried can see you’re interest in those names (and it wouldn’t be hard to determine with a high probability that you are indeed torrenting something, though WHAT you are torrenting can’t really be determined by you merely accessing certain servers which have torrent trackers active, unless a specific server only tracks a single torrent, which would be pretty weird).

Things like peers aren’t DNS resolved since they already come as IP adresses.

So when it comes to torrenting as far as I know all that the DNS can leak is the information that you ARE torrenting but not specifically WHAT you are torrenting.

It’s more in things were you’re constantly doing DNS queries, such as browsing, that DNS leaking can endanger you privacy: if for example somebody is going to “hotsheepbestialityporn.com”, somebody at their ISP could determine that person’s very specific sexual tastes from seeing the DNS queries for hotsheepbestialityporn.com coming in the open from their connection.

It might be a DNS problem.

I vaguely remember that Mullvad has a setting to make sure that DNS queries go via the VPN but maybe that’s not enabled in your environment?!

Another possibility is that Mullvad going down and then back up along with your physical connection when your ISP forces a renewal of the DHCP is somehow crapping up the DNS client on your side.

If you have the numerical IP address of a site, you can try and access the site by name in your browser when you have problems in the morning and then try it by nunerical IP address - if it doesn’t work by name but it does by numerical IP it’s probably a DNS issue.

PS: you can just run the “ping” command from the command line to see if your machinr can reach a remote machine (i.e. “ping lemmy.dbzer0.com”) and don’t need to use a browser (in fact for checking if you can reach machines without a webserver, the browser won’t work but the ping command will).

Even if Mullvad did erroneously allow applications to access your physical network connection for a moment, because you bound qbittorrent explicitly to the network device of the Mullvad VPN, qbittorrent will never use the physical connection.

You can check this out easily by disconnecting Mullvad and trying to torrent something on qbittorrent and also browsing the Net: you’ll notice the browser gets through just fine but qbittorrent will not.

Mullvad leaking would be a problem if what you’re worried about is loss of privacy or government surveillance, not for torrenting if your torrent server is correctly bound to the VPN device.

You can configure launchers such as Lutris to run your games inside a proper sandboxing application such as “firejail”.

Just look into “Command Prefix” under Global Options in Lutris: a sandboxing app like firejail is used by really just running the sandbox app with the original command as a parameter of it, so that means you “prefix” the original command with the sandbox app and its parameters.

You can go as crazy as you want if you do sandboxing like that (down to only allowing access to whitelisted directories). In my case I’ve actually limited networking inside the sandbox to localhost-only.

I’m running the games in Linux, using Lutris as a launcher with a default configuration that wraps them in a firejail sandbox (for anybody interested, you add firejail as the “command prefix” under Global Options or in the System Options of the game) which amongst other things blocks networking.

In fact I went and figure out how to do all that exactly because I wanted to run pirated games in Linux in a safe way and you can’t just rely on the lower probability of Windows games of having code that tries to determine if it’s being run with Wine and accesses Linux-specific functionality and files if it is.

PS: That firejail stuff also works for Linux native games (it just wraps whatever you’re running to start the game, be it Wine or directly the game Linux binary).

You can keep on seeding after downloading and your torrenting program will still manage to upload to any member of the swarm for that torrent that it connected to (even if only to check their status) during the download phase.

This should be enough to get you consistently above a 1:1 upload to download ratio for any popular public torrents, though for those with very few leechers you might never get there.

The lack of port forwarding is only a problem for remote machines your program has not connected to during the current session for a torrent (i.e. not yet seen machines that try to connect to your client), which means you can’t seed at all in a purely for seeding session or upload to machines that joined the swarm after your download was done in a mixed session.

If your pattern of usage is that of mainly a downloader of public torrents who tries to give back to the communy at least as much as they took and whose not mainly into obscure stuff, it works fine.

It massively depends on the country - it’s probably fine in Southern and Eastern Europe but not for example in Germany were if I’m not mistaken copyright violation is even part of Criminal Law rather than Civil Law as in pretty much the rest of the World.

Personally ever since I lived in the UK - which has the most insane levels of civil society surveillance in Europe, including of Internet usage - I got into the habit of doing pretty much everything behind a VPN, which also helps with peace of mind for the whole torreting thing no matter which country I’m living in at the moment, plus I pay 5 euros a month for the VPN which is less than a single streaming service, so in a way it pays itself (it’s funny how piracy compensates for the costs of protecting myself from dragnet surveillance).

Bullshit!

The tariffs on the tools required for the mandatory cock and ball torture would be set higher than for everything else imaginable.

As somebody from a poor EU country with good weather - Portugal - if Albania is anything like here, it’s a great place to live as long as your income is at the level of somewhere else.

The problem is to live in such a place with the level of salary of such a place.

A lot more humane, though, as the flies get upright much more easilly than the cows.

Gruesomely mass murdering civilians using bombs to get the rest to comply with your will is only “Terrorism” if the bombs were placed on the ground and then exploded, not when they were dropped from the air.

Hence the smaller per-capita representation of white people in the count of terrorists.

Same here.

In my transition from Windows to Linux on my main machine, one of the more funny discoveries I made was that for many older Windows games, Linux with Wine has better backwards compatibility than Windows.

That’s also my experience: there’s a certain generation of games, around 10 - 20 years old which have more likelihood of problems running in Linux than both older games and newer games.

I suspect it’s partly to do with the kind of DRM used by AAA publishers back then - for example the Steam Windows version of The Sims 3 will simply not work in Linux but a pirated version will work fine with no tweakings needed whilst other AAA games from that era need a lot of tweaking to get to work in Linux.

Meanwhile the most recent stuff just works with no need for tweaking.

I run my pirated games in Linux sandboxed using firejail (Wine itself doesn’t sandbox anything as it’s only an adaptor layer) configured to block a lot of things including network access.

Then again I also run my non-pirated games in Linux in the same way.

I can log into my GOG account with Lutris and it will NOT auto-update my games but rather works as a pull-only manager, which I prefer since over 2 decades in Software Engineering have taught me that shit getting updated at the convenience of a 3rd party is a great way to randomly and for no good reason have stuff that works stop working. Even in Windows I refused to use GOG Galaxy for exactly that reason and kept downloading offline installers (and that’s also part of the reason I favored GOG over Steam). You could say it’s a professional quirk 😀

I’m definitely one of those people who swears by Lutris and even went to the trouble of figuring out how to run games from it automatically sandboxed and have mine configured to run them with Firejail set for, amongst other things, no network access (it looked into it because I wanted to make sure any pirated game wouldn’t hack my system, but it also works well to stop official versions of games from doing any funny business - mainly privacy invasive stuff - so I have it set up as default for all games).

I too was holding back from having Linux as my main by the lack of availability of games that would run on Linux - and I’ve been playing around with Linux and even using it professionally since the early 90s - so I’m very happy with how this transition from Windows to Linux turned out for me and, like you, almost all of the games that I know won’t work are games I don’t have interest in playing anyway (mainly because the Online Multiplayer experience for AAA games nowadays is horrible even when compared to the 2000s and early 2010s, worse compared to LAN gaming in the 90s).

Well, my Steam collection isn’t all that big (I mostly buy from GoG) plus I’ve only changed to Linux about 6 months ago, so out of the 6 Steam games I have tried so far in Linux, only for 1 (The Sims3, an EA game from 2009) has it failed to run from Steam whilst a pirated version ran perfectly fine with Lutris and Wine.

If I remember it correctly since the very beginning this game was problematic even in Windows because of its excessive DRM and if you look at ProtonDB, most recent experiences reported with the Sims 3 are either negative or problematic.

I’ve tweaked a lot of problematic games to get them to run in Linux (mainly GoG games with Wine and Lutris, though in addition to the Sims 3, one of the other 6 Steam games I’ve tried require tweaking in Steam, which for that one worked and I got it to run) plus I know enough about tweaking Wine to get pirated games to run in Lutris (Lutris doesn’t have install scripts for downloaded “releases” like that, so they often requires tracking in the logs the missing DLLs and figuring out what to install with Winetricks or even if the problem requires forcing use of the native DLL in WINEDLLOVERRIDES) so it’s not as if by now I’m devoid of experience at tweaking that stuff.

In summary, my total rate for problems running Steam games under Linux is 33.3%, half of which I could solve with tweaking and half I could not, though it’s a pretty small sample so the error margin is large.

For comparison sake, with Wine and Lutris out of maybe 20 games, looking at my notes - because I write the tweaks down for future reference - 5 required tweaking (so around 25%) and only for 1 of those (10% off the total) I failed to get it to run properly.

Compared to the last time I tried gaming on Linux (maybe a decade ago), it’s incredibly good.

In some cases my 0 minutes played are because I bought it in Steam but had to go get a pirate version to play it in Linux (via Lutris and Wine rather than Steam and Proton) since the Steam version didn’t work in Linux but the pirate one did (probably something to do with the game’s own DRM, which in the pirate version has been cracked)

Which, IMHO, is more sad than just buying a game because it’s cheap and never actually getting around to playing it.

This is the Wine side of it, changing it to use that feature which is now in the Kernel.

Acting techniques improved massively during the XXth century, so stuff that relies on that (basically anything but slapstick Comedy and mindless Action) will feel less believable, which impacts mostly things from the 60s and earlier.

Then there are the Production values: the scenarios in early XXth century films were basically Theatre stages whilst more recent stuff can be incredibly realistic (pay attention to the details in things like clothing and the objects and furniture in indoor scenes in period movies) and Sci-Fi benefited massive from the early XXIst century techniques for physically correct 3D rendering and Mocap techniques so there is a disjunction in perceived realism between even the early Star Wars Movies and something like The Mandalorian.