0 sats \ 3 replies \ @anon 17 Mar \ on: API Keys by ekzyis · Pull Request #915 · stackernews/stacker.news meta
Hey I'm glad there's some sort of progress in the API arena, and I don't want to sound ungrateful, buuuut:
If you have to manually apply for access this is never going to take off. Why put a lot of effort into writing some SN-api-wielding software if every single one of its users has to beg and plead and make their case to you deities in order to use it?
Look man, this is how it's done: https://github.com/HackerNews/API
See that? Short, simple, sweet. No API keys, no "extract this kooky string from the dev tools in your browser". It just works.
PERMISSIONLESS
Lemme say that again, PERMISSIONLESS.
Look, I don't want to sound ungrateful and all. I assume the reason you can't throw the gates open is that your API is GraphQL, and because of that people can grind your server to a halt with complex queries. If that's the case, stop working on the API. Focus whatever time you have available for API stuff into a non-GraphQL interface. Don't worry about public API access until that's taken care of first.
Hope that didn't come across as too entitled. You are heroes, btw.
reply
Also don't ever forget you have the world's most powerful anti-DoS tool already implemented: micropayments.
I agree it's a powerful anti-DoS tool but with great power comes great responsibility. We like to prioritize UX over "slapping fees on something and calling it a day". Micropayments are not our revenue. They only exist to enhance the SN experience.
Why not just get rid of the API keys and charge users sats for API calls?
This would only charge the users who don't know how to use the API for free like the frontend
reply