Couldnt we add some "usb descriptor flag" which says whether WebUSB should be allowed or not? Then firefox/chrome would not need to maintain a blocklist.
Yes. And in the past days email notifications on android had some "off-by-1" error for me: when a new mail came in, the notification had the subject of the previous email. Did anyone else observe this?
(They are not accepting bug reports on their github repo currently.... )
I can totally second this. Embedded rust in general has been an excellent experience for me. And async with embassy-executor works really well and takes a lot of pain off the whole rtos design process.
(Paying customer)
Yes! I cant believe I still cant share a folder with another account on proton drive (apart from read-only sharing via link), but now instead they add .....
I would love to see a reverse engineering approach of the original mcu firmware.
So far everything I found seems to cover the IR protocol only. The MCU seems to be unlabeled (https://github.com/sueppchen/PixMob_waveband/wiki/MCU )
I've also tried to optimize c++ compile times on large projects a few times. I never got IWYU working properly and I always hated the fact that I still have to care about header files at all. Then I switched to doing rust full time, which made all the fiddling with header files obsolete. This felt amazing. But now I'm facing the same problem, slow compile times :). Only this time I have to rely on the compiler team to make the improvements and I cant do much on my side AFAIK.
I feel like release tarballs shouldnt differ from the repo sources. And if they do, there should be a pipeline which generates and upload the release artifacts....
Can somebody write a script which diffs the release tarballs from the git sources for all debian packages and detects whether there are any differences apart from the files added by autotools :)?
Did I read this correctly and audio fingerprinting is mainly about identifiying the used browser version and OS or laptop, but it cant identify end-users in a stable way?
I gave the webapp and android app a quick test. It looks nice, but it is still not as smooth as google photos or similar. E.g. the photos are not preloaded fully and I still need to wait a few milliseconds to get a photo fully rendered. (Also there is some white flickering when swiping through the photos on android)
I wonder how the big players do it. Of course they have a lot more manpower, but maybe the also have some clever caching/rendering lib..?
Kudos for doing this and opensourcing everything. I really appreciate this and I might stick around.
off topic, but why does the page (step 2) rant about protonmail?
Can somebody elaborate?
>Be advised that Protonmail is generally known to be a pretty bad email host. [...] Not to mention their mistreatment of open source and false promises of security! You should consider a different mail provider.