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

The context here is Free and Open Source Software that accesses email.

Software that, for now, under Google's current interpretation of the rules, is allowed to use their OAuth without paying these fees.

The question I'm asking is, what happens next year when Google decides to silently change their interpretation of the rules? Do you, as a FOSS email client writer working on JohnnyMail, risk a massive yearly bill of 1/6th or more of your salary that you are contractually obliged to pay - or just say "Sorry Google, you've outpriced me" while their interpretations are still favourable?

It's not "undoubtedly better for end users" that free email apps be excluded from Gmail. It's not better for end users that open source software developers are given a sword of Damocles hovering above their heads. Sure, it's undoubtedly better if these free apps can be guaranteed to be secure, it would be even better if Google could do that in a way that didn't cost a massive amount or a surprise bill.

I'm glad you had the resources to be able to go through the process, and that you found it a useful process to go through. But it doesn't justify the uncertainty.



This isn’t about profit. Google doesn’t want to pay for security audits. You pay the auditor directly.

I suppose Google could charge for future access. Any platform could. But not retroactively. That would need to be in a contract and it’s not.




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

Search: