I’m beautiful and tough like a diamond…or beef jerky in a ball gown.

  • 3 Posts
  • 67 Comments
Joined 4 months ago
cake
Cake day: July 15th, 2025

help-circle




  • Iced Raktajino@startrek.websitetoSelfhosted@lemmy.worldJellyfin Dongle
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    6 days ago

    Maybe one of those HDMI “stick” PCs you can get? There’s x86 Android builds you can run or you can do like I did with my media PCs and boot into Openbox and just launch a fullscreen browser right to Jellyfin and control it from your phone. (My main setup uses Emby but should be able to do the same with JF).

    I’ve actually got a portable Jellyfin server I take with me. Built on the OrangePi Zero 2W with a USB->NVMe acting as media storage (as well as the Jellyfin DB). It’s got several other services running as well as a second Wifi adapter so it can also act as a travel router.

    For playback, I pretty much just use my laptop or phone but have thought about adding one of the “stick” PCs as a client for it.





  • The only reason I gave up on Docker Swarm was that it seemed pretty dead-end as far as being useful outside the homelab. At the time, it was still competing with Kubernetes, but Kube seems to have won out. I’m not even sure Docker CE even still has Swarm. It’s been a good while since I messed with it. It might be a “pro” feature nowadays.

    Edit: Docker 28.5.2 still has Swarm.

    Still, it was nice and a lot easier to use than Kubernetes once you wrapped your head around swarm networking.


  • I had 15 of the 2013-era 5010 thin clients. Most of them have had their SSDs and RAM upgraded.

    They’ve worn many hats since I’ve had them, but some of their uses and proposed uses were:

    1. I did a 15 node Docker Swarm setup and used that to both run some of my applications as well as learn how to do horizontal scaling.
    2. After I tore down the Docker Swarm cluster, I set them up as diskless workstations to both learn how to do that and used them at a local event as web kiosks (basically just to have a bunch of stations people could use to fill out web based forms).
    3. One of them was my router for a good while. Only replaced it in that role when I got symmetric gigabit fiber. Before that, I used VLANs to to run LAN and WAN over its single ethernet port since I had asymmetric 500 Mbps and never saturated the port.
    4. Run small/lightweight applications in highly-available pairs/clusters
    5. Use them to practice clustered services (Multi-master Galera/MariaDB, multi-master LDAP, CouchDB, etc)
    6. Use them as Snapcast clients in each room
    7. Add wireless cards, install OpenWRT, and make powerful access points for each room (can combine with the above and also be a Snapcast client)
    8. Set them up as VPN tunnel endpoints, give them out to friends, and have a private network

    Of the 15, I think I’m only actively using 4 nowadays. One is my MPD+Snapcast server, one is running HomeAssistant, ,the third is my backup LDAP server, and one runs my email server (really). The rest I just spin up as needed for various projects; I downsized my homelab and don’t have a lot of spare capacity for dev/test VMs these days, so these work great in place of that.


  • Because:

    1. I’m not a lazy, smooth-brained rube.
    2. I’m not in the business of selling AI to lazy, smooth-brained rubes
    3. I have no stake in the supply chain nor do I stand to profit from those selling AI to lazy, smooth-brained rubes.

    Furthermore:

    1. I don’t trust “AI”. If I’m going to have to fact check it anyway, might as well just do it myself and earn the damn knowledge.
    2. AI does not work for me (or you). It works for the companies who are forcing it on you and sucking up your data.
    3. The energy costs and water requirements are mindbogglingly staggering
    4. I refuse to feed or ride any hype train
    5. It’s creating scarcity of things that could be put to better use (energy, water, computer components, land, talent, you name it).
    6. It’s not even AI. It’s just a dead-end bullshit generator

  • do GSI roms still contain google binaries (play store, play services, etc…) or is it similar to a AOSP rom where its just a bare android image

    Yes. That’s to say they can be either depending on how the ROM was built. All of the GSI ROM builders I’ve worked with usually have multiple releases of the same build with different configurations: root, no root, with Google services (often MicroG), without Google services, combinations of both, etc.

    To my understanding, GSI ROMs are basically just the “userland” portion of a full ROM. Basically they use the stock/existing kernel, drivers, etc but replace the rest of the system that runs on top of it. If memory serves, they’re possible due to Project Treble. Sadly, they still require an unlocked bootloader to install, so they’re not a total fix-all.

    They’re also very generic generic images (hence the “G” in the term). They’re not optimized for any specific device and can be hit-or-miss feature wise depending on the device. If you’re already reading about a specific device on XDA forums, then you’ll probably be able to see what works and what doesn’t.

    TL;DR: Running a GSI ROM is like upgrading to a newer Linux distro but without upgrading the kernel.








  • Ooh, I haven’t tried RTL-SDR on it yet, but I think I’m nearing capacity on what it can do at once lol.

    Here’s the block diagram for it (in spoiler below). Everything’s up and running except the Bluetooth Receiver -> Snapcast (it works on the bench but I don’t have the scripting/automation done yet). I’m also adding an SMA connector for an external antenna, but the new base part is still printing. Photo shows it “as is” of this writing.

    SSL for the web apps was a PITA since I wanted real certs. Had to make a wildcard domain under my main hobby domain, so all my apps are like “https://{APP_NAME}.mobile.mydomain.xyz/”

    As soon as I can get the Bluetooth + Pulseaudio scripting done, I’m gonna try to do a write up and maybe a show/tell post.

    Block Diagram

    Current Case


  • I would love to have a small Wikipedia browser that can survive the apocalypse.

    I’ve got the full 120 GB Wikipedia dump running in Kiwix on a Raspberry Pi Zero. Works great (surprisingly)

    E-ink display, mini keyboard

    Have been using a Minimal Phone for a few months now which has both of those. Can connect to the Pi easily.

    multiple ways/ports to transfer info,

    Add a USB-C hub (or add a hub to the Pi) and you’re set

    All wrapped up in a heavy duty equipment case that’s able to survive a building collapses and burns in an earthquake, that’s shielded from EMP.

    And that’s where I’m limited - My 3D printer can only do so much lol. 😆

    I’ve been working on a side project this week with a Orange Pi Zero 2W (Pi Zero “clone” but with better specs). It’s got the Kiwix+Wikipedia like my older Pi (described above) plus a bunch of other neat stuff. It’s kind of a combination travel router, portable web app server, party box, and extremely over-engineered bluetooth speaker all-in-one. Hoping to put together a show-and-tell post about it when I get the last of it squared away.