Admiral Patrick

I’m surprisingly level-headed for being a walking knot of anxiety.

Ask me anything.

Special skills include: Knowing all the “na na na nah nah nah na” parts of the Three’s Company theme.

I also develop Tesseract UI for Lemmy/Sublinks

Avatar by @SatyrSack@feddit.org

  • 123 Posts
  • 1.21K Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle
  • Yeah. On the surface it seems like it would be a positive. But in practice, it shields people from criticism of their behavior.

    Yeah, yeah, “use your words” and all that, but some comments are just so brain-dead or trollish that they’re not worth a response, and even a downvote is expending far more effort than the comment is worth. So the person who made it sees 3 upvotes but not the 50 downvotes, so their takeaway is that “wow, 3 people liked my braindead comment” rather than everyone except 3 people hated it.

    I get the appeal of disabling downvotes, but if I say something stupid, I wanna know.














  • Yep. Works great, at least for my small instance.

    You have to install the ffmpeg-vaapi plugin and then under Config->VOD set the profile to the vaapi one it creates. I’m not using remote runners, but from what I’ve read, this doesn’t work with remote runners since you can’t install plugins on those. You may be able to shim in rffmpeg instead, though.

    The only sticking point is I cannot get the peertube user (inside the container) to consistently have permission to write to /dev/dri/renderD128 .

    Eventually I’m going to tweak the image so this isn’t necessary, but for now have a startup script that brings up the stack and chmod’s the device endpoint to allow any user inside the container to write to it:

    #!/bin/bash
    cd /opt/peertube
    docker compose up -d
    docker compose exec peertube bash -c "chmod o+rw /dev/dri/renderD128; ls -lah /dev/dri/renderD128"
    

    Rather than have Docker engine manage the stack’s lifecycle, I have that startup script called by a systemd unit (ExecStop just does a docker compose down).

    Edit: The other sticking point I ran into is the video studio not working well (or at least the few videos I tried). I haven’t really tried to pin down what that problem is.

    Edit 2: I did have to build a custom image to include the Intel drivers/modules.

    debian.sources (copied from the bookworm image and edited to include non-free)
    # http://snapshot.debian.org/archive/debian/20251117T000000Z
    URIs: http://deb.debian.org/debian
    Suites: bookworm bookworm-updates
    Components: main non-free
    Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
    
    Types: deb
    # http://snapshot.debian.org/archive/debian-security/20251117T000000Z
    URIs: http://deb.debian.org/debian-security
    Suites: bookworm-security
    Components: main non-free
    Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
    
    Dockerfile
    FROM chocobozzz/peertube:production-bookworm
    COPY debian.sources /etc/apt/sources.list.d/debian.sources
    RUN apt update && apt install -y --no-install-recommends vainfo intel-media-va-driver-non-free
    

    I should probably add the step here to setup permissions for /dev/dri/renderD128




  • Agree. Which is why I get so irrationally annoyed when sharing a good piece of journalism that’s not catering to ad-clicks and the peanut gallery here grabs their torches and pitchforks while shouting “PaYwALL!” despite me posting the gist of the article in the post body (enough to get the gist but not the full article for copyright reasons). It’s one of several reasons why I don’t even bother anymore.

    Like, good journalism costs money. That money’s gotta come from somewhere if you want good journalists to be able to eat and keep doing what they do.




  • The thing about these deprecated tools is that the replacements either suck, are too convoluted, don’t give you the same info, or are overly verbose/obtuse.

    ifconfig gave you the most relevant information for the network interfaces almost like a dashboard: IP, MAC address, link status, TX/RX packet counts and errors, etc. You can get that with ip but you’ve got to add a bunch of arguments, make multiple calls with different arguments, and it’s still not quite what ifconfig was.

    Similarly, iwconfig gave you that same “dashboard” like information for your wireless adapters. I use iw to configure but iwconfig was my go-to for viewing useful information about it. Don’t get me started on how much I hate iw’s syntax and verbosity.

    They can pry scp out of my cold dead hands.

    At least nftables is syntax-compatible.