Issues - jnunemaker/twitter

jnunemaker / twitter

137

624

Description:

API wrapper for Twitter and Twitter Search API's

Sort by: Priority | Votes | Last Updated

Loading…

1.

5 votes

Mash/extlib don't like each other
10 comments Created 8 months ago by jnunemaker

Title

Body
Currently there's no way to use twitter gem along with ExtLib gem (which is e.g. used by DataMapper). Both ExtLib and mash gem (used by twitter) declare separate notions of a Mash class with different semantics. This results in infinite recursion ("stack level too deep" error). This bug is also posted here: https://mbleigh.lighthouseapp.com/projects/10112-mash/tickets/3-mash-conflicting-with-extlib
or cancel
Currently there's no way to use twitter gem along with ExtLib gem (which is e.g. used by DataMapper).

Both ExtLib and mash gem (used by twitter) declare separate notions of a Mash class with different semantics. This results in infinite recursion ("stack level too deep" error).

This bug is also posted here: https://mbleigh.lighthouseapp.com/projects/10112-mash/tickets/3-mash-conflicting-with-extlib

Comments
be9 Thu Apr 16 20:49:43 -0700 2009 | link

Ha, I tried to reply at the lighthouse, but that shop has already been closed :)

The problem is fixed e.g. in the peterpunk-mhash gem (http://github.com/peterpunk/mhash/tree/master). It renames Mash to Mhash, resolving the conflict.

Comment
Ha, I tried to reply at the lighthouse, but that shop has already been closed :) The problem is fixed e.g. in the peterpunk-mhash gem (http://github.com/peterpunk/mhash/tree/master). It renames Mash to Mhash, resolving the conflict.
or cancel

jefflarkin Thu May 07 11:32:34 -0700 2009 | link

This tree no longer seems to exist. Is there another patch available somewhere?

Comment
This tree no longer seems to exist. Is there another patch available somewhere?
or cancel

be9 Sun May 10 05:18:03 -0700 2009 | link

@jefflarkin: http://github.com/peterpunk/mhash/tree/master

Comment
@jefflarkin: http://github.com/peterpunk/mhash/tree/master
or cancel

deedubs Wed Jun 03 21:34:01 -0700 2009 | link

I've patched this to use Mhash avoiding the above error http://github.com/deedubs/twitter/tree/master

Comment
I've patched this to use Mhash avoiding the above error http://github.com/deedubs/twitter/tree/master
or cancel

richcollins Wed Jul 15 01:14:17 -0700 2009 | link

http://github.com/peterpunk/mhash/tree/master doesn't exist. Does anyone have a copy they can email me? (richcollins@gmail.com)

Comment
http://github.com/peterpunk/mhash/tree/master doesn't exist. Does anyone have a copy they can email me? (richcollins@gmail.com)
or cancel

deedubs Wed Jul 15 06:05:11 -0700 2009 | link

I've put the version I had online @ http://github.com/deedubs/mHash/tree/master

Comment
I've put the version I had online @ http://github.com/deedubs/mHash/tree/master
or cancel
mislav Wed Nov 04 01:11:35 -0800 2009 | link
require 'dm-core' Object.send(:remove_const, :Mash) if defined? ::Mash require 'twitter' # fix for Mash v0.0.3 Mash.class_eval do def stringify_keys() self end end
Comment
require 'dm-core' Object.send(:remove_const, :Mash) if defined? ::Mash require 'twitter' # fix for Mash v0.0.3 Mash.class_eval do def stringify_keys() self end end
or cancel
pengwynn Tue Nov 17 06:49:19 -0800 2009 | link

Just released 0.7.5 that includes a patch from hassox that replaces Mash with its successor Hashie. Hopefully this resolves this issue.

Comment
Just released 0.7.5 that includes a patch from hassox that replaces Mash with its successor Hashie. Hopefully this resolves this issue.
or cancel

mislav Tue Nov 17 07:15:34 -0800 2009 | link

The issue was already resolved when Mike (of Mash) pushed fixed 0.0.x Mash versions. But yeah, in the long run using Hashie is probably better.

Comment
The issue was already resolved when Mike (of Mash) pushed fixed 0.0.x Mash versions. But yeah, in the long run using Hashie is probably better.
or cancel

mislav Tue Nov 17 07:19:26 -0800 2009 | link

To be clear, the issue I was saying was resolved was only this which required the monkeypatch. If you are using twitter 0.7.3 with mash 0.0.6 you still need the remove_const hack above. So yeah, it's probably just best to use twitter 0.7.5.

Comment
To be clear, the issue I was saying was resolved was only this which required the monkeypatch. If you are using twitter 0.7.3 with mash 0.0.6 you still need the `remove_const` hack above. So yeah, it's probably just best to use twitter 0.7.5.
or cancel

Parsed with GitHub Flavored Markdown
2.

7 votes

[PATCH] "Sign in with Twitter" feature.
3 comments Created 7 months ago by [deleted user]

Title

Body
"Sign in with Twitter" is the pattern of authentication that allows users to connect their Twitter account with third-party services in as little is one click. Read more: http://apiwiki.twitter.com/Sign-in-with-Twitter PATCH: http://gist.github.com/107505
or cancel

"Sign in with Twitter" is the pattern of authentication that allows users to connect their Twitter account
with third-party services in as little is one click.

Read more: http://apiwiki.twitter.com/Sign-in-with-Twitter

PATCH: http://gist.github.com/107505

Comments

[deleted user] Wed May 06 05:00:11 -0700 2009 | link

Hmm, it's impossible to attach files here. So I post the patch to gist: http://gist.github.com/107505 , and send it to u by email

Comment
Hmm, it's impossible to attach files here. So I post the patch to gist: http://gist.github.com/107505 , and send it to u by email
or cancel

tjgillies Thu Oct 29 15:57:16 -0700 2009 | link

why not just fork it and send a pull request?

Comment
why not just fork it and send a pull request?
or cancel

pengwynn Wed Nov 04 07:04:32 -0800 2009 | link

I assume our [deleted user] will/has submitted a patch.

Comment
I assume our [deleted user] will/has submitted a patch.
or cancel

Parsed with GitHub Flavored Markdown
4.

0 votes

Potential ambiguity in friendship_create method
2 comments Created 7 months ago by nipunj

Title

Body
Twitter has updated the friendship_create method so that it can consume an explicit user_id or screen_name parameter vs the potentially ambiguous "id", which could be either of those values. Would be best to reflect this specificity in the Twitter gem. (Sorry, I'm a n00b. Wouldn't knwow where to begin.) Note, I haven't taken a pass over the Twitter API to see if this change was made to other methods that consume "id" as a param. Thanks.
or cancel

Twitter has updated the friendship_create method so that it can consume an explicit user_id or screen_name parameter vs the potentially ambiguous "id", which could be either of those values.

Would be best to reflect this specificity in the Twitter gem. (Sorry, I'm a n00b. Wouldn't knwow where to begin.)

Note, I haven't taken a pass over the Twitter API to see if this change was made to other methods that consume "id" as a param.

Thanks.

Comments

jnunemaker Thu May 14 14:39:45 -0700 2009 | link

I use to name it id_or_screen_name but twitter has changed the method a few times so i just labeled it id. You can still use either a screen_name or an id, the parameter is just named id.

Comment
I use to name it id_or_screen_name but twitter has changed the method a few times so i just labeled it id. You can still use either a screen_name or an id, the parameter is just named id.
or cancel

nipunj Thu May 14 14:48:13 -0700 2009 | link

Thanks, John. I get that "id" can be either user_id or screen_name.
But, in the odd case that you have a user_id that's actually the same as an existing screen name, there's ambiguity.
Twitter has tried to disambiguate this by offering explicit "user_id" or "screen_name" params, like so:
http://twitter.com/friendships/create.xml?user_id=1401881
http://twitter.com/friendships/create.xml?screen_name=101010

Did I miss it, does the gem's friendship_create method handle these variations as well?

Comment
Thanks, John. I get that "id" can be either user_id or screen_name. But, in the odd case that you have a user_id that's actually the same as an existing screen name, there's ambiguity. Twitter has tried to disambiguate this by offering explicit "user_id" or "screen_name" params, like so: http://twitter.com/friendships/create.xml?user_id=1401881 http://twitter.com/friendships/create.xml?screen_name=101010 Did I miss it, does the gem's friendship_create method handle these variations as well?
or cancel

Parsed with GitHub Flavored Markdown
5.

1 vote

Use OAuth 0.3.4
2 comments Created 7 months ago by yevgeny

Title

Body
Twitter gem uses OAuth 0.3.2 instead of the current version.
or cancel

Twitter gem uses OAuth 0.3.2 instead of the current version.

Comments

bumi Tue Jun 16 13:13:32 -0700 2009 | link

This should be 0.3.5, shouldn't it? ;) (for oauth 1.0a)

Comment
This should be 0.3.5, shouldn't it? ;) (for oauth 1.0a)
or cancel

pengwynn Wed Nov 04 07:04:48 -0800 2009 | link

I believe this has been resolved.

Comment
I believe this has been resolved.
or cancel

Parsed with GitHub Flavored Markdown
7.

1 vote

uninitialized constant Twitter::OAuth
2 comments Created 6 months ago by mwilliams

Title

Body
In an attempt to use the Twitter gem in my Rails app, I'm being presented with the following exception: uninitialized constant Twitter::OAuth It occurs when trying to instantiate OAuth. oauth = Twitter::OAuth.new(ServiceAPIKeys.twitter['api_key'], ServiceAPIKeys.twitter['secret_key']) I have all of the dependencies installed and the gems are unpacked in my vendor/gem directory. Thoughts?
or cancel

In an attempt to use the Twitter gem in my Rails app, I'm being presented with the following exception: uninitialized constant Twitter::OAuth

It occurs when trying to instantiate OAuth.
oauth = Twitter::OAuth.new(ServiceAPIKeys.twitter['api_key'], ServiceAPIKeys.twitter['secret_key'])

I have all of the dependencies installed and the gems are unpacked in my vendor/gem directory.

Thoughts?

Comments

mwilliams Tue Jun 09 08:09:42 -0700 2009 | link

Problem found... I was clashing with another vendored gem, Twitter4r. Ugh.

Comment
Problem found... I was clashing with another vendored gem, Twitter4r. Ugh.
or cancel

alainravet Fri Aug 07 05:01:05 -0700 2009 | link

Same problem here, but not the same cause (Twitter4r is not installed on my system.).
I don't know the source of the conflict, but I solved it by inserting 'gem "twitter"', as in :

require 'rubygems' gem 'twitter' <<--- INSERT THIS require 'twitter'

It would be a good idea to update the examples to make sure they work for everybody.

Comment
Same problem here, but not the same cause (Twitter4r is not installed on my system.). I don't know the source of the conflict, but I solved it by inserting 'gem "twitter"', as in : <code> require 'rubygems' gem 'twitter' <<--- INSERT THIS require 'twitter' </code> It would be a good idea to update the examples to make sure they work for everybody.
or cancel

Parsed with GitHub Flavored Markdown
12.

0 votes

Need to use this gem with OAuth 0.3.5
1 comment Created 5 months ago by bradleybirnbaum

Title

Body
Can you please bump up the OAuth gem to 0.3.5.
or cancel

Can you please bump up the OAuth gem to 0.3.5.

Comments

pengwynn Wed Nov 04 07:38:03 -0800 2009 | link

Fixed, closing.

Comment
Fixed, closing.
or cancel

Parsed with GitHub Flavored Markdown
13.

0 votes

Mash modifies Hash class, breaks my app.
1 comment Created 3 months ago by ssoroka

Title

Body
title says it all. Mash redefines stringify_keys and stringify_keys! to have deep-stringify type functionality, but it should not be modifying Hash. Can we avoid using (or patch) mash?
or cancel

title says it all. Mash redefines stringify_keys and stringify_keys! to have deep-stringify type functionality, but it should not be modifying Hash.

Can we avoid using (or patch) mash?

Comments

pengwynn Wed Nov 25 18:47:25 -0800 2009 | link

Believe this is closed with the move to Hashie

Comment
Believe this is closed with the move to Hashie
or cancel

Parsed with GitHub Flavored Markdown
14.

0 votes

Deprecate #replies in favor of #mentions
1 comment Created 2 months ago by rmm5t

Title

Body
Twitter dropped /statuses/replies in favor of /statuses/mentions. Likewise, this branch deprecates #replies in favor of #mentions. http://github.com/rmm5t/twitter/commits/replies_to_mentions
or cancel

Twitter dropped /statuses/replies in favor of /statuses/mentions.

Likewise, this branch deprecates #replies in favor of #mentions.
http://github.com/rmm5t/twitter/commits/replies_to_mentions

Comments

pengwynn Wed Nov 04 07:36:51 -0800 2009 | link

Thanks! Applied.

Comment
Thanks! Applied.
or cancel

Parsed with GitHub Flavored Markdown
15.

1 vote

user_timeline option
1 comment Created about 1 month ago by tjgillies

Title

Body
what about adding count option to user_timelime
or cancel

what about adding count option to user_timelime

Comments

pengwynn Wed Nov 04 07:10:57 -0800 2009 | link

I updated the comment, but the option has always been there. You can pass anything option the Twitter API accepts for that method

Comment
I updated the comment, but the option has always been there. You can pass anything option the [Twitter API accepts for that method](http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline)
or cancel

Parsed with GitHub Flavored Markdown
16.

0 votes

Version constraints for Mash (v0.0.3) and other dependencies
3 comments Created about 1 month ago by mislav

Title

Body
Twitter gem should use pessimistic version constraints for dependencies. My proposal: oauth ~> 0.3.5 mash ~> 0.0.3 httparty ~> 0.4.3 Right now the dependencies are: oauth (>= 0.3.5, runtime) mash (= 0.0.3, runtime) httparty (= 0.4.3, runtime) This means when newer "mash" is released (github version is v0.0.7 now) with much needed bugfixes, twitter gem will currently not load it because it's locked to v0.0.3. With a pessimistic version constraint, it will load any newer 0.0.x version. Also, currently if an incompatible new OAuth gem is released—let's imagine v0.5.0—twitter gem will load it without second thought and that might break functionality. With a pessimistic version constraint, it will only load newer 0.3.x releases, but never 0.4.0 or higher.
or cancel
Twitter gem should use pessimistic version constraints for dependencies. My proposal:
```
oauth ~> 0.3.5
mash ~> 0.0.3
httparty ~> 0.4.3
```
Right now the dependencies are:
```
oauth (>= 0.3.5, runtime)
mash (= 0.0.3, runtime)
httparty (= 0.4.3, runtime)
```
This means when newer "mash" is released (github version is v0.0.7 now) with much needed bugfixes, twitter gem will currently not load it because it's locked to v0.0.3. With a pessimistic version constraint, it will load any newer 0.0.x version.

Also, currently if an incompatible new OAuth gem is released—let's imagine v0.5.0—twitter gem will load it without second thought and that might break functionality. With a pessimistic version constraint, it will only load newer 0.3.x releases, but never 0.4.0 or higher.
Comments

pengwynn Wed Nov 04 07:03:14 -0800 2009 | link

Agreed. I'll make the change.

Comment
Agreed. I'll make the change.
or cancel

pengwynn Wed Nov 04 07:37:04 -0800 2009 | link

Applied.

Comment
Applied.
or cancel

mislav Wed Nov 04 07:59:56 -0800 2009 | link

Thanks. I suggest you go through tickets here about Mash/OAuth versions … there are quite a few and should probably be consolidated down to one or two.

Comment
Thanks. I suggest you go through tickets here about Mash/OAuth versions … there are quite a few and should probably be consolidated down to one or two.
or cancel

Parsed with GitHub Flavored Markdown
17.

0 votes

Add support for statuses/home_timeline
1 comment Created about 1 month ago by coderifous

Title

Body
From Twitter API Wiki: _This home_timeline is identical to statuses/friends_timeline except it also contains retweets, which statuses/friends_timeline does not (for backwards compatibility reasons). In a future version of the API, statuses/friends_timeline will go away and be replaced by home_timeline._ This branch adds support for home timeline: http://github.com/coderifous/twitter/commits/add_home_timeline
or cancel

From Twitter API Wiki:

This home_timeline is identical to statuses/friends_timeline except it also contains retweets, which statuses/friends_timeline does not (for backwards compatibility reasons). In a future version of the API, statuses/friends_timeline will go away and be replaced by home_timeline.

This branch adds support for home timeline:
http://github.com/coderifous/twitter/commits/add_home_timeline

Comments

pengwynn Wed Nov 25 18:46:36 -0800 2009 | link

Thanks! Patched and released in 0.7.6.

Comment
Thanks! Patched and released in 0.7.6.
or cancel

Parsed with GitHub Flavored Markdown
19.

1 vote

Do you support blocks/blocking?
3 comments Created 15 days ago by kostya1241

Title

Body
Can't find how to call this API: http://apiwiki.twitter.com/Twitter+REST+API+Method%3A-blocks-blocking Please point out if I missed it.
or cancel

Can't find how to call this API: http://apiwiki.twitter.com/Twitter+REST+API+Method%3A-blocks-blocking
Please point out if I missed it.

Comments

pengwynn Sat Dec 12 10:21:52 -0800 2009 | link

Yes it's blocked_ids

Comment
Yes it's blocked_ids
or cancel

kostya1241 Sat Dec 12 10:54:30 -0800 2009 | link

Yep, thanks, I've seen the "blocked_ids" option.
I was asking if you support exactly "blocks/blocking", that "Returns an array of user objects that the authenticating user is blocking."

Comment
Yep, thanks, I've seen the "blocked_ids" option. I was asking if you support exactly "blocks/blocking", that "Returns an array of user objects that the authenticating user is blocking."
or cancel

kostya1241 Sat Dec 12 11:37:08 -0800 2009 | link

Resolution: supported since version 0.7.10
Thanks pengwynn.

Comment
Resolution: supported since version 0.7.10 Thanks pengwynn.
or cancel

Parsed with GitHub Flavored Markdown
3.

2 votes

Crack error when creating friendship
0 comments Created 7 months ago by shanev

Title

Body
Not sure if this is an issue with Crack or with this lib, but every time I try to create a friendship, I get this error: >> base.friendship_create('anyone') Crack::ParseError: Invalid JSON string from /Library/Ruby/Gems/1.8/gems/crack-0.1.2/lib/crack/json.rb:14:in `parse' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/request.rb:73:in `parse' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/request.rb:48:in `make_friendly' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/request.rb:34:in `perform' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/request.rb:10:in `post' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/base.rb:162:in `perform_post' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/base.rb:76:in `friendship_create'
or cancel
Not sure if this is an issue with Crack or with this lib, but every time I try to create a friendship, I get this error:
base.friendship_create('anyone') Crack::ParseError: Invalid JSON string

from /Library/Ruby/Gems/1.8/gems/crack-0.1.2/lib/crack/json.rb:14:in `parse' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/request.rb:73:in `parse' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/request.rb:48:in `make_friendly' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/request.rb:34:in `perform' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/request.rb:10:in `post' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/base.rb:162:in `perform_post' from /Library/Ruby/Gems/1.8/gems/twitter-0.6.8/lib/twitter/base.rb:76:in `friendship_create'
Comments

Parsed with GitHub Flavored Markdown
6.

2 votes

Methods on Twitter class don't check for errors
0 comments Created 6 months ago by bkocik

Title

Body
The methods on the Twitter class (firehose, friend_ids, follower_ids, status, user) assume that no errors will occur, but all of them can at least return a 50x error. An example using FakeWeb: <pre> >> FakeWeb.register_uri(:get, 'http://twitter.com/statuses/public_timeline.json', ?> :string => '{"request":"\/statuses\/public_timeline.json","error":"Bad gateway"}', ?> :status => ['502', 'Bad Gateway']) => [#<FakeWeb::Responder:0x7f3b2138 @options={:status=>["502", "Bad Gateway"], :string=>"{\"request\":\"\\/statuses\\/public_timeline.json\",\"error\":\"Bad gateway\"}"}, @method=:get, @uri="http://twitter.com/statuses/public_timeline.json", @times=1>] >> Twitter.firehose NoMethodError: undefined method `stringify_keys' for ["request", "/statuses/public_timeline.json"]:Array from /usr/lib/ruby/gems/1.8/gems/mash-0.0.3/lib/mash.rb:131:in `deep_update' from /usr/lib/ruby/gems/1.8/gems/mash-0.0.3/lib/mash.rb:50:in `initialize' from /usr/lib/ruby/gems/1.8/gems/twitter-0.6.11/lib/twitter.rb:34:in `new' from /usr/lib/ruby/gems/1.8/gems/twitter-0.6.11/lib/twitter.rb:34:in `firehose' </pre>
or cancel
The methods on the Twitter class (firehose, friend_ids, follower_ids, status, user) assume that no errors will occur, but all of them can at least return a 50x error. An example using FakeWeb:
```
>> FakeWeb.register_uri(:get, 'http://twitter.com/statuses/public_timeline.json',
?> :string => '{"request":"\/statuses\/public_timeline.json","error":"Bad gateway"}',
?> :status => ['502', 'Bad Gateway'])
=> [#["502", "Bad Gateway"], :string=>"{\"request\":\"\\/statuses\\/public_timeline.json\",\"error\":\"Bad gateway\"}"}, @method=:get, @uri="http://twitter.com/statuses/public_timeline.json", @times=1>]
>> Twitter.firehose
NoMethodError: undefined method `stringify_keys' for ["request", "/statuses/public_timeline.json"]:Array
        from /usr/lib/ruby/gems/1.8/gems/mash-0.0.3/lib/mash.rb:131:in `deep_update'
        from /usr/lib/ruby/gems/1.8/gems/mash-0.0.3/lib/mash.rb:50:in `initialize'
        from /usr/lib/ruby/gems/1.8/gems/twitter-0.6.11/lib/twitter.rb:34:in `new'
        from /usr/lib/ruby/gems/1.8/gems/twitter-0.6.11/lib/twitter.rb:34:in `firehose' 
```
Comments

Parsed with GitHub Flavored Markdown
8.

0 votes

Error handling 404 from Twitter::Search (JSON error)
0 comments Created 6 months ago by chubas

Title

Body
When you request a search with a :since_id parameter too old, according to [Twitter](http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search): > This method will return an HTTP 404 error if since_id is used and is too old to be in the search index which results in a +Crack::ParseError+ exception
or cancel

When you request a search with a :since_id parameter too old, according to Twitter:

This method will return an HTTP 404 error if since_id is used and is too old to be in the search index

which results in a +Crack::ParseError+ exception

Comments

Parsed with GitHub Flavored Markdown
9.

3 votes

stringify_keys error in Mash.new when using Twitter::search
6 comments Created 6 months ago by metrostar

Title

Body
happens periodically, presumably when twitter search services returns a string for a response instead of a hash?
or cancel
happens periodically, presumably when twitter search services returns a string for a response instead of a hash?

Comments
labzero Mon Jun 22 14:38:37 -0700 2009 | link
I had a similar issue on Ubuntu something was funny in Net::HTTP and was sending requests that twitter couldn't process (400 response). Here's what I put in my environment.rb to fix it:
module Twitter class Search
def fetch(force=false) if @fetch.nil? || force query = @query.dup query[:q] = query[:q].join(' ') query[:format] = 'json' #This line is the hack and whole reason we're monkey-patching at all. response = self.class.get('http://search.twitter.com/search', :query => query, :format => :json) @fetch = Mash.new(response) end @fetch end
end end
Comment
I had a similar issue on Ubuntu something was funny in Net::HTTP and was sending requests that twitter couldn't process (400 response). Here's what I put in my environment.rb to fix it: <code> module Twitter class Search def fetch(force=false) if @fetch.nil? || force query = @query.dup query[:q] = query[:q].join(' ') query[:format] = 'json' #This line is the hack and whole reason we're monkey-patching at all. response = self.class.get('http://search.twitter.com/search', :query => query, :format => :json) @fetch = Mash.new(response) end @fetch end end end </code>
or cancel
metrostar Tue Jun 23 11:49:16 -0700 2009 | link

labzero. Thanks a bunch. This worked for us! I tried doing a HTTP.new('search.twitter.com', nil).get('/search.json?q=obama') in irb and this would yield the same result. Your patch sidesteps that somehow. This problem just started occuring...I think after the ruby BigDecimal patch on EngineYard I believe, but that may be a coincidence. Any further insights?

Comment
labzero. Thanks a bunch. This worked for us! I tried doing a HTTP.new('search.twitter.com', nil).get('/search.json?q=obama') in irb and this would yield the same result. Your patch sidesteps that somehow. This problem just started occuring...I think after the ruby BigDecimal patch on EngineYard I believe, but that may be a coincidence. Any further insights?
or cancel

labzero Tue Jun 23 12:52:17 -0700 2009 | link

Glad it worked for you! I have no idea why it's happening on my Ubuntu servers, they haven't changed and I just started using the twitter gem... The bug didn't happen locally on Leopard.

Comment
Glad it worked for you! I have no idea why it's happening on my Ubuntu servers, they haven't changed and I just started using the twitter gem... The bug didn't happen locally on Leopard.
or cancel

jeremyw Fri Jul 03 07:52:17 -0700 2009 | link

I've been experiencing this consistently with 2 apps hosted on Heroku. I'll try the patch.
UPDATE: Solved my problem on Heroku! Thanks!

Comment
I've been experiencing this consistently with 2 apps hosted on Heroku. I'll try the patch. UPDATE: Solved my problem on Heroku! Thanks!
or cancel

andion Mon Jul 13 15:23:27 -0700 2009 | link

Solved also my problem on heroku. Thanks!

Comment
Solved also my problem on heroku. Thanks!
or cancel
tibbon Sun Sep 06 16:46:35 -0700 2009 | link
This is still acting up for me, even when I drop that code into my code. Still get the error randomly:

/var/lib/gems/1.8/gems/httparty-0.4.3/lib/httparty/response.rb:15:in send': undefined methodstringify_keys' for #<String:0x7fe66b8cc4a0> (NoMethodError)

from /var/lib/gems/1.8/gems/httparty-0.4.3/lib/httparty/response.rb:15:in `method_missing' from /var/lib/gems/1.8/gems/mash-0.0.3/lib/mash.rb:131:in `deep_update' from /var/lib/gems/1.8/gems/mash-0.0.3/lib/mash.rb:50:in `initialize' from pullterm.rb:63:in `new' from pullterm.rb:63:in `fetch' from /var/lib/gems/1.8/gems/twitter-0.6.14/lib/twitter/search.rb:109:in `each' from pullterm.rb:86:in `query_term' from pullterm.rb:127
Comment
This is still acting up for me, even when I drop that code into my code. Still get the error randomly: /var/lib/gems/1.8/gems/httparty-0.4.3/lib/httparty/response.rb:15:in `send': undefined method `stringify_keys' for #<String:0x7fe66b8cc4a0> (NoMethodError) from /var/lib/gems/1.8/gems/httparty-0.4.3/lib/httparty/response.rb:15:in `method_missing' from /var/lib/gems/1.8/gems/mash-0.0.3/lib/mash.rb:131:in `deep_update' from /var/lib/gems/1.8/gems/mash-0.0.3/lib/mash.rb:50:in `initialize' from pullterm.rb:63:in `new' from pullterm.rb:63:in `fetch' from /var/lib/gems/1.8/gems/twitter-0.6.14/lib/twitter/search.rb:109:in `each' from pullterm.rb:86:in `query_term' from pullterm.rb:127
or cancel
Parsed with GitHub Flavored Markdown
10.

-1 votes

A user-agent is required for twitter searches
0 comments Created 6 months ago by esilverberg

Title

Body
I think this may be a new change to twitter, but user-agents are now required or else it will return a 400 Bad Request. Add this line to work around it for now: Twitter::Search.default_options = {:headers => {'User-Agent' => 'YOUR_USER_AGENT_STRING'}}
or cancel
I think this may be a new change to twitter, but user-agents are now required or else it will return a 400 Bad Request.

Add this line to work around it for now:
```
    Twitter::Search.default_options = {:headers => {'User-Agent' => 
        'YOUR_USER_AGENT_STRING'}}
```
Comments

Parsed with GitHub Flavored Markdown
11.

4 votes

JSON parsing error with Crack
3 comments Created 6 months ago by dacort

Title

Body
Crack seems to have problem's with Twitter's JSON format. If I use the Rails json gem instead, I have no problems. /Library/Ruby/Gems/1.8/gems/crack-0.1.1/lib/crack/json.rb:14:in `parse': Invalid JSON string (Crack::ParseError)
or cancel

Crack seems to have problem's with Twitter's JSON format. If I use the Rails json gem instead, I have no problems.

/Library/Ruby/Gems/1.8/gems/crack-0.1.1/lib/crack/json.rb:14:in `parse': Invalid JSON string (Crack::ParseError)

Comments

brookr Thu Jul 16 01:05:24 -0700 2009 | link

I am seeing this error as well (but i'm only using HTTParty, but assuming the issue is the same with the Twitter gem?), but it only seems to be on large data sets (like @barackobama's twitter friends):

/Library/Ruby/Gems/1.8/gems/crack-0.1.3/lib/crack/json.rb:14:in `parse': Invalid JSON string (Crack::ParseError)

Comment
I am seeing this error as well (but i'm only using HTTParty, but assuming the issue is the same with the Twitter gem?), but it only seems to be on large data sets (like @barackobama's twitter friends): /Library/Ruby/Gems/1.8/gems/crack-0.1.3/lib/crack/json.rb:14:in `parse': Invalid JSON string (Crack::ParseError)
or cancel

tibbon Sun Aug 16 20:07:12 -0700 2009 | link

Some of it 'seems' to be unicode issues potentially. I've had to write some stuff to get around the followers/tweets that blow it up, but I can't figure out which ones are causing it. Its always the same tweet/user however, which makes me think of some unicode issue causing improper JSON that blows up Crack.

Comment
Some of it 'seems' to be unicode issues potentially. I've had to write some stuff to get around the followers/tweets that blow it up, but I can't figure out which ones are causing it. Its always the same tweet/user however, which makes me think of some unicode issue causing improper JSON that blows up Crack.
or cancel

nextstep Mon Aug 17 14:30:09 -0700 2009 | link

I'm getting the same error regardless of the user I'm trying to unfollow (friendship_destroy), with crack-0.1.4.

Comment
I'm getting the same error regardless of the user I'm trying to unfollow (friendship_destroy), with crack-0.1.4.
or cancel

Parsed with GitHub Flavored Markdown
18.

0 votes

Problem with list_remove_user
1 comment Created 25 days ago by pengwynn

Title

Body
list_add_member works just fine but when trying list_remove_user i get this error Twitter::RateLimitExceeded: (400): Bad Request - You must specify a member Which is the same error you get if you use the api via curl and leave off the id http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-DELETE-list-members It has nothing to do with the rate limit. twitter gem just returns all 400's as a ratelimitexceded. There is no rate limit for adding and removing list items and also my account is white listed.
or cancel

list_add_member works just fine but when trying list_remove_user i get
this error

Twitter::RateLimitExceeded: (400): Bad Request - You must specify a
member

Which is the same error you get if you use the api via curl and leave
off the id
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-DELETE-list-members

It has nothing to do with the rate limit. twitter gem just returns all
400's as a ratelimitexceded. There is no rate limit for adding and
removing list items and also my account is white listed.

Comments

pengwynn Tue Dec 01 07:39:12 -0800 2009 | link

I think the same fix we just put in for list_add_member might need to be applied here. I'll investigate

Comment
I think the same fix we just put in for list_add_member might need to be applied here. I'll investigate
or cancel

Parsed with GitHub Flavored Markdown

Labels

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments