• 0 Posts
  • 6 Comments
Joined 10 months ago
cake
Cake day: December 25th, 2025

help-circle


  • As another user of the og Fairbuds, the issue with charging is actually due to the rubber they use to make the battery compartment a little sweat resistant. If it moves it can stick out a hair enough to visibly keep the case from closing all the way. Grab the rubber and rotate it back to where it should be (there’s a notch) and it’ll charge just fine.

    As far as daily use, audio isn’t amazing, it’s also not terrible. I’ve had worse earbuds in quality come with iPhones. Touch controls were a bit finicky but have gotten easier as I’ve adjusted to using them. It seems like people expect pro-audio speaker level of quality out of Bluetooth earbuds nowadays and that isn’t what they’re getting with any of these between the quality loss of the Bluetooth codec and the tiny speakers in the earbuds. Maybe I’m crazy but earbuds just need to play music acceptably while traveling, they’re not a replacement for good headphones or good speakers…



  • This is such a nothing burger, they’re using those first five to get partial matches then doing the actual checks locally on the hash…

    To be transparent: this check isn't new, it has been part of the Supervisor for years. It checks app options that are marked as passwords. A recent release fixed the warning that surfaces it, which is why you're seeing it now. Privacy was a design requirement for this feature from the start, which is why your secrets never leave your system. The Supervisor hashes them locally and sends only the first 5 characters of the SHA-1 hash to Have I Been Pwned. HIBP returns every hash starting with that prefix, and the matching happens on your own instance. You can see exactly what it does here: https://github.com/home-assistant/supervisor/blob/main/supervisor/utils/pwned.py. You are right that our documentation should have explained this, including how to turn it off. We'll get that page updated. ../Frenck