Developer
Advocate
On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com
wrote:
Hi,
We're seeing this as well starting at approximately the same time
as
described. We've backed off on searching but are seeing no
reduction in the
sporadic limiting. It also appears
I'm seeing this as well. Including filter:links or setting that language
causes the search to fail. I get an error message saying since_id has been
adjusted due to a temporary error. I'm *not* including a since_id in the
search parameters.
Hayes
On Mon, Nov 29, 2010 at 10:08 AM, Randomness
I did some investigation into the snowflake algorithm recently and yes, it's
safe for 64bit signed longs. Even if Twitter moved away from using
scala/java longs internally (which are definitely signed), you'd still have
something like 65 years from now before the algorithm rolled past the 2^63-1
Hi,
I was attempting to test my apps with the new status_ids but it appears that
the new_id field is no longer being included in the Streaming API json. They
were there earlier in the week but are no longer being included. According
to John Kalucki's post on the subject[1], I was under the
, I believe, ever explicitly documented that
it supported SSL. I wasn't aware of this change and have some issues with it
-- I'll see what I can do. In the meantime, please use non-SSL.
Taylor
On Wed, Oct 6, 2010 at 3:35 PM, Hayes Davis ha...@appozite.com wrote:
Hi all,
For several months
Hi all,
For several months now, we've been connecting to the streaming api filter
resource over SSL without issue. Today it suddenly disconnected us and
wouldn't let us reconnect. We tried from multiple IPs to connect without
success so it doesn't appear to be some sort of blacklist issue. Is
I believe the twitter-stream[1] ruby library supports OAuuth as of the
latest version. I haven't personally used the OAuth yet but it's been rock
solid for me with basic auth.
Hayes
[1] http://github.com/voloko/twitter-stream
On Wed, Aug 4, 2010 at 7:39 PM, Mark McBride mmcbr...@twitter.com
Any update on these messed up responses? I'm currently seeing users/
lookup.json responses get truncated if I request more than a small
number of users.
Hayes
On Jul 19, 4:28 pm, jsleuth jsle...@gmail.com wrote:
Yes indeed. It's a weird one.
Thanks for the feedback.
JS
On Jul 19, 4:36
+1 on this. I'm frequently getting 0 results from the search API (not an
error, just 0 results) when including the since_id even though a search
without the since_id shows that there are tweets with larger ids for the
same query string.
Hayes
On Mon, Nov 23, 2009 at 1:16 AM, Karthik
.
I know you all have a lot on your plate right now but let us know what we
can do to get un-blocked.
Hayes
--
Hayes Davis
Founder, Appozite
http://cheaptweet.com
http://tweetreach.com
On Thu, Aug 6, 2009 at 3:56 PM, Mario Menti mme...@gmail.com wrote:
Thanks Alex - just to confirm, no requests
Are you going to shut off the S3 URLs immediately or will they still be
accessible for a time? I understand that newly updated avatar images would
not be updated at S3 after the switch but I'd like to know when we can
expect any S3 URLs we may have in our caches to all go dark.
Thanks.
Hayes
On
On Thu, Jul 9, 2009 at 6:09 AM, Hayes Davis ha...@appozite.com wrote:
Are you going to shut off the S3 URLs immediately or will they still be
accessible for a time? I understand that newly updated avatar images would
not be updated at S3 after the switch but I'd like to know when we can
expect
happens if I use from and since together. If I
use each independently, no problems.
Should I file a bug?
Hayes
--
Hayes Davis
Founder, Appozite
http://cheaptweet.com
http://tweetreach.com
Sounds related to my earlier post[1] about issues using from and since (as
opposed to since_id).
Hayes
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/2960bcdf84fef6d6
On Mon, Jun 29, 2009 at 8:36 PM, primedynasty primedyna...@gmail.comwrote:
I am having issues
I'm also curious about this phenomenon. It does seem that certain
high-profile users are indexed poorly in search. It doesn't seem to
correlate exactly with follower numbers but I've not done much in the way of
empirical analysis on that.
It's causing me some trouble on tweetreach.com as I often
Guys,
I don't see any notice on the status blog or other official channels so I
figured I might as well say something. None of my account timelines have
updated in more than 45 minutes and all search queries I'm looking at are
that old as well.
Hayes
very quickly with new API functionality.
Would it be possible to have it included among the available libraries on
the wiki?
Please let me know if you have any feedback, suggestions for improvement,
etc.
Thanks.
Hayes Davis
@hayesdavis
Thanks.
Hayes
--
Hayes Davis
@hayesdavis
On Thu, Mar 19, 2009 at 3:11 PM, Luke l...@codegent.com wrote:
I have exactly the same problem. How can we update images with OAuth?
Agree that base64 encoded would be a good workaround for now.
- Luke
@luke_bkk
On Mar 18, 8:55 pm, Zachary West
I'm seeing the same thing. It's returning true for me no matter what when I
make the call in the way Pierre describes. It also seems to be returning the
raw true in the response body like it used to instead of the JSON repsonse
I thought it was changed to back in January.
Hayes
--
Further investigation shows the XML format is working fine. Seems to
be a problem only with the JSON version.
Hayes
--
http://cheaptweet.com
20 matches
Mail list logo
