We also now have a formal privacy report for the LVFS, which is becoming more important both with the increase in the the data collected, and also with the number of clients connecting to it. Comments, as always, welcome.

Quick poll for all you people that care about privacy. There's been a proposal that the machine running fwupd should "phone home" to the LVFS with success/failure after the firmware update has been attempted. This would let the hardware vendor know there are problems straight away, rather than waiting for frustrated users to file bugs. The pingback would just contain a salted-hash of the machine-id and a boolean, but obviously including the IP address too. Please vote below, including comments if you can. Opt-in isn't really an option as this makes the whole exercise pointless, but opt out would be available in the daemon.conf file. Thanks!

If you need to update your Thunderbolt controller firmware on Dell hardware, it might be your lucky day...

tl;dr: Most Bluetooth speakers and headphones are now updatable using fwupd, but we need the vendors to upload firmware to the LVFS.

Does anybody know an API call or file that only changes when you reboot the machine, but stays static for the current boot? Ideally some key be of hash value that works for x64/i386/arm etc. Thanks!

Try two: Lets phone home with permission... Comments welcome.

I think I've just discovered and reported my first ever CVE-worthy security bug. I can't go into details obviously, but I'm intrigued how the whole process works from the "other side" so to speak.

I'm planning to kiss goodbye to my inbox if anyone posts this on Reddit...