Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DG
Posts
2
Comments
53
Joined
4 mo. ago

  • One of my cats, despite being an extreme clinger, absolutely will not tolerate being picked up under any circumstance.

    Lone exception? If there’s a bug she wants but can’t reach, she will meow until I come lift her up to catch it. One hand under her hind legs, one under her stomach - so she has both front paws free to pin the bug with. Fortunately, she’ll let me summon her too, so whenever there’s a moth or something hanging out on the ceiling, I yell “bug” and the cat comes running to catch it for me.

    Right ol’ on-demand vacuum cleaner, that one.

  • There is a massive functional difference to anyone with two braincells to rub together.

    The core devs can (and should) step in front of a bus (or tank) tomorrow; the core project will just fork, and LW and the other non-triad instances will do fine without them. I’ve had no issue on Lemmy blocking .ml client-side.

    The only reminder of the triad’s existence is infiltrator trolls who make alts on other instances to post bad-faith arguments glazing the core devs.

  • You misunderstood the pinned post; it’s soliciting donations for core Lemmy development, not for the .world instance.

    The core devs use donations to the project to fund their tankie .ml instance, which is why they’re getting pushback. There is zero comparable pushback among the community towards funding .world or other instances.

  • Since it seems like you don't know much about bash at all, I promise the book will help you.

    You can be someone who actually knows what they're talking about instead of making embarrassing, snarky comments that expose your lack of education on the topic at hand.

  • Bash has had some nice minor features and syntax sugar added, but the fundamentals are entirely the same. All the examples in the book work just the same today as they did when it was written.

    What was added in 4.X or 5.x that you can't live without? What do you think has changed that merits inclusion?

  • It's a 36 y/o language, mate. I still reference my copy all the time, and found it to be a great definitive resource when I was learning.

    How many bash 4/5 features are you seriously using on a regular basis? What do you think is out-of-date?

  • I highly recommend O'Reilly's Learning the Bash Shell in paperback form: https://www.oreilly.com/library/view/learning-the-bash/0596009658/.

    The other responses you've received so far don't offer much insight into the historical background and underlying mechanics of the shell, which are crucial to understanding the "Why?"s of command-line quirkiness.

  • League ran fine for many years on Linux. The problem is Tencent, not Linux.

    Per Riot's own stats, the rates of scripting in competitive league went way up AFTER they rolled out Vanguard, so it's not about anti-cheat either.

  • I agree with your overall point.

    However, as a professional codemonkey, I promise you that root-level AC is in fact less secure than server-side heuristic AC + user reporting, and tends to be user-hostile due to false-flagging of modified systems. Root-level AC can be bypassed rather easily these days with DMA and other out-of-band tooling.

    As a case-study, League of Legends lacked any root-level AC for well over a decade, and was arguably the most popular game in the world at points. Cheaters were extraordinarily rare; the average player would typically encounter well under a dozen cheaters per thousand games.

    Riot Games then released Valorant with full root-level AC, and had an aimbot explosion within a few months - mostly because they devalued player feedback & reporting in favor of their “robust” automated AC solution. Their overall anticheat strategy became less reliable on the whole, but they stuck to it because root-level AC is cheaper and easier to execute from the corporate-profit POV.

  • For anyone who missed it, the Windows Terminal team is infamous for claiming that it would require PhD level expertise to implement some basic optimizations suggested in a Github thread. Within a few hours, another developer countered that claim by submitting a functioning PR with said improvements implemented.

    Windows Terminal team lead Dustin Howett then went on to double down on the original claim that said optimizations were unfeasable, and publicly attacked the author of the original suggestion thread on Hacker News. He issued an extremely half-assed apology and is still a Micro$haft employee to this day.

    https://blog.royalsloth.eu/posts/it-takes-a-phd-to-develop-that/

  • Synology runs a proprietary OS OOTB that's had multiple sloppy vulns exposing full remote access to users' files. Putting your data in the hands of fuckups who have and will continue to leak it is the opposite of total control.

    It's completely trivial to store any data you want to in a cloud provider 100% securely just by piping it through openssl before uploading.

  • See also: atuin - a shell history tool that records your shell history to sqlite.

    Seamless sync across shell sessions & machines, E2EE + trivially self-hostable sync server, compatible with all major shells, interactive search, etc.