> Thanks for the feedback, guys. We'll consider extending Basic Auth's
> life, or maybe granting a "stay of execution" to known-good apps. At the
> very least, we'll try not to pull the rug out from under anyone.
I appreciate the consideration. :)
--
perso
Thanks for the feedback, guys. We'll consider extending Basic Auth's
life, or maybe granting a "stay of execution" to known-good apps. At the
very least, we'll try not to pull the rug out from under anyone.
funkatron wrote:
Agreed. I do believe that the use of HTTP Basic Auth was key to the
This isn't the only spam/abuse/"SEO"/"marketing" product out there for
Twitter. We have a bunch of metrics in our system that keep tools like
these from being effective in the long-term. I do not wish the
developers well, to say the least.
Max wrote:
So just to be a dick (and cuz I'm bored
So just to be a dick (and cuz I'm bored), I downloaded the demo and
decompiled the JAR files. In attempts to work around the API limits
they post directly to the web forms using httpswell I assume its
to work around the API limits, either that or they are slightly stupid
and did alot of work
Agreed. I do believe that the use of HTTP Basic Auth was key to the
quick growth of the 3rd-party app community of Twitter, as the auth
scheme is so well-understood and supported. This may or may not be as
important at this point business-wise, as I suspect the Twitter
userbase is large enough to
Any chance of a easy way to map this to usernames? We want the friends list
for Witty (and I imagine others), but we don't need full profiles, just this
+ username. This won't help us otherwise since we'll need to map the entire
list to usernames, which will require too many requests.
JD
On Wed,
On Wed, Feb 4, 2009 at 1:07 PM, Burhan TANWEER wrote:
> Wonderful news !!!
>
> We will be using for our social search engine application. Thanks for
> coming up with these new API for friends and followers ids. I apprecaite it.
>
> On Tue, Feb 3, 2009 at 8:01 PM, Alex Payne wrote:
>
>>
>> Happ
> Sorry for chiming in on this late by I have been working with
> @mrtall on the OAuth code. Your first question about allowing OAuth
> and Basic Auth to co-exist is one we've covered a few times in this
> group but it's sort of buried in the documentation [1]. We plan to
> keep Basic
I do like how they randomly put "TODAY" in double quotes. (maybe that's air
quotes?)
On Wed, Feb 4, 2009 at 6:37 PM, Cameron Kaiser wrote:
>
> > Hey Alex and gang,
> >
> > I am sure you have seen this, but just out of curiosity you got
> > anything special planned for this?
> >
> > http://tweett
> "Cameron" == Cameron Kaiser writes:
>> Hey Alex and gang,
>> I am sure you have seen this, but just out of curiosity you got
>> anything special planned for this?
>>
>> http://tweettornado.com/
Cameron> I'm sure they're not greatly concerned about a product that can't
Cameron> even spell
Eric,
Please do provide some basic recreate steps... not much to go on here.
@dougw
On Feb 4, 9:08 pm, pnoeric wrote:
> I've been having some strange issues with following new people-- I'm
> issuing the createFriendship call as always, Twitter doesn't appear to
> be returning any error or other
> Hey Alex and gang,
>
> I am sure you have seen this, but just out of curiosity you got
> anything special planned for this?
>
> http://tweettornado.com/
I'm sure they're not greatly concerned about a product that can't even
spell 'niche' correctly. I think the users of that product have more
I've been having some strange issues with following new people-- I'm
issuing the createFriendship call as always, Twitter doesn't appear to
be returning any error or other result code, but then when I manually
check on my account, we're not following the new person. I didn't see
anything specific
Hey Alex and gang,
I am sure you have seen this, but just out of curiosity you got
anything special planned for this?
http://tweettornado.com/
-Max
Chad, Very nice :)
suggestion: allow filter by language (if the API supports this).
Rob Iles
2009/2/4 Chad Etzel
>
> I thought about doing that, but I don't want to overload people's
> browsers and memory by loading a metric-ton of images. From my
> experience, most browsers don't handle dyna
The response should be ordered with most recent followed/followers first
in the list.
Another developer noted duplicates; we'll look into that.
Matt K. wrote:
Alex -
This is a great addition to the API - will make things much easier.
Quick question (and I apologize if this is already docum
http://apiwiki.twitter.com/FAQ#WhatstheDataMiningFeedandcanInbsphaveaccesstoit
ym wrote:
So I played a bit with your API and I can call public_timeline to get
20 recent statuses. My IP address should be white listed on your
servers by now; how do I access the data mining feed? do I just call
pu
So I played a bit with your API and I can call public_timeline to get
20 recent statuses. My IP address should be white listed on your
servers by now; how do I access the data mining feed? do I just call
public_timeline and it will return 600 statuses every min.? I didn't
find any docs about it.
T
If I'm already whitelisted, how can I access the DM feed? I can access
the public timeline using the REST API to get 20 recent statuses, but
I need a lot of data, so it would be much faster if I can get 600
every min.
Thanks!
ym
Hi all,
Sorry for chiming in on this late by I have been working with
@mrtall on the OAuth code. Your first question about allowing OAuth
and Basic Auth to co-exist is one we've covered a few times in this
group but it's sort of buried in the documentation [1]. We plan to
keep Basic A
I'm getting duplicates in some of my calls to these methods. I've only
seen it happen in those with a very large number of followers
http://twitter.com/Wossy - 56, 000 followers with 11 duplicates.
http://twitter.com/stephenfry - 120, 000 followers with 164
duplicates.
http://twitter.com/kevinros
Hi,
I have developed an application to read public timeline but it shows
status in multiple languages. I did not see any attribute about
language. How can I differentiate multiple languages from public
timeline?
2009/2/4 Gustavo Melo :
> We need to understand how OAuth will affect ours app's...
> Twitter authentication with username and password will totaly stop work?
> How many days we will have to change our app's?
> And for me the most important question is, "OAuth before copmleted
> authentication fo
Unless these messages are known to be in the same timeline where you
could parse them out, you have to use serial requests of statuses/
show.
You can always open a new enhancement issue, as this is something that
I know a number of people would like:
http://code.google.com/p/twitter-api/issues/l
So this is where your gripes about JS freeing memory come from that I
saw you tweet about days ago...
On Feb 4, 12:32 pm, Chad Etzel wrote:
> I thought about doing that, but I don't want to overload people's
> browsers and memory by loading a metric-ton of images. From my
> experience, most bro
Awesome. I still do downloads of follower lists because it is an easier way
to get a batch of
information from the profile data than requesting every single one, but this
already is a huge advancement.
Small suggestion: Add a last changed info to it for social graph change or a
number?
Like if I
Hello Guys, Matt and Alex...
We need to understand how OAuth will affect ours app's...
Twitter authentication with username and password will totaly stop work?
How many days we will have to change our app's?
And for me the most important question is, "OAuth before copmleted
authentication for us
Wonderful news !!!
We will be using for our social search engine application. Thanks for coming
up with these new API for friends and followers ids. I apprecaite it.
On Tue, Feb 3, 2009 at 8:01 PM, Alex Payne wrote:
>
> Happy to announce two new API methods today, delivered in response to
> de
I thought about doing that, but I don't want to overload people's
browsers and memory by loading a metric-ton of images. From my
experience, most browsers don't handle dynamically generated pages'
memory or garbage collection too well. I come from an embedded
point-of-view, so my definition of "
looks great Jazzy! Works extremely well too.
I was thinking one thing, once it got to 200 pics, it could throw up a "page
2" tab, and so on.
On Wed, Feb 4, 2009 at 9:09 AM, Chad Etzel wrote:
>
> Thanks to those who provided feedback.. I have made some small tweaks:
>
> - Added an "Auto-Scroll"
This is great news. Will make life much easier for a lot of people.
Thanks!
On Feb 4, 4:19 am, rhysmeister wrote:
> A great addition to the API. Thanks for lsitening!
>
> Rhys
>
> On Feb 4, 1:01 am, Alex Payne wrote:
>
> > Happy to announce two new API methods today, delivered in response to
>
Thanks to those who provided feedback.. I have made some small tweaks:
- Added an "Auto-Scroll" option which will scroll the page as new pics come in.
- Added "Auto-Resume after 200 pics" option for
continuous/screen-saver type mode.
- Made Pause/Resume links mutually-exclusive with
Fade-In-Fade-
I have read through the documentation for REST API and Search API and
could not find an answer to this.
Is there a way to retrieve multiple status messages in a single
request? i.e. I have status ids 1234, 1235, 1236 and would request
using http://twitter.com/statuses/index.xml?id[0]=1234&id[1]
try increasing your connecttimeout
On Feb 3, 8:48 am, Cameron Kaiser wrote:
> > On Sunday (1 Feb 2009) I embedded the following code in my website
> > (with appropraite variables set correctly):
>
> [...]
>
> > Which worked fine up until Monday morning (02 Feb 2009, 10:00 GMT
> > ish). It then f
2009/2/4 Chad Etzel :
> With many thanks to Noah Everett (the TwitPic dude) for allowing the
> use of TwitPic thumbnails, I have created TwitPicGrid at
> http://tweetgrid.com/twitpicgrid as a mashup. Watch new TwitPics
> arrive as they are tweeted, or search for keywords associated with the
> pic
A great addition to the API. Thanks for lsitening!
Rhys
On Feb 4, 1:01 am, Alex Payne wrote:
> Happy to announce two new API methods today, delivered in response to
> developer demand for an easier way to keep tabs on users' social graphs.
> The methods, /friends/ids and /followers/ids, return
36 matches
Mail list logo
