• 1 Post
  • 18 Comments
Joined 8 months ago
cake
Cake day: March 4th, 2024

help-circle
  • /mnt is meant for volumes that you manually mount temporarily. This used to be basically the only way to use removable media back in the day.

    /media came to be when the automatic mounting of removable media became a fashionable thing.

    And it’s kind of the same to this day. /media is understood to be managed by automounters and /mnt is what you’re supposed to mess with as a user.



  • Tracing a call is instant. It took longer back in the days when there were physical switches, but that’s been a long, long time ago.

    Yup. Back in the days of analog phone exchanges, you literally had to send a guy to check electrical connections between lines. Which is why it took time and which is why they encouraged the people to keep on the line as long as possible.

    Digital exchanges added call tracing as a design requirement. Everything gets logged. Even if you spoofed or blocked your number, the phone company knows what you did. They are the Phone Company.




  • Why would I want a whole circuit to be cut because of a single device fault

    Dunno, if I have a fault in my home, I want it to be spectacular.

    A couple of years ago I literally had massive blood pressure and walked like 2 km to go buy a box of fuses.

    Burning two fuses, I figured out one of the extension strips was bad.

    If I plug something in and half of my apartment goes black, TWICE, and needs a fuse replacement each time, maybe that thing needs to be tossed anuway. I’m no electrician, I can’t troubleshoot a power strip. It has served its years. Bye.



  • In Wikimedia projects (and MediaWiki systems in general) you actually have to pay attention to other people’s usernames (when working with histories and in article discussions), and at least in Wikipedia long long time ago there was a lot of trolling/vandalism where people impersonated other users (particularly the admins) and made bunch of sockpuppets with tiny variations in names when they got banned. So this rule makes sense.


  • umbraroze@lemmy.worldtoLinux@lemmy.mlWhat distro he uses? 🐧💻
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    7 months ago

    Debian, the cool guy distro in 1999. The machine overlords run on Red Hat.

    In the low budget parody version, Neo ran Slackware, and the climatic battle was basically about Agent Smith somehow fucking up his libc.so.6 but then Trinity got him a copy of the file on 3.5" floppy from another system. Or something.


  • Scrivener!

    The frustrating thing is that, at least for me, there are no perfect word processors geared for novels and other scenarios where you manage large text masses.

    Scrivener is one of those cases where you have a pretty excellent software that doesn’t have a lot of problems OSS alternatives have. I have smooth time with it. But at the same time, the software always could be better.

    Probably the best OSS novel writing software I’ve used is Org-Mode for Emacs. But, you know, it’s based on Emacs, so it squeaks around the edges and gives the impression that it’s a miracle it runs as brilliantly as it does.




  • Yeah, I just tried upgrading my Gitea Windows instance to Forgejo via Docker, and it actually works pretty much as easily as it did before. Fantastic! Might just leave it here instead of shoving it all in the VM - I can always do that later if it’s necessary. Having a full VM does have upsides, but in this particular instance this is definitely good enough.


  • Heh, your comment actually made me finally go and resolve a problem I’ve had since I got this laptop in 2020. I didn’t have SVM virtualisation acceleration enabled because that made Windows unable to boot somehow. A bit of twiddling after, it finally did! VirtualBox runs! Docker runs!

    …but why would I use Docker for something like this. Might as well blow the dust off of my FreeBSD virtual machine and run Forgejo there!


  • What’s the latest on Forgejo’s Windows builds? Last I checked there was no Windows build due to no volunteers for build/test - Gitea’s old build stuff should still be good.

    Which is a mild shame because Gitea’s Windows version was an insanely simple way to run it if you are a solo dev on Windows and need a private Git site. Drop the binary on an USB hard drive, run it on terminal, boom, done.

    (Currently contemplating just setting up a Raspberry Pi server.)



  • I’m going to just say that I’m exteremely sceptical on how this will turn out, just because there has been quite a few Wikipedia forks that have not exactly worked out despite the best interests and the stated objectives they had.

    Now - Wikipedia isn’t exactly an entity that doesn’t have glaring problems of its own, of course - but I’m just saying that the wiki model has been tried out a lot of times and screwed up many times in various weird ways.

    There’s exactly two ways I can see Wikipedia forks to evolve: Crappily managed fork that is handled by an ideological dumbass that attracts a crowd that makes everything much worse (e.g. Conservapedia, Citizendium), or a fork that gets overrun by junk and forgotten by history, because, well, clearly it’s much more beneficial to contribute to Wikipedia anyway.

    I was about to respond with a copy of the standard Usenet spam response form with the “sorry dude I don’t think this is going to work” ticked, but Google is shit and I can’t find a copy of that nonsense anymore, so there.