If you're getting that then you're getting more than me.
I'm just doing:
require 'rubygems'
gem 'twitter'
require 'twitter'
Twitter::Search.new('foo').each do |r|
puts r.inspect
end
And I get only this back now:
/var/lib/gems/1.8/gems/httparty-0.4.3/lib/httparty/request.rb:56:in
Is your library following redirects?
On Aug 7, 10:18 am, David Fisher tib...@gmail.com wrote:
If you're getting that then you're getting more than me.
I'm just doing:
require 'rubygems'
gem 'twitter'
require 'twitter'
Twitter::Search.new('foo').each do |r|
puts r.inspect
end
And I
im having the same problem. im just lucky my app is still in test.
RT @twitter Due to defense measures some Twitter clients are unable to
communicate with our API, and many users are unable to tweet via SMS.
I think we can only wait for twitter to normalize de api.
On 7 ago, 12:20, diddy
I can't be sure if my client is following redirects. Probably not. I'm
just using the Ruby Twitter Gem which haven't been updated for a month
or so I think
dave
On Aug 7, 1:15 pm, lucasnicolato eternitya...@gmail.com wrote:
im having the same problem. im just lucky my app is still in test.
You can use Wireshark or any other packet sniffer to determine whether your
client is following redirects. I'm not sure what ruby twitter client you're
using, but if it's John Nunemaker's, I believe it does follow redirects.
Larry Wright/@larrywright
On Fri, Aug 7, 2009 at 2:03 PM, David Fisher
Yea I'm using John's. Have to pull out the packet sniffer soon
On Aug 7, 3:32 pm, Larry Wright larrywri...@gmail.com wrote:
You can use Wireshark or any other packet sniffer to determine whether your
client is following redirects. I'm not sure what ruby twitter client you're
using, but if
