bummed at the thought of having to
rebuild my app to support the new 'timelines' that Twitter is
requiring clients to support, but for the sake of evolution of the
platform, I am happy to see the progress. I also somewhat agree that
the solution to adding comments and crediting the origin
I must admit that I didn't put enough weight on the fact that the new
retweet API will not incorporate the ability to edit/append/comment on
the original tweet. I do have to agree with you, Paul on how common
place that practice is.
My mindset was that why hold back a feature that solve
posts to the public timeline API per
authenticated user?
Thanks,
Will Kern
On Aug 11, 11:08 pm, "jim.renkel" wrote:
> 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
se of Content. The Twitter API
exists to enable this."
thanks
On Mon, Mar 8, 2010 at 10:06 PM, John Kalucki wrote:
> Not at the moment, as we expect that the number of services that this will
> apply to is small. We'll be clarifying data access and licensing over the
>
We are seeing the same behavior on http://www.mapleprimes.com
Any chance this will be fixed in @anywhere? If not, we'll likely need
to remove @anywhere from our site.
On Jun 1, 10:57 am, Steve C wrote:
> Right, I understand that it's not supported on older browsers but I
>
I built an application that aggregates data a few times per day based
on a hashtag search term. My search results for tweets I've done as
tests are not showing up in the search.
What's the delay time before they show up? My client is asking and I
have no idea what to tell them. The application is
Okay. Do we at least know how delayed? I posted a test tweet as we
launched the website yesterday with my publicly accessible Twitter
account and that was at 3:40 PM PST yesterday. It's been almost 24
hours and I still don't see it come up in search.
http://search.twitter.com/search?q=%23befantast
#x27;t work, then I'm not sure what else I can do.
Those "delayed" tweets in the search will eventually show I hope :(
I'm checking out a tutorial I found for the stream API (having not
worked with JSON much) and am getting an error.
fgets(): supplied argument is not a valid stream resource
This is happening when I run it locally under WAMP as a test and also
on a live production server (Media Temple). Any ideas?
I am currently getting a HTTP 400 response when interacting with the API,
with a error message of "Rate limit exceeded. Clients may not make more than
0 requests per hour."
OAuth for authentication.
No calls currently working, but same result on both
http://api.twitter.com/1/statuses/user_timelin
One other thing, API calls to http://search.twitter.com do appear to be
working correctly.
Requests here seem to be working correctly again, thanks.
It is working correctly on a G1 running Android, but getting the non mobile
version on a Nexus One. User-Agent is
*Mozilla/5.0 (Linux; U; Android 2.1; en-us; Nexus One Build/ERD79)
AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17*
I'm trying to to get xAuth to work with my application, using libcurl
and a modified TwitCurl engine. Whenever I attempt to obtain an
access token, I get a 401 error that contains a single space character
(0x20) and nothing else, which is extremely unhelpful. Whenever I try
to do other things tha
Was the cause of the empty response body ever discovered? I'm having
a similar issue, except my 401 response body has "Content-Length: 1"
containing an empty space " ".
On Nov 19 2010, 3:44 pm, Matt Harris
wrote:
> Hey Chrys,
>
> Agreed. The authentication header doesn't have to be in order but
I would like to be added as well!
Twitter Username: http://twitter.com/will_00
Site: http://www.willm.me
Email: will.mrk...@gmail.com
Programming: PHP, MySQL, Web Design, Java
16 matches
Mail list logo
