The number of requests/second @infura_io must handle is insane. Every active Metamask user is sending them ~25 eth_getBlockByNumber calls a minute. If 50% of Metamask users have the extension enabled thats 200k requests/second right there.
-
-
Nice to do it this way because people stink at deadlines, aren't actually checking your updates, and might forget to update some of their code paths.
Show this thread -
I'm mainly fixating on API changes because I've run an API company for several years and breaking changes truly stink. You have to give really long notice and keep supporting the deprecated stuff while also rolling out new features. Can choke your eng team's productivity
Show this thread
End of conversation
New conversation -
-
-
Thanks for the input
@backus. We're actively working hard on a new authentication format for improved security and we are working on a transition plan very similar to your proposal. -
Cool! Good luck :) I think you guys are doing things the right way so far, I was just talking with an eye to the future since I know iterating on API companies in particular can be tricky
End of conversation
New conversation -
-
-
Could the web3 providers offload that onto users? Somethieng like requiring users to have their own API key.
-
Yeah that is way trickier for things like Metamask where they can't exactly ship the same api key to every user. Basically I'm suggesting user agents as an easier way to know something about unauth'd users while also focusing on api keys long term
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.