Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Application for Twitter Developer Account #144
Just creating an issue for record purposes...
I received an email from Twitter on 01-Oct-2018:
I'm pretty slow at getting around to things (sorry)... I have just done part 1) of this; We already had a developer account, this is the newer style developer account. Will follow-up with 2) when they've reviewed it...
...I'm actually unsure why we need "elevated POST access", but it seems we do.
I wonder if it's worth just throwing away our old creds and create new. It could be that there are still old installs using the version that included a default application key. I haven't received these notices for the other two accounts I use with OysTTYer.
For the record these are the emails
1 - My initial email - basically filling in the same info they'd asked for on the web form
sending this information again as requested.
Oysttyer is the official fork of the now defunct TTYtter from
Oysttyer does not analyse Tweets, users or their content.
Oysttyer, being a command line client, does not independently Tweet,
As a text based command line client it displays people's timelines in
[EXAMPLE OF MY TIMELINE]
2 - Their response
Thank you for your response.
At this time, we still do not have enough specific information about your intended use case to complete review of your application. As a reminder, we previously requested additional information about:
The core use case, intent, or business purpose for your use of the Twitter APIs
Note that “business purpose” in this context includes uses not necessarily connected to a commercial business. We require information about the problem, user story, or overall goal your use of Twitter content is intended to address.
If you are a student, learning to code, or just getting started with the Twitter APIs, please provide details about potential projects or areas of focus.
If you intend to analyze Tweets, Twitter users, or their content, share details about the analyses you plan to conduct and the methods or techniques
Note that “analyze” in this context includes any form of processing performed on Twitter content. Please provide as detailed and exhaustive an explanation as possible of your intended use case.
If your use involves Tweeting, Retweeting, or liking content, share how you will interact with Twitter users or their content.
If you’ll display Twitter content off of Twitter, explain how and where Tweets and Twitter content will be displayed to users of your product or service, including whether Tweets and Twitter
Where possible, please share links to illustrations and/or sample work products. Note that we can’t view attachments.
To provide this information to Twitter, reply to this email. Failure to provide the necessary information will result in the rejection of your application.
Thank you for your interest in building on Twitter.
3 - My reply to that response
On 16-Oct-2018 13:42:02, firstname.lastname@example.org wrote:
Ok, thanks. I shall try to provide enough detail this time. Sorry for
On the "elevated POST access" note: We provide Oysttyer as source code
The main aim of this project is to provide a text based command line
Not a student. It's an opensource project so students may be
Ok, in this case the tweets are "analysed" - i.e. the tweets are
Here's an instance of processing of data to get media URLS from
A instance of processing of the API data to construct a "tweet"
An instance of how "quoted" tweets are displayed inline:
I.e. we try to replicate Twitter's display preferences as much as
These actions are performed via Readline commands:
Here's a lot of detail on the user interaction required:
Providing some more examples of what timelines look like:
[EXAMPLE OF MY CURRENT TIMELINE]
[EXAMPLE OF MY REPLIES]
This generic email today:
So doesn't seem like a huge deal for us if folk are using their own keys.
Ok, submitted that...
Can "normal" folk create their own applications any more? Maybe that's the whole issue. I'm a little bit out of the loop with things. I.e. I syndicate (some) tweets through my website and created an app for that, but that was before the whole "developer account" requirement came in.
Ugh (and not at Twitter this time):
I think the answer here, if I understand the problem, is to revoke the app keys we used to ship with. We've been suggesting BYO key for a while, so this shouldn't be too much of an issue for the user base. Heck, it's one of the few things we actually have documented
Sent this for now to buy some time to think things over:
Wow, ok. That was unexpected.
As an open-source (Perl based) application the oauthkey and secret are
We are thinking this over. The problem is we are in a bit of a catch-22
Will be back in touch soon.
Just an idea, but perhaps a middleman proxy/firewall service that users connect to that enforces limitations. Users can be authenticated (i.e. OAuth) and limitations can be imposed per user or limitations can just be imposed per IP. If going with authentication, each authenticated user can only be associated to one Twitter account and each Twitter account can only be associated to one authenticated user. This one-to-one will further help prevent abuse from multiple accounts on either side. Maybe requiring e-mail and/or phone verification could also be implemented to further secure it.
It would essentially be a buffer service to protect the Oysttyer developer account, while users will always also have the option of, of course, creating their own developer account if they don't like the shared restrictions. And since Oysttyer is designed to talk directly to Twitter and not through a middleman, it means the functions of the middleman can be kept relatively simple and primarily just forward along the messages, or not, while gathering statistics, unless there's interest in creating a whole new API which might provide some enhancement/improvement over the current Twitter API.
An added benefit of using a middleman service is that statistics can then also be gathered, anonymously of course, to know the average volume and frequency of tweets per user so reasonable limitations based on average usage as well as overall population usage can be better calculated. The overall population usage is also important since all users are essentially in the same pool under the same Oysttyer developer account and obviously not every user is "average."