• 11 Posts
  • 113 Comments
Joined 1 year ago
cake
Cake day: July 22nd, 2023

help-circle

  • We survived the Cold War. We survived that mild awkward moment where there were just 10,000 humans or something. We survived the Paleolithic by throwing and walking kinda good despite having super-mediocre body builds compared to the lithe apex competition.

    Sure, a United Statesian might not know what price elasticity means when they go pro-tariffs, and shoot their foot on a national scale. Sure, “Eastern” youths might stretch themselves systemically thin to leap through an education colander into a limited, demanding job seat. Sure, there’s a whole terror cloister awkwardly just below South Korea, a crap ton of eyes on the Ukraine, and the new context of exponentially advancing tech compared to the last kabillion years.

    But I believe in the human spirit. Call me a fool. We don’t even need to be enlightened to not destroy ourselves. We just need to be what we always fuckin been, what we always fuckin will be.

    Stupid endurant.

    in all three senses of the shit.


  • You probably already know, but scheme artists avoid pure #000000 out of contrast concerns. (e.g. DarkReader can give some headaches if the background is straight black with offwhite text). That makes a #000000 scheme very rare - manual intervention required :P

    If you still wanna get crackin’, just tweak a preexisting dark theme and change navies/greys to black. And if you’re talking about the palette instead of actual themes to install, this still works – just check the source for whatever colors they’re using and tweak those. (grep for hexes then sort uniq? shell exercise is left to the reader)

    I’d recommend taking one of vinceliuice’s themes and just turning navy blues into blacks. For example, Graphite-gtk (has a matching qt theme) is pretty grey even with a --black tweak, but you could blacken it with some effort. Same with Colloid-gtk (also has a --black tweak).

    You could probably even blackify the KDE theme’s greys if you so fancied, but then you’d need to tune down the contrast on the other colors in the set. And this and that…

    If this is too inexact an answer, then ouch. I wish you luck!


  • fool@programming.devtoAsklemmy@lemmy.mlA/S/L
    link
    fedilink
    arrow-up
    1
    ·
    5 hours ago

    We have the Venn overlap of people who want privacy and people who dislike enshittification. Then some join Lemmy.

    ⇒Nonresponse bias by people who scroll by and don’t care to read other people’s info or post their own. Huge sieve, these comments aren’t even seen.

    Then we have curious people who are probably curious about tech or tinkering or protecting themselves or more organic forums like Lemmy.

    ⇒Nonresponse bias by people who check this out by curiosity (e.g. comment/upvote ratio, are people really giving out their info or faking it with jokes?) but then they definitely choose to not comment. They et al. might upvote the above comment or not, and nope out.

    We can’t even get good Linux user demographics. A large survey sometime back said “Wayland was leading over Xorg, according to users who replied” – obviously false, take a look at Indian corporate use of Ubuntu Desktop LTS, or the legacyness of X11.

    Blah blah, 2.5/mitosis/deep sea geysers



  • I assume the envisioned discussion was supposed to be

    Q: Thoughts on the Orphan Crushing Machine?

    A: The CDC says crushing orphans is bad for our health.

    A: The government in Orphania is expanding the definitions of orphans to all seniors, allowing a cascading orphan-crushing effect.

    where we all experience the same negative emotion in a fuller, mildly variable way.

    But yeah, it’s kind of… predictable, isn’t it?

    <thread> FOSS, big bad powerfuls, companies, governments, Stallman </thread>



  • So instead of commenting inside of nix files, you put nix files into .org documents and collate them so you can make your nix files an OS and a website and a zettelkasten-looking set of linked annotated nodes.

    That puts a stupid grin on my face (ᐖ )

    Dammit I was sure I was just going to stick with Arch until I saw this

    Questions:

    • You have home on tmpfs. Isn’t that volatile? Where do you put your data/pictures/random git projects? Build outputs? How’s your RAM? (Sorry if I’m missing something obv)
    • What’s your bootup like?
    • Another commenter mentioned difficulties in setting up specialized tools w/o containerizing, and another mentioned that containers still have issues. Have you run into a sitch where you needed to workaround such a problem? (e.g. something in wine, or something that needs FHS-wrangling)

  • The “stable unstable” setup is a beautiful concept. Thanks for the dotfiles mention – I keep hearing “you need to rebuild if you edit a dotfile” but I guess that’s a myth encountered by people trying to nix too nixily, falling into said archetypal rabbit hole

    Questions:

    1. Does mixing streams “infect” other packages? I remember an old Gentoo thing where ~amd64 unstable packages would want to spread on its own. Since it’s nix I assume that an unstable package will require a bunch of unstables but they’d be installed alongside respective stable versions – i.e. taking up disk space but not “spreading” per se

    For packages its basically 0 time.

    Is that really true for you? I assume you refer to the length of time it takes to copy paste a flake from online but how reliable is that really? And the other commenters mention that there’s still wrestling to be had for certain tools


  • Thanks for the input!

    I’m nervous about faking FHS as well, especially for specialized stuff. I don’t know much about steam-run or its caveats – so I can’t debug it (Maybe it turns out to be really simple and solid? Who knows…)

    Thanks for mentioning the gpu accel issues in distrobox – I was considering using containerization to fight off any FHS issues but it seems I can’t jump the gun. I’ll probably just tighten dev envs by trickling in nix-shell usage; multiple versions of a package at once is an issue I’d def love to solve (in a way that’s more than just dockerfile)

    Interesting that this is the third comment suggesting just using btrfs snapshots to resist Arch update experiences. I have root and home on two flat btrfs subvols so it shouldn’t be that hard to implement. (yeah yeah “What backup?” is bad)

    Seems like the simplest way out is those two smallish changes. Wish I could transcend into declarativity but the thread’s nix survivor ratio is grim




  • When it comes to installing stuff, I’m very trigger-happy. So, from experience…

    Installing stuff on Windows (safely)

    • Hope it’s on Chocolatey (choco install)
    • If not, search for the website online
    • Scroll past the AI slop and suspicious Softonic downloads
    • Click the website
    • Find the correct download button
    • Download
    • Scan with MalwareBytes (don’t want an STI)
    • Run setup.exe
    • Verify PATH and wanted feature set
    • I do not want to bundle Candy Crush or McAfee
    • skim the Privacy Policy to see if they’ll grind my bones to dust
    • Install Microsoft C++ Redistributable 2014-2018 (wtf? I already have 4 of these)
    • Wait
    • Sort the installation shortcuts into my folders

    Installing stuff on Linux (safely)

    • paru some_software
    • If on AUR, skim PKGBUILD
    • If not packaged at all (rare), git clone it and either skim the install.sh or Makefile
    • Done

  • Sometimes friends, in their curiosity, come up to me and ask me, Jordan Belfort-style, “Sell me this pen Linux.” Why do I like it so much, they wonder?

    And I always tell them:

    "Linux is like… the vegan OS. (bear with me) Mac and Windows people don’t really care about OSes. People who switch to Linux either find they couldn’t be assed to deal with it, or they love it, and those who love it love it. Then they always tell people lol.

    A good thing though: because everyone’s such an opinionated nerd, the lateral set of problems you run into won’t be ‘solved’ by random Microsoft Forums /sfc scannows or arcane regedits, but by a nut who debugged the entire thing 30 minutes after the bug came to exist to find a workaround. True story.

    Buuuut Linux is more of a lateral movement in terms of problems, it’s just a tool after all. You solve Microsoft Recall and start menu ads but run into new but tiny annoyances. I find Linux problems easier to fix than Windows ones because of the nerd army thing but if your Windows setup works for you, it works and that’s really all that’s important. If you do start Linuxing though you’ll learn a lot just by osmosis."

    And they usually laugh and decide to keep their routines in place. Don’t hate me vegans.


  • I use Firefox everywhere else, but for my Android I’m on Brave.

    Sure, adblock and tab grouping is a plus but my main reason I use it (i.e. over Firefox) is because of memory. When I have six FF tabs open, my Samsung model shoots at least three down the moment I enter another activity or open a new tab. They survive on Brave.

    I’d still use Brave on iOS devices too – as another commenter said, it’s a webkit reskin but at least it’s got good Adblock.



  • In a similar way, I’d learnt an eeny bit about visual composition at one point, and it’s helped me understand how something pretty can be uninteresting and something ugly can be interesting. (Maybe it was more obvious to everyone else, especially with the whole image gen sitch (ー﹏一))

    Oddly it’s made me respect internet-ugly MS Paint stuff more. Like this ancient shitpost.

    And nature too of course. The way a red sky refracts in cirrus clouds. Ladybugs on leaves. Elk.

    All stuff I normally wouldn’t have noticed :p




  • Wow, that’s definitely a few. Didn’t expect an entire set of chainmail to show up in these comments!

    And I seem to notice something:

    …the armor. But because I want to be done in less than a year (will be part of my wedding outfit)

    “Hey, what if I not only learn to play the [Hurdy (Nerdy?) Gurdy, but also learn to play it for my wedding”

    Someone’s wedding is going to be very interesting.