• 2 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle

  • Sir Gareth@programming.devtoSelfhosted@lemmy.worldPost your Servernames!
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    6 months ago

    Mine are all named after dairy products.

    I have whey as the main docker host and first mon, milk as my main x86 osd, leben-{1,2} as more (arm64) osds, kumis-{1,2,3} as more (arm64) mons, kefir and ghee are old x86 mons (maybe Ill repurpose them as docker hosts someday. I have lassi-{1,2} as rpi 3b+ but they arent in use at the moment because I dont need them yet. Ive got pytia as my spine, and yoghurt as my edge, leaf is l2 so no hostname.

    My main windows gaming pc is butter, the wifes pc is something similar but its not turned on and I cbf checking router logs.











  • My threat model doesn’t need to include people hacking my locks. The average junkie breaking into my house to steal shit isnt doing it with the blessing of some hacking group. There are no cat-burgulars coming for my collection of antique dildos. I can definitely understand not e-locks for a museum or a bank, but they use integrated security systems that are far out of reach of home users. Another point is that the tumblers in most home door locks are trivial to pick, more trivial than hacking an e-lock.




  • People talk a lot about home-assistant but there is another part to that setup; the devices themselves and the firmware they run.

    If you stick to ESP8266 devices mostly you can use things like Tasmota and ESPHome. Zigbee/Z-wave is good I’ve heard but nothing compares to the interoperability of good 'ol WiFi.

    It costs like less than $15 for a Sonoff Basic R2, another $5 for a knock off FTDI USB programmer. With a tiny bit of soldering you can put some programming pins on the Sonoff and flash Tasmota. From there you can use Mosquitto to control it, or the HTTP API, both open and interoperable protocols.