lahackerit was more the dismissiveness.. the industry dogma applies to centralized third-party apps with databases of Twitter username/passwords that *must* be held in plaintext for re-use.. my context is so vastly different, really more akin to an in-browser password manager.. and even though it was acknowledged that the system wasn't built for my context i was still practically bullied into complying anyway
[KevinMarks]You did trigger a cultural memory of bad practice there. Reviving "enter your password" is likely to cause backlash from the places whose passwords you're entering, which is a little hypocritical, yes, given that many of them used to do it too. The thing is, OAuth was a big mutual disarmament treaty for that kind of thing.
lahackeri spent OVER A YEAR talking to a Twitter bot to try to get an old account recovered.. they pushed a new auth system and something changed and I was able to recover..
aaronpkwell this is the other problem with twitter's API... it requires a client secret (or whatever it was called in oauth 1) which has that exact problem you mention, you can't safely ship software like an ios app or SPA containing that secret cause then other users could abuse it
[tantek]that's perhaps something we should start considering recommending against because of both the process tax (what lahacker described as OVER A YEAR above), and the API permission (token / client secret?) fragility
[fluffy]Yeah, my experience with adding Twitter auth to Authl was… not fun. Twitter’s API really isn’t intended for any experience other than building a Twitter client, except ironically they’ve removed all the stuff that’s useful for Twitter clients too.
[fluffy]So basically all you’re left with is something built to auto-tweet things you do on other websites and MAYBE use twitter as a centralized/siloed authentication service.