• 9 Posts
  • 90 Comments
Joined 2 years ago
cake
Cake day: July 9th, 2023

help-circle


  • There’s no guarantee bugs get fixed in a newer version, but there’s a higher chance of a software feature working if it’s been out for awhile with a few patch releases than it is for a brand new feature to work day one on a YYYY.MM.0 release. Home Assistant generally holds new features for those YYYY.MM.0, but patches get backported.


  • Past vulnerabilities doesn’t mean there is active mpdern vulnerabilities especially ones in widely tested operating systems that’s exploited by as many apps as people claim are listening when security researchers also regularly reverse engineer and analyze the source code of popular apps to figure out what they’re doing. You can decompile Android apps pretty easily to see what they’re doing. Some are obfuscated so it takes some effort.

    Its one thing to claim there’s some a system level bypass for the icon that the NSA uses to spy on its enemies, it’s another thing to claim that it’s being exploited on a wide scale by a tech companies on different apps, iOS and Android, multiple versions/devices.

    The reality is that we leak tons of info through other mediums that are easier and cheaper to collect than through microphones.


  • update 2.1.3 once update 2.1.4 becomes available

    I wouldn’t use that policy because what if 2.1.4 includes a fix for an issue in 2.1.3?

    My update policy is wait until a month comes put, then update to the newest previous month’s version. Patches for bugs go into mainline and are backported so this minimizes bugs in the new features.













  • I stopped using it to pay because then I’d have to set up a PIN, and then type in the PIN every time I want to use it

    This shocked me when I went from my Galaxy Watch 3 to a Galaxy Watch 6. I used to only have to put a PIN when I wanted to pay, but now it’s anything on the watch?

    Because of that, I also disabled the payment app.