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 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 or
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
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 james.ren...@gmail.com wrote:
In working with the new cursorized statuses/friends and statuses/
followers methods, 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
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
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 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=gstq=ReTweet+API#2d10a6a22e55133e
but, unfortunately, have not yet received an
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
Fortunately, when I tried that it didn't work.
Jim
On Aug 26, 11:29 am, JDG ghil...@gmail.com 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 jroessl...@gmail.com wrote:
How is that scrapping? He is just
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
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
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
=raashidbhat...
On Aug 20, 9:29 am, jim.renkel james.ren...@gmail.com 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-Developer-Should-Know#6Therea...
for more information
Um, I don't see any way for a user to turn the geo_enabled attribute
on and off. Oversight, I hope?
Jim
On Aug 20, 4:18 pm, Joel Strellner j...@twitturly.com wrote:
Hi Ryan,
Will this data be available in the streaming API too?
-Joel
On Thu, Aug 20, 2009 at 2:11 PM, @epc
On Aug 18, 7:35 pm, jim.renkel james.ren...@gmail.com 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 aretweetid number to the status/show
method? An error? The retweeted
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 a retweet id number to the status/show
method? An error? The retweeted status message is returned along with
information about all of
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
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
:
jim.renkel wrote:
7. If retweets and status updates are numbered from the same sequence
of IDs, then presumably statuses/destroy can be used to delete a
retweet. If retweets and status updates have separate ID sequences,
then I don't see any way to delete a retweet. I think the ability
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,
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 c...@twitter.com
, jim.renkel james.ren...@gmail.com wrote:
Yup, when you doback-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
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
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! :-)
Jim
On Aug 11, 10:50 pm, jim.renkel james.ren
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
then?
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 dpr...@gmail.com wrote:
On Aug 10, 11:02 pm, jim.renkel james.ren...@gmail.com wrote:
My logic is now: Ifratelimiting
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
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),
, 2009 at 4:29 PM, jim.renkel james.ren...@gmail.com wrote:
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
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
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
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 case, I would
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 replying to several messages in the twitter API discussion
threads, get a reply that the post
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
35 matches
Mail list logo
