StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POTweeting using Twitter gem and Omniauth
primarykey
Id
5884909
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-04T14:22:53.200
FavoriteCount
4
LastActivityDate
2012-11-14T12:10:17.357
LastEditDate
LastEditorUserId
0
OwnerUserId
289614
ParentId
0
PostTypeId
1
Score
2
ViewCount
3391
LastEditorDisplayName
text
Body
I'm developing a web app that will let users tweet posts and links, but I can't seem to get Twitter and Omniauth to play nicely together. I'm currently running on Rails 3.0.6 and Ruby 1.8.7, with the Twitter gem 1.4.1 and Omniauth gem 0.2.5 I can authenticate the users fine, but when it comes to sending a tweet, I'm just given the error: <pre><code> POST https://api.twitter.com/1/statuses/update.json: 401: Incorrect signature </code></pre> I followed <a href="http://blog.assimov.net/post/2358661274/twitter-integration-with-omniauth-and-devise-on-rails-3" rel="nofollow">this tutorial</a>, and have placed my consumer key and consumer secret in a Twitter configure block in my Omniauth initializer, but not the oauth token or oauth secret because these will surely be used on a per-user basis. omniauth.rb <pre><code> Twitter.configure do |config| config.consumer_key = "XXXXXXXXXXXXXXXXXXXXXX" config.consumer_secret = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" end </code></pre> user.rb <pre><code> def twitter unless @twitter_user provider = self.authentications.find_by_provider('twitter') @twitter_user = Twitter::Client.new(:oauth_token => provider.token, :oauth_token_secret => provider.secret) rescue nil end @twitter_user end </code></pre> I then form the request using: <pre><code> current_user.twitter.update("Hello World!") </code></pre> And that's what then gives me the 401 error. Any ideas? Thanks!
Tags
<ruby-on-rails-3><twitter><omniauth>
Title
Tweeting using Twitter gem and Omniauth
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USwastedhours
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.