4 ms·
As someone who is apparently "old", I continue to not understand how Twitter has managed to trick an entire generation of developers into believing they need Tw
by saurik 8y ago
As someone who is apparently "old", I continue to not understand how Twitter has managed to trick an entire generation of developers into believing they need Twitter's permission to develop a third-party Twitter client. Has the law changed in some noticeable way to make reverse engineering the official Twitter client and extracting their first party keys for purposes of interoperability suddenly illegal? We used to do this all the time, at scale before Twitter's invention of the "API key", and the only recourse the service has is to try to detect weird usages of their backend and then punish the users... something that tends to be something of a PR nightmare. (FWIW, I am totally willing to believe the issue is that Apple won't accept them, but then that is Apple being the asshole, and we should be looking into ways of making that market collusion illegal, assuming of course that it isn't already.)
- dmitrygr 8y agoThey could claim copyright over the API key (unlikely) or (more likely) ask a friendly prosecutor to charge you with violating CFAA. You are accessing their systems, not in a way they authorized. Enjoy some jail time. Sadly, yes, it has come to this. Eg: https://www.newsweek.com/most-hated-law-internet-and-its-many-problems-cfaa-448567 https://www.newsweek.com/most-hated-law-internet-and-its-man...
- tptacek 8y agoThey don't need a prosecutor; CFAA includes civil causes of action.
- saurik 8y agoThe CFAA has existed since the 80s, and yet I have not heard of it being used successfully to stop all of the work we did in the 90s on third-party clients. Meanwhile, all of the recent stuff I have heard about the CFAA has been that precedent is being set that its super vague provisions can't be used to enforce a mere terms of service. https://www.eff.org/deeplinks/2018/01/ninth-circuit-doubles-down-violating-websites-terms-service-not-crime https://www.eff.org/deeplinks/2018/01/ninth-circuit-doubles-...
- tptacek 8y agoI think you're reading something into that 9th Circuit decision that isn't there. That decision held that the federal government couldn't use a TOS violation as a predicate for a felony CFAA charge. It did not hold that TOS agreements are unenforceable. Even the EFF isn't saying that TOS contracts are unenforceable --- and here we're not talking about browse-wraps, but on Twitter informing people directly as to their terms, and then having those people deliberately circumvent controls that enforce those controls. For a straightforward counterexample to your argument about TOS enforceability, see 3taps. Or Facebook v. Power Ventures.
- tptacek 8y agoI don't understand this argument. Twitter hasn't tricked anyone. They have an enforceable terms of use agreement with their users. If you deliberately circumvent controls described by that agreement, they have civil recourse. It's their site and always has been.
- citilife 8y ago> I don't understand this argument. Twitter hasn't tricked anyone. They have an enforceable terms of use agreement with their users. If you deliberately circumvent controls described by that agreement, they have civil recourse. It's their site and always has been. That's actually not true, if it's public information, then you're free to grab it. See below: https://www.theverge.com/2017/8/15/16148250/microsoft-linkedin-third-party-data-access-judge-ruling https://www.theverge.com/2017/8/15/16148250/microsoft-linked... By reverse engineering the API, sure they can shut you down, but a lawsuit? Hardly.
- tptacek 8y agoWhoah, hold on. You're referring to a preliminary injunction issued in a case that hasn't been tried yet; not only that, but LinkedIn appealed that judgement, and their appeal is still pending. That case also revolved around antitrust liability, which Twitter doesn't have. It is not at all settled that anything in front of a login screen is public and not protected by TOS's. And, of course, here we're talking about things that appear after a login page. https://www.ca9.uscourts.gov/media/view_video.php?pk_vid=0000013344 https://www.ca9.uscourts.gov/media/view_video.php?pk_vid=000... The 5-minute spans around minute 20 and around minute 53 are particularly interesting. Even HiQ agrees that they have no right to ignore TOS terms pertaining to things behind login screens.
- sulam 8y agoYou can see tweets without logging in. People do it all the time, and websites do it even more.
- 8y ago
- deleted 8y ago[deleted]
- elorant 8y agoI can see two counter arguments. One, you don't want to go with Twitter, or any large corporation for that matter, to court. They have a legion of lawyers and you don't. They have budgets for these kind of cases, you don't. Even if any dispute you have with them won't make it to a court you'll lose precious time and resources consulting with lawyers in order to answer their C&D demands, which I guess at some point will escalate if you keep ignoring them. Then you have the practical part. Would you really base your project on reverse engineering and hacking a third party service? It will end up being an arms race. Everytime they change something you'll race to hack it again. In the meantime your service will be inoperable. If your user base is in the tens of thousands that will kill you. I can't think of any reliable service that every couple of months or so would go offline even for a few hours until the developer finds a way to circumvent whatever countermeasure Twitter came up with. So you play nice and follow their rules. Even if they suck, which by the way is the main reason why Twitter lost all the love of developers and has stagnated for the last years.
- gluelogic 8y ago> Would you really base your project on reverse engineering and hacking a third party service? It will end up being an arms race. Everytime they change something you'll race to hack it again. In the meantime your service will be inoperable. If your user base is in the tens of thousands that will kill you. Depends on what the service is. youtube-dl faces this issue but is some of the best software I have ever used.
- s73v3r_ 8y ago"I continue to not understand how Twitter has managed to trick an entire generation of developers into believing they need Twitter's permission to develop a third-party Twitter client. " It's Twitter's API, and Twitter's servers. "Has the law changed in some noticeable way to make reverse engineering the official Twitter client and extracting their first party keys for purposes of interoperability suddenly illegal?" If you don't have permission to use someone else's stuff, you don't use it. We were all taught that in kindergarten. "We used to do this all the time" The fact that you abused other's web servers back then doesn't mean that it was right then or now.
- omarforgotpwd 8y agoTwitter is a public company owned by shareholders, running a private service on their own servers. They have a right to try and control how their service is used by users and developers. If Twitter tells me I can't access their API, I probably won't develop that client not because I technically cant but because it would be an uphill battle to develop and put something out there if it depends on someones third party servers and that person does not want me to use said servers.
- oceanghost 8y agoI spent... 6 months trying to write a remote control for the google chrome dongle (not using Google's API). It was pretty clear that the official SDK had access to an entirely different API, and because it was all encrypted, I would never, ever, see any of it. The bits and pieces of an API I did piece together (from older protocols), were stunningly unreliable. I am sure they were left in only to frustrate people trying to do exactly what I was.