site banner

Culture War Roundup for the week of July 24, 2023

This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.

Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.

We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:

  • Shaming.

  • Attempting to 'build consensus' or enforce ideological conformity.

  • Making sweeping generalizations to vilify a group you dislike.

  • Recruiting for a cause.

  • Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.

In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:

  • Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.

  • Be as precise and charitable as you can. Don't paraphrase unflatteringly.

  • Don't imply that someone said something they did not say, even if you think it follows from what they said.

  • Write like everyone is reading and you want them to be included in the discussion.

On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.

13
Jump in the discussion.

No email address required.

I disagree. The reason RAID is not a backup is because it does not protect against accidentally deleting data, and compared to an external backup the chance of something breaking both drives is greater because they're next to each other. However, it is not better than external backups in terms of capacity; the data is just as big regardless of where you store the drives or how you access them. It's less space-efficient than having a single external copy, but that's not a backup, that's your primary copy being stored elsewhere.

And practically speaking, RAID is more reliable than external backups because it's being constantly checked through normal disk usage. If your external backup has had an error, you won't find out until you access it, which is really bad if the reason you're accessing it is because your primary copy doesn't work. In a company you can make it someone's job to verify the backups by periodically restoring them to a test system, but most individuals won't be doing that.

However, it is not better than external backups in terms of capacity; the data is just as big regardless of where you store the drives or how you access them. It's less space-efficient than having a single external copy, but that's not a backup, that's your primary copy being stored elsewhere.

I mean if I have 10 disks and split 5 into a data pool with no mirroring/parity and 5 into a backup set, then I have half the total capacity of all disks. However if I turn 5 into a raid, I’ll have some number of disks capacity -N depending on raid level. I could then turn the backup set into the same raid level (online backup) to match, but in this case raid gives me less than half the total capacity of all disks due to extra parity storage.

And practically speaking, RAID is more reliable than external backups because it's being constantly checked through normal disk usage. If your external backup has had an error, you won't find out until you access it, which is really bad if the reason you're accessing it is because your primary copy doesn't work.

True, however my approach would be to have both online and offline backups. Online ZFS backup should help here. To keep costs down, this is just 3 disks for every dataset zpool I’d set up. Then, an additional 3 disks when that runs out. Add another disk or tape in to this for offsite backup if you want.

Also offline guards against ransomware.

What do you think, what is your approach?

For relatively unimportant stuff I just use RAID. If ransomware wants me to pay for my Factorio saves I can start a new game instead. My more important private stuff is all documents, so I keep an extra printed copy (and for the really important stuff I also keep copies with my relatives in case I lose everything in a fire). For important stuff that I don't need to hide, I use immutable storage on the internet (e.g. git, bittorrent, ipfs). That would be my advice to anyone who wants to hoard books electronically: find a like-minded community, make a torrent with everything you want to hoard, and ask them to seed it.

On the latter point of immutable storage, I’m not convinced we won’t have some sort of on onerous blackout from a “global cybersecurity incident” as defined from the WEF. No route to host, but I want my data. So I do keep hoarding locally.