Yes? The error should at least show basic info. Requiring checking the logs when the error message could just show some info is silly and clearly doesn’t work well given how many people are asking for help with it.

Because there’s no error code attached or any details about what specific error it was, what file it happened on, what mount it happened on, etc…

They only load if you load images, every email client I’ve used does not load them by default for this reason.

You can also run an DNS adblocker like Adguard Home or PiHole and that will block a lot of the domains commonly used for tracking pixel images.

Technically yes, but the access someone would need to make use of that vulnerability would be pretty significant I’d think, and at that point you’re probably hosed in many other ways too.

I probably wouldn’t expose it, while I don’t think it’s been a problem in the past, with LLMs being used to find vulnerabilities so much in the past few months it seems prudent to do everything you can reasonably do to secure things.

Tailscale is so easy to use it seems worth the bit of extra hassle.

Yeah if you read my other reply I meant it as it often just fails silently with wine, I’ll open an exe, it’ll do something in the background, and then nothing happens. No errors, no explanation of what went wrong…

It’s more that wine tries but often fails silently for some reason, hopefully this is more user friendly and will actually just tell me “you need .net framework click here to install” and that sort of thing.

This sounds like I can just double click an exe like I do on windows and it’ll work. That never seems to work with wine so it’ll be nice to have something function properly.

Wired earbuds are what I use, with a cheap USB-C to 3.5mm adapter I leave permanently on the cable.

Not if your BT DAC supports lossless codecs.

That could be made illegal as well if the FCC felt inclined to. Radio direction finding would make tracking down mesh nodes fairly trivial for them.

It’s pretty good, generally don’t find anything I can’t do on it.

The only annoyance is performance really, it can get some odd lag at times.

The article says it’s people giving their login info to their AI agent, so nothing to do with the bank security or being hacked in that sense.

I’m re-thinking a few things, mostly moving exposed services onto a VM or two that are on their own VLAN, and don’t contain any important data (it would be my website, gameservers like Minecraft, etc…). I might move to podman as well so nothing has a possibility of running as root, docker can run rootless but that setup seems more confusing to me.

I already use a VPN via Wireguard on my router for access to my private services when out of the house, so my changes are just separating the public from the private as much as possible on the server side of things…

Essentially if someone manages to drop a crypto miner or something on my website that’s fine, I’ll get an alert pretty quickly through Beszel that the server load is high and I can go roll back a backup or whatever. I just want to make sure there’s no access to anything else for them.

I generally stick with the main TLDs. Like com or net.

.com is fairly cheap and won’t be on any blocklists, where some other TLDs can be.

But if you’re in the EU then .eu probably makes sense to use.

There have been a few major ones this year, I’m sure they are fixed at this point though. https://app.opencve.io/cve/?vendor=jellyfin

Plex uses a code signin system where you open the app on your phone or just a browser, and enter the code there.

So there’s no typing/entering anything on the TV at all.

Some rare stuff is on brew but you also need to know that it’s there somehow, it’s a pain to deal with. Especially since Bazzite doesn’t tell me where the safe version of the package exists, just warns me “don’t do it that way!”

Jellyfin has plenty of issues with public instances too. It’s just the reality of exposing to the public internet, unless it’s something that has a lot of dedicated work going into security it’s going to have problems.

If it breaks I either fix it (often it’s just an issue where the new version needs extra config added), or roll back to a backup and pin the old version temporarily if it really went wrong and I can’t recover otherwise.

Backups run early AM before any auto updates start, and no one is using services and changing data then, so nothing should really ever be lost by rolling back.