What makes you think your next cloud instance isinvulnerable to being hacked??

Of course client-side encryption is a must

It breaks a lot of things when you turn it on. It doesn’t really work. It is off by default for a reason

NextCloud doesn’t support e2ee

I use Debian in Qubes. Checkmate.

I guess you don’t want e2ee

Why would you expect that your self-hosted solution is less-likely to be hacked than a hosted solution with literally teams of people paid to secure and update them?

Rust is not objectively better. That’s your opinion

That’s it, I’m packing my bicycle and moving to Holland

Sure there is. Don’t do it in a browser.

Lol why? Lemmy isn’t a privacy platform. The devs don’t give a shit about your data rights or the instance admins legal obligations to your data rights

Open Funk. I want more kitchen equipment that wont die when i give it a hard task, and i can repair myself if it does. But I don’t know where to begin

What does this do?

Wtf why would you intentionally not be POSIX compatible?

$IFS splits files at spaces

Right, so it has a depend and it won’t work for many users

Now do it with a for loop on every file in a dir with thousands of files

I put an unnecessary amount of spaces in all my file names to break anyone who wants to use CLI tools on them

i use windows btw

No, static sites are usually more js heavy because they offset all the processing to the client.

This is one reason I avoid static sites, and just heavily cache the server.

Sounds like JS is a depend

Lol wut. What was the issue with TrueCrypt? I don’t think we ever found out. The anon dev just bailed and hilariously told people to use bitlocker. Personally I think they were just trying to be funny. Fortunately veracrypt took over development.

I only use VPNs over here. Honestly I think this is probably only an issue on Lemmy.world and nowhere else