I take my shitposts very seriously.

  • 5 Posts
  • 275 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle
  • Important addition: don’t just shut the fuck up.

    First, in some jurisdictions, failure to identify is an arrestable offense. Full name, date of birth, relevant cards/papers.

    Second, if you need to reach for something, say something so they don’t think you’re about to pull a weapon on them. Officer safety is always a concern in the land of handing out guns like candy.

    Third, explicitly state that you are exercising your fifth amendment rights. Otherwise you might run into an “I want a lawyer, dawg” situation.




  • rtxn@lemmy.worldtolinuxmemes@lemmy.worldAverage systemd debate
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    11
    ·
    2 days ago

    My full-time job literally involves dealing with systemd’s crap. There is a raspberry pi that controls all of our signage. Every time it is powered on, systemd gets stuck because it’s trying to mount two separate partitions to the same mount point, whereupon I have to take a keyboard and a ladder, climb up the ceiling, plug in the keyboard, and press Enter to get it to boot. I’ve tried fixing it, but all I did was break it more.


  • rtxn@lemmy.worldtolinuxmemes@lemmy.worldAverage systemd debate
    link
    fedilink
    English
    arrow-up
    25
    ·
    edit-2
    2 days ago

    I’ll preface this by saying that I’m a Wayland user (Hyprland, then KDE Plasma, and I’ll be giving Cosmic a fair shot), and don’t see myself returning to X and having to choose between massive screen tearing and massive input lag.

    Wayland is missing many features that are required for some people or some applications. There’s no way for a multi-window application to tell the compositor where to place the windows, for example to have one window snap to and follow the other. Color profiles were implemented very recently. Wayland’s isolation of applications, while a significant improvement to security, has made remote input software and xdotool-like programs highly dependent on third-party interoperability solutions (specifically dbus and XDG Desktop Portal). The same isolation broke most accessibility tools like screen readers. Dockable windows, like the toolbars in QT Creator or QOwnNotes, are often difficult or impossible to dock back into the main window.

    Because Wayland compositors have to implement all protocols (as opposed to deferring to the X.Org server; which is why wlroots is such a big deal) or rely on XDG Desktop Portal (which has never worked right for me), feature parity between compositors is never guaranteed, and especially problematic with GNOME dragging its heels.

    Wayland is nowhere near feature parity with X11 today, and that is a legitimate prohibitive issue for many people. Wayland will never reach total feature parity with X11 in some areas, and that will always be prohibitive for some people.

    But the worst (in my opinion) is the development process of the Wayland protocols. The proposal discussion threads read like the best and/or worst sitcom you’ve ever seen. It took them several months of back-and-forth just short of ad hominem attacks to decide how a window should set its icon. Several months for a pissing WINDOW ICON!








  • TMI had zero fatalities, minimal release of radiation, and no measurable effect on health. Residents of the area were exposed to less radiation from the accident than the yearly background dose.

    Some layers of safety failed, but the rest did their job. That’s why we call it an accident and not a disaster. The plant continued to operate for decades with no issues. The only reason it’s so prevalent in the public consciousness is because of faulty reporting and irresponsible, ignorant people (like you) parroting the first thing they hear from sensationalist media.


  • Calling it “the worst nuclear disaster” is not just incorrect but stupid. Just off the top of my head, I can name a worse reactor accident and a worse non-reactor nuclear accident on US soil.

    SL-1, a low-power reactor in Idaho, exploded because of poor design and human error. An operator retracted the manually operated control rod too far. The reactor went prompt critical, causing a steam explosion, destroying the reactor vessel and killing all three operators. To this day, SL-1 is the only fatal reactor accident on US soil.

    Cecil Kelley, a worker at Los Alamos, was fatally irradiated when a plutonium reclaimer machine went critical. The machine contained an aqueous mixture of plutonium slag of a much higher concentration than it should have, causing an excursion when the stirring was turned on. He died two days later. His autopsy was performed by one Dr. Lushbaugh, who removed several organs for experiments without permission.

    TMI had zero fatalities, minimal release of radiation, and no measurable effect on health. Area residents were exposed to less radiation than the yearly background dose.