From maybe to definitely not.

Just to clarify: OwnCloud or OwnCloud Infinite Scale (OCIS)?

The main advantage of SB is TPM. At runtime the key isn’t available and unlocking your disk works automatically as long as nothing has been tampered with (which is then also a nice canary: if you suddenly have to enter your password during boot, something’s off).

Even having no pre-boot PIN with SB on is nice, then you only need your user space login where you could even use fingerprint reader if you like. For servers they can already start serving without anyone having to intervene manually (which is nice after power outage, for example).

So yeah, SB, TPM and FDE are a very nice bundle that heavily secures against the most relevant attack vectors.

For the user they come with the OS

That’s my point, though. Plasma isn’t an OS. You can can have a OS that ships Plasma with Calligra instead of LibreOffice and Falkon instead of Firefox. Or neither, and instead they give you a greeter with the choice to pick your browser. Or the OS is minimal and doesn’t bundle any of them. In Arch for example you normally don’t even get Konsole or Dolphin unless you install them (or you pick the nuclear option and install _all _ KDE packages which also includes a ton of stuff you likely never need).

Probably some fastboot shit. I like the idea of fastboot… if only it wasn’t so tied to Windows.

The ONLY thing I don’t like about it is having to finish the install of windows before you can wipe the ssd.

Why? Can’t you get to the bios, change to usb boot loader, boot linux and wipe the disk?

AUR is the place for unverified submissions. The verified stuff typically ends up in the main repos.

The preinstalled apps are not a feature of KDE (or Gnome, XFCE, etc.). Actually they all are structured in a very modular way where you can use or omit individual components. Firefox and LibreOffice are completely independent of it even; they merely add compatibility layers to make the integration more seamless.

What you experienced was something to attribute to the distribution you chose. They are the ones to decide which components to bundle and preinstall. That is also the reason why so many distributions exist in the first place, because different teams/devs have different visions about what the desktop should look and feel like after install.

If your client(s) accept irregularly changing remote certs (i.e. they don’t do cert pinning), it should work. If both cloudflare and you use the same CA, it would likely work even with cert pinning. Certainly possible, but increases the complexity of the overall setup.

Possible, true. But then the setup also becomes more complicated. In addition you end up with different certs for local and remote access, which could cause issues with clients if they try to enforce cert pinning for example.

Cloudflare tunnel likely terminates TLS on the edge. So if you bypass it, you don’t have HTTPS. Not a problem locally, but then destroys the portability of the URL (because at home you need http and outside you need https). Might as well use different hosts then.

If it sells well on Steam, it also rises in the charts there, becoming more visible to an even larger audience. While the margin is lower due to the cost of the store, the profit might still heavily exceed the alternative (and since there’s no per unit cost for software, that’s quite nice).

I think you won’t regret it. If the container startup installs stuff, you might lock yourself out when the remote server has issues, your network has issues, or if the package you install changes due to an update.

With it baked into an image, you have reproducible results. If you build a new image and it doesn’t work anymore, you can immediately switch back to the old one and figure out the issue without pressure.

The idiomatic way would be to build your own image. That’s exactly the strength of the layering of container images.

The thread is about snap and why it’s worse than flatpak.

Wanna meet? /s

Does it make a difference, if that setting uses a trailing slash? Might be it redirects you to the path without, which triggers caddy to redirect you again, and so on and so forth.

You could also, instead of redirecting, rewrite it. Then it is handled serverside without sending the client somewhere else.

Are all the *arr services aware that they are expected to have a certain basepath?

LOL, ok, fair 😁

You should in any case consider your backup strategy. If you have reliable backups, your fuckups can’t be as bad anymore. If you don’t have reliable backups, a “raw” storage doesn’t help you either. Maybe even the contrary: you won’t notice, if individual files get corrupted or even lost until it’s too late. (Not talking about disk corruption, against which the right filesystem can guard you… but I am not sure you trust filesystems either 😛)