jeremycherfas, [KevinMarks] and [schmarty] joined the channel
#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
#lahacker"actively harming everyone in the industry"
#lahacker"you’re free to do anything you want, just know that you’re "on the wrong side of history here"
#lahacker"we’re just discouraging you from shipping that software to anyone else and encouraging them to use it the same way"
#aaronpklet me rephrase my comment to be more about personal experiences
#aaronpk"...actively working against the security education work that myself and my coworkers do"
#aaronpki'm sorry it came across as bullying, that wasn't my intent, but i'm not likely to change my opinion on the matter itself
#[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..
#lahackeri tweeted @TwitterHelp dozens of times over months
#lahackeri'd be a complete fool to assume that doing "the right thing" now won't result in a revoked token when i have users..
jeremycherfas joined the channel
#lahackerwhy don't they have a simple user token? to maintain this precise level of control and authority over their service..
#[KevinMarks]A user token would be a big improvement, yes
#lahackerand T R I V I A L, no? am i missing something? like, the lack of a user token should say everything
#lahackeri mean i'm just going to go for a walk, come back, start writing some aggressive prose to describe the situation to the end user
joe1 joined the channel
#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
#aaronpka user token seems like it'd solve all these concerns, and plenty of other services support that kind of thing already too
#[tantek]this is a general problem of building anything on top of Twitter *for others to use*
#[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
[Emma_Humphries] and [fluffy] joined the channel
#[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.