"What Twitter doesn't allow us to do"

[judofyr]

Let's show the world exactly why rstatus was created and how silly the new rules in the Twitter API is. I'd love to see a page that says everything which we are not allowed to do with the new rules.

[judofyr]

For instance, "You may not use Twitter Content or other data collected from end users of your Client to create or maintain a separate status update or social network database or service." Which means that we can't use the Twitter API to find friends that are already using rstatus (which is something everyone does at the moment).

[caleywoods]

Why not just run it as a dickbar across your user homepage?

[steveklabnik]

I both like and dislike this.

There's a fine line to walk between 'we're awesome' and 'twitter sucks' as a focus, you know?

[judofyr]

I see your point, but we should at least mention (somewhere, somehow) why rstat.us doesn't have feature/itegration x, when the reason is that Twitter API rules are very strict.

[caleywoods]

@steveklabnik I agree but it seems I've seen several instances where a bit of public shaming went a long way towards changing things for the better. Though i'd also guess there are many times when at best it does nothing and at worse irritates the wrong people.

[steveklabnik]

Totally. Like I said, fine line. We should find it.

[brack]

I'm with judofyr- might work smoothest as an entry on a FAQ.

Q: "Why can't I X?" A: As per Twitter TOS(link to TOS), we're unable to implement X without violating said TOS

Then it's not a blatant point on the homepage, but if someone's looking for the answer, they'll find it without thinking "omg this rstatus thing blows i can't do X"

[colindean]

Or, implement it for every other service which allows it and have a link which says, "Where's Twitter?"

[steveklabnik]

This ticket has been moved to lighthouse: http://rstatus.lighthouseapp.com/projects/73488-rstatus/tickets/11-what-twitter-wont-let-us-do