• 0 Posts
  • 10 Comments
Joined 2 years ago
cake
Cake day: August 8th, 2023

help-circle

  • I’m currently using the Nothing CMF Pro 2.

    You configure it with the proprietary app to get the initial paring key, then you can switch to Gadgetbridge and disable or even remove the Nothing app.

    The Good: cheap device cost, nice UI elements, machined aluminum bezel looks premium. Push notifications and most features work.

    The Bad: semi-annoying workaround to get it set up initially, not all features work, not using the proprietary app disables using the Nothing watch face library so you’re stuck choosing from the 5 or 6 default designs that come with the watch.






  • If I had to come up with a steelman argument for small “AI focused” systems like this, I’d say that the more development in this space, makes the cost of entry cheaper, and actually eventually starves out the big tech garbage like OpenAI/Google/Microsoft.

    If everyone who wants to use AI can locally process queries to a locally hosted open-source model with “good enough” results, that cuts out the big tech douchebags, or at least gives an option to not participate in their data collection panopticon ecosystem.



  • Side note -

    I literally have the reader pictured in the thumbnail. It is a Kindle keyboard from 10+ years ago at this point. It still works fine. At one point the original battery went to shit, and it cost very little to get an aftermarket replacement and install it myself.

    I keep it offline and read 100% sideloaded .epub books from various sources. The lockscreen ads don’t even try to display anymore.

    Sure it isn’t backlit or waterproof but it still functions flawlessly as a generic reader. Old tech like this is awesome. Why not get a decade of use (or more) out of something that still works?


  • The most-aggressively short timelines don’t apply until 2029. Regardless, now is the time to get serious about automation. That is going to require vendors of a lot of off-the-shelf products to come up with better (or any) automation integrations for existing cert management systems or whatever the new standard becomes.

    The current workflow many big orgs use is something like:

    1. Poor bastard application engineer/support guy is forced to keep a spreadsheet for all the machines and URLs he “owns” and set 30-day reminders when they will expire,

    2. manually generate CSRs,

    3. reach out to some internal or 3rd party group who may ignore his request or fuck it up twice before giving him correct signed certs,

    4. schedule and get approval for one or more “possible brief outage” maintenance windows because the software requires manually rebinding the new certs in some archaic way involving handjamming each cert into a web interface on a separate Windows box.

    As the validity period shrinks and the number of environments the average production application uses grows, the concept of doing these processes manually becomes a total clusterfuck.