

Oh i see. I thought there was more to it – but I guess it’s just Java being horrible as usual.
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.
Oh i see. I thought there was more to it – but I guess it’s just Java being horrible as usual.
In a good internet, you shouldn’t have to pay someone else for your own identity.
It’s (un)amusing how the Fediverse of all things still depends on a system of identity that relies on forcing trust on a third party that can take that identity from you at any point and without recourse (within that system). Or, you know, you can “forget to drink your internet identity verification can for the commercial god”, which is just as (un)funny.
Internet posts are being loaded!
Oh dear!
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.
About 70% of your pizza is 70° hot!
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
.
Enshitification is entropy for businesses
Can I have this on a T-shirt?
Bue nos dí as pro fe sor
Ubiquitousness is not an aspect of the codec, let alone a technical one. It’s yet another failure of capitalism.
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.
We’re here to help! We just need someone to implement doomscroll / infiniscroll into Lemmy, lol.
Never said they conflict. Said they’re not a “basic feature”. Sigleplayer has lived without cloud saves since around 1960.
Heck, most modern consoles have a USB port, I’d consider “offline save” more “basic” than “cloud save”. After all we all know by now the corporate internet can’t be trusted.
Hey! Someone else remembers floppy disks!
Looking at the various recent mishaps, like this one, I’m two steps from offering my services as an instance admin. Or would be, if I wasn’t already busy with a half-time job and the other half of the time wasn’t trying to have a social life.
endless feed
to fight algorithm addiction
endless
feed
to fight algorithm addiction
Uuuuuh that’s not the way to fight an addiction, right? Who is this person working for, exactly?
That would help lots… if Texans knew how to read!
Technically the only way you can vet, is by having root access to their servers and law officer level access to their documents.
Failing that, I can think of four baseline conditions to venture that a given product “shouldn’t” enshittify, or that at least the utility of the project is recoverable (or forkable) if it does:
Req 0: Copiability. The software actually provides a full offline (or local) service. There’s no way (that I know of!) to enshittify something that can live fully independently from its “mothership”.
Req 1: “Letter and Spirit”. License has to be Free Software (not just “Open Source”) with all the liberties that come with it. (I assume in the future, an exception might be made to allow for New Ethical licenses that would be not FOSS as per the current definition)
Req 2: Reproducibility. Someone else has to have verified that using the source release builds the whole product (at most excepting “assets” like logos). This is usually verified empirically by someone getting to run and maintain a competing instance.
Req 3: No bite hand. The provider must have not used legal measures to exercise violence or restrictions against users of the product (be those consumers or devs). This includes eg.: using the DMCA to punish reviews, or punish implementation of req 2.
If a combination of provider and product completes those four requirements, I feel relatively well assured that the product can’t reasonably enshittify, or at least that if it were to happen, there will be enough advance notice and devel momentum that the value of the product can be recovered from it.