st get
the screen names, ya get almost everything twitter knows about the
user, including their current status! What more could you want! :-)
Jim Renkel
On Sep 29, 12:40 pm, "jim.renkel" wrote:
> In working with the new "cursorized" statuses/friends and statuses/
> foll
As an alternative to a hard coded 7 days for the interval to the
removal of geocoding information from a tweet, I suggest that an
optional "expires" parameter be added to the statuses/update method.
The value of this parameter would give the number of days between the
tweet creation and when the g
In working with the new "cursorized" statuses/friends and statuses/
followers methods, I noticed that in the block of users returned by
these methods that contain the last of the users following or followed
by the requesting user, the next_cursor value is "0".
Is this a reliable, guaranteed indic
I just noticed this in the API wiki, under the statuses/update method:
"Currently, all geolocated information will be removed after seven
days."
Two questions:
1. What exactly will be removed: the geocoding attached to the tweet?
Or the whole tweet?
2. Why? I.e., why remove the geocoding o
I have suggested previously that the capability of an application to
geo-code a users tweets and the capability of an application to opt-in
to geo-coding for a user be made OAuthorizable.
The application would request these capabilities when registering. If
twitter didn't trust the application, i
The blocks/blocking method appears to be similar to the statuses/
friends and statuses/followers methods, but I believe the
documentation is incomplete for all three.
According to the API spec, each call to statuses/friends and statuses/
followers returns a "page" of up to 100 users (and their mo
My website (http://twxlate.com) now supports Open Authentication with
twitter, and it was way easier than I expected, thanks to the signpost
library from Matthias Kaeppler.
It took me longer to convert the code I already had for Basic
Authentication to Apache Http Components 4.x than it did to
su
Raffi,
I fully understand the concern about privacy. To that end, here's
something you may want to consider:
Have application / web-site "over-rides" of the geo-code enable be
another option on OAuth. This way a user can control the creation of
geo-coding in their tweets on a finer grain basis.
I've opened a feature request for this in the issues database:
http://code.google.com/p/twitter-api/issues/detail?id=1011
If you like this idea and / or think it's a good thing, please
indicate your support both here and in the issues forum.
If you don't like it and / or don't think it's so hot
I asked this, and similar but more detailed questions, in my Aug 18,
7:35 pm post to this thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1e07e332ec3d449d/2d10a6a22e55133e?lnk=gst&q=ReTweet+API#2d10a6a22e55133e
but, unfortunately, have not yet received an ans
Raffi,
Another question came up as I was thinking about support for this in
my web-site (http://twxlate.com):
Will the elements returned in the responses to API requests
include information that indicates whether or not the user has opted-
in to geo-coding of their tweets?
I would like to see
Fortunately, when I tried that it didn't work.
Jim
On Aug 26, 11:29 am, JDG wrote:
> Yeah there is, albeit not a very nice one: You can dohttp://user:p...@site/
>
>
>
> On Wed, Aug 26, 2009 at 09:24, Josh Roesslein wrote:
> > How is that scrapping? He is just launching IE and pointing the brow
Hmm, using some command line test programs I've developed, I'm still
getting 'rel="nofollow"'. For example:
--
Public timeline
20 statusses
Status 0: from HandsomeSmokes, 35229362, Mula Smokes , Brooklyn
userImgURLhttp://a3.twimg.com/profile_images/372445265/IMG00064_
Wajahat,
This is just a wild guess, but it's something you should check: are
you or your API libraries transcoding the tweet to UTF-8 as you post
it?
If not, all sorts of strange things can happen.
Hope this helps.
Jim
On Aug 26, 4:14 am, Syed Wajahat Ali wrote:
> Hi,
>
> Me and my team deve
I have a similar, perhaps broader, issue and a suggestion for a
solution.
My problem is that my site, http://twxlate.com, supports 40+ languages
for its user interface, not just the two supported by twitter.com. By
that I mean that the user interface is available in 40+ languages, not
just that i
Is there any possibility of a test site, with these API response
changes, being made available before the changes are introduced to the
real site?
This would allow us to test our sites and applications against the
test site and fix any bugs and bombs before users would otherwise
experience them w
Um, I don't see any way for a user to turn the attribute
on and off. Oversight, I hope?
Jim
On Aug 20, 4:18 pm, Joel Strellner wrote:
> Hi Ryan,
>
> Will this data be available in the streaming API too?
>
> -Joel
>
> On Thu, Aug 20, 2009 at 2:11 PM, @epc wrote:
>
> > Will twitter validate the
ser_timeline.xml?screen_name=raashidbhat...
>
> On Aug 20, 9:29 am, "jim.renkel" wrote:
>
> > Yes, the *per request* limit is 200, but using the page parameter you
> > can retrieve up to the last 3200 status updates.
> > Seehttp://apiwiki.twitter.com/Things-Every-Deve
Yes, the *per request* limit is 200, but using the page parameter you
can retrieve up to the last 3200 status updates. See
http://apiwiki.twitter.com/Things-Every-Developer-Should-Know#6Therearepaginationlimits
for more information.
I've implemented and tested this in my site (http://twxlate.com)
correct.
Comments expected and welcome.
Jim
On Aug 18, 7:35 pm, "jim.renkel" wrote:
> Marcel: thank you for the quick response to my questions.
>
> Not surprisingly, your answers have raised a couple of more
> questions. :-)
>
> 1. What happens if I give aretweeti
en make that same assumption when
mentions, favorites, friends, and followers are displayed: no retweets
displayed, ergo no retweets exist. That may or may not be correct.
'Nough for now.
Comments expected and welcome.
Answers demanded! "-)
Jim Renkel
On Aug 17, 1:56 pm, Marcel Molina
Brian,
Good catch on deleting a retweeted tweet! It was on my list of issues,
by I forgot to include it in my post.
Hopefully, the twitter folk will respond to this as fast as they added
retweet_id so ya can delete retweets! :-)
Jim
On Aug 17, 1:33 pm, "Brian Smith" wrote:
> jim
This post, containing philosophical issues with the proposed retweet
API, is the promised companion to my post containing practical issues.
I realize this retweeting API and UI are probably a fait a complis
(sp?), modulo addressing practical concerns that I and others have
raised, but I'll throw
I have both practical and philosophical concerns and questions with
this proposal. Since I'm a little late in commenting on this, some of
these have already been raised. Where I know that is the case, I'll
keep it short, but include it to show my support (or not) of the
issue.
This post contains
Just to make things crystal clear, it should be stated that the 20k
rate limits apply only to GET requests to the so-called REST-API.
Other request types (I.e., POST) and / or other APIs (I.e., search,
streaming) have other rate limits.
Jim Renkel
On Aug 13, 3:58 pm, Chad Etzel wrote:
> Hi Ther
IANAL, but I don't think all is doom and gloom, or at least not as
doomy and goomy as previous posts to this thread (Including one of
mine, if it is not read as tongue-in-cheek, as intended) portray.
Yes, if you have a trademark, you have to aggressively defend it or
risk losing it. No, completel
was trying to do, perhaps not too well, is point out that the
API TOS may need to be revised to say that developers may use
twitter's trademarks, but only in "approved" ways.
BTW, twitter is trademarking "tweet" as well as "twitter". You have
been warned! :-)
Ji
An interesting implication is buried in all of this.
FACT: http://apiwiki.twitter.com/Terms-of-Service states: "Please give
us a nod in your app, perhaps by including one of these stylish
"Powered by Twitter" badges", which I read as "If ya use the API you
must acknowledge twitter."
FACT: The le
As I've pointed out in other posts to this group, and I will be the
first to acknowledge that there are conflicting opinions and facts on
this, it is my understanding and experience that for GET requests that
require authorization the rate limit is per user per IP address:
-If *EITHER* the use
/exponential-backoff-in-distributed.html
etc.
Hope this helps.
Jim
On Aug 11, 12:01 am, hansamann wrote:
> Can someone post a link to some online resources explaining more
> aboutgeometricback-offs? Did a search, did not find a whole lot.
>
> Thx
> Sven
>
> On Aug 10, 7:18 pm
?
Either way, I agree that we now need a very clear affirmation from
twitter as to the policy.
I sure hope I don't have to eat my words! :-)
Jim
On Aug 10, 9:08 pm, Dewald Pretorius wrote:
> On Aug 10, 11:02 pm, "jim.renkel" wrote:
>
> > My logic is now: "Ifratelimitin
Yup, when you do back-offs, ya can't do them deterministically, ya
gotta do them for a random amount, generally uniformly distributed
between some upper and lower bounds.
It's the bounds that increase geometrically or exponentially, up to
some limit, but the each back-off should be random between
Dewald,
Respectfully, I must (now) disagree that rate limiting should not be
per user, i.e., that it *SHOULD* be per user based.
When my site, twxlate.com, was white-listed and I saw how the white-
listing worked, namely that for authenticated requests each user of
each white-listed IP address g
Owkaye,
Thanks for the comment and suggestion.
The problem with implementing this locally at associated web sites
rather than centrally at twitter is that:
- each site would have to implement it separately; and
- users would have to sign up and create a private ID at each site
they use.
That re
My experience with this is, I think, a little bit different than what
you describe.
It appears to me that each user of a white-listed site gets 20k
requests per hour, independent of any other users of that site or any
other uses of the twitter API at other sites by that user.
I didn't think this
My concern with this proposal is that it opens up denials of service,
not to twitter.com, but to "associated" sites such as twitpic, or my
site twxlate, among others
For example, Lance Armstrong is a heavy user of twitpic. It is very
easy for anyone to find Lance's twitter ID (@lancearmstrong), v
information in 'source_has_a_pending_request_for_target' and 'target_has_a_pending_request_for_source', etc start to get somewhat unwieldy.
>
> > On Tue, Jun 9, 2009 at 4:29 PM, jim.renkel wrote:
>
> >> It seems from the examples, but not explicitly stated anywhe
It seems from the examples, but not explicitly stated anywhere, that
the values of the following and followed_by items are booleans,
implying that a user either is or is not following another user.
While at first blush that seems true, I think in reality the situation
is a little more complicated
Richard,
I think the problem you're trying to solve here is: given a URL of the
form http://twitter.com/xxx, is xxx a valid twitter username? (At
least that's a problem that I'm trying to solve for an application I'm
developing.).
A static list of such xxx's, although interesting, can't be devel
, but
> > it's something we'll consider for the next major release of the API.
>
> > On Thu, Oct 9, 2008 at 8:14 PM, jim.renkel <[EMAIL PROTECTED]> wrote:
>
> > > Lukas,
>
> > > Thank you for the pointer to and the effort put into creating the WADL
Groups now (I've seen it on several others I am on or maintain).
>
> --
> Ed Finklerhttp://funkatron.com
> AIM: funka7ron
> ICQ: 3922133
> Skype: funka7ron
>
> On Tue, Oct 14, 2008 at 8:05 PM, jim.renkel <[EMAIL PROTECTED]> wrote:
>
> > I've tried r
When you request a list of a user's friends (ah, others being
followed, in the new terminology :-) ), you get back their latest
status updates, which is useful for many applications, including the
one I am developing.
What my application REALLY needs is the last location update of each
of the use
I also like and vote for what Joel has proposed.
Jim Renkel
On Oct 14, 2:58 pm, "Vinuth Madinur" <[EMAIL PROTECTED]> wrote:
> +1 to what Joel said.
>
> On Wed, Oct 15, 2008 at 12:37 AM, jstrellner <[EMAIL PROTECTED]> wrote:
>
> > Personally I've always liked URI's that can be broken into name/va
I've tried replying to several messages in the twitter API discussion
threads, get a reply that the post was successful, but the message
doesn't show up.
I've done this many other times in other Google groups with no
problem. Any ideas what I might be doing wrong here? Anybody else
seeing this?
I too like Joel's idea.
Jim Renkel
On Oct 14, 2:58 pm, "Vinuth Madinur" <[EMAIL PROTECTED]> wrote:
> +1 to what Joel said.
>
> On Wed, Oct 15, 2008 at 12:37 AM, jstrellner <[EMAIL PROTECTED]> wrote:
>
> > Personally I've always liked URI's that can be broken into name/value
> > pairs. In this c
I've too have noticed this with location updates: updates from the web
page are seen immediately in the web page and by the API; changes via
the API aren't seen by either the API or the web page until after some
delay.
As Lars, said this is very annoying and makes very difficult
development of a
Lukas,
Thank you for the pointer to and the effort put into creating the WADL
and WSDL.
I'm new to the group, and to Twitter for that matter, but I'm somewhat
surprised that there aren't an official WADL and WSDL for the service.
Or any other complete specification that I can find. Am I missing
47 matches
Mail list logo
