Does the adage “know your rights” simply denote “self-identify then stfu then get a lawyer” – and nothing else? If not, where can a layperson find the useful-to-knows? (Yes, look up local law, but it’s basically all scholarly articles or superficial news reports)

This part is the crux of my question

Pot Brothers! That’s the video I was thinking of.

Stfu is widely best (better to do nothing than go negative), but there’s the caveats of self-identification being necessary in some places, and drawing police hostility, isn’t there? (e.g. oh, we’re all nice and joyful? oh… no? nvm… hmm, I sense a traffic violation)

I’m primarily concerned about that part. What if stfu lets me get framed or get a short end of a stick? How do I prepare? Is stfu the be all end all?

Haven’t seen the Regent one, I’ll give that a watch.

Can’t Ventoy bypass secure boot with the shim thing? i.e. ENROLL_THIS_KEY_IN_MOKMANAGER.cer

Or is secure boot just to ensure that “this kernel uki hasn’t been tampered with”?

Furthermore, if it’s secure boot autounlocked by TPM, won’t I have to password protect my bootloader too to avoid kernel parameter oopsies? (Lol changing kernel parameters right then and there reminds me of the windows utilman trick)

The secure boot route seems fraught but perhaps I’m looking at it wrong

Organizing is one thing but it’s better to reduce your brainpower-spending regardless of what you do.

On Windows? Custom iconed folders and explorer bookmarks go a long way. Better than relying on Quick Access or whatever.

On desktop Linux? Tools like fd and zoxide (z) save you as long as your directory names are consistent. Sticking to names-like-this reduces guesswork and you can skip around in seconds. (Saved me many a due date.)

On Android, consult Indiana Jones. Your files are a treasure – they’re staying hidden

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!

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

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

Yep this is my diagnosis. I had a lot of time at the start to config horns and halos and miniguns and waffle toasters onto my craptop but now everything is constrained

o(╥﹏╥)o

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.

Building on this, I recommend zoxide instead of only fzfing or regexping.

For people who like to keep everything they ever create, like college students, you can use z 18.04/1 to get to a directory like ~/hw/random-school/fresh-1/analysis-18.04/pset1.

Lets you nest without fear.

(Also, about your question: I’ve personally used ~/git/<projname>/ and ~/git/<org>/<projname> at the same time – e.g. ~/git/aur/fuzzel-git)

Stunningly simple, solely a shift. I love MVPs… we can possibly even remove the -P completion func switch :P

At a level that the user doesn’t have much control over, I fear both stock systems are about the same in terms of privacy.

According to an analysis by Köllnig et al. (2021) on 500k+ free Google Play/App Store apps, tracker libraries such as Google Play Services/Apple’s SKAdNetwork/cross-platform libraries are used in about equal percentages on both app stores’ free apps. These free apps’ trackers are generally not configured to follow GDPR data-minimization practices, even for kids’ apps, but it’s to be noted that Android has a disadvantage in that advertising ID is more used in Android apps than Apple apps. However, Apple has disadvantage too: the researchers noted that Android’s intent system and different permission model makes apps seem “more privileged” than Apple’s, but Apple makes accurate analysis of their apps’ reach difficult, judging by the larger failure rate in app decompilation as well as the more opaque approach to permission disclosure. Although the paper might imply Apple has improved over time, since it mentions Apple’s implementation of opt-in tracking in 2021, after the study, as a limitation, keep in mind Apple’s new movement towards advertising as a form of revenue, as discussed by Apple Insider (Owen, 2022) and Bloomberg (Gurman, 2022).

Of course, Köllnig’s study only reflects tracking in “curated apps” for either platform. It does not discuss hardware/firmware/system app-level privacy, which users have little control over (Leith, 2021 – easier reading with TomsGuide). Leith found that either OS phones home (lol) every ~4.5 minutes, and even though Google may send more data (even from the clock app!), Apple profiles your social network via MAC addresses on your Wi-Fi as well as location geotagging, which the TomsGuide article called “quality vs. quantity”. This builds on the idea that Apple might seem more private, but only ostensibly so, judging by these more particular looks at their data collection and the trend of their increasingly data-focused business model.

Does that mean the choices between stock OS don’t matter? Well, no – as for me, who can’t afford a Pixel anytime soon, I’ve chosen Android on account of freedom outside of curated app stores. Yes, PrivacyGuides may not recommend F-Droid, but the opportunity cost in security there may be negligible compared to the convenient and easily-handled privacy received in exchange*, at least for typical less-savvy threat models like my own. (This favorability is illustrated in a forum debate here (Lukas, 2023), though in a context less relevant to stock OS comparisons.) Ignoring the facet of freedom with stock Android, the possibility of large privacy advantage one way or the other, strictly in terms of stock Android and stock iOS operating systems, is marginal if it even exists.