Welp... that was quick (around 4 minutes to get banned at "/c/linuxsucks)...

4 days ago by Artwork to c/yepowertrippinbastards

Most Linux firmware tools (flashrom, coreboot utilities, vendor‑reverse‑engineered scripts, NVMe tools) load the firmware into ram (assume it’s ECC), trust the RAM is correct, and write directly to SPI/EC/NVME. There’s no double-buffering, memory integrity checks, vendor-grade validation, protected memory regions, or automatic rollback. If the buffer is corrupted, Linux flashes it anyway. Windows OEM flashers never trust raw RAM blindly. Because vendors don’t ship Linux flashers, users rely on flashrom, fwupd (reverse‑engineered metadata), Community EC flashers, Community NVMe firmware tools, and Coreboot scripts. Reverse‑engineering = incomplete understanding = higher brick risk. Windows uses official vendor tools with signed capsules, verified update paths, vendor QA, and recovery logic. Linux gives userspace access to /dev/mem /dev/spidev I²C/SMBus EC registers and PCI config space which is terrible for safety. Windows blocks almost all of this.

It's sorrowful some people choose to hate, complain, ridicule, and block everything that does not fit their choice...

With just a single idea shared, a lone message posted in a community, with your finite priceless time and experience invested, you may get banned instantly, and permanently, instead of actually learning and discover together...


The single message that resulted in my immediate permanent ban:

Message

It's not Linux, but your distribution, or you, what makes it "unsafe".
There are numerous options to harden your Linux environment, and it's relatively trivial to keep it safer if you ever want it, or actually stop blaming and complaining.

For example, to limit the access for root or custom group hwaccess, without much fuss but to give you an idea, for the most popular distros as Debian-based:

  1. Add a Udev rule:
# /etc/udev/rules.d/90-hwaccess.rules

KERNEL=="mem",        GROUP="hwaccess", MODE="0660"
SUBSYSTEM=="spidev",  GROUP="hwaccess", MODE="0660"
SUBSYSTEM=="i2c-dev", GROUP="hwaccess", MODE="0660"
  1. Set at boot:
setfacl -Rm 'g:hwaccess:rwX' -- \
    /sys/kernel/debug/ec \
    /sys/bus/pci/devices/*/config;

You may then setup SELinux, AppArmor, and secure it via SecureBoot's shim, too.
Yet, you chose to effortlessly complain instead...

Broadfern 21 points 3 days ago

You broke the comm’s rules:

Rules:

  1. FOSS (especially GPL) advocates and Linux (specifically GNU/Linux) evangelists aren't welcome (GNU Hurd will count as Linux). -We ask that you block us and we will perma-ban for violations of this rule.

That is entirely on you.

path: 0 24338053, hotness: undefined, score: 21, children: 1
artwork 2 points 3 days ago

Oh... I see... Thank you!
I could not even imagine such a rule when I noticed the post at home page of LemmyWorld instance, and commented on it... ^^"

path: 0 24338053 24338585, hotness: undefined, score: 2, children: 0
limer 12 points 3 days ago

Ydi, you spoke reason in a troll community that has rules that any tech savvy person could see as a danger sign.

Don’t feed the trolls

path: 0 24338390, hotness: undefined, score: 12, children: 0
Proprietary_Blend 8 points 4 days ago

Oh no. Anyway

path: 0 24337339, hotness: undefined, score: 8, children: 1
artwork -1 points 4 days ago

Yes, indeed... it was just... unexpected to get banned in just 4 minutes participating in that community... ^^"
Though, re-considering the purpose of the community, it may be...

path: 0 24337339 24337353, hotness: undefined, score: -1, children: 0
RickyRigatoni 7 points 3 days ago

YDI for feeding the troll.

path: 0 24342234, hotness: undefined, score: 7, children: 0
Harvey656 6 points 3 days ago

Linux gives userspace access to /dev/mem /dev/spidev I²C/SMBus EC registers and PCI config space which is terrible for safety.

I might be ignorant, but isnt that information technically different per distro?

path: 0 24337861, hotness: undefined, score: 6, children: 3
artwork 3 points 3 days ago

Of course it is! Thank you! And hence mentioned it in the comment, too!

path: 0 24337861 24338597, hotness: undefined, score: 3, children: 2
Harvey656 3 points 3 days ago

There's been a ton of antis recently spreading straight up misinformation.

Saw one recently saying anticheats dont work on linux because the apps can't run root. Which is massively wrong. Weirdos.

path: 0 24337861 24338597 24338715, hotness: undefined, score: 3, children: 1
A404 6 points 3 days ago

just wait until they find out that you have to literally use a exploit to load your own kernel drivers on windows

path: 0 24337861 24338597 24338715 24339111, hotness: undefined, score: 6, children: 0
frongt 3 points 3 days ago

Yeah I mean technically PTB, but it's a community specifically for that, so what did you expect?

path: 0 24338349, hotness: undefined, score: 3, children: 0
csolisr 2 points 3 days ago

Do they happen to have the same moderators as the subreddit? Because they're also famous for being trigger-happy with the ban-hammer

path: 0 24340005, hotness: undefined, score: 2, children: 0
yepowertrippinbastards
yepowertrippinbastards

@lemmy.dbzer0.com

login for more options
1786
391
625

This is a community in the spirit of "Am I The Asshole" where people can post their own bans from lemmy or reddit or whatever and get some feedback from others whether the ban was justified or not.

Sometimes one just wants to be able to challenge the arguments some mod made and this could be the place for that.


Posting Guidelines

All posts should follow this basic structure:

  1. Which mods/admins were being Power Tripping Bastards?
  2. What sanction did they impose (e.g. community ban, instance ban, removed comment)?
  3. Provide a screenshot of the relevant modlog entry (don’t de-obfuscate mod names).
  4. Provide a screenshot and explanation of the cause of the sanction (e.g. the post/comment that was removed, or got you banned).
  5. Explain why you think its unfair and how you would like the situation to be remedied.

Rules

  • Post only about bans or other sanctions that you have received from a mod or admin.
  • Don’t use private communications to prove your point. We can’t verify them and they can be faked easily.
  • Don’t deobfuscate mod names from the modlog with admin powers.
  • Don’t harass mods or brigade comms. Don’t word your posts in a way that would trigger such harassment and brigades.
  • Do not downvote posts if you think they deserved it. Use the comment votes (see below) for that.
  • You can post about power trippin’ in any social media, not just lemmy. Feel free to post about reddit or a forum etc.
  • If you are the accused PTB, while you are welcome to respond, please do so within the relevant post.
  • Keep the comments in YPTB posts about the moderation action itself, not about the general topic in which the moderation took place.

Expect to receive feedback about your posts, they might even be negative.

Make sure you follow this instance's code of conduct. In other words we won't allow bellyaching about being sanctioned for hate speech or bigotry.

YPTB matrix channel: For real-time discussions about bastards or to appeal mod actions in YPTB itself.


Some acronyms you might see.

  • PTB - Power-Tripping Bastard: The commenter agrees with you this was a PTB mod.
  • YDI - You Deserved It: The commenter thinks you deserved that mod action.
  • YDM new - You Deserved More: The commenter thinks you got off too lightly.
  • BPR - Bait-Provoked Reaction: That mod probably overreacted in charged situation, or due to being baited.
  • CLM - Clueless Mod: The mod probably just doesn't understand how their software works.

Relevant comms

go to feed...