I have been informed by some users that some searches for hashtags are
returning 0 results, while searching for the term *without* the
hashtag works fine:
example:
#laundryalternative
http://search.twitter.com/search?q=%23laundryalternative
0 results.
laundryalternative
Well, as much as I love Twitter, it's not on Google's infrastructure.
Speaking of which, Jaiku has gone open source and supports XMPP:
http://code.google.com/p/jaikuengine/
http://code.google.com/p/jaikuengine/source/browse/trunk/doc/design_funument.txt
Twitter Team: maybe there's something to
Well, as much as I love Twitter, it's not on Google's infrastructure.
*cough*praisethelord*cough*
--
personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- Please dispose of this message
Has Jaiku gone XMPP yet? We're having a discussion about jaiku on the
GAE list now. I believe XMPP is almost-but-not-quite-ready? They're
involved in a pubsubhub project on GAE to make it happen, if I paid
enough attention to that convo.
On Sat, Mar 14, 2009 at 5:59 AM, Adrian
I've noticed that the Search API page has recently been changed to
say:
The standard API rate limiting is liberal enough for most use cases.
If you find yourself encountering these limits, please contact us and
describe your app's requirements.
Recently, this page stated that the rate for
Chad,
I see that, too. Going to have to wait for traveling Matt to chime in.
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Sat, Mar 14, 2009 at 2:39 AM, Chad Etzel jazzyc...@gmail.com wrote:
I have been informed by some users that some searches for hashtags are
returning 0
Hi,
There is a rate limit for the Search API but it is higher than 100 requests
per second imposed by the REST API. The limiting is performed by the IP
address. The default limit is high enough that most applications shouldn't
be affected.
As the search architecture has no notion of accounts, it
Hi all,
I am in the process of designing a new twitter app.
The app needs to make twitter api calls on behalf of the users and queries the
user for his/her twitter credentials and stores them such that they
can be used
subsequently for making twitter api calls.
I plan on storing them in the DB
I'm currently working on a c++ wrapper for the twitter API. Everything
works smooth except uploading images. Both profile images and
background images. The image I use is a png which already has been
used as an Twitter avatar. So the response about a big image does not
seem very likely.
I send a
(IDNSOWFT)
Is there a Twitter recommended Best practice on how third party apps
should store
twitter credentials?
You should avoid it. If you must, store them in as encrypted a fashion as
possible, and make your accesses with SSL to avoid inadvertent exposure.
I read on the net that
Hi Einar,
You seem to be submitting your POST request incorrectly. This is how I
(successfully) submit my update_profile_image:
Content-type: multipart/form-data; boundary=BOUNDARYHERE
--BOUNDARYHERE
Content-Disposition: form-data; name=image; filename=FILENAMEHERE.png
Content-Type: image/png
Just came across another example of this. March 14, 21:22 PST
(shouldn't I be drinking green beer or something??)
@GpsU1m
XML shows proper spammy friends/followers count (776/27) while JSON
shows 0/0 for both.
Another couple:
@IMe1kV 557/15 XML vs. 54/0 JSON
@wemPr2 796/50 XML vs. 0/0 JSON
FWIW, I've had trouble uploading a profile picture using the web
interface itself (it seems to accept it, but then doesn't show it). It
hardly seems like the most robust feature. Normally I just keep trying
and waiting a few minutes to see if it actually went through.
13 matches
Mail list logo
