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

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

help-circle

  • 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








  • I’m about that same age but am so glad we’ve largely abandoned the “www” for websites.

    On my personal project website, I have a custom listener setup to redirect people to “aarp.org” if they enter it with “www” instead of just the base domain. 😆

    server {
        listen              443 ssl;
        http2		        on;
        server_name         www.mydomain.xyz;
    
        ssl_certificate     /etc/letsencrypt/live/mydomain.xyz/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/mydomain.xyz/privkey.pem;
        ssl_dhparam         /etc/nginx/conf.d/tls/shared/dhparam.pem;
        ssl_protocols       TLSv1.2 TLSv1.3;
        ssl_session_cache   shared:SSL:10m;
        ssl_session_timeout 15m;
      
        ...
        
        location ~* {
          return 301 https://aarp.org/;
        }
    }
    







  • I learned a long time ago to never install manufacturer printer drivers. Or, at least, never install them from the provided Setup.exe.

    They’ve always installed a bunch of bloatware (HP has always been the worst but other brands are just as bad).

    If you look in the setup folder, there’s usually the raw drivers you can install from Device Manager. If the driver package is just a single .exe file, you can usually unpack it with 7zip and get at its inner contents.

    If that fails, the system-included HP LaserJet 4200 PCL driver is about as close to a universal print driver as you can find lol.