• 0 Posts
  • 27 Comments
Joined 2 months ago
cake
Cake day: March 10th, 2026

help-circle
  • Every discussion I have seen on the subject says that docker ipv6 is pretty busted from a security perspective and you have to implement a bunch of workarounds.

    I don’t have to time both to migrate to podman (and maybe have to run dual stacks for what isn’t available) AND migrate to ipv6. But apparently the way podman does it is also kind of a hacky way (I am far from a networking expert) so I will sit with my pretty decent, secure, and working ipv4 lol









  • Having done a lot of research into this, the state of things sucks right now. The current open-source options have very bad tracking (like, just a very rough estimate) and are much more focused on smart-watch interfaces, which I get because having made a smart watch development board myself, PPG AFEs are a black hole of NDA-riddled bullshit, manufacturer lies and bad documentation, and no support (looking at you Analog Devices). ZSWatch is the most promising open source project using the best openly - available sensor set with the potential to hit 80% heart rate accuracy, but that is still years away.

    Honestly for half-good tracking, your best bet js Gadgetbridge + a proprietary smart device that is entire locally supported.

    For example, the 100€ Amazfit Helio Strap (no screen) has great heart rate tracking and better than average sleep tracking (old strap style or bicep strap) and you can run it once in the official app to update firmware and extract the encryption keys, then from then on run it completely locally on gadgetbridge and uninstall the official app completely.

    Letting perfect be the enemy of good enough sadly leads to almost useless tracking data in the open source wearables world. For now at least. Making wearables is insanely expensive and to get the best sensors you need NDAs and quantities >10k per year which is unobtainable for community open source projects right now, and you need massive amounts of user data to build good algorithms to analyze the data from the sensors.



  • Cool project! Epaper is awesome and crazy microfluidic tech.

    The M5stack M5paperS3 is 60€ (56,70€ at Tinytronics in NL) and is auch more readable size, integrated battery, 4.7inches. More like an older smartphone screen and have very fast refreshing.

    Nicco loves Linux (KDE contributor and a sort of blogger) made a whole to-do app/system that runs on it so it is temporarily out of stock at Tinytronics, but I think the problem with the small screen is having to refresh >3x as much to read the same amount killing battery life on an already smaller battery.

    I think personally I would have trouble either with font size, or only being able to read a few sentences before scrolling.




  • Because America runs off of shirking responsibility to blame someone else: using precedents as loopholes to not have to argue a case.

    1 state does it: 25 others follow suit immediately and it gets insta-passed because “there is a precedent”. See: flock cameras, Bibles in schools, book banning, abortion banning, sweeping climate protection rollbacks, etc… Once one does it, the rest of the cowards use it as a shield like children: “B-B-But theeey doooo iiiit!”






  • Spinning up and down hard drives repeatedly drastically reduces their lifespan though. Once a day or so, fine, but if you set a 30 minute idle time or something and it spins them down a dozen times per day, you are putting acceleration forces on the drive many more times than intended.

    If you have to buy a new HDD twice as often because you spin it down, any financial or environmental savings is instantly negated and in the end it is much, much worse in both respects.