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 @[email protected]

  • 848 Posts
  • 5.22K 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.
























  • RNode and Meshtastic cannot interact.

    I did ask in the Reticulum Discord if it was possible to run Reticulum over Meshtastic by using the serial transport in Reticulum connected to the serial module in Meshtastic. It is technically possible but inefficient. The person who answered my question said you’d need to use Meshtastic in ShortFast mode to make it even remotely practical.

    Essentially it was using the serial transport connected to a Meshtastic node in place of the RNode thus allowing the Meshtastic device to perform the role of both.

    [Reticulum] --Serial Transport---> Meshtastic Node's UART1 ---> Meshtastic Serial Module --->Meshtastic LoRa  ---> Remote Meshtastic Node's Serial Channel --> Remote Meshtastic Nodes UART1 --> [Remote Reticulum Client]
    
    

    They also pointed me to a Github project of theirs that basically did just that, but I cannot for the life of me find it to link it.






  • 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