I'm not associated with anyone in this thread or the situation being discussed. I'm interested how we understand and use cultural signals. Here's some Pepe detail for the similarly curious:

The alt-right got wise to new media in the 2010s. They started meme-washing their hate mongering and trying to normalize coded hate speech in internet culture using Pepe memes and other popular formats. It snowballed and the Pepe meme = Nazi user association is a product of lasting trends from that time. It's similar to clocking someone for wearing straight-laced Doc Martens or khakis and a white polo.

For those in the know one of those items is a small red flag. The wearer could be completely ignorant that these are known dog whistles/identifiers for members of hate groups. If someone is wearing a lot of small red flags then it's less likely the wearer is accidentally serving white supremacist. That's the point of stealing and manufacturing these kinds of symbols though: most people don't know they exist or what they intend to mean so the user can feign ignorance with plausible deniability. They're the inverse of modern progressive advocacy symbols. Wearers can hide in plain sight with just enough Nazi showing that other insiders see them. Pride icons for cowards.

The artist who created Pepe has publicly denounced the character's use as a hate symbol and regressivist propaganda tool. Whether or not a community or individual "liberates" Pepe from the prison CHUDs built is up to them.

For what it's worth: I lean toward liberate most of the time (fight against the thieving bigots) but in this situation, even given a permissive setting, adding "posts Pepe" as a mark against is sensible. It's clear the user is either intentionally pushing hate propaganda or else under enough alt-right influence that their intentions aren't relevant to the evaluation.

laughs in home lab

Not that I'd buy it but, if I did, that power button might get used twice a year. Likely less since I wouldn't be able to upgrade or maintenance its hardware.

That's no different from VMware or Hyper-V if you switch the specifics around. There are many more administrators running virtualization clusters that have very little knowledge of the internals than there are subject matter experts or weekend deep divers. The barrier to entry for these things is low because they're designed well enough and half decently documented. Proxmox isn't unique in this respect.

OK. So we have a disagreement then. What part of Proxmox requires expertise?

Toss a message at Scott Reeder (Scott Prop and Roll). I'd bet money he either knows folks who worked that set or knows someone who knows someone. I've no idea if he'd respond but he seems chill like that.

I'm not sure I'm parsing your fifth paragraph correctly. Are you suggesting Proxmox is DIY and unsuitable for Production? That Proxmox is suitable for Production and those who think they can roll their own hypervisor are in for a bad time? Something else?

That's a fair take. Silver Blue is great and, in the spirit of the thread, if I were helping an interested but hesitant lifelong Windows/Intel/Nvidia user migrate to Linux today I would:

1. Buy them a new SSD or m.2 (a decent 1tb is ~$50 & a good one only ~$100).
2. Have them write down what applications, tools, games, sites, etc they use most often.
3. Swap their current Windows OS drive with the new drive and, if needed, show them how and why that works or provide an illustrated how-to (so this choice is not a one-way street paved with anxiety. If they want to swap back, or transfer files, or whatever else; they can. Easily). Storage drives are just diaries for computers. The user should know there's nothing scary or mystical about them.
4. Install Fedora Kinoite on that new drive.
5. Swap them from Fedora's custom Flatpak repository to Flathub proper. A decision that should be given to the user on install IMO but I digress.
6. Install their catalogue of goodies from step 2 so they're not starting from scratch.
7. Install pika and configure a sane home directory backup cadence.
8. Ask them to kick the tires and test drive that Linux install for at least a month.

Kinoite is going to feel the most like Windows and, once configured, stay out of the way while being a safe, familiar, transparent gateway to the things the user wants to use.

My personal OS choices are driven by ideals, familiarity, design preferences, and a bank of good will / public trust.

I disagree with some of Red Hat's business model. I fully support the approach SUSE takes. I'm also used to the OpenSUSE ecosystem, agree with most of their project's design philosophies, and trust their intentions. I'm not a "fan" though and will happily recommend and install Silver Blue or any other FOSS system on someone's computer if that's what they want and it makes sense for them! Opinionated discussion can be productive and healthy. Zealotry facilitates neither.

That said: Aeon has been out of beta for a while. The latest release is Release Candidate 3 and they're closing in on the first full release. Nvidia drivers work after a bit of fiddling. 🙂

I'm going to edit my previous post to add the Kinoite suggestion for posterity's sake.

Check out Aeon and Fedora Silverblue. I'm installing Aeon on Desktops and MicroOS on Servers. My computer needs to be a reliable tool. Immutable distros make it exactly that.

The last thing I want to do in my free time or during my work day is be forced to fiddle with some poorly documented and/or implemented idiocy on my personal computer because I forgot to cast the correct incantation prior to updating something. I'm not a masochist.

EDIT To the hesitant but hopeful Windows+Nvidia user: give Fedora Kinoite a try. Check my reply to @independantiste@sh.itjust.works below for details.

I was taught something different growing up and had to check myself with a quick read. Holy shit. You're right. Thanks for sharing.

My partner has chronic pain. I'm stealing this as a tool for future conversations. Thank you!

C

The right thing to do is offer a program to replace the battery. Even more right would be not designing anti-repairability into your products. 🙊

Throttling the processor to extend the life of the phone is a reasonable temporary alternative IF it's transparent and opt-in. Effectively forcibly downgrading the hardware spec of a device I own without even telling me is a serious breach of trust at the very least, no?

I agree the decision may have resulted in less e-waste but, even if so (and assuming all is well-intended), that can't justify hijacking consumer's belongings. That's a dangerous precedent to set.

I have a deep appreciate for this level of discernment. Moderating posts and their discussions in good-faith and abiding by the spirit/intention of the rules instead of strict enforcement by letter fosters community trust and makes it more difficult to argue against removals/bans when they do happen.

Thanks for volunteering and keeping the lights on.

Honey badger shadow beings.

edit 0: words

edit 1: that is an incredible band name

That's not true for all sites. If the page is static then it'll have no clue. If it's dynamic and running a client-side script to report this info back, and if that information is collected, then I can see how that might be a useful supplement for fingerprinting if the server owner is so inclined. At that point though I'm wondering why a security-conscious user is raw dogging the internet and allowing scripts to run in their browser without consent (NoScript saves browsers).

Even then it's unclear when/how altering the page to render it differently is commonly communicated back to the server, how much identifying information that talk-back is capable of conveying, and how we might mitigate those collections (wholesale abstinence and/or script control aside). What are the specific mechanisms of action we're concerned about? This isn't a faux challenge for the sake of hollow rhetoric. I'm ignorant, find the dialogue interesting, and am asking for help being less dumb. :)

I found some brief and useful discussion in this Privacy Guides thread. Seems like the concern is valid but minimal for all but the most strict/defensive postures.

Trying to validate this myself for Dark Reader without breaking out Wireshark and monitoring some big tech site while I toggle color modes (which I might do later if I think of it and find the time) I see Dark Reader is open source, an Open Collective member, and seems to engender little hand-wringing. The only public gripe I can find is this misguided Orion Browser feedback thread.

Thanks for the interesting diversion!

How so?

This is admittedly a bit pedantic but it's not that the risk doesn't exist (there may be quite a lot to gain from having your info). It's because the risk is quite low and the benefit is worth the favorable gamble. Not dissimilar to discussing deeply personal health details with medical professionals. Help begins with trust.

There's an implicit trust (and often an explicit and enforceable legal agreement in professional contexts (trust, but verify)) between sys admins and troubleshooters. Good admins want quiet happy systems and good devs want to squash bugs. If the dev also dons a black hat occasionally they'd be idiotic to shit where they eat. Not many idiots are part of teams that build things lots of people use.

edit: ope replied to the wrong comment

That wasn't the question, was unnecessarily rude, and not something you could possibly know. The only reason to post your comment is to wound a stranger. Your cruelty is obvious and you should be ashamed of yourself. Do better.

A speaker's public record provides context for their current commentary. Trump's tells us he is a bigot. Specifically a white supremacist. His recent rhetoric leans in to this. When pressed to clarify, justify, or recant these statements he either deflects or doubles down.

There is no reason to think he is suddenly well intentioned, operating in good faith, or otherwise deserving of some deference of judgement.