Just to throw my 2 cents in. Without a reasonable replacement for
mobile devices, we'll likely remove it, and I'm expecting a
substantial backlash from UberTwitter users. It does look like it
would be relatively simple to roll-your own with the streaming api,
which makes me wonder why this is bei
Are there still issues with the API this morning? We have many of our
UberTwitter users reporting timeouts when trying to retrieve timelines
and send tweets. We are not using OAUTH.
Any info would be greatly appreciated!
-CodeWarden
Up until yesterday this had been working fine for months. Now, if I
send the following query to the search API it gives me an error that I
have to enter a query
Here is the call that used to work:
http://search.twitter.com/search.json?geocode=39.031721,-77.50482,5mi&rpp=100
HTTP Return Code: 4
Hello,
My mobile app uses the search api, and we do fill in the User Agent
header to identify our application. Starting around last week it
appears as though the search api is limiting our searches, which
originate directly from our user's mobile devices.
Does anyone have any thoughts around t
Hello,
Really looking forward to the ability to include lat/long with
tweets. However, since all of my users are on mobile devices, it
would be most useful if they could change the geo_enabled flag via the
API. Before you enable this capability could you allow the update
profile method to also
xxx -d "id=6444795764"
http://twitter.com/CodeWarden/2074698/members.json
== Info: About to connect() to twitter.com port 80 (#0)
== Info: Trying 128.121.146.228... == Info: connected
== Info: Connected to twitter.com (128.121.146.228) port 80 (#0)
== Info: Server auth using Basic with user
Thanks Ed! Must of really run a-muck!
-Paul
On Dec 8, 12:27 am, Ed Costello wrote:
> 6444795764 does not appear to be a valid twitter user id / id number, nor does
> 2074698.
> The only list you appear to have is "my-uber-peeps" with id "2074438".
>
> So, try using a valid user id number and co
Matt,
In your example you show an unsigned long that uses the full 64 bits
bits, which fails to be properly represented on a Java platform. In
a later explanation you say that there will only ever be 63 bits
used. Can you confirm one way or the other? i.e. will we ever see
an unsigned integer
?
-CodeWarden
Whether they did or didn't change it, the one that the twitter API is
returning is the one that doesn't work. If they changed it, you would
think that the one returned by the API would be the correct one, and
perhaps the one accessed through the twitter web site might get
cached.
-Paul
On Feb
Hello,
Why is the profile_image_url in the public timeline now only ever
pointing to the image that is used if you don't set an avatar?
I have verified that this is the case with both the JSON and XML
formats through the api, they all only point to
http://static.twitter.com/images/default_profi
As we count-down to June 30th and plan our own client releases with
app store approvals, etc. Can someone at Twitter give us a planned
roll-out date for the fixes to the Oauth page and exactly which fixes
are to be included?
I am most interested in the correct rendering for mobile devices.
-Pau
Arnaud - Can someone give some links to some tweets with the photos so
we can test our thumbnail/viewing implementation?
Also - Can someone give a synopses of what changed in the api_terms ?
thx,
Paul
On Jun 1, 2:34 pm, Arnaud Meunier wrote:
> Hey developers,
>
> We have just announced a coupl
13 matches
Mail list logo
