stockhorn

"Built with hate"...? Too bad. Love the rest of the project.

A bit off topic, but how is the bitwarden browser extension protected against supply-chain attacks (npm dependencies)?

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.

Go and give rust a go instead

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 .....

Now I can finally parse (X)HTML with Excel ;)

An article from 2013 with an adobe photoshop version 1.x from 1990....

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 had to reload the page on Android FF, then I got past "Loading"

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?

Ah this totally makes sense! Do you use progressive JPEGs already when opening the full image?

If only there was a progressive encoding which lets you get a perfectly downscaled (not blurry) version of an image by just reading parts of the file.