how do you design a server to be “better” if it has to trust data from a remote client?

Because it doesn’t have to.

Happy Cake Day, @Stamets@lemmy.world ! 🥳

This video by Middle East Eye is a decent summary of the reasons IMO.

Specifically the fact that Saudi Arabia was in the process of normalizing relations with the occupiers, but no longer is.

Same, it’s just too American for my tastes

Thank you, was wondering what happened there.

What?

😳

Exactly

To quote the post more specifically:

Even as our species destroys its only home, we assume that the solutions to climate change must lie in technology, without stopping to examine the role that this very attitude has played in the crisis.

This is so deeply ingrained in our social consciousness that, when there is a new impressive technology, we assume that it must be here to solve one of our big problems. As the AI hype quickens the pace of our ecological devastation, we're so dazzled by the technology that there is actual debate in supposedly serious publications as to whether AI is going to save us from climate change, despite all evidence pointing to the contrary.

You can also do the following to prevent unwanted writes when something is not mounted at /mnt/thatdrive:

# make sure it is not mounted, fails if not mounted which is fine
umount /mnt/thatdrive

# make sure the mountpoint exists
mkdir -p /mnt/thatdrive

# make the directory immutable, which disallows writing to it (i.e. creating files inside it)
chattr +i /mnt/thatdrive

# test write to unmounted dir (should fail)
touch /mnt/thatdrive/myfile

# remount the drive (assumes it’s already listed in fstab)
mount /mnt/thatdrive

# test write to mounted dir (should succeed)
touch /mnt/thatdrive/myfile

# cleanup
rm /mnt/thatdrive/myfile

From man 1 chattr:

A file with the 'i' attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file, most of the file's metadata can not be modified, and the file can not be opened in write mode.
Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute.

I do this to prevent exactly the situation you’ve encountered. Hope this helps!

Then you might like this tech blog: https://theluddite.org/#!post/ai-hype

One only blinks the truth and the other only blinks falsehoods. Which direction do you turn?

That’s the one, thanks!