196
Community Rules
You must post before you leave
Be nice. Assume others have good intent (within reason).
Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.
Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.
Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".
Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.
Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.
Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.
Avoid AI generated content.
Avoid misinformation.
Avoid incomprehensible posts.
No threats or personal attacks.
No spam.
Moderator Guidelines
Moderator Guidelines
- Don’t be mean to users. Be gentle or neutral.
- Most moderator actions which have a modlog message should include your username.
- When in doubt about whether or not a user is problematic, send them a DM.
- Don’t waste time debating/arguing with problematic users.
- Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
- Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
- Ask the other mods for advice when things get complicated.
- Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
- Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
- Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
- Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
- Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
- First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
- Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
- No large decisions or actions without community input (polls or meta posts f.ex.).
- Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
- Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.
view the rest of the comments
As others have pointed out, it depends. The most I would need to do is identify the faulty stick and pull it. That's pretty trivial to do and I would be back up and running within the hour.
The only thing that can't fail (or the system stops working), is the motherboard and the power handling equipment. The power supply is redundant but the power from the power supplies needs to be handled before it gets to the system components, so there's a small PCB that connects to both power supplies and provides power to everything in the system.
Of course the motherboard connects everything together.
My GPU is also unique in the system, but I have less powerful spares laying around that I have stopped using, so I can literally just grab a different GPU and be back up and running at nearly the same capacity, minus the gaming graphics performance that's lost....
On top of all of that, I upgraded to my current Dell precision from a different Dell precision. It's an older model and definitely showing it's age, but it still works. So that's available to me in a pinch.
Basically, I have backups for my backups when it comes to hardware. I have a handful of spares for my SSD array disks too....
Worst case, I hook up my framework laptop as a stand in for my desktop until a replacement part ships to me.
Backups of backups.
are you talking ECC RAM? because normal RAM sticks tend to fail in ways like "after 2 years of use this random page of memory is now reporting the 17th bit of every word as 1, no matter what value you actually write to it". if you have faulty RAM like that, RAID won't save you; copy a 1 GB file from ~/a to ~/b: it's read into RAM, 100 bits are flipped, the RAID system takes what's in RAM and commits it to disk, congrats: your RAID array will reliably preserve that corrupted file for 100 years. worse is when the bad bits aren't file data but internal filesystem structures, and then you just lose half your directory tree.
so yeah, get ECC RAM. or if you don't for some reason then when your bulletproof storage system starts reporting filesystem-level corruption 2 years from now, remember this comment and run
memtest
before spending $100's replacing all the drives, motherboard, etc.My system is a Dell precision rack 7910, with dual Xeon E5 processors (I forget the exact model off the top of my head) and yes, 64G of ECC memory. DDR 4 IIRC.
I'm telling you, the system is rock solid. I got it refurbished, so it was put through its paces before I got it. Any defective parts will have already failed and been replaced.