James

I hope people use Twitter less

2 min read

Alex Gaynor wrote this great piece "I Hope Twitter Goes Away". I agree with a lot of what he says.

His basic argument is that Twitter is all about Broadcast, and the side effects that has. This makes communities and genuine discussion very hard, and makes abuse more likely.

But I don't want Twitter to go away; in some specific cases it's really good. At conferences, the broadcast of random information that is immediately useful and thoughts can really help people know whats going on and feel involved. In general, passing round the headlines of what news and new blog posts people think are interesting is good. And some of the bad jokes are pretty good.

But I do want people to use it much less.

I find it really odd when someone gives a talk and they only have a Twitter handle as a contact detail on their slides. Why not an email address? (This especially applies at the more Open Source orientated events. "We want freedom from central control .... unless you want to contact me!").

I find it really odd when people refer to themselves by a Twitter handle.

I hate getting into any serious discussion longer than a few tweets back and forth.

And after saying it can be good as a Broadcast medium, not always - I hate it when Twitter is the only broadcast and communication medium someone uses.

I guess you could also read this as an apology for my own Twitter account. I feel I use it as a broadcast tool only, and it's not very interesting. I'll try to blog more instead ...

 

James

Idea: An evil twitter bot

1 min read

An evil twitter bot that searches for people posting things like "Only 5 more followers until we have 500, please RT!". It then follows them and waits a couple of days before replying with "Quality is more important than quantity. *unfollow*" - and unfollowing.

I won't do this, but thought I'd mention it ...

James

Dealing with Twitter apps inflexible permissions

3 min read

Facebook apps, which can ask for any set of permissions from a user at any time, can start by requesting some basic permissions and can request others later when the users trust has been won. In contrast, Twitter apps are very inflexible. You must set what permissions you want and ask for them at the start, with no chance to change them.

If your Twitter app could work equally well with both read-only or write permissions, what do you do? If you ask for read permissions part of your app won't work, and if you ask for write permissions then some users may be scared to give them to you and just abandon your app.

For ShowShift, I had this problem and I decided to try a different approach. I made 2 Twitter apps, one with read-only permissions and one with read and write permissions.

When the user signs up

The login link they first click is for the read-only app; then they are logged into the app and can use it at will. But they are prompted that if they let us have write permissions, they get more features.

The yes button takes them to Twitter to authorise the write app.

Behind the scenes

You now may have two sets of tokens for each user; one for the read-only app and one for the write app. Store them in separate columns in your user table and then use what ever is appropriate for what your doing.

CREATE TABLE user_account (
  id BIGINT NOT NULL,
  ....
  read_only_oauth_token VARCHAR(250),
  read_only_oauth_secret VARCHAR(250),
  write_oauth_token VARCHAR(250),
  write_oauth_secret VARCHAR(250),
  PRIMARY KEY(id)
);

When the user returns

The login link they first click is for the read-only app; so the login and sign up link is the same. This is enough to authenticate them and let them into the app.

Is this worth it?

Is having two apps, and the fuss of having to ask the user for authorisation twice to much? Is the proportion of users who are put off by your app asking for write permissions to start with so small that this added complication isn't worth it? For some apps, maybe.

However, the users of ShowShift are going to be quite geeky to start with because of what it does, so I thought I'd give it a go and see what happens. The challenge now is to tweak the user interface to make it easy to understand. Comments welcome!