Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

big take away: if you're using dependencies that talk across the internet, make sure they're ALSO using HTTPS


There's genuinely no excuse for Flurry (or any other vendor) to have an API that is not secured with HTTPS by default. I can't think of any reason other than stupidity or laziness, and those aren't excuses.

This is especially true of Flurry, which is tailored for connections directly from devices.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: