silent_water [she/her]

wait, no, this is how everyone does math. right? …right?

idk, I just know that the old instance already have problems with power users and reifying that will make the problem worse.

I think this was always an intended feature (I’ve certainly been hearing about it for years as something people want/devs want to add), in addition to a user tagging system (i.e. users adding tags to their own usernames (e.g. pronoun tags). the main difference, though, was that it was something the poster or mods/admins could add and not something for the userbase at large to vote on. I think making it a voting system allows abuse. like consider a large group of transphobes adding tags to posts in trans comms, for instance.

a trusted user system is it’s own can of worms.

adhd posting tip: when you inevitably write a 2000 word response to someone, go back when you’re done and rewrite the first paragraph so it actually sets up what you ended up writing about - cause otherwise it’s confusing for other people to read.

vegan archbishop also sounds pretty cool but then people are gonna assume you’re catholic

nix overall is a much better solution to this problem.

no joke it’s how I learned linux, bootstrapping a gentoo install from the toolchain on up, with a printed manual. it’s surprisingly effective, if time-consuming (took me about 2 weeks to get to a booted system, though most of that was compilation time - took ages back then).

I don’t want Google to have my info. the ads are secondary.

literally every other distribution can solve this problem but Ubuntu can’t?

I think one of the issues with nixos learning materials is that they eschew talking about how to write your own packages. but to really understand anything, you have to get your head around writing and modifying packages. in nix, a package is just a build step that can do I/O during particular phases and produces an output to the nix store, so they’re an essential building block for anything that isn’t utterly trivial.

the other major stumbling block is working out how modules (the things that let you write config for the system) can actually be composed. adding a new module to imports gives you new config params you can set so you can organize your system config in terms of modules and packages to make things work the way you like.

Nix Pills are the canonical learning material for packages. I don’t know of any good learning material for modules - I learned by working on nixpkgs and another involved project that made extensive use of modules.

lastly, nix config files are written in the nix language and it’s a bit idiosyncratic. it almost looks and feels like Haskell but it’s slightly different in important ways. there’s no way around learning it if you have multiple systems and want to share config between them.

frustration, usually, hoping against hope that the answer is relevant.

I use stackoverflow for minutes at a time and it almost never has answers to the questions I need answers to. if it has an answer, it’s usually “you can’t do that”. reference docs are 100% of the time more helpful. so no, I don’t think so.

the owners of SO make far more than the benefit provided to any single dev. if that were not true, they wouldn’t be in business.

proper earbuds will block out most everything. get ones that actually fit into your canal and play something you’d rather hear. when I put mine in, I literally can’t hear anything but my music.

kids are people, but yeah, point stands

To those passengers who got mad, you know what I think: Fuck you!

based

yep stuck on Xorg forever gang

dear god if I could just run xmonad and dmenu on windows or mac I’d hate employers that tried to force me to use one or the other so much less.

when you say “something is not properly supported” what do you mean? like nvidia/amd haven’t released graphics drivers yet for linux? or some peripheral isn’t recognized?

basically, by buying new hardware just after it launches, you’re effectively one of the very first people to boot that hardware with linux. you can usually make it work but most hardware manufacturers don’t work with the linux devs to make sure support is in place. so devs have to get ahold of the hardware retail and then fix whatever is broken. the exception to this is AMD and Intel - both companies have people working on linux so they will merge support for new hardware into the kernel before that new hardware is even announced to the public. so if you stick to cpus and video cards from those two manufacturers, you’ll make your linux life easier.

even then, though, the support might exist in the latest version of the kernel, but the last Ubuntu or Mint release is still several versions behind. so you’re effectively forced to use a distro that releases updates much faster (ie rolling release), or be willing to make modifications to the system post-install to get it to work.

tl;dr: you’ve got a constellation of requirements that can’t all be met at the same time. either give it 3 to 6 months after release of new hardware or be willing to learn how to make it work. expecting software to work with hardware it hasn’t yet been designed to work with is always going to be a recipe for failure.

more stuff just works, if it doesn’t, you might be able to fix it but it’s rough.