Are there any other active twitter forums?
--
Have you visited the Developer Discussions feature on
https://dev.twitter.com/discussions yet?
Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi
Unsubscribe or
Is it possible to authenticate from a web page without any server-side
program? I would like to use javascript (and jsonp with query-string
oauth, I am guessing) and hard code my access_token in a javascript
variable.
I know this would be a major security no-no. I have no intention of
putting th
g?
On Jul 22, 8:33 pm, Jonas wrote:
> When I attempt to register a new app onhttp://dev.twitter.com/apps/new
> I always get this error: "Website: Not a valid URL format." I get
> this error no matter what I type in the Website field. I've tried
> every variation of
When I attempt to register a new app on http://dev.twitter.com/apps/new
I always get this error: "Website: Not a valid URL format." I get
this error no matter what I type in the Website field. I've tried
every variation of URL format I can think of.
I also tried to register my app on http://twit
automated. Looks like I need to register an App but I'm not
sure if Twitter allows setting up apps just for testing and I don't
know how I would go about storing keys etc so people can test it but
not abuse it.
Jonas
--
Twitter developer documentation and resources: http://dev.twitter
I am using search.json and track.json and I noticed that the date
format for created_at is different.
search.json: Tue, 11 Aug 2009 20:23:36 +
track.json: Tue Aug 11 20:23:36 + 2009
Is there a reason why Twitter uses different formats for the same
information?
Is there any interest in u
-- forced or passive.
Thanks, Jonas
On Jun 22, 11:08 am, Matt Sanford wrote:
> Hi Jonas,
>
> The issue here is that /users/show allows both authenticated and
> un-authenticated access. Unlike the bug you referenced [1], the RFC
> does not really mention what to do in that
When I send incorrect credentials with a user/show.json command I
expect to get a 401 code from twitter. However, when I do this from a
browser using xmlhttprequest I get 400 instead. Actually, for the
first 100 tries I get 200 codes, and there after I get 400 codes,
because there is a rate limi
ting 400 errors.
I'm not sure what the problem is. I am able to authenticate using
curl -u, so I know I should be able to get authentication working with
XMLHTTPRequest. Anyone have any suggestions? Is there more to it
than calling open with user/password?
Jonas
How does one set the http referrer and user agent?
On Jun 16, 12:33 pm, Doug Williams wrote:
> Hi all,
> The Search API will begin to require a valid HTTP Referrer, or at the very
> least, a meaningful and unique user agent with each request. Any request not
> including this information will be
I'm curious why there have been no progress updates regarding issue
646. Can anyone speak to the status of this problem.
See http://code.google.com/p/twitter-api/issues/detail?id=646
ng if there will be any more improvement, or if this is the
best it will be.
Thanks,
Jonas
On Jun 3, 1:20 pm, Matt Sanford wrote:
> Hi there,
>
> This is a known issue [1] we're working on. Some servers are
> behind and we're trying to get them back up to date. Mark t
When I do: http://search.twitter.com/search.atom?q=blah
The most recent tweet is a couple of minutes old. The next time I do
it the most recent is an hour old. The next time a half hour old.
The next time a minute old, etc, etc.
mp;rpp=10&since_id=1967746107&page=1
and
http://search.twitter.com/search.atom?q=blah&rpp=10&page=1&since_id=1967746107
What I'd like to do is query pages 1 through 15 with rpp=100 and
since_id=.
Jonas
p;from=&to=&ref=&near=nyc&within=15&units=mi&since=&until=&rpp=10
Jonas
On May 27, 4:28 pm, Matt Sanford wrote:
> Hi Jonas,
>
> Yes, they are. The since= parameter should not be required, can
> you share the URL you're getting the error from?
Matt,
Okay, I'm switching back to search.atom. However, I still get an
"Invalid Parameter" error when since= is not empty.
Are all the parameters that are available to the search command also
available to the search.atom command?
Jonas
On May 27, 3:41 pm, Matt Sanford wr
urned rss always contains a
twitter:warning element.
2) When near= is not empty (for instance near=NYC) I always get a 406
http error.
Thanks,
Jonas
17 matches
Mail list logo
