Functional programming, UX, tech
Twitter • GitHub • LinkedIn • RSS
My book, Functional Programming in Scala, uses Scala as a vehicle for teaching FP. Read what people are saying about it.
Unison: a friendly programming language from the future
unison.cloud: the worldwide elastic computer (coming soon)
Type systems and UX: an example
CSS is unnecessary
[ tech ]
Twitter has a problem with abuse. Everyone knows this. I’ll explain the core issue, and then explain one way to fix it.
Here’s the core issue:
Anyone on Twitter can cause a tweet to arrive in my notifications, just by mentioning my Twitter handle. And related to this, anyone viewing my timeline or following me can see these tweets, assuming they are replies to tweets I’ve made.
So, if some hateful nutjob decides they don’t like me, they can tweet at me, and I’ll have to see it or at least know it’s there, and people who expand the thread under each of my tweets can see it also. I haven’t granted this person the capability to contact me, yet Twitter allows it by default. If a mob of hateful nutjobs get together to abuse someone via Twitter, there is no real way to prevent it. The person being abused can block individual accounts, can report individual accounts, but that’s really unsatisfactory:
All right, now here’s a simple solution. I’ll make a few tweaks to it below, but this is the basic idea:
Twitter should expose a setting which prevents Tweets from “untrusted” people from arriving in my notification timeline, or being visible to people who follow me.
It would be up to each Twitter user to define their “trusted” set of people. Here are some suggestions:
You get the idea. Rather than just blindly trusting everyone with the authority to write to your notification timeline (about as sensible as giving everyone on the planet your home address and a key to your house) you instead assign trust more explicitly.
Let’s see how this plays out:
I have a couple improvements to this scheme:
Without the ability to communicate with their victims, Twitter is no longer an easy vector for abuse. I won’t say that it’s impossible, but the costs of perpetrating abuse have become higher, and it’s easier to combat. If Twitter implemented something like this, I believe it would have a huge positive effect.
Some people might object that one of the points of Twitter is that anyone can contact anyone else in a sort of free-for-all global conversation. And Twitter gets used for “activism” for that reason. If a politician does something awful, it can be a good thing that a “mob” of people can rise up on Twitter and make their voice heard. If that politician had his/her trust level turned way down, this sort of uprising can’t happen as easily.
My response to this is that we should encourage public officials and the like to publicize their trust levels and generally keep them set in a way that lets them and everyone else see just about all communication directed at them. That is, the way to deal with politicians or public figures who don’t want to engage with the public is with simple social pressure. It’s simply expected that certain people have communication lines open with the public.
Another objection is that if this gets implemented, Twitter would get used less because fewer messages are being delivered and thus fewer conversations are taking place. To me this doesn’t seem like a problem, since the messages that aren’t being delivered are the messages that users have explicitly indicated they don’t want delivered. If some good messages get missed, why is this such a bad thing? Unless you spend all your time on Twitter, you miss some good messages anyway because the signal to noise ratio is so low!
Furthermore, the fact that Twitter provides such a rampant abuse vector has a very chilling effect. People avoid joining the platform, speaking their mind, or participating in conversations out of concern that that they’ll be exposed to nasty responses.
But honestly, I don’t really care whether this feature improves or hurts Twitter’s bottom line. I think it’s just the right thing to do.
comments powered by Disqus