Twitter Tells Users Being Harassed to File DMCA Takedowns

Crazy story at Medium by a woman who was being harassed by anti-vaxxers. The harassers got hold of a photo of the woman’s baby that she had posted online, and began tweeting out copies of the photo.

When she contacted Twitter, they suggested that she file a DMCA takedown notice for the images. For fuck’s sake. That is such bad advice on so many levels, not the least being that DMCA notices are generally going to result in the contact information of the individual or organization filing it to be shared with the person being served the notice.

And that’s what happened. She filed the DMCA notice which led to the image disappearing almost instantly from Twitter, but now the people harassing her were handed her personal contact information.

This is not the first time Twitter has suggested to users that they send DMCA notices to deal with harassing content without providing notice of what doing so entails.

There are so many things that Twitter could do to curtail abuse on its platform, and many of its heavy users have laid out in detail what they’d like to see change. Most of the suggestions by John Scalzi’s What I Want Out of Twitter would significantly dial back the level of abuse that individuals are exposed to:

1. Timed mutes.

2. Mutable phrases/hashtags in the web/mobile Twitter UI.

3. Make mute/block lists native to Twitter and shareable across clients.

4. Make mute/block lists easily shareable through Twitter between followers.

5. Robust filtering. [by account creation date/# of followers/account icon]

6. Muting in Notifications and Direct Messages.

7. The ability to see only replies/notifications from those you follow/whitelist.

8. An optional tab where muted/blocked account replies can go.

Unfortunately, Twitter seems completely uninterested in implementing these sort of suggestions. It seems to see Twitter as solely a link sharing/news service (hence the execrable Moments “feature”) rather than a discussion platform, and doesn’t seem to care about improving its system for those of us who use it for the latter purpose.

Reducing Trolling on Twitter

In Australia, television celebrity Charlotte Dawson has recently been hospitalized twice because of suicide attempts that were blamed, in part, on trolls inundating her with abuse on Twitter. Whether or not the trolling was responsible for Dawson’s suicide attempts, Julia Baird argues that something needs to be done about online trolls. Specifically she recommends that users should:

Encourage Twitter to keep a record of those who are blocked for bullying; if a certain number is reached, delete accounts. If persistently savage, violent attacks occur, there should be consequences. There must be a way to punish serial bullies without triggering the possibility of broad censorship.

That, of course, is an awful idea since it would take about 5 seconds for the folks who controls hundreds of thousands of fake Twitter accounts to realize they have a quick way to remove any Twitter account. Instead of preventing bullying behavior, such a simplistic solution would quickly enhance and enable the trolls.

Instead, Twitter seems like one of the few cases where something the like a Real Time Blackhole List could be useful. Twitter already has a Lists feature that allows users to assemble lists of users, typically related to subject categories (top soccer players, famous atheists, etc.)

Why not take that a step further and allow me to turn the people I am blocking into a list that others can subscribe to and, if they wish, in turn block anyone I block.

There are few people whose judgment I’d trust enough to automatically block, but there are some. I’d like to automatically block anyone that my wife and a few trusted friends block. Moreover, once such a feature was implemented, there would certainly be Twitter accounts created to serve as a Real Time Block List for Twitter which users could decide for themselves whether to trust or not.

This would not, of course, eliminate trolls or all abuse on Twitter, but it would have the advantage of being at least as effective as Baird’s solution while still offering a solution that errs on the side of free speech.


CrypTweet is an attempt to create a tool to encrypt Twitter DMs. Unfortunately, pretty much as soon as it was released it faced an enormous backlash for a number of implementation errors. The author frankly admits to the numerous problems on the CryptTweet website now and says the tool is only for experimental purposes.

Personally, if I had a need to send encrypted Tweets I’d use one of the PGP tools for smart phones or computers (such as AGP for Android) and encrypt the text before posting.

Some critics of CryptTweet wondered what the point would be of encrypting Twitter DMs. However, I can think of some interesting ways to use something like Twitter in conjunction with PGP to securely coordinate activities that might otherwise be easily observed/intercepted by police and other government authorities.

Death of Email, Episode VII

It seems like someone is constantly proclaiming the death of email as in this GigaOm article about IT firm Atos Origin planning to stop using email in its internal operations.

GigaOm writer Miguel Valdes Faura points to things like social networking and tools like Salesforce’s Chatter as things that are gradually replacing email.

Look, here’s the thing — the beauty of (most) email is that it is based on an open protocol, SMTP. I have email I sent and received in the late 1980s that I can still read on an email client that was just released yesterday, thanks to the wide support for SMTP.

I’ve also had the same email address for 16 years even though I’ve changed email hosts 6 or 7 times during that period. During a small part of those 16 years, my email was hosted at another company, but for most of the time I’ve owned the server that my email domain ran on. Today, it is dirt cheap for anyone to grab a domain name and a hosting account that includes a mail server.

Social networking and similar systems are largely the antithesis of prevailing state of affairs with email. I can use my Google+, Twitter, Facebook and other accounts only because those companies have decided to continue to allow me to — and their Terms of Service make it clear they can change their mind at any moment and cut me off for pretty much any reason.

On the other hand, if I get fed up with one of my social networks, there’s little I can do but close my account and leave. Since all of these companies use proprietary standards, I can’t easily move my Twitter account to Facebook, much less even consider moving either account to my own webserver.

I can (and do) get my data out of these systems, with varying degrees of difficulty, but just having static copies of the data doesn’t come close to replicating my account. Moreover, most of these systems seem to be getting less open. Twitter, for example, used to make it obvious where the RSS feed for your tweets was, but now they hide it like they’re ashamed of it (or, more likely, can’t figure out how to monetize it).

Every time I read someone write about relying on social networking or closed systems, I always think of the BBC’s Domesday Project — an early attempt at creating a digital artifact in which more than a million people participated. But, of course, the Domesday Project is famous in part because the BBC chose to use a proprietary technology that quickly became obsolete and almost rendered the entire project unreadable.

Social networking, as it is currently constituted, is one giant Domesday Project just waiting to happen.

WordTwit Pro

WordTwit Pro is one of the few commercial WordPress plugins I’ve paid for, and am extremely happy with. This is another plugin designed to let users automatically tweet blog posts. I’ve played around with quite a few of these, but this is the only one that had all the features I needed.

What I especially liked was the ability, seen in the screenshot below, to schedule tweets to occur a certain amount of time after a post gets published. WordTwit Pro also supports a variety of URL shorteners, including self-hosted YOURLS installs, and has a very simple but thorough interface for editing what finally gets tweeted.

Finally, I didn’t have any problem at all actually getting it to tweet without having to jump through a bunch of hoops. Most of the other post-to-Twitter plugins I tried were a pain in the ass to configure to actually work properly with Twitter.

Expensive ($39 to $99 depending on the number of sites you want to install it on) but worth it.