The current endpoint for creating a new list is:
http://api.twitter.com/1/user/lists.format
But the user part is meant to be the user's screen name.
If your application is oAuth, you don't necessarily know or care about
the user's screen name.
You can easily get it with a verify_credentials
On Nov 7, 12:31 pm, Matthew Terenzio mteren...@gmail.com wrote:
Can someone explain this?
GET '/:users/lists/:list_slug.:format'
Show a specific list you can use the new resource.
is scripting examples of how to use the Lists API will help, take a
look at:
Hi,
Any plans to implement timezone support?
It's weird to say Good morning at 5h45 from Switzerland and see it
appear as 19h45 in the public timeline / on some profiles... It doesn't
make sense to me... The time should be written with the mention of the
time zone, e.g.: 05:45 CEST.
An other
Any update on when a similar policy will be put into place on
api.twitter.com? This was promised a year and a half ago. A lot of
folks are asking for it, as can be seen in this thread:
http://groups.google.com/group/twitter-development-talk/browse_frm/thread/e35a708400b529b3
On Nov 6, 8:40 pm,
Twitter API team seems to want to make the API more RESTful. So that
is my guess why that
end point is /:user/lists.xml POST versus something like /lists/create.xml
Josh
On Sun, Nov 8, 2009 at 2:25 AM, Dimebrain daniel.cre...@gmail.com wrote:
The current endpoint for creating a new list is:
Please keep us updated w/ discussion on relaxing the crossdomain
policy on api.twitter.com. Currently it is impossible to build full
featured in-browser Flash clients for Twitter without using a proxy,
which is part of the reason so many of them are desktop AIR apps.
Twitter is doing itself a
I thought this too when I first saw the new list api. Is the Twitter
team moving away from id/screenname based query parameters and simply
using screen names?
I suppose the point being that Daniel was making is that screen name
is superflous when using authentication especially since all the
Yeah I agree and wished twitter would have just kept the design more
consistent to what is
already there. If they want to change the design, do it all at once
and save it for another version (maybe 2 or something).
On Sun, Nov 8, 2009 at 10:59 AM, Paul Kinlan paul.kin...@gmail.com wrote:
I
hi emrah.
this sounds interesting -- how do you handle people who are traveling
and may not be in their home timezone when they say good morning?
Hi,
Any plans to implement timezone support?
It's weird to say Good morning at 5h45 from Switzerland and see it
appear as 19h45 in the public
hi!
we're definitely discussing it heavily internally now that
api.twitter.com has been launched and we are attempting to migrate all
developers to use that endpoint instead of the twitter.com endpoints.
we'll definitely keep people updated as we think these through. of
course, we
I'm seeing 404s from OAuth suddenly, when trying to hit...
http://api.twitter.com/1/oauth/request_token?[query string removed[
...but getting normal responses from
http://api.twitter.com/oauth/request_token
I thought the /1/ was standard at this point. Was I mistaken, or is
this just a blip?
oauth, as it is not being versioned is available at api.twitter.com
(and not, /1) -- we may consider aliasing it at some point if necessary.
I'm seeing 404s from OAuth suddenly, when trying to hit...
http://api.twitter.com/1/oauth/request_token?[query string removed[
...but getting
Very glad to hear that! I'm going to reach out to my fellow Flashers
again to see who can give solid advice on opening up the crossdomain
policy while maintaining security.
On Nov 8, 6:55 pm, Raffi Krikorian ra...@twitter.com wrote:
hi!
we're definitely discussing it heavily internally now
that sounds great -- please feel free to continue this discussion on
this list, or just reach out to me personally.
Very glad to hear that! I'm going to reach out to my fellow Flashers
again to see who can give solid advice on opening up the crossdomain
policy while maintaining security.
Raffi Krikorian wrote:
hi emrah.
this sounds interesting -- how do you handle people who are traveling
and may not be in their home timezone when they say good morning?
:) Timezone code could be set per Tweet as a parameter. E.g.: on mobile
phones, the time is usually updated from the
Chad Etzel c...@twitter.com wrote:
After discussing this internally, we have decided that we will make
thecrossdomain.xml policy more open on the api.twitter.com domain. We
don't know exactly what that entails yet or when it will go into
effect, but this is something that we want to open up.
Is there a way to use the Twitter API to search for a user using
partial strings or booleans? Let's say, searching for hello and
coming back with @helloluis, @hellotoni, @helloworld, etc.?
(Ideally, hashes of these users' profiles?)
If not, is there a way to cobble this functionality
Hi, sorry for the trouble caused, think have managed to solve it. turns out
to be my mistake, i did not remove the negative sign from the example, i
just replace the number which is why i could not get anything. Thanks a lot
for your help!
On Thu, Nov 5, 2009 at 5:14 PM, Rich rhyl...@gmail.com
Hi, tried using the geocode
http://search.twitter.com/search.atom?q=NYPgeocode=1.356771%2C103.824062%2C25kmpage=1rpp=100,
location is Nanyang Polytechnic in Singapore and its surrounding 25km.
The latest result it returns is from the 4th of Nov when today is
already 9th Nov and when i remove the
19 matches
Mail list logo
