• 0 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: July 21st, 2023

help-circle





  • glue_snorter@lemmy.sdfeu.orgtoAsklemmy@lemmy.mlBypassing "wifi pausing"
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    2
    ·
    10 months ago

    Racial origins of those terms? Citation needed.

    Black and white, in the sense of good and evil, have had their connotations for a fucking long time, whereas black and white to describe skin colour are relatively recent etymologies. I’m pretty sure that Romans didn’t call themselves “white” or others “black”, for example.

    I’m willing to be taught, but this sounds like bullshit to me.

    The etymology being wrong doesn’t mean that we shouldn’t drop freighted terminology, I just don’t want false justification. Bullshit is never a valid reason to do something.


  • Pure FUD. Worse, it’s wilfully stupid.

    Are you in the habit of picking pipeline commands at random? Do you not usually have a purpose in mind? OBVIOUSLY the receiving end has to understand what it’s receiving, or what the fuck are you even doing?

    Do you believe that your text processing commands don’t have to understand what they receive?

    Let’s get the ports of the node container.

    Bash:

    docker ps | grep node | cut -n 6 -f ' '
    

    Pwsh:

    docker-ps | where name -eq 'node' | select ports
    

    First the grep command shits the bed because at some point you started a new container running a nodejs image.

    Then the cut command fails because you had a container with a space in the name, so it outputs mounts instead of ports.

    That’s a non-issue with sematic tools. Semantic tools are also legible. Yeah, I can figure out what that awk command does, but it’s meaningless unless I also know the shape of the data is supposed to operate on.

    You don’t write “USE 2nd DATABASE; SELECT 3rd COLUMN FROM 10th ROW”, do you? Why would you want to do that in a shell?




  • My understanding is that the Windows terminal sucks? I don’t know why, it just looks bad.

    Your understanding is wrong. I’ve tried 8 different terminals on mac, arch and kubuntu, and I miss Windows Terminal every day. It looks good and the config is a pleasure. I don’t expect Linux to look pretty, but MacOS had fucking awful font rendering and it’s supposed to be this upmarket OS for moneyed pricks in black turtlenecks. Was everyone in unixland busy doing drugs while Microsoft was implementing anti-aliasing? Is clear legible type for losers?







  • glue_snorter@lemmy.sdfeu.orgtoSelfhosted@lemmy.worldOld PC as Server
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    11 months ago

    It’s OK, but I’d suggest:

    Atom > arm64 > arm32

    I ran on a Pi 4, but switched to a PC for jellyfin. The pi can’t transcode for shit. It was slow to boot and slow over SSH.

    Look for a NUC - they’re designed for desktop use, so they have more poke than a Pi. The N6005 CPU is a good choice, the N5105 is ok. These are x64, so you’ll have the widest range of packages. 4GB will do, if its upgradeable later. NUCs usually take SODIMMs, which you can pick up on ebay for peanuts.

    Bear in mind that network chipset will be your bottleneck in some use cases. If it has a “gigabit port” but only a cheap chipset, and you use it as a router, you might max out at ADSL speeds… in that case you’ll wish you’d gone for a box designed for soft routing, which are a fair bit pricier.



  • They don’t supply PoE, mind.

    I’m planning an ubiquiti deployment:

    • 5-6x AP 6 Pro (haven’t done survey yet)
    • 1x TL-SG1016PE PoE switch (yuck, but cheap)
    • 1x R86S running opnsense and docker VMs, with unifi controller and pihole in docker

    The R86S is the same price as the dream machine, but good luck running pihole on the DM.

    I considered Mikrotik, but my mum would have to call me every time there was an issue, and it would only be marginally cheaper. I expect any competent local tech to be able to support unifi and opnsense.