And it was in 1996!!! 27 yrs ago! And it worked really well.
It is now 2023. The lack of automated enforcement as we face record traffic fatalities is really not cool.
@aaronpk From a dev standpoint it's just good practice, right? Distributing your consumer secret keys to so many devices so your team never misplaces it, right?....
It's like when I share my ssh private key in my public github repo for backup purposes along with a list of all servers it can access. (/sarcasm)
@aaronpk From a dev standpoint it's just good practice, right? Distributing your consumer secret keys to so many devices so your team never misplaces it, right?....
It's like when I share my ssh private key in my public github repo for backup purposes along with a list of all servers it can access. (/sarcasm)
@aaronpk Oh lord are they charging for their *oauth* APIs too? That would be... incredibly short-sighted
@aaronpk FWIW, OAuth appears to be treated separately from APIv1.1 and APIv2. itโs feasible that it will keep working for free. but itโs anybodyโs guess at this point https://developer.twitter.com/en/docs/api-reference-index
@aaronpk I get the feeling Twitter doesn't know either.
@aaronpk itโs very odd since I believe their devices like firetv have this sort of flow implemented. So they know how just for some reason donโt do it?