• 2 Posts
  • 485 Comments
Joined 2 years ago
cake
Cake day: June 6th, 2023

help-circle
  • Looking for Group. As someone else said, the ability to click “queue for dungeon”, be dropped into an instance with a bunch of random, and proceed to faceroll the dungeon without any thought or patience required.

    The fun part of old school MMOs was the journey, not the destination. Modern MMOs have all optimized the journey out by making everything doable without ever being dependent on another player.




  • ZigBee devices form a mesh network, which WiFi devices don’t do. This means I can have my hub on one side of my house and a bunch of bulbs and smart outlets maintain a backbone through the house for a bunch of low power devices (like thermostats and door sensors) to connect to it.

    If you’re having a bad ZigBee experience, I recommend making sure your bulbs can serve as a general ZigBee bridge, and not just a bridge for other bulbs of that brand. Otherwise, a well placed smart outlet can serve the same purpose.


  • I also don’t want devices I’m actively using to needlessly compete with random logistical packets from a dozens of devices around my house. I also don’t want the devices themselves to need all the power of a WiFi connection when another protocol suited to low power home automation devices is sufficient.

    ZigBee/zwave were fine for me, though. I personally haven’t seen a clear benefit to matter+thread yet.














  • Unfortunately, the windows bootloader issues are also ingrained in UEFI for many motherboards. Every few days I start my PC up and it has decided my grub entry is garbage and does me the favor of removing it and defaulting back to the windows bootloader.

    I’ve worked around this by adding a bootcfg entry to the windows bootloader that points at grub. Now any time this happens, I pick the grub entry from the windows bootloader, my PC reboots, and now it’ll keep defaulting to grub again until the next time it decides to wipe it.



  • It is not standard workflow in git to change the commit history for a branch on the remote. You have to use --force, and the next time someone pulls they also have to --force their any local tracking branch to follow the remote. Every git guide on the internet warns against pushing a rebase for this reason.

    Locally you can do whatever. I’m not familiar with Mercurial, but I assume it must work the same as git: I can do whatever I want locally, and only what I push matters. And when I’m doing stupid stuff locally as I organize my changes, rebase is handy.