Just turn the updates off. Might want to remove the seatbelts from your car too, so annoying having to put them on and take them off every time you need to drive somewhere.

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.

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.

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

Edit: just wanted to add I don’t think well. I use it at work.

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

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.

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.

I have a feeling the people making fiber internet faster aren’t the same people installing it in neighborhoods.

The product was an LLM.

I never switched to Proton for exactly this reason. I’d much rather use a service that does one thing really well than one that does 20 things okay.

It’s all just to keep you locked into your subscription. Now they want you to keep other money tied up in it too.

The issue is that the docker container will still be running as the LXC’s root user even if you specify another user to run as in the docker compose file or run command, and if root doesn’t have access to the dir the container will always fail.

The solution to this is to remap the unprivileged LXC’s root user to a user on the Proxmox host that has access to the dir using the LXC’s config file, mount the container’s filesystem using pct mount, and then chown everything in the container owned by the default root mapped user (100000).

These are the commands I use for this:

find /var/lib/lxc/xxx/rootfs -user 100000 -type f -exec chown username {} +;
find /var/lib/lxc/xxx/rootfs -user 100000 -type d -exec chown username {} +;
find /var/lib/lxc/xxx/rootfs -user 100000 -type l -exec chown -h username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type f -exec chown :username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type d -exec chown :username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type l -exec chown -h :username {} +

(Replace xxx with the LXC number and username with the host user/UID)

If group permissions are involved you’ll also have to map those groups in the LXC config, create them in the LXC with the corresponding GIDs, add them as supplementary groups to the root user in the LXC, and then add them to the docker compose yaml using group_add.

It’s super confusing and annoying but this is the workflow I’m using now to avoid having to have any resources tied up in VMs unnecessarily.

I’ve been doing this for at least a decade now and the drives are just as reliable as if you bought them normally. The only downside is having to block one of the pins on the SATA connector with kapton tape for it to work.

Damn I forgot no content existed online and could be profitable before YouTube came along and saved us all from the dark ages.