I've played for many hours and I think they nailed a lot of the mechanics, so the game is fun.
I'm not even sure what you're trying to say, what does the year have to do with anything? It's 2024 and not 2014, and therefore I should only play modern shitty live service games?
No one is pretending anything, and no one is claiming these laws aren't specifically targeting trans people, of course they are. What they are claiming is that the same law would apply to what is being depicted in the photo, which is true.
There is no NDA for Deadlock, and anyone in it can invite anyone they want, as often as they want. It's not like Valve has no idea how to privately test their game. I think they made these decisions deliberately.
Honestly, I think Valve is just kind of doing a soft release/announcement and are trying to build up hype slowly like this. If they were really worried about leaks they wouldn't have given anybody in it unlimited free invites to send to anyone.
It's not too daunting. It has the same guide system as dota so you can just pick a build someone else made and follow it to learn them. It also has a lot of voice lines to help with reacting to item effects, like the item with an active that makes you invulnerable to bullets makes heroes say a "I can't shoot them" or "don't waste your ammo" voice line.
If you're not completely giving up on privacy I would avoid cloudflare. I just run an always-on wireguard tunnel that routes back to my home network from my wife's and my phones, and that kills like 3 birds with one stone (phone traffic is encrypted and hidden from my carrier, home server is accessible, and ads are blocked via DNS).
I'd just install UFW and either set the default for incoming and outgoing to deny and unblock the game ports manually, or just set incoming to deny and outgoing to allow.
You could pair that with OpenSnitch to see all attempted incoming and outgoing connections and block them by default, and then just allow the ones you want as they happen.
I use notifications in Thunder and I've had no issues. I haven't compared the difference or anything, but when I've happened to check battery usage it's always been a reasonable amount for how much I've used it that day. It does generate a decent amount of network traffic since it's regularly checking with you instance for it, and that traffic is generated for each account you have reaching out to each instance. That should be how any FOSS app works though, the alternative would be something like Sync where you pay to have actual pushes sent from their server.
I think I'm one of the very few people that actually like this game. I bought it when it came out and have played it a few times. This is all very valid criticism of it though.
My theory is that the RTSP port (554) is for streaming and that when I go to the local address (that is on 80), the site ITSELF initiates a connection to port 554 in the background. However, this apparently does not happen when I connect remotely.
I think you're on the right track here. The DVR is probably telling your browser to connect to http://192.168.1.222:554 for the stream, which on LAN is fine because you have a route to 192.168.1.222, but when connecting externally you won't be able to get to 192.168.1.222.
You can probably check the network connections in dev tools in the browser to confirm that.
Edit: Editing this to also stress the importance of the advice given by @SteveTech@programming.dev. My home cameras are also only accessible from outside my network via wireguard.
I've played for many hours and I think they nailed a lot of the mechanics, so the game is fun.
I'm not even sure what you're trying to say, what does the year have to do with anything? It's 2024 and not 2014, and therefore I should only play modern shitty live service games?