Regarding things like dockers and flatpaks, I mostly “solve” it by only running official images, or at least images from the same dev as the program, where possible.

But also IMO there’s little to no reason to fear when using things like flatpaks. Most exploits one hears of nowadays are of the kind “your attacker needs to get a shell into your machine in the first place” or in some cases evn “your attacker needs to connect to an instance of a specific program you are running, with a specific config”, so if you apply any decent opsec that’s already a v high barrier of entry.

And speaking of Debian, that does bring to mind the one beef I have with their packaging system: that when installing a package it starts the related services by default, without even giving you time to configure them.

I don’t.

Yeah, hot take, but basically there’s no point to me having to keep track of all that stuff and excessively worry about the dangers of modernity and sacrifice the spare time I have on watching update counter go brrrr of all things, when there’s entire peoples and agencies in charge of it.

I just run unattended-upgrades (on Debian), pin container image tags to only the major version number where available, run rebuild of containers twice a week, and go enjoy the data and media I built the containers and installed for software for.

Forgejo gives you a registry built-in.

Also is it just me or does the docker hub logo look like it’s giving us the middle finger?

Persistence of “mental state” mostly. By setting up a compose, you have a written down notion of things like volumes, environment variables and other elements stored somewhere for the behaviour of the container, that can not be ignored or defaulted if you don’t wish it, for when you need to undo and redo a container and default behaviours are important.

While sure, those elements can be set in a loooong ${engine} run... command, it’s easy to forget to set up something important or copy and paste an accidental endline. A compose file (plus a sample envfile, if you so wish) helps keep the way to set up variables and state under control. Made much easier now that we have both docker-compose run and podman-compose run.

Fam, the modern alternative to SSHFS is literally SSHFS.

All that said, if your use case is mostly downloading and uploading files but not moving them between remotes, then overlaying webdav on whatever you feel comfy on (and that’s already what eg.: Nexctloud does, IIRC) should serve well.

Ewwwww, it uses AI!

Imagine wanting to support something as efficient and energy-friendly as SQLite, then throwing an AI on top of it.

Oh you mean, not using something like the internet?

The OP doesn’t say that they have a trademark. For me it sound as they don’t have one.

Ooooh might have misinterpreted that, still not fully sure on a second read. But in which case, it’s even more important that they get that “hoarder dot app” trademark filed.

Absolutely depends on what do you want it for and what resources can you apply on it (learning, set-up, etc).

That said, MySQL is owned by Oracle. The more-or-less blessed alternative IIRC is MariaDB.

Trademark is weird. Like, from what I can understand (IANAL and all the ANAL disclaimers) you can’t trademark “motherfucker” or “mother fucker”, but you can trademark “Mother Fucker’s” for, say, an escort service of dirty nuns.

They registered “hordr”, not “hoarder”. It’s not your fault that there exist valid words in the dictionary, that describe what your app is doing, that they are not using.

This is just the usual case of domain and trademark squatting. If they attempt to further raise a finger (which from what I have read, from a judiciary point of view they haven’t), you have good grounds to countersue. You can also provide the C&D as evidence of threatening and harassment and probably counts for suing the party who sent it if they used a third party, as there’s supposedly a penalty for issuing false or trolling C&Ds.

That said: in a decent legal system no one should be able to trademark dictionary words. I’d suggest you change your trademark from “hoarder” to “hoarder.app” or something similar, as at the moment you trying to trademark a dictionary word is a vulnerability point that opponents with more money to waste can use to attack you, as this shows.

Did you follow any particular tutorial for this migration to k3s that you could recommend?

, I strongly suggest pulling podman from Trixie

Question since I try to use backports and stuff where possible: Is trixie more advisable than pulling from sid for stuff like this?

You made me snort what fortunately was only tea and not a carbonated drink! XD

…backup servers? 👀

My primary phone belongs to my work.

So it’s not yours. Looks from here that’s the one issue you have to solve before everything else.