So if I download an image from the web with GPS data, and then open it in an app that just reads images (so it doesn’t need location permissions)… That app (on some phones) gets a modified version of the file?

Which could make me think that the image doesn’t have location information.

Which could result in me uploading that file using a browser (that does have location permission turned on) to a website, and I think it’s safe to share because there’s no private information in the image, but my phone has conspired to mislead me.

Yes, that is cursed.

Page 15 of the pdf has this chart

(note the vertical axis starts at 60% acceptance rate)

I really do appreciate the work you put into Beehaw, but to echo what others have said, I don’t think anyone wants this to be unsustainable for you, or anyone else working on Beehaw.

At the least I think it could be reported as part of donations/expenses? Rough numbers would be fine too (because the overhead of tracking hours is not fun). So I’m imagining something like:

400 hours unpaid work (2 full time people working, 1 part-time) (if paid, that’s $6,000 at minimum wage, $8,800 at a livable wage)

Which is a lot of money, and very scary, but at least it makes the behind-the-scenes work visible.

That said, I’m going to go set up a monthly donation now 🤗

From what I recall they were saving all the packets being broadcast as they drove past. (as opposed to only logging SSIDs)

Edit: Yup, it is as I had thought - but also it was more intentional than I had remembered: https://www.wired.com/2012/05/google-wifi-fcc-investigation/

(unpaywalled link) https://12ft.io/proxy?q=https%3A%2F%2Fwww.wired.com%2F2012%2F05%2Fgoogle-wifi-fcc-investigation%2F