834 karma · joined November 20, 2014
Socials: - x.com/KrauseFx
---
- https://krausefx.com/blog/ios-privacy-instagram-and-facebook... - https://krausefx.com/blog/announcing-inappbrowsercom-see-wha...
- https://krausefx.com/blog/ios-privacy-instagram-and-facebook... - https://krausefx.com/blog/announcing-inappbrowsercom-see-wha...
However, I believe all of this won't matter for too long after the press the last few days.
> Overall, having spent a significant amount of time building this project, scaling it up to the size it’s at now, as well as analysing the data, the main conclusion is that it is not worth building your own solution, and investing this much time. When I first started building this project 3 years ago, I expected to learn way more surprising and interesting facts. There were some, and it’s super interesting to look through those graphs, however retrospectively, it did not justify the hundreds of hours I invested in this project.
- The data is stored in my own, private database, not connected to any service - Much of the data visualised on that page, is data many larger companies already have about you. I figured, why wouldn't I want to benefit also? - The data shown above seems very personal but doesn’t actually expose any real sensitive information. For example, disclosing your current location, your home address, or stores and places you frequently visits is sensitive and potentially dangerous. Even looking at the map of my movement data on my page, you won’t get any more information that what most people have in their public Twitter bio.
I made sure all graphs are non-interactive, and had all personal information stripped out.
- The data is stored in my own, private database, not connected to any service - Much of the data visualised on that page, is data many larger companies already have about you. I figured, why wouldn't I want to benefit also? - The data shown above seems very personal but doesn’t actually expose any real sensitive information. For example, disclosing your current location, your home address, or stores and places you frequently visits is sensitive and potentially dangerous. Even looking at the map of my movement data on my page, you won’t get any more information that what most people have in their public Twitter bio.
I made sure all graphs are non-interactive, and had all personal information stripped out.
> An alternative approach would be to have an extra permission layer to access the picture's metadata.
You are right, installation is not super easy right now, due to Ruby dependencies, which also depend on Nokogiri and phantomjs.
Have you seen the guide, that helps you with getting and up and running quite quickly? https://github.com/KrauseFx/fastlane/blob/master/GUIDE.md
I tried this on a fresh Yosemite installation, and it went quite fluent.
Let me know if that helps you and how I can link the guide better to make it better visible.