Hi there , I'm new to this group, so hello everyone,
I'm tryng to set my first (php) use of the twitter API using CUrl and
I'm experiencing a strange behaviour:
I get this http_code zero when my post has been added and also when
I can't authentificate. I read a previous post on this group saying
Sorry, I should have seen it. You are right. Thanks a lot.
Martin
On 12 Jul., 03:25, John Kalucki wrote:
> Unless there's been a server restart and some unusual resulting
> backlog, nearly all tweets from /track will be forwarded within a
> second or two of being posted.
>
> I suspect you are co
We'll mail again and post on the @twitterapi account before we cry
havoc and let slip the hounds.
-John
On Jul 11, 2:26 pm, Joel Strellner wrote:
> John,
>
> Any chance you can allow us to send an additional variable when we
> connect and you guys send it in the new format? This would allow
Unless there's been a server restart and some unusual resulting
backlog, nearly all tweets from /track will be forwarded within a
second or two of being posted.
I suspect you are conflating the created_at of the user with the
created_at of the status. I've done this many times.
-John Kalucki
twi
It's different from basic auth in the way that oauth was primarily designed
to be different -- the app need not know your password (thus preventing a
rogue app from stealing it) and it need not send it over the wire with every
request (thus preventing a rogue entity from monitoring and trapping it
There's a published roadmap for the next big iteration of the API
(version 2) [1]. Your suggestion is already listed under "Users" and
is assigned to ticket #357 [2].
1. http://apiwiki.twitter.com/V2-Roadmap
2. http://code.google.com/p/twitter-api/issues/detail?id=357
--
Chris Thomson
On 11
Sorry, if I should know it. But is it usual that the results of the
track method could be 6 months old? When I played with it I got tweets
from Dec. 2008 or May or April or nearly realtime. Any way to get just
the newest?
Thanks Martin
Is there a published road-map? Thanks.
On Sat, Jul 11, 2009 at 6:53 AM, Doug Williams wrote:
> Samir,
> User search is something we would like to offer in the future through the
> API. The project is not highly ranking on the current overall roadmap, so
> there is no ship date to report.
>
> T
John,
Any chance you can allow us to send an additional variable when we
connect and you guys send it in the new format? This would allow for
overlap and testing.
-Joel
On Jul 11, 2009, at 7:04 AM, John Kalucki wrote:
Laurent,
There are examples of the new objects on the Streaming AP
> > No, there's really not a good solution for open source developers. :(
>
> If there really isn't a good solution for open source developers, there
> isn't a good solution for *any* developers unless you're running through
> a private proxy (and even that has problems).
>
> I think that the PI
I'm sure many people agree. Is there an existing Twitter API issue
for it? If not, perhaps start one and let people vote on it as a
feature?
-damon
--
http://twitter.com/damon
On Sat, Jul 11, 2009 at 12:39 PM, M. Edward (Ed)
Borasky wrote:
>
> I've been talking with some of my Twitter friends
I've been talking with some of my Twitter friends in the Portland area
and they / we are somewhat frustrated by the fact that we can only
retrieve the most recent 3200 tweets via the API. I can't speak for
everyone, but when I started on Twitter, it was a smallish phenomenon,
known to some of the
Duane Roelands writes:
> No, there's really not a good solution for open source developers. :(
If there really isn't a good solution for open source developers, there
isn't a good solution for *any* developers unless you're running through
a private proxy (and even that has problems).
I think t
Samir,
User search is something we would like to offer in the future through the
API. The project is not highly ranking on the current overall roadmap, so
there is no ship date to report.
Thanks,
Doug
On Fri, Jul 10, 2009 at 2:53 PM, SamirR wrote:
>
> Are there plans to implement user sear
I noted that the screen name (and user id) are returned along with the
Access token and secret.
It this a documented feature that I can rely upon?
The only related thread that I found on this topic was:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/8b24ab7dbb326d5
Laurent,
There are examples of the new objects on the Streaming API wiki. The
XML and JSON formats are, sadly, not orthogonal. The objects aren't
flowing to give developers time to adjust. We'll probably enable this
in the middle of next week.
-John
On Jul 11, 12:34 am, Laurent Eschenauer
wr
No, there's really not a good solution for open source developers. :(
On Jul 10, 3:57 pm, Cameron Kaiser wrote:
> > After reading that thread, it seems there is no good solution :(
>
> That is also my conclusion.
>
> --
> personal:http://www.cameronkaiser.com
ENGLISH VERSION:
Hello,
Is it possible to have Twitter in French languages, thanks.
I could translate (it take some times of course).
Have a nice day.
JLOX
FRENCH VERSION / VERSION FRANÇAISE:
Bonjour,
Serait-il possible d'avoir Twitter en Français, merci.
Je pourrai faire une traduction (cela
Hi John,
I can't find such thing as a status or delete object in the JSON feed.
There is indeed a enveloppe in the XML, but the corresponding
JSON object seems to be already one level deeper, only encapsulating
the data from the status itself.
Could you please clarify what we should be expectin
I just started to work toward incorporating OAuth with my application
BigTweet using Perl. I have been following the excellent
documenation at http://oauth.net. Jesse Stay's article at
http://staynalive.com/articles/2009/05/19/social-coding-how-to-code-twitters-oauth-using-netoauth-and-perl/
Are there plans to implement user search in the API (http://
twitter.com/search/users?q=)? Thanks!
Samir
From what I understand, it is UTC time. The +/- is the offset
depending on what zone you are in.
This allows for a time value that is the same across the world, but
can be offset for any particular locale.
I think http://en.m.wikipedia.org/wiki/Coordinated_Universal_Time will
explain
22 matches
Mail list logo
