I’ve been using it as my primary browser on Android for years so I don’t really have much to compare it to, but I haven’t had any issues with extension compatibility. It includes changes from Tor browser and Arkenfox so it’s more privacy-focused than on performance.

I’ll just throw out Mull from DivestOS’s third-party f-droid repo as an up to date alternative. The newest versions are incompatible with the main repo but here is their explanation:

Updated Mull to 131.0.0, has 14+1+25 security fixes from the previous 129.0.2 release. In order to resolve the compilation issue introduced in 130, Mull is now compiled using Mozilla’s prebuilt clang toolchain. This however is incompatible with the F-Droid.org inclusion criteria, so these updates (for now at least) will only be available via the DivestOS.org F-Droid repository. Please note, while this adds a prebuilt dependency, the result does still remain FOSS.

For me it has always just defaulted to the left-most monitor. I had a script that would disable that monitor with xrandr when sddm loaded and then re-enable it on logon, but I couldn’t get something similar working in Wayland.

They’re already ignoring robots.txt, so I’m not sure why anyone would think they won’t just ignore this too. All they have to do is get a new IP and change their useragent.

Avoid local retail in favor of what, a website? If you’re concerned about the data mining potential of this robot rolling around a strip mall then you should avoid the internet at all costs.

What you’re describing completely defeats the purpose of the inspections (trying to catch someone in the act of hacking them, somehow) and they were scheduled. Also, you have only replied to me on this post.

You seem very confused.

When did I say anything about anyone having sex? What?

They’re doing visual inspections of rooms because they don’t trust the scary hacker people in them. What do you think telling them you’re in the room is going to accomplish?

Did you even read the article?

I mean sure if you wedge the door or something, but then you’re just going to get kicked out.

Every hotel with those has a tool they can use to easily unlatch that lock.

Cool, best of luck. I’ve been using lightly for a couple months via the AUR package and I really like it.

Another lemmy echo chamber… It’s pointless to show another kind of opinion.

Sounds like you maybe just have a habit of entering conversations on topics you don’t know much about (and in this case self-admittedly don’t even care about), so you get a lot of people who are more informed and do care expressing their disagreement with you?

Have you considered just not doing that?

What is sketchy about downloading a torrent that it could save you from? Wouldn’t it be executing whatever you downloaded on another machine that would be the risky part?

How would a thinking emoji make it clear your question isn’t serious? Also, things have been available for a limited time long before phishing attempts were a thing, and will continue to exist for legitimate purposes long after. You can’t expect the entire rest of the world to stop doing something innocuous just because it’s also used as a tactic to fool a small subset of inattentive people.

If you’re going to be looking at network requests on this granular of a level you should use something like OpenSnitch so you can be sure what is actually generating them.

This is already implemented on a lot of the settings pages on 11.

lol I would open every port on my router and route them all to wireguard before I would ever consider doing this

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).

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 use Nextcloud with Nginx Proxy Manager and just use NPM to handle the reverse proxy, nothing in Nextcloud other than adding the domain to the config so it’s trusted.

I use Plex instead of Jellyfin, but I stream it through NPM with no issues. I can’t speak to the tunnel though, I prefer a simple wireguard tunnel for anything external so I’ve never tried it.

Edit: unless that’s what you mean by tunnel, I was assuming you meant traefik or tailscale or one of the other solutions I see posted more often, but I think one or both of those use wireguard under the hood.