Twitter shuts down 30 sites dedicated to saving politicians' deleted tweets
theverge.com
theverge.com
Yes, it would be like these ... um ... thingies that Twits never heard of like, oh, e-mail and Usenet.
And older thingies like writing letters. And, for example, having a "letter to the editor" published in a newspaper, which is then archived in a library.
Publishing should be nerve-wracking and terrifying.
You know, you can still buy calendars filled with George W. Bush gaffes. Should those be cease-and-desisted?
Here, for "site" we can also substitute "archive". Archives don't have to process cancels or supersedes, and can ignore X-No-Archive headers.
The first thing many people do when they see a controversial tweet (especially from someone well known) is to take a screenshot. This changes nothing.
Many of these sites didn't originally spring up to serve the public interest. They're an offspring of something that started a couple years ago: Twitter bots that scrape for anyone's deleted messages and then highlight them.
Those services are extremely toxic. They meant that as friends of mine joined the service I'd have to warn them: don't delete things on Twitter, because there are asshole bots that will use deleted messages to fuck with you.
The public interest implications of some of these new political Twitter services are more straightforward, but that doesn't mean it's Twitter's obligation to sacrifice user experience for what is probably a marginal public interest benefit. Twitter is legitimately caught between the public interest and their own interests, and I'd have trouble blaming them either way.
Why do I think the public interest implications here are marginal? A bunch of reasons:
* Politicians are quickly going to learn how hostile Twitter is, and assign professional spindroids to their accounts (or to filter the messages that they themselves post).
* It's not like Twitter can prevent deleted tweets from leaking. They'll get screenshot anyways. This just keeps the delete-shaming phenomenon from being shoved in everyone's face.
On a previous thread about Twitter, someone pointed out that Twitter shouldn't do this because they should behave like infrastructure. But Twitter doesn't want to be infrastructure; the infrastructure market position is very bad for them.
Scraping is against most sites (and Twitter)'s ToS.
I think you could probably make an argument that it is fair use to save and display a tweet from a politician without violating anyone's copyright, but I'm not sure if it's possible to do it in an automated way without violating the TOS and possibly the law.
Scraping a site that doesn't want to be scraped is legally dangerous in the US.
The point isn't to stop deleted tweets from being disseminated at all - that's impossible and I'm sure they're smart enough to know that.
The sole purpose of sites like Politwoops was to undo a feature of Twitter's product. Not only that, but they were using Twitter's own API to accomplish that. Twitter's goal is to set the precedent that that's not ok.
The analogy holds because Twitter is 1:N, not 1:1. They are publishing information to a large amount of people that people use to educate and inform themselves.
And I already stated that doing this for every Twitter user is slimy. But retaining the record of how a politician has communicated with the public? That's in the public interest.
Where they cross the line is in only doing deleted tweets, and marketing themselves that way. The entire purpose of their product is to undo a feature of someone else's product.
This story is being framed a certain way: "Twitter is a big corporation attacking the little guy in defense of evil politicians," and kids on Reddit are outraged. I don't think that's what's happening here at all. They're just defending the integrity of their product.
They should address this truthfully on their blog. Letting something like this twist in the wind while their base users go apeshit is a surprising decision. They did this on a Friday- they've had all weekend to craft a statement.
Or, just run strings on the Twitter iOS app bundle... or just look at traffic in Charles...
But I create API key for site: xyz.com where I use the stream API to get all tweets from users a-z
Then I push those to site zyx.com
There is no way for twitter to know what API generated those tweets. Especially if site xyz.com DOES obey the delete notifications (which also triggers site zyx.com to go into action in checking the deleted tweet)
I don't see how this is a total non-story
On another note, I wonder how strongly this would hold up against an individual. e.g. suing someone that was permbanned from your site because they used a proxy to access the site
Beyond being difficult to find/sue the individual - and it being well beyond worth the costs of the lawsuit itself - I wonder if it would hold up in court.
I'll keep this bookmarked as a (rather empty) threat against trolls who are ban evading.
Important difference.
Especially given someone who uses web scraping doesn't necessarily mean they attempted to use the API, had an API key, or ever had the possibility of said non-existent API key being revoked.
back-bench political deal
Or just enforcing a ToS they've had in place for a while.There is need .. stealthy and robust .. tweet scraper.
Nothing new in this link.