Re: [twitter-dev] consistency and ecosystem opportunities
Scott, I don't think it's ludicrous to think that Twitter may eventually pull the plug on, say, statuses/home_timeline, effectively eliminating clients. If Twitter's concern is ad revenue, all they'd need to do is add a clause to their TOS specifying that all third-party clients must show in-line ads or the quickbar or whatever else Twitter uses to generate revenue. Then the issue is very clear for developers -- either integrate Twitter's revenue-producing content into your client, or don't make a client at all. The fact that they seem to be going about this a different way, and being a bit unclear as to what might happen to a client-only app, leaves open the possibility that they simply want to close down the market so the only access to one's timeline is via a first-party app. Scott Wilcox wrote: > Hello, > > For a few days now I've read what people have said in reply to the update > from Ryan. There are some crazy reactions and responses to what Ryan has > said. In essence, the entire reaction is my opinion is completely overblown. > > Not in any sense what-so-ever have Twitter said that you can no longer post > updates on behalf of users. Its ludicrous to suggest so. What they have have > said (and in my opinion - quite clearly) is that it is better to direct your > time and effort into a product that is not just a simple client and does more > than just provide viewing and posting of tweets. There are so many half-arsed > clients out there that do little more than just show and post tweets. If by > chance a user was to use these low grade applications as their first > experience of Twitter, it would probably put them off using it in the long > term. > > I do fully believe that is why they have released their own branded clients > for iOS, Macs and other devices. It provides a consistent experience for the > end-users. > > The other thing that people seem to completely overlook is that Twitter are > providing a freely accessible API at no charge to developers. It pains me to > see so many developers standing the moral high ground. If you were paying for > access to a service or product and it changes, you have a very valid reason > to complain. To complain about a service provided free of charge for you to > use at the end of the day frustrates me to no end. No single developer has a > god given right to have access to the API, perhaps that should be remembered. > > Scott. > > On 13 Mar 2011, at 00:16, Adam Green wrote: > > > Interesting that neither Ryan or anyone else from Twitter has replied once > > to any of the questions here, (way to go on showing your interest in the > > developer community, Ryan), so I'll address this question to everyone else > > in the group. I don't read Ryan's message as demanding that apps are no > > longer allowed to send tweets on behalf of users. Is that supposed to be > > what he said? I think he is saying that apps should be more than *just* > > clients that let you read and post tweets. How to tell the difference, I > > have no idea, but I think in Ryan's mind there is a difference. > > > > I'll ask it as clearly as I can. Is it still allowed for an app to accept a > > tweet from a user and post it into their account? > > > > Is the /statuses/update api call still allowed in an app? > > > > Let's not wait for Twitter to respond, since they clearly don't want to any > > longer. Let's try and figure this out ourselves. What does everyone think? > > Can apps still send tweets? > > > > If yes, there is still a market for Twitter API developers. If not, the > > Twitter API is over. It is that simple. > > > > Maybe Ryan or anyone from Twitter can also find the time to answer this. > > > > On Sat, Mar 12, 2011 at 6:45 PM, Duane Roelands > > wrote: > > Wow. "Thanks for getting so many people interested in Twitter. Now > > get lost." > > > > This is appalling. > > > > -- > > Twitter developer documentation and resources: http://dev.twitter.com/doc > > API updates via Twitter: http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > > http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > > http://groups.google.com/group/twitter-development-talk > > > > > > > > -- > > Adam Green > > Twitter API Consultant and Trainer > > http://140dev.com > > @140dev > > > > -- > > Twitter developer documentation and resources: http://dev.twitter.com/doc > > API updates via Twitter: http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > > http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > > http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: consistency and ecosystem opportunities
*"a new client that would probably not get a large user base due to the official clients marketshare"* That would sort itself out without the need for Twitter to change their TOS -- the app would simply remain unpopular and eventually whither away. The fact that Twitter is moving toward disallowing clients indicates they see clients as a threat, otherwise they wouldn't have bothered with this. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Do new ToS conditions apply to my app?
Another use case: what about semi-private, hobby clients that do not generate revenue? If my app is forbidden because it's a "client", I'd like to maintain it for personal use (i.e., just a few user accounts). -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Do new ToS conditions apply to my app?
(Howard, I don't mean to hijack your thread, but I'm guessing a lot of people will have the "is my app okay?" question so I will keep mine here rather than start a separate thread.) I'm also curious if my app is okay. It's purpose is to let the user filter their Twitter, Facebook, and RSS feeds. Think of Echofon's recently added "mute" feature, but it gives a lot more control than that, and it also lets you make tweets more prominent as well as hide them. It's a web app, and it doesn't get any content (trends, who to follow, etc) or generate anything outside of Twitter's API (aside from Facebook and RSS, of course, which are kept separate). -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] since_id only returns ~20 results?
I didn't see this mentioned explicitly in the documentation, but it seems that calling statuses/home_timeline?since_id=XYZ only returns ~20 statuses. I'm developing an app that is intended to be able to list all tweets (respecting the limit of 200 statuses, of course). As far as I can tell, the correct solution seems to be to find the oldest ID returned in that set of 20, then make another call using max_id, and keep repeating until status XYZ is returned in the set? It seems like it would be a lot more efficient if since_id would simply return up to 200 statuses the first time since the call clearly indicates I'm looking for all tweets since that ID, but I suppose we can't all have everything we want in life ;)
[twitter-dev] Re: Entities not working?
I've retooled my app a bit to avoid using "count=X" in my REST
requests, and I've been getting the entities very consistently.
Is no one else having issues using 'count' along with
'include_entities'?
On May 28, 12:23 pm, Ellsass wrote:
> Strangely, it's working along with the parameter since_id under some
> conditions.
>
> My web app initially loads home_timeline?count=100 (the app is in its
> infancy and only I use it, otherwise I'd be using since_id and a
> cache). Every three minutes thereafter, an ajax call gets new tweets
> using home_timeline?since_id=[id]&include_entities=true. That works --
> it retrieves the entities.
>
> However, if I manually refresh (i.e., call the exact same ajax
> function explicitly rather than wait for the setTimeout to do it), I
> get the error 500 page as the response, as described below.
>
> On May 27, 9:40 pm, Ellsass wrote:
>
> > For most of the day I was getting the new entities just fine, but for
> > the last hour or two my home_timeline XML request is met with the
> > "Something is technically wrong." page as the response.
>
> > I am using PHP & EpiTwitter. This works fine:
> > $twitterInfo = $twitterObj->get_statusesHome_timeline(array("count" =>
> > "$numTweets"));
> > This was working for most of the day, but not recently:
> > $twitterInfo = $twitterObj->get_statusesHome_timeline(array("count" =>
> > "$numTweets" , "include_entities" => "true"));
[twitter-dev] Re: Entities not working?
Strangely, it's working along with the parameter since_id under some
conditions.
My web app initially loads home_timeline?count=100 (the app is in its
infancy and only I use it, otherwise I'd be using since_id and a
cache). Every three minutes thereafter, an ajax call gets new tweets
using home_timeline?since_id=[id]&include_entities=true. That works --
it retrieves the entities.
However, if I manually refresh (i.e., call the exact same ajax
function explicitly rather than wait for the setTimeout to do it), I
get the error 500 page as the response, as described below.
On May 27, 9:40 pm, Ellsass wrote:
> For most of the day I was getting the new entities just fine, but for
> the last hour or two my home_timeline XML request is met with the
> "Something is technically wrong." page as the response.
>
> I am using PHP & EpiTwitter. This works fine:
> $twitterInfo = $twitterObj->get_statusesHome_timeline(array("count" =>
> "$numTweets"));
> This was working for most of the day, but not recently:
> $twitterInfo = $twitterObj->get_statusesHome_timeline(array("count" =>
> "$numTweets" , "include_entities" => "true"));
[twitter-dev] Entities not working?
For most of the day I was getting the new entities just fine, but for
the last hour or two my home_timeline XML request is met with the
"Something is technically wrong." page as the response.
I am using PHP & EpiTwitter. This works fine:
$twitterInfo = $twitterObj->get_statusesHome_timeline(array("count" =>
"$numTweets"));
This was working for most of the day, but not recently:
$twitterInfo = $twitterObj->get_statusesHome_timeline(array("count" =>
"$numTweets" , "include_entities" => "true"));
[twitter-dev] Re: Invalid application, intermittently
1. Yes, I'm sure.
2. On one occasion I requested new API keys, and on another occasion
(as mentioned above) I deleted the app and re-registered it from
scratch. Here are the three scenarios:
A. Get new API key. App works fine for a while (a few [10?] page loads
over perhaps 5-10 minutes), before getting the error. If I wait a
while (an hour, maybe) it will work again, but only for a few page
loads/10 minutes. (A page load = 3 API calls: statuses/home_timeline,
statuses/mentions, and account/verify_credentials.)
B. Delete app, re-register from scratch. Same as above: app works fine
for a while (a few page loads or about 10 minutes), then the error,
then after waiting a while it will work again for a short time.
C. Do neither of the above (keep the same API key). Same results as
above.
As I said before, I hadn't made any changes to my API calls for a day
or two prior to the error. (I was working on the HTML/JS/CSS, so I was
making API requests, but certainly <150 per hour.) Once the errors
began, the only API-related changes I tried were to request 100
statuses from statuses/home_timeline instead of 200.
I'm not sure if this factors in, but the app isn't publicly available
(I'm blocking access to the directory with .htaccess) and it's hard-
coded to use my Twitter screen name (the same one the app is
registered under).
The only other thing I observed was that often the page would work
fine on my PC (Firefox), but as soon as I tried loading it on my
iPhone it would fail (and then fail on the PC as well). I didn't do
any careful experimentation to determine whether this was repeatable
or just a coincidence, but it's something I noticed in hindsight.
And again, everything has been working just fine for over 36 hours
now. Not a single hiccup.
On May 18, 7:02 pm, Taylor Singletary
wrote:
> Thanks, Ellsass.
>
> A few more questions to better help us identify the issue:
> - You're sure you're using the same consumer key and secret for these
> requests and not switching between different API keys and possibly
> mis-matching access tokens with the wrong consumer key?
> - Have you been making any changes to your application record on
> twitter.com or dev.twitter.com before or during these requests?
>
> Thanks!
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Tue, May 18, 2010 at 3:27 PM, Ellsass wrote:
> > Today (5/18) I haven't gotten the error at all. It was happening
> > occasionally on 5/16 and very often on 5/17 during the daytime and
> > evening, eastern US.
>
> > My request, in PHP (I've modified EpiTwitter slightly to deal in XML
> > rather than JSON):
>
> > $twitterObj = new EpiTwitter($consumer_key, $consumer_secret,
> > $_COOKIE['oauth_token'], $_COOKIE['oauth_token_secret']);
> > $twitterInfo = $twitterObj-
> > >get_statusesHome_timeline(array("count"=>"$numTweets"));
>
> > and then the contents of $twitterInfo->responseText is this:
>
> >
> >
> > /statuses/home_timeline.xml?count=100
> > Invalid application
> >
>
> > On May 18, 9:55 am, Taylor Singletary
> > wrote:
> > > This sounds strange. Can you share the return XML you get when it says
> > > "invalid application?"
>
> > > Taylor Singletary
> > > Developer Advocate, Twitterhttp://twitter.com/episod
>
> > > On Mon, May 17, 2010 at 3:56 PM, Ellsass wrote:
> > > > When attempting to retrieve a timeline (or mentions, etc) I am getting
> > > > the response "Invalid application" in the XML. I am using Oauth (with
> > > > EpiTwitter). It just started today, and occasionally I will be able to
> > > > retrieve the timeline with no problems. I am not hitting my rate limit
> > > > (I am the only one using the app) and there are no messages on
> > > > dev.twitter.com. If I delete and re-register the app it will work a
> > > > few times, then die again, going back to working intermittently.
>
> > > > Any idea what could be causing this? I haven't changed any of my API-
> > > > calling code for a few days.
[twitter-dev] Re: Invalid application, intermittently
Today (5/18) I haven't gotten the error at all. It was happening
occasionally on 5/16 and very often on 5/17 during the daytime and
evening, eastern US.
My request, in PHP (I've modified EpiTwitter slightly to deal in XML
rather than JSON):
$twitterObj = new EpiTwitter($consumer_key, $consumer_secret,
$_COOKIE['oauth_token'], $_COOKIE['oauth_token_secret']);
$twitterInfo = $twitterObj-
>get_statusesHome_timeline(array("count"=>"$numTweets"));
and then the contents of $twitterInfo->responseText is this:
/statuses/home_timeline.xml?count=100
Invalid application
On May 18, 9:55 am, Taylor Singletary
wrote:
> This sounds strange. Can you share the return XML you get when it says
> "invalid application?"
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Mon, May 17, 2010 at 3:56 PM, Ellsass wrote:
> > When attempting to retrieve a timeline (or mentions, etc) I am getting
> > the response "Invalid application" in the XML. I am using Oauth (with
> > EpiTwitter). It just started today, and occasionally I will be able to
> > retrieve the timeline with no problems. I am not hitting my rate limit
> > (I am the only one using the app) and there are no messages on
> > dev.twitter.com. If I delete and re-register the app it will work a
> > few times, then die again, going back to working intermittently.
>
> > Any idea what could be causing this? I haven't changed any of my API-
> > calling code for a few days.
[twitter-dev] Invalid application, intermittently
When attempting to retrieve a timeline (or mentions, etc) I am getting the response "Invalid application" in the XML. I am using Oauth (with EpiTwitter). It just started today, and occasionally I will be able to retrieve the timeline with no problems. I am not hitting my rate limit (I am the only one using the app) and there are no messages on dev.twitter.com. If I delete and re-register the app it will work a few times, then die again, going back to working intermittently. Any idea what could be causing this? I haven't changed any of my API- calling code for a few days.
