I don’t want AI slop from big corpo and you think I am gonna want AI slop that’s just as wasteful and harmful just because it’s “locally produced”? That’s Republican-ish crap line of thought.

Shout out to !iso8601@lemmy.sdf.org !

It seems they don’t care.

Then get that in writing.

You don’t need years for a terminal, at least not for the stuff a normal user would have to expect to do with it (so eg.: not browsing files, that has good UIs already). But you should expect to have to learn something. We require people to learn and even certify their learning when they are to drive a car for example, and for computers we are not even askng 1/6th of that, even tho the last few decades show we maybe should.

You don’t need to do everything on the terminal – even today, you don’t have to. But you should not fear the terminal, the same way you should not fear a piano because you play a violin. Windows also has a terminal, there’s stuff that tells you to go there to enable some Powershel things, and no one complains.

Or with cooperatives. Cooperatives are a good alternative to corporations.

Since you mention stuff like “the video isn’t important”, “other services” (plural), I’d consider not just one alternative but several. The big problem with big name social media is that they provide a all-in-one experience that is designed for profit, and as such looks and acts worse than any of its independent parts (not to mention, the sum is artificially made more addictive to users).

• For publishing campaign materials itself, all you need is a filehost or filebin - something like pastebin.com but that allows you to upload and organize any kind of files. Any of the offerings in the FOSS market will do, but if you are going to focus on posting quickie (rich¡) text documents that are easy to build and parse I’d suggest a Markdown-based document bin like Hedgedoc.
• If your campaign is gonna run like a chat, XMPP / Jabber. There’s servers like Prosody or ejabberd that are easy to set up.
• If your campaign is gonna run in web “play by post” mode, any modern web forum system will do, for example Discourse. Heck, even oldie-style web forums might do, like phpBB.
• Voice: Jabber has access to audio IIRC. I’ve also heard very good things about Mumble.

Just sell the car to a derby demolition show. We all win.

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?

Doesn’t need to (but yeah yeah they’re Google, I know…). They just should name it “Gulf of México” or whatever the translated name is to the user’s device, and add an asterisk somewhere that shows a note to the effect of “a small fraction of Confederate remnants think it should be called ‘Gulf of America’”.

What else do people expect them to do?

1.- Refuse-

2.- Apply only the part of the name change that’s actually covered by US jurisdiction. The Gulf of Mexico extends noticeably beyond US’s borders.

But hey this is Google we’re talking about.

Besides, it still say Gulf of Mexico if you’re outside the USA.

If I’m a eg.: Colombian, it should be “Gulf of Mexico” “Golfo de México” wherever I stand, not “Gulf of America”.

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!

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.

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.

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.