• 0 Posts
  • 45 Comments
Joined 1 year ago
cake
Cake day: August 4th, 2023

help-circle

  • Inktvip@lemm.eetoScience Memes@mander.xyzBoosting that CV
    link
    fedilink
    English
    arrow-up
    3
    ·
    5 days ago

    I have a cousin that works at a petrochem plant. He told me that all the “common trips” never really happen since they’ve been drilled on how and what to do and how to prevent them, but the second shit really does go down you better have a senior around that has seen that specific trip before. Especially considering there’s tens/hundreds of thousands worth of produce being burned off by the second until things are back under control.



  • Having moved to iPhone fairly recently I do like the overall experience, however Face ID is by far the biggest downside over a good under screen fingerprint scanner.

    When picking up the phone and holding it in front of my face it works perfectly well, but that’s probably less than 50% of the unlocks I do.

    Most of the time the phone would lie flat on a desk, on a nightstand, couch armrest etc. I can see and interact with the screen just fine, but the phone can’t see me properly. Making me pick the phone to quickly check a notification.

    I’m probably entering my password about 4-5x as much as my old phone because of that







  • If it’s only you (or your household) that is accessing the services then something like hosting a tailscale VPN is a relatively user friendly and safe way to set-up remote access.

    If not, then you’d probably want to either use the aforementioned Cloudflare tunnels, or set up a reverse proxy container (nginx proxy manager is quite nice for this as it also handles certs and stuff for you). Then port forward ports 80 and 443 to the server (or container if you give it a separate IP). This can be done in your router.

    In terms of domain set-up. I’ve always found subdomains (homeassistant.domain.com) to be way less of a hassle compared to directories (domain.com/homeassistant) since the latter may need additional config on the application end.

    Get a cheap domain at like Cloudflare and use CNAME records that point domain.com and *.domain.com to your dyndns host. Iirc there’s also some routers/containers that can do ddns with Cloudflare directly, so that might be worth a quick check too.




  • Guess I’m a bit too young for that still lol. We got a pair of ISDN2 lines in 1994 (so technically also 256k lol) at home, but I was too young to remember that. With cable internet coming in 97, that was technically still slower than bonded isdn at the very start.

    In a way I was very privileged growing up when it came to Internet. My dad’s company at the time paid good money to get all the latest (often testing phase) stuff to his house in return for being available 24/7.


  • Talking about Lan uplinks, in the early 2010’s I had the joy of working with a 20gb uplink at a small university LAN (the sysadmin got a good amount of free pizza and beers for that one). I spent a large amount of my savings on a 10gb NIC only to find out my hard drive couldn’t keep up lol.