!iso8601@lemmy.sdf.org gang, rise up
Server had been down for about two days but just got it crossposted there, thanks!
I write English / Escribo en Español.
Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.
This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.
!iso8601@lemmy.sdf.org gang, rise up
Server had been down for about two days but just got it crossposted there, thanks!
Oh i see. I thought there was more to it – but I guess it’s just Java being horrible as usual.
Internet posts are being loaded!
Wayland
Java support
…what?
It’s incredible that wayland is so incapable that it can’t even keep this kind of state, and we’re back to having to basically having to write .xinit scripts. Because that’s what little so far wayland offers: less than xinit.
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?
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.
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.
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?