There's an open issue about this:
http://code.google.com/p/twitter-api/issues/detail?id=2197
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
Matt,
If I understand correctly, activate the new permission, all Read and
Read/Write user_tokens issued to third-party applications will lose
their ability to read direct messages.
That is a HUGE and MAJOR headache for existing apps and their
thousands of users who are currently using any of
The more I think about this, the less it makes any sense whatsoever to
force everyone through a re-authentication if DM access is required.
Here's why:
1) For existing user tokens, the users have already granted access
with the knowledge that it is to their DMs as well. In other words,
they have
that way. It is disrespectful when you treat your business partners
that way.
Does Twitter like pointing a loaded gun at its own foot and pulling
the trigger, again and again?
On May 6, 4:38 am, Arnaud Meunier arn...@twitter.com wrote:
Dewald,
These rules apply to third party apps. @twittersuggests
With reference to @twittersuggests, is other unsolicited @reply spam
now also officially sanctioned by Twitter?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
or approved this action in advance?
If not, then you may have de facto invalidated that section of your
rules and by implication exempted all developers and applications from
it.
On May 5, 12:45 pm, Arnaud Meunier arn...@twitter.com wrote:
Hey Dewald,
Neither our TOS nor our Automation Rules Best
Twitter, are you aware that your API is throwing 502s left right and
center on blocks/create/nnn.json and report_spam.json?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
Here's one of the best and most thoughtful articles yet on this latest
ecosystem bomb:
http://radar.oreilly.com/2011/03/twitter-developers.html
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements
Sometimes it takes just a slightly different perspective for the sun
to raise its head above the horizon of the blatantly obvious. And
everything suddenly makes perfect sense.
In other news, Echofon Pro is a better iPhone client, IMHO.
--
Twitter developer documentation and resources:
Raffi,
You wrote, ...focus your efforts on that and just follow our lead
with tweet rendering and interaction.
This approach perpetuates and aggravates the fears and hostility in
the developer community that you (Twitter) sprouted when you bought
Tweetie, and absolutely nothing has been said or
I used to be counted in the 90% until they defaced Tweetie, sorry,
Twitter for iPhone with that moronic #DickBar that shoves irrelevant
nonsense in your face. It's like yelling at you, I KNOW YOU DON'T
WANT TO SEE THIS AND HAVE NO INTEREST IN THIS, BUT HERE, TAKE IT
ANYWAY. LEARN
You're missing the next step, Scott. The #DickBar will become
mandatory for all clients.
On Mar 13, 3:54 pm, Scott Wilcox sc...@dor.ky wrote:
You still have the ability to change to a newly developed client if you want
to.
Sent from my iPhone
On 13 Mar 2011, at 18:50, Dewald Pretorius dpr
, they don't show ads next to them
that yell, #WHATNOTTOSAYTOAFATWOMAN.
On Mar 13, 4:18 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
On Sun, 13 Mar 2011 11:49:45 -0700 (PDT), Dewald Pretorius
dpr...@gmail.com wrote:
I used to be counted in the 90% until they defaced Tweetie, sorry
Raffi,
Can you (Twitter) please get your message straight?
Here's what Ryan said, More specifically, developers ask us if they
should build client apps that mimic or reproduce the mainstream
Twitter consumer client experience. The answer is no.
No you're saying something different. So, which
Raffi, now is the right time to ask for a raise. Just saying...
On Mar 13, 8:09 pm, Ryan Sarver rsar...@twitter.com wrote:
To be clear, Raffi is clearly articulating the situation. It's a complex
thing and we can't expect to get it perfectly right the first time, so the
dialogue and questions
The most telling change in the Terms of Service occurred in sentence
#2 or paragraph #1 under section Rules of the Road.
It used to read: We want to empower our ecosystem partners to build
valuable BUSINESSES around the information flowing through Twitter.
It now (since March 11, 2011) reads: We
Apart from implementing reCAPTCHA on tweet submission, follow, and
unfollow, I can't see what Twitter can do to prevent that kind of
abuse (can you imagine the revolt by bona fide users?). How else do
you determine that it is an actual human and not a piece of automated
software behind the browser
:
It sends you an event when our subject user follows someone else, unfollows
someone else, or when they are followed by someone else. It does not send
an event when they are unfollowed by someone else.
Tim.
On Tue, Feb 15, 2011 at 3:08 AM, Dewald Pretorius dpr...@gmail.com wrote:
If I
If I remember correctly, Site Streams sends you a transaction only
when the user follows another user (adding to Following). It does not
send you a transaction when someone else follows that user (adding to
Followers). I don't know if this work the same in User Streams.
Clarification by Twitter
If you're basing your business on the Search API it definitely sounds
as if you're not aware yet of the [mostly unofficially documented]
limits and constraints [mostly just alluded to by John Kalucki and
others through their exhortations on this list for people to rather
use the Streaming API] on
.
On Nov 18, 12:48 am, John Kalucki j...@twitter.com wrote:
Every search engine, social network, blogging platform, content aggregator,
and to a certain extent, every used book store and used record store...
-John
On Wed, Nov 17, 2010 at 1:04 PM, Dewald Pretorius dpr...@gmail.com wrote
Ryan,
The Gnip blog post states:
[QUOTE]Twitter Decahose. This volume-based product is comprised of 10%
of the full firehose. Starting today, developers who want to access
this sample rate will access it via Gnip instead of Twitter. Twitter
will also begin to transition non-display developers
Ryan,
Thanks. Can I then suggest that you request Gnip to modify the
description of their Twitter Decahose feed. They refer to it as a
sample rate, which immediately creates confusion with your statuses/
sample.
On Nov 17, 2:09 pm, Ryan Sarver rsar...@twitter.com wrote:
Dewald,
The basic
The minimum Gnip charge is $500 per month, with a minimum of a year
contract, if you want to use Gnip in a production application.
And that's before the -- still unknown -- additional access charges
for the Twitter feeds.
You can't use Gnip in a production application if you are not an
By the way, if you get Twitter data from Gnip, you are not bound to
the Twitter TOS. Your business and contractual relationship is with
Gnip, not Twitter.
On Nov 17, 3:28 pm, Dewald Pretorius dpr...@gmail.com wrote:
The minimum Gnip charge is $500 per month, with a minimum of a year
contract
what are the benefits for the
developer.
On Nov 17, 3:49 pm, Adam Green 140...@gmail.com wrote:
Dewald, I can't speak for Twitter, but I think you are missing the
path they seem to be building. As an independent developer you can
still use the streaming API at the default level of 400 keywords
:
That's explicitly not true. You are bound by both the Twitter API
Rules and Gnip's TOS
On Wed, Nov 17, 2010 at 1:31 PM, Dewald Pretorius dpr...@gmail.com wrote:
By the way, if you get Twitter data from Gnip, you are not bound to
the Twitter TOS. Your business and contractual relationship
-
cell: 1.510.333.0295 Twitter - rycaut
On Wed, Nov 17, 2010 at 10:09 AM, Ryan Sarver rsar...@twitter.com wrote:
Dewald,
The basic levels of all of the streaming APIs -- Spritzer, Follow,
Track -- will remain open, free and direct from us. Elevated levels
you can
use any access token, or must request a token from an endpoint
specific to the Streaming API.
On Nov 8, 7:46 pm, Tom van der Woerdt i...@tvdw.eu wrote:
Streaming API doesn't differ from the REST API with it's authentication.
Both use OAuth 1.0.
Tom
On 11/8/10 11:55 PM, Dewald
Please update your documentation [1] for more detail information on
authenticating on the Streaming API with OAuth.
We need to know the same type of information that you currently
provide [2] for REST OAuth.
[1] http://developer.twitter.com/pages/stre0aming_api_concepts#authentication
[2]
Are any of the other POST methods now also similarly rate limited, or
is it only destroy friendship?
On Oct 5, 11:13 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi James,
I'll re-post this in the group thread as well.
Due to potential abuse, we've begun locking down bulk
Matt,
I'm aware of those rate limits. I was referring to methods that used
to be, Give us all you got, such as destroy friendship. For example,
create block, destroy block, etc.
On Oct 6, 3:38 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Dewald,
There are other methods which
Is the URL format
http://twitter.com/themattharris
earmarked to be phased out at some point in the medium future?
In many places in my app the @username is linked to
http://twitter.com/username
and I will have to modify all those URLs to
http://twitter.com/#!/username
if the old
They must have known that this was going to be discovered. We're
developers. We like building, testing, and breaking stuff.
Unequal applications of the rules. Happens all the time. Months after
you've disabled something at the request of Twitter, you find well-
known services that do exactly the
Twitter folks, how are you going to ensure that t.co links are not
affected by over-capacity situations on your infrastructure?
If you're routing t.co links through your existing infrastructure,
absolutely *everyone's* links are going to be broken when you start
throwing fail whales, even when
I'm seeing a similar thing. Some of my users who have been OAuth
authorized for many weeks now suddenly get an invalid OAuth signature.
On Sep 1, 1:59 pm, mostafa farghaly keepon...@gmail.com wrote:
Hi,
i switched to oauth since 2 weeks or so, and deprecated basic auth
completely, and all my
This is super news.
However, if you're going to force web services to use Site Streams
when it is in production (sites must only use the REST API for data
that is not available through User Streams), then please add the
ability to subscribe only to certain elements. For example, we need
the
John,
Is that page cached, because the third sentence of the first bullet
under Important Items still says *exactly* the same?
On Aug 30, 5:15 pm, John Kalucki j...@twitter.com wrote:
Thanks. I've clarified the language.
-John
On Mon, Aug 30, 2010 at 12:42 PM, Dewald Pretorius dpr
the foggiest idea of which service it could be,
because they will have no record of API requests, or pattern of
requests, for received and sent DMs.
On Aug 30, 5:15 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
Quoting Dewald Pretorius dpr...@gmail.com:
Here's another issue
A mathematician is a device for turning coffee into theorems. - Paul Erdos
Quoting Dewald Pretorius dpr...@gmail.com:
Ed,
Developer responsibilities and developer agreements mean absolutely
nothing to that person who wants to abuse users' DMs.
In fact, they will probably trick users to authorize
Raffi,
Will the new error construct always be:
[errors][code]
[errors][message]
Or can it be sometimes:
[errors][0][code]
[errors][0][message]
[errors][1][code]
[errors][1][message]
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter:
Taylor,
I don't any longer have the details of the errors during that 18-24
hour period.
But, all seems to be good now.
On Jul 15, 10:57 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Dewald, you mentioned having problems with user/show -- can you elaborate?
On Wed, Jul 14, 2010
Please give us something credible to tell our users.
users/show has been effectively down for the past 18 hours.
I've beaten the Soccer World Cup excuse to a bloody pulp, but now it
doesn't fly with my users any more. The SSL certificate thing is also
wearing thin guys, especially since this the
, 11:42 am, Dewald Pretorius dpr...@gmail.com wrote:
We all need something to tell our users. Telling them Twitter is
falling apart is not an option.
...@twitter.com
wrote:
There is no SSL certificate for developer.twitter.com or dev.twitter.com --
there's only one for twitter.com. Normally that form submits via SSL to
twitter.com and then redirects back to dev.twitter.com. It will be fixed
soon.
On Wed, Jun 16, 2010 at 7:53 AM, Dewald Pretorius dpr
Login to developer.twitter.com kicks back developer.twitter.com uses
an invalid security certificate.
Are things falling apart in the Twitter world?
On Jun 15, 4:55 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Sorry for all the issues around this login -- I really want to get this
Perhaps I'm missing something here, but I do not see any security in
this solution, except for the user not having to enter his Twitter
credentials in an app that only he uses anyway.
Open source means, well, open (readable and modifiable by anyone)
source. Meaning, your API Consumer Key is
My guess is that Twitter uses the Google SafeBrowsing API, in addition
to other blacklist APIs.
http://code.google.com/apis/safebrowsing/
Google SafeBrowsing is basically two databases, which you can host
locally, and are constantly updated by Google. One database consists
of potential phishing
Initially I did not see a privacy issue with t.co But, having thought
more about Twitter forcing us to use the t.co link as the first-hop
destination, I believe there are some potential privacy issues that
need to be clarified.
1)
Normally you need to specify in your service or product's
This thing really is a can of worms, in terms of:
1) The impact on the ecosystem if characters are counted after link
wrapping.
2) The impact on Twitter's core system and SMS communication if
characters are counted before link wrapping.
3) The perception that there is no guaranteed stability in
Rich,
That of course would be the right thing for Twitter to do. In other
words, if they want this change, then they must take the bulk of the
pain, instead of creating a problem and dumping it on the developers
to solve.
On Jun 9, 11:46 am, Rich rhyl...@gmail.com wrote:
My proposal is you need
Raffi,
I'm fine with everything up to the new 140 character count.
If you count the characters *after* link wrapping, you are seriously
going to mess up my system. My short URLs are currently 18 characters
long, and they will be 18 long for quite some time to come. After that
they will be 19 for
This is not unique to me. This will be problematic for anyone who uses
a shortening service that shortens URLs to less than 20 characters.
In these cases, you are basically adding characters to the submitted
text, and then rejecting the submitted text as being too long.
On Jun 8, 8:33 pm, Dewald
wrote:
its true, and we understand that.
just to correct my previous post, however -- t.co links are 19 characters.
On Tue, Jun 8, 2010 at 4:53 PM, Dewald Pretorius dpr...@gmail.com wrote:
This is not unique to me. This will be problematic for anyone who uses
a shortening service
Raffi: Never mind. I just saw the Twitter blog post. The motivation
for this is to get metrics for Promoted Tweets and Resonance. Hence,
the answer is: Suck it up.
DeWitt: Yikes, discarding all shortens between t.co and the final link
will seriously mess with the click stats of a few million
How can this query be too complex?
http://search.twitter.com/search?q=%22for+sale+by+owner%22+near:%22fort+worth%22+within:100mi
It's a very simple geo-targeted query.
Has Search suffered a frontal lobotomy? These searches used to work
before.
On May 24, 2:32 am, Cameron Kaiser
Taylor,
I don't understand. Why would Twitter on the one hand do duplicate
checking and on the other hand advise people to add some kind of
unique string to the tweet to circumvent the duplicate checking?
You're basically saying it's okay for an application to automatically
add a randomly
, and there are corner cases where duplicate tweets can be
useful. I'm not here to tell you how to use Twitter.
On Thursday, June 3, 2010, Dewald Pretorius dpr...@gmail.com wrote:
Taylor,
I don't understand. Why would Twitter on the one hand do duplicate
checking and on the other hand advise people
Mo,
I think the word injected is causing the confusion. As I understand
it it means:
- I pull a list of tweets from the API into an array.
- Before displaying the list to the user, I inject entries that look
like tweets (but are actually entries I get paid to display) into that
array.
- Then I
Taylor,
Read this part of that FAQ: Paid Tweets injected into any timeline on
a service that leverages the Twitter API (other than Promoted Tweets).
This applies to any Twitter stream, whether user based, search based,
or other.
Do you realize how confusing that is?
1) Does it mean I can
Taylor,
Perhaps you should ask someone to add the http://bit.ly/twitter-ad-faq
link as a further reading reference into the 2. Advertising Around
Twitter Content section of the API TOS.
Stuff is very fragmented at the moment, and you have to accidentally
discover pages on separate domains just
I've seen the same thing with some of my own searches, and I just
figured the search algo was broken, because it returns results that
have absolutely nothing to do with the phrase you searched for.
On May 26, 6:24 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com
wrote:
So we have customer that
Jeepers. With one blog post Dick has killed the business of more than
a few companies that have been doing what they've doing for many
months, if not spanning more than a year.
I fully understand Dick's rationale, but, phew, why don't you guys
consider grandfathering in businesses that existed
Liz,
You are 100% correct in summarizing the problem. Not only were those
businesses built with the full knowledge of Twitter, Twitter even had
specific rules governing sponsored tweets (had to be clearly marked as
sponsored, etc.).
I'm really baffled by this decision of Twitter, because I don't
Ed,
What I find is people sometimes forget that they've set up an auto-
follow service to work on their account. Gosh, I get people who sign
up today, and the next day they ask for support because they've
forgotten their password.
These things will be easier to debug for your friend once
Raffi,
This is all good, but can you please make the inclusion in the tweet
payload optional? Meaning, only include it if it is requested by an
additional parameter?
I, and I'm sure a lot of others, are already parsing the tweet text.
This is just going to consume additional bandwidth and not
Since late yesterday (May 10), I've been getting intermittent 401
Could not authenticate you errors.
This is on Twitter accounts and code that have been working for a very
long time. My code has not changed, and there is nothing wrong with
the Twitter accounts either. They are not suspended, or
In fact, the API seems to be really borked at the moment.
I've been running more tests on friends_timeline.json, and the
following happens:
1) Sometimes the connection is refused.
2) Sometimes I get a 200 OK with an empty JSON array, and seconds
later with the very next call on the same Twitter
makes are proprietary business information.
On May 11, 11:34 am, glenn gillen gl...@rubypond.com wrote:
On May 11, 3:21 pm, Dewald Pretorius dpr...@gmail.com wrote:
As well (I know it has been discussed elsewhere), I am consistently
seeing API response times in excess of 3 seconds per call
Over time I've learned it is a best practice to check the integrity of
a returned Twitter object despite the fact that the HTTP response code
is 200.
http://media.twitter.com/blackbird-pie/
Can you guys add a meta data element to a tweet, which will provide a
blackbird pie hyperlink for a tweet.
Basically, the code behind the link should generate the code block
that Blackbird Pie currently generates. That way one can include a
Blackbird Pie
John, Sorry, I should have update this thread.
It was the ThePlanet.com outage that affected me.
On May 3, 2:21 am, John Kalucki j...@twitter.com wrote:
Did this happen to start at 10pm PST / 05:00 UTC?
On Sun, May 2, 2010 at 10:16 PM, Dewald Pretorius dpr...@gmail.com wrote:
I'm getting
I'm getting tons of connection refused errors.
What's going on?
The API status is till giving a 100% up indicator.
I can't think of a use or requirement that would need more than 1,000
tweets per day.
Unless you're promoting teeth whitening affiliate links that
absolutely must be sent at a rate of one tweet every 30 seconds,
because we all know how quickly the teeth of some followers turn
yellow.
On Apr 29,
To be quite frank, you are filling a hole.
The functionality you are describing, identifying and getting rid of
spam followers, is Twitter's job and should be part of their core
system.
On Apr 28, 8:41 am, deadlychaos deadlychaos...@gmail.com wrote:
Hi there,
We are very excited to develop an
Ducking the artillery shells and verbal mortar rounds in this thread,
I just want to ask:
Did you know @shitmydadsays actually uses status.net, and pushes its
tweets from there into Twitter via the StatusNet-Twitter bridge?
On Apr 28, 11:21 am, Dossy Shiobara do...@panoptic.com wrote:
On
Cory,
I have had similar issues. When you get that 401 error, you need to
back off for a second or two, recalculate the nonce, and then resubmit
the request.
On Apr 28, 10:52 pm, Cory cory.imdi...@gmail.com wrote:
Anyone have any ideas about this? I'm really not sure where to go or
what to
, Abraham Williams 4bra...@gmail.com wrote:
It is not twitter telling you it is China.
--
Little androids dreaming of Nexus Ones compiled this text.
On Apr 25, 2010 6:53 PM, Dewald Pretorius dpr...@gmail.com wrote:
Raffi,
We really need a resolution for this issue before Basic
In fact, you could set a threshold per consumer key that you can vary.
In other words, you can then allow a higher percentage XAuth (even
100%) to an app that caters largely to a Chinese market. And 0% or 10%
to an app that caters largely to the USA market.
On Apr 26, 9:43 am, Dewald Pretorius
Raffi,
We really need a resolution for this issue before Basic Auth is
deprecated.
It sounds as if Twitter is telling developers of web apps that they
cannot provide service to Chinese users, and other users behind
firewalls that block access to twitter.com. But that can't be right,
can it?
On
Raffi, that is super awesome. Thank you.
Any chance that you will have OAuth 2.0 in production before then?
On Apr 24, 12:40 pm, Raffi Krikorian ra...@twitter.com wrote:
hi all.
you're going to be hearing a lot from me over the next 9 weeks. our plan is
to turn off basic authorization on
Brian,
It is not unreasonable for developers to hope that Twitter does not
suspend applications for could violate rules and possible rule
violations. I trust this was just a slip of the tongue on your part.
We know you must maintain a good-citizen ecosystem.
For that to happen, we really do
-- transparently behind
the scenes it issues the Twurl console an access token and makes calls on
your behalf.
I'll look to get this business with read/write access resolved quickly.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Thu, Apr 15, 2010 at 3:06 PM, Dewald
Does @anywhere check whether JQuery is already available/loaded on the
page?
If not, will it cause any problems / conflicts / bloating to have
JQuery loaded twice?
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Perhaps Twitter should return more meaning full error messages when
API features are disabled, so that users don't see this:
http://twitpic.com/1g0e3w
On Apr 16, 1:23 pm, Abraham Williams 4bra...@gmail.com wrote:
http://status.twitter.com/post/516695583/local-trends-disabled
Marcel,
I'd strongly urge you to consider a more structured and controlled
environment for annotations.
Ideally, I think an OAuth app must register a namespace, or subscribe
to an existing namespace of another app, before it can create
annotations in that namespace. And these registrations and
Raffi,
It's not about people using or not using rogue apps. It's about rogue
apps poisoning the annotation data and ruining it for everybody.
Rogue apps can continue to refresh their consumer keys with new
accounts and OAuth app registrations, as soon as the one currently in
use is suspended.
How about an @anywhere hovercard for hashtags?
Get those promoted tweets displayed all over the place? ;-)
--
To unsubscribe, reply using remove me as the subject.
In that case, you might not want to edit your app settings through
dev. because since early this morning, the old edit URL [1] has been
throwing a fail whale. You won't be able to restore your r/w setting.
[1] http://twitter.com/oauth_clients/details/
On Apr 15, 5:12 pm, Mike Davis (mcdavis)
, Dewald Pretorius dpr...@gmail.com wrote:
In that case, you might not want to edit your app settings through
dev. because since early this morning, the old edit URL [1] has been
throwing a fail whale. You won't be able to restore your r/w setting.
[1]http://twitter.com/oauth_clients/details
John,
I know it is still some ways off into the future, but would you
consider segmenting out the areas of user streams that don't have
privacy implications, to make those parts of the stream available to
services as a higher priority compared with the rest?
For me, social graph changes are the
OAuth has benefits all around for everybody. In addition to the
benefits already mentioned:
1) For a web app like mine, it saves a TON of support workload with
people who change their Twitter password, don't change it in my
system, and then blame my system for not working because it's not able
to
From John's announcement:
User streams permissions are not tuned for service-to-service
integration, rather they are tuned for end-user-display applications.
Needless to say, it is a big disappointment that the user streams API
is not available for services, but only for desktop apps.
I could
, Dewald Pretorius dpr...@gmail.com wrote:
From John's announcement:
User streams permissions are not tuned for service-to-service
integration, rather they are tuned for end-user-display applications.
Needless to say, it is a big disappointment that the user streams API
is not available
Okay, this seriously rocks.
Congrats to everyone who worked on making dev.twitter.com happen.
--
To unsubscribe, reply using remove me as the subject.
Raffi,
Is the planning for everyone's annotations to be available to everyone
else, or will there be private namespaces accessible only to the
source application?
--
To unsubscribe, reply using remove me as the subject.
Don't be too hasty with that ad blocking code.
1) It sounds as if Twitter will share ad revenue with external apps.
2) It very well might be against (new) API TOS to use the API and
block ads (I would do that if I were them).
On Apr 13, 10:48 am, Duane Roelands duane.roela...@gmail.com wrote:
I notice that the Chirp channel is set to a private channel.
http://www.justin.tv/twitterchirp
Is it going to be made public on Wednesday, or else, where do we get
the Access Code?
--
To unsubscribe, reply using remove me as the subject.
http://api.twitter.com/1/
This also works:
http://api.twitter.com/raffi/
Wouldn't it make more sense to kick back 404s on the api subdomain?
Is Basic Auth going to be deprecated (as in hard switched-off) in
June, or are you in June going to announce depracation, with the hard
switch-off then coming a few months later?
--
To unsubscribe, reply using remove me as the subject.
1 - 100 of 482 matches
Mail list logo
