Aaron Parecki

@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.