grep_name

Eh. Your argument keeps coming back to that same snippet from Wikipedia, which is unconvincing. Wikipedia isn't the end-all-be-all arbiter of language. "Social media" is a useful term for discussing a lot of specific phenomena that have come out of sites like facebook, instagram, twitter, etc which all rely on metrics of social graphing to track popularity and guide content exposure and interaction. (Due to the nature of your argument I feel compelled to say that I'm not trying to formalize a complete airtight definition here)

There is a distinct experience and ecosystem that arises from those types of sites that we all recognize, which didn't exist in the same way before the advent of social media sites. And it warrants discussion. When you try to say "actually, technically, ALL human communication is social media!" and won't let it go, you derail a conversation in a way that benefits nobody and is functionally (if not literally at this point) untrue for anyone who's experienced the internet over the last 20 years.

This doesn't pass the smell test for me.

It seems like you've taken a system of reasoning that was built through careful consideration (Kantianism), called the conclusions it meticulously built 'presuppositions' and hand-waved it without making substantive counterpoints.

The problem then, of course, is that burning down previous philosophy and starting 'without presuppositions' will lead inevitably to conclusions again, which you can once again call presuppositions and hand-wave.

Surely there is a makerspace in Seattle? The one near me in Atlanta has all the things you mentioned and more, plus an abundance of space, a neat community, and classes for most skills you could use there

Eh. I've been using nixOS for years now and still find that I often desperately, desperately wish I could upgrade just one program that I need a new version of without risking that, you know, any individial single one of my installed packages has a change between the last update and now that messes up my workflow. Or that I could pin a version of a software that I'm happier with that version of without essentially rolling my own package repo. It is, in fact, the only package manager I'm aware of that makes it such a pain to do that. It's only because people in this thread are insisting it's doable that I say 'such a pain' instead of just 'impossible'.

A few weeks ago I needed to update firefox for a bug fix that was causing a crash, but of course that meant updating all of nixpkgs. When I finished the switch, the new version of pipewire was broken in some subtle way and I had to roll it back and have been dealing with firefox crashing once a week instead. I can't imagine pitching this to my team for development when I'm having this kind of avoidable issue just with regular packages that aren't even language dependencies.

To those who say 'if you want to lock your dependencies for a project, you can just build a nix flake from a locked file using the <rust | python | npm> tools' I say, why the hell would I want to do that? Being able to manage multiple ecosystems from the same configuration tool was half the draw of nix in the first place!

This looks interesting, just speed-read the readme. Is there a way to use this from the commandline, similar to steam-run, if you're just trying to sloppily check out some repo without building a whole flake?

I tried doing it for awhile but wasn't able to ever get it to work for the main project I was trying to build, which was a VR project called LÖVR. I could have made and submitted a package using one of their appimage releases, but was doing it as an exercise to see how far I could push things.

I also went through a phase where I had AI write a lot of simpler flakes, but they turned out surprisingly different from each other, enough so that I wasn't able to learn a pattern as a base to grok what was happening. At some point I'll try again from first principles, but for some reason the AI flakes hindered more than helping

C/C++ is a PITA and I'm not a C/C++ developer, but I do find that I'm able to get around the issue 90% of the time using steam-run (although that feels kludgy as hell and I really wish there were a better option for getting linked libraries working normally). I think the real answer is to get good enough with nix to build a flake quickly for the project you're working with, but that seems like a lot to learn. Maybe easier if you're more familiar with C/C++ dependencies and build tools than me though.

Musnix looks really interesting. My whole audio setup looks like this in my nixconfig:

   hardware.pulseaudio.enable = false;
   services.pipewire = {
     enable = true;
     alsa.enable = true;
     alsa.support32Bit = true;
     pulse.enable = true;
     jack.enable = true;
   };

   hardware.bluetooth.enable = true;
   hardware.bluetooth.powerOnBoot = true;
   services.blueman.enable = true;

This works great for my workflow of using headphones + BT 100% of the time, but weirdly it almost never works for the built-in speakers on my framework. I might try musnix if that ever bothers me, but it's actually kind of a feature for me since my laptop can never just start blaring whatever I was watching / listening to into public

I thought I was pretty clear? It would be nice to be able to call functions from org-mode and its related packages without having Emacs installed, or with some minimal subset of emacs meant for the commandline which caters to the needs of people running headless commands. It would solve a whole ton of issues for me. In particular, org-roam-ui is amazing. To run it, I have to open emacs and then... have emacs launch it into a browser for me. But the hosted interface won't export to anything that can be statically (or dynamically, really) hosted, so I can never access this awesome note-viewing interface from the web, even though to do it locally I already have to use a browser?

I have a project for hosting org-roam-ui as a website that took a ton of finagling to figure out and is extremely brittle. I had to finally load a custom .el script to prepare emacs to even try to evaluate the 'org-roam-ui' command from the commandline. If emacs prioritized headless / cli operations, this wouldn't have been such a nightmare, but it absolutely was. Just finding the right ports and re-assigning them to get out of each others way was a huge learning curve even for a seasoned emacs-er.

> It's like wishing for java programs to be able to execute without JVM, or Erlang-code without BEAM

No, it's not. It's wishing for basic functionality offered by all other markup languages of which I'm aware. That includes latex and everything supported by pandoc. Org-mode can do all sorts of crazy rendering tasks from its files, and it is worse than pulling teeth to get that functionality into a build pipeline of any kind.

Do you use guix? I've used nix for years now, and I really wanted to use guix instead, but I could never wrap my head around it for some reason. Once I installed nixOS, I felt like I could just kind of get rolling without the confusion. I couldn't tell you where that confusion comes from though.

However, after these last few years, I have a few gripes that I'd like to check with a guix user to see if they're represented in guix.

1) I can't easily pin a software I'm using to a specific version, it seems like everything has to be from a specific hash of nixpkgs

2) Relatedly, I can't upgrade firefox without upgrading every single piece of software installed on my computer

3) Dynamic linking doesn't work. I can get around it with steam-run, but that's hacky and I worry it won't be supported forever

I use nixOS, do a ton of container development, and have never had issues or been confused about containers? I have two lines that enable docker in my nix config:

    virtualisation.docker.enable = true;
    users.extraGroups.docker.members = [ "green" ];

Since then, docker's been completely seamless. How far into kubernetes have you gone before? I'm a little confused about what you mean by "Install kubernetes". I used to use minikube but now use k3d, and those were both just packages available in nixpkgs. K8s (especially local k8s) is kind of hard to wrap your head around, but not because of NixOS

Not the parent, but I also tried to switch around two or three years ago and was very frustrated. The draw was the 'built-in LSP' with all these new features, along with treesitter.

'Built-in LSP' turned out to mean installing and configuring three pretty involved lua plugins at the time iirc. The experience really highlighted for me how un-seamless lua was in the project compared to vimscript. I found it to be a nightmare to configure and get used to. I came away wondering how it could possibly be such a pain, and baffled as to why it was claimed to be 'built-in' when getting ALE to work on vanilla vim took way less time, and felt way more in line with the rest of the program. Ironically it actually gave me an appreciation for vimscript that wasn't there before.

Eventually issues continued to kind of build up for me until I decided to just cut it. Everywhere I encountered lua felt crufty and difficult to work with, and those integrations made the concise, tight vim I'd gotten used to feel really nebulous and unweildy. I never quite got the treesitter syntax highlight to work correctly, and even when it did work having the highlighting dynamically change while typing frustrated me. I ended up slowly switching back to my old vim-compatible plugins one by one, until eventually I just went back to vim, since a lot of the neovim features that diverged from the original design philosophy bugged me and since I'd developed a strong aversion to anything involving lua in the program I wasn't getting anything out of using neovim.

People definitely sleep on emacs, which is a shame, but I do get it. I switched to emacs fulltime for coding for my work a few years ago, and really had it tailored to my preferences but drift (that took just slightly too long for me to keep up with while on the job) combined with AI features in other editors led me to land on Zed for code, which saddened me but is probably the best fit for coding.

However, Org-Mode is seriously a killer feature that is well worth it on its own. I use emacs to handle all my finances, notes with org-roam, blogging with ox-hugo, dotfiles in a massive org-tangle document, etc. I couldn't find anything remotely to compare it to, and have failed attempts at switching. There are tons of ways of interacting with Emacs that are just lightyears ahead of anything else. Literate programming and tangle are a godsend for tons of different use cases for me as well. I even keep running notes in the base of my codebase so I can hop to various files and capture locations in the relevant files as links in notes.

The only pain point for these tools for me is trying to use them as part of a commandline integration. I really wish org-mode and org-roam's functions were callable outside of emacs, e.g. for automated document generation from org-mode. One of the most painful things I've had to setup is an org-roam-server integration that updates and deploys org-roam-server when the git repo containing its files is updated. Only way to do that seemingly is to run emacs in a very strange way inside of a docker image. Intuitively it feels like org-roam-server should be able to build itself into a static website for deployment. Might seem like a nitpick, but it's really not -- that interface is a huge part of why I use it and not being able to host it without horribly hacky workarounds seems like a massive weakness.

If abbreviations aren't allowed, couldn't you just do "6SPEED"?

Thank you, the pass / fail addon will help a lot I think, in addition to the FSRS features included in the article. I'll come back to this comment for setting up my settings before starting up again with Anki.

If I'm planning to learn several topics at once (I'm never preparing for anything I will be tested on or hit a deadline for, this is not for a school, work, or travel program), is it better to treat the decks as one big combined review do you think?

I've tried to get into anki a bunch of times but never stick with it. It's an on-and-off thing for me that I end up looking into again every few years, which I've gone through about 5 times now. Here's how it usually goes:

* Get interested in memorizing something / multiple things

* Find that the decks available to me are actually not so great

* Get reading online, people say that the real way to benefit from it is to make your own deck (which ups the time commitment significantly)

* Read online about how to get the most out of anki, find out that everyone universally agrees that the default settings are terrible but nobody quite agrees on how to set it for best results

* Try to hit a happy medium, but find that the overhead of 'rating' the difficulty of recall for cards (and how it interacts with the complex settings that I still don't have complete confidence in) adds an incredibly (to me) distracting amount of overhead and never get used to it

* Miss a few days, get overwhelmed with the amount of cards stacked up, don't feel good about my settings (which have implications for what cards show up like, a year + down the line)

* Ultimately fizzle out

I'm probably going to start the cycle over again soon. I really do want it to work out for me. Any tips to avoid this issue? I'm planning to actually pay for some decks this time to see if that gets me to the quality I want, and going to skip the whole 'trying to make my own deck' thing for now

Well, that character judgement (if you want to call it that) was based on dillydog's shared thoughts about a long article that itself reflects a very specific way of viewing people. To compare that conclusion to someone who purports to confidently extrapolate someone's self-worth, philosophy regarding how they view themselves and others, the 'narrowness' of their understanding or love for the world (what?), and more just by watching them stand around at a wedding for an afternoon seems strange. It's a much more solid base to draw that conclusion from, in my opinion. The character judgement is that they are "a person who affords everyone a rich and deep inner life," and the judgement comes from the fact that applying their perspective is impossible unless they afford everyone a rich and deep inner life. It's emergent from their stated philosophy in a way that the examples in the article are not.

> My read of the article is that the author ascribes negative traits without judgement and just as easily as positive ones

I don't think this is true at all? The 'negative traits' she assigns to people are things like desperation, self-hatred, 'hating the world (or having a very narrow understanding of it)', 'thinking they are better than everyone'. It's hard to call those categorizations anything but judgemental. She even goes as far as to say she has a 'favorite kind of person' by these categorizations. That she ascribes them as easily positive ones is meaningless. It's the ascribing that is the problem.

My take away is that the article is a small list of things that most people know (i.e. it's easy to tell if someone is actually interested in something or not) paired with a series of ways to judge someone based on some extremely surface-level traits, which slowly veers into a sort of prescriptive take on which combination of those traits makes a person identifiably good. It has a feel-good tone, but I found the article difficult to get through because it put me off so much.

> Heck, as I see it, big part of empathizing with someone is recognizing how all their conditions and traits are natural and operate similarly inside ourselves to one degree or another.

See, to me applying the 'insights' outlined in the article seems like the opposite of empathizing. It's couched in gentle phrasing, but it essentially boils down to "here's how you put someone into a box by looking at them."

> Playing an instrument is a complex skill that requires a lot of work and an expensive piece of equipment

Or it's something you just, you know, do? I listen to and play a lot of tunes from the Appalachians and you really do get the sense that just about everyone played something back in the day. They developed complex and extremely localized traditions that did not require formal music education to pass down. Some of them were musical geniuses, many were middling, just like with most things people do.

Even poor families would often have an heirloom fiddle around to learn to play on (sometimes even brought with them from Europe), and ownership of family possessions was much more communal. Many parlors or bars would have a banjo or parlor guitar around for whoever wanted to make some music while hanging around. Those without access or with limited woodworking skill also often made their own fretless banjos (which look different from what you might normally recognize as a banjo) out of wood and hide, or other simpler instruments like dulcimers. Not that there weren't also semi-skilled luthiers making non-concert-grade fiddles at more affordable prices. All this culture is well documented in the Foxfire manuals on Appalachian folk traditions, complete with schematics on how to make those things from different regions. Pretty far from 'made up'. Hell, a lot of American music traces its roots back to music made by actual slaves. It's hard to think of a group of people with less means and access to the things you've mentioned, and yet, music.

Music theory may have a nearly limitless ceiling for both complexity of understanding and expense of instruments, but your statement here completely ignores the entirety of global folk tradition. And it does seem like an accurate observation to me that participation in casual musicianship in everyday contexts has declined significantly in correlation with a lot of the trends in modern living.

As someone who's been to Scotland but not Ireland, do you have midges?

I've been using nixOS on my laptop for over a year now and I still don't have an answer for 'my version of firefox/darktable has a bug in it, but I can't update it without upgrading the entire rest of all the software installed on my machine.' I keep thinking there has to be a way around this, but it doesn't seem like there is one that's clean and not hacky / brittle. Other than that I love it, but that's a pretty huge caveat

> Compared to basic RAID to get support for magical hard disks that can be yoinked without affecting workloads?

These things aren't mutually exclusive though. I've spent the last few years working with kubernetes at work and running a 'simple'(but with tons of containers and weird edge cases / uses) unraid server at home for all of my needs. At some point I flipped over from 'jeez kubernetes is just too much, almost nobody should ever use this' to 'wow I have to migrate 99% of my home services to a cluster, this is driving me nuts.' I haven't quite gotten around to that migration, but I do think that k8s cluster for services / temporary storage / parallel jobs and separate unraid box that runs NFS (and doesn't do much else) is going to be a great setup for a home lab.

Not the GP but for me personally, no, never. I only sync a couple of text files which I update and reference regularly enough to need them to be synced across machines constantly.

I don't really understand HN's seeming aversion to having a headless server that handles centralized tasks like downloading, storing, and serving files. It's a great model for personal computing with a ton of upsides. As far as I'm concerned all storage on my laptop is totally disposable, and I should be able to wipe and reinstall everything quickly without loss of important data.

I've been meaning to migrate to tube archivist forever, but I have several TB of youtube videos I don't want to re-download which I gathered using tubesync. Luckily I have the format string used to save the files by name and since tubesync uses django and a postgres backend I might be able to tie them to the youtube ID. But migration still seems like it might be a bit of a nightmare

> contact info: mail in profile

I don't think it is actually. Lot of shared interests here though

Just my experience, but I absolutely had to take an ethics class to get my CS degree. Not just any ethics class either, but one focused specifically on real-world implications of the work software engineers do, with breakout labs to discuss various case studies and evaluate different choices based on established ethical frameworks. The textbook used was 'Computers, Ethics, and Society,' and I reflect on that course more than most courses I completed in college

I remember that now. It really is frustrating that this is what passes for a really open device in the e-reader space. I would pay a 3x markup easily for the same device running KOReader natively (not sideloaded through nicklmenu after starting up the proprietary operating system) if it would just let me use the device like I own it without authenticating with a 3rd party just to its most basic functionality.

> it's an open device

I actually also own a kobo and have been running KOReader on it for a couple years now, but my memory is that when I first got it I booted it up and it requested to be connected to the internet, then wouldn't allow me to progress without logging in through a 3rd party (there were many offered, walmart.com was the first option listed). I remember having to do something weird to bypass that (removing a .db file I believe after connecting via commandline?), and then ending up in a state where I don't need to connect to some company's cloud login but I also can never connect this device to wifi, ever, or it will do that again.

Are they more open these days?

I don't think seatbelts are an honest comparison, nor are you representing the arguments of others fairly here. Seatbelts are a strap you add to a chair. They don't significantly affect the function of a car, don't add much to the maintenance overhead or up-front cost, they are easily removable/replaceable, etc. This is a much more invasive legislation.

I actually love sawstops. In fact I don't use table saws that don't include that functionality. But I would never, ever push for this kind of legislation. I'm not sure if you (or anyone commenting here) have ever used one of these saws personally, but the added expense and ongoing operating cost is not negligible. It's about $150 to fix it every time it triggers. People love to say 'cheaper than a trip to the hospital!' and while that's true it's also pithy and hand-wavy given how often these things trigger.

There are a ton of edge cases that can make these trigger (including mysterious triggers that seemingly have no cause), and there are whole classes of people who don't make enough to deal with that regularly but still operate saws safely for entire careers. Those are the people that are upset, not hypothetical hobbyists, who are the most likely to be able to afford the extra cost and be able to always operate in pristine conditions.

Powertools in a site setting need to operate in all kinds of conditions, and for a jobsite saw the money spent installing sensors and gadgets to meet regulations would be better spent on literally anything else for such a tool. People working in those settings are just going to turn this feature off and will strictly be hurt by this. (There's no way they can force these features to be always-on as that would prevent tons of materials from ever being able to be run through a table saw again.) To make it literally illegal to produce the right tool for site workers is an overreach coming from out of touch people.

Woodworking is an interesting space where people generally accept the risks they take and in return are more or less trusted to make that assessment by regulatory bodies at least in the US. A better comparison than seatbelts would be the european regulations around dado blades, which as I understand are fairly unpopular. Sawstops are great for HN types. That doesn't mean it should be illegal to produce sensorless saws.

The only thing that keeps me from trying nebula is my inability to download videos. There are very few youtube channels that I particularly care for, some of them are pretty small and over the years I've found myself recommending things that have disappeared to people one too many times.

So I run an autodownloader that downloads a bunch of channels as well as my liked videos for posterity. I'd like to give nebula a try, but ultimately it's important to me that I'm able to save the content I consume and access it later

It's good to see the other side of this. I don't use most social media apps, but I had a friend who told me they used tiktok mostly to see videos about 'foraging and luthiery', which gave me pause. Sometimes I wonder if I could benefit from the platform if I had the right subs. Maybe even learn something interesting.

Ironic to see that tiktok is being made worse by trying to compete with youtube. I absolutely hate youtube shorts and am annoyed to no end that I can't remove them from my youtube experience. Doubly ironic that I'm more likely to give tiktok a chance than to ever succumb to youtube's wheedling insistence that I click on their 5-second content clips.

How is this different from tmux popups though? I think I have the exact same workflow in tmux