Issues - mbleigh/twitter-auth

mbleigh / twitter-auth

276

Description:

Standard authentication stack for Rails using Twitter to log in.

Sort by: Priority | Votes | Last Updated

Loading…

11.

4 votes

0.2.0
x

Integrate Grackle
0 comments Created 6 months ago by mbleigh

Title

Body
I've decided that [Grackle](http://github.com/hayesdavis/grackle/tree/master) is close enough to my lightweight and "not too much magic" approach to API access that it should be the default way people access Twitter through TwitterAuth. I will be bringing in Grackle as a dependency and utilizing it instead of the current dispatcher. I will also, however, be wrapping it up so that everything still works the same and providing the same HTTP verb methods as currently. You'll just *also* be able to do something like this: user.twitter.statuses.replies?(:since_id => 123)
or cancel
I've decided that Grackle is close enough to my lightweight and "not too much magic" approach to API access that it should be the default way people access Twitter through TwitterAuth. I will be bringing in Grackle as a dependency and utilizing it instead of the current dispatcher. I will also, however, be wrapping it up so that everything still works the same and providing the same HTTP verb methods as currently. You'll just also be able to do something like this:
```
user.twitter.statuses.replies?(:since_id => 123)
```
Comments

Parsed with GitHub Flavored Markdown
7.

1 vote

0.2.0
x

Support for search?
2 comments Created 7 months ago by davidw

Title

Body
I had a dig through the code, and a number of things indicate that twitter's search methods are not supported. For instance, the base_url is https://twitter.com, whereas the search API says that it's necessary to use search.twitter.com: http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search Thanks, Dave
or cancel
I had a dig through the code, and a number of things indicate that twitter's search methods are not supported. For instance, the base_url is https://twitter.com, whereas the search API says that it's necessary to use search.twitter.com:

http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search

Thanks,
Dave

Comments
mbleigh Wed Apr 22 21:24:07 -0700 2009 | link
The Search API doesn't require authentication so I haven't worked in any support for it yet. You can just make straight up calls to the API like this:

require 'open_uri' require 'json' def twitter_search(query) JSON.parse(open("http://search.twitter.com/search.format?q=#{CGI.escape(query)}").read) end

That's a simple example, but it works. I will be adding Twitter Search support as an eventual result of #1 because I will be integrating search into my TwitterDispatch gem. Hope that helps.
Comment
The Search API doesn't require authentication so I haven't worked in any support for it yet. You can just make straight up calls to the API like this: require 'open_uri' require 'json' def twitter_search(query) JSON.parse(open("http://search.twitter.com/search.format?q=#{CGI.escape(query)}").read) end That's a simple example, but it works. I will be adding Twitter Search support as an eventual result of #1 because I will be integrating search into my TwitterDispatch gem. Hope that helps.
or cancel
mbleigh Fri May 08 11:39:28 -0700 2009 | link

This will be implemented once Grackle is integrated into TwitterAuth.

Comment
This will be implemented once Grackle is integrated into TwitterAuth.
or cancel

Parsed with GitHub Flavored Markdown
12.

3 votes

0.2.0
x

Catch the exception while twitter service is under maintaince.
1 comment Created 6 months ago by sishen

Title

Body
Sometimes twitter is under maintaince and as a result the app can't request the oauth token. We need to do something instead of directly raising the exception to the top, such as catch the exception in the SessionsController#new, rescue Exception => e authentication_failed("We're currently experiencing issues with Twitter's OAuth Service. Please try later.") and return
or cancel
Sometimes twitter is under maintaince and as a result the app can't request the oauth token. We need to do something instead of directly raising the exception to the top, such as catch the exception in the SessionsController#new,

rescue Exception => e
```
authentication_failed("We're currently experiencing issues with Twitter's OAuth Service. Please try later.") and return
```
Comments

mbleigh Fri May 08 16:24:00 -0700 2009 | link

Yeah, I noticed that as well. Will work in a catch for that sometime soon.

Comment
Yeah, I noticed that as well. Will work in a catch for that sometime soon.
or cancel

Parsed with GitHub Flavored Markdown
2.

4 votes

Refactor to Mixin
2 comments Created 7 months ago by mbleigh

Title

Body
Make the TwitterAuth functionality a mixin instead of a superclass, so that TwitterAuth can be more configurable and added in a less strict manner. Example: class User < ActiveRecord::Base twitter_authenticated :via => :oauth end
or cancel
Make the TwitterAuth functionality a mixin instead of a superclass, so that TwitterAuth can be more configurable and added in a less strict manner.

Example:
```
class User < ActiveRecord::Base
  twitter_authenticated :via => :oauth
end
```
Comments
bjeanes Fri Apr 17 18:52:05 -0700 2009 | link

This is perfect for those of us wanting to add twitter login as an optional way to authenticate, in addition to traditional login with username and password

Comment
This is perfect for those of us wanting to add twitter login as an optional way to authenticate, in addition to traditional login with username and password
or cancel
mbleigh Fri Apr 17 21:09:43 -0700 2009 | link
Ok, this is something I'd like to tackle in the near future. This is my proposed laundry list, tell me if I'm missing anything:

Allow TwitterAuth to be added to a model via a twitter_authenticated mixin

Allow enough configuration to keep it from conflicting with other authentication solutions. (I might namespace all of the functionality into a proxied twitter object that does more than the current dispatcher).

Remove the validations from being required (this way apps that don't solely use TwitterAuth can have blank fields for some of those fields).

Support legacy versions of TwitterAuth by making the GenericUser automatically call twitter_authenticated

Tweak the generator to take advantage of the new refactor.

Obviously this isn't a small task and I'll be starting work on it in a mixin branch sometime soon.
Comment
Ok, this is something I'd like to tackle in the near future. This is my proposed laundry list, tell me if I'm missing anything: * Allow TwitterAuth to be added to a model via a `twitter_authenticated` mixin * Allow enough configuration to keep it from conflicting with other authentication solutions. (I might namespace all of the functionality into a proxied twitter object that does more than the current dispatcher). * Remove the validations from being required (this way apps that don't solely use TwitterAuth can have blank fields for some of those fields). * Support legacy versions of TwitterAuth by making the GenericUser automatically call `twitter_authenticated` * Tweak the generator to take advantage of the new refactor. Obviously this isn't a small task and I'll be starting work on it in a `mixin` branch sometime soon.
or cancel
Parsed with GitHub Flavored Markdown
3.

0 votes

Support Multiple Services
2 comments Created 7 months ago by mbleigh

Title

Body
Support Twitter-Compatible APIs alongside Twitter in the same application (Laconi.ca, Present.ly).
or cancel

Support Twitter-Compatible APIs alongside Twitter in the same application (Laconi.ca, Present.ly).

Comments

drnic Thu Apr 23 16:02:51 -0700 2009 | link

I don't understand what this request is for?

Comment
I don't understand what this request is for?
or cancel

mbleigh Thu Apr 23 16:22:27 -0700 2009 | link

The ability for a single application to have users authenticating to multiple Twitter-Compatible APIs (e.g. one user connects to Twitter, another to Present.ly).

Comment
The ability for a single application to have users authenticating to multiple Twitter-Compatible APIs (e.g. one user connects to Twitter, another to Present.ly).
or cancel

Parsed with GitHub Flavored Markdown
14.

0 votes

need separate table to store users in db
1 comment Created 6 months ago by tansaku

Title

Body
So I think twitter-auth is great. However I have run into one issue trying to cache twitter data in the database. I find that I have to have a separate twitter_user table to store user information about friends and followers. If I try and drop it into the users table created by twitter-auth I get validation errors like 'login required'. This means my current db caching of twitter data is a little un-DRY. I wonder if it might be valuable to extract the twitter user data available over the wire to a separate table, and then have the data needed for oauth in a separate table?
or cancel

So I think twitter-auth is great. However I have run into one issue trying to cache twitter data in the database. I find that I have to have a separate twitter_user table to store user information about friends and followers. If I try and drop it into the users table created by twitter-auth I get validation errors like 'login required'. This means my current db caching of twitter data is a little un-DRY. I wonder if it might be valuable to extract the twitter user data available over the wire to a separate table, and then have the data needed for oauth in a separate table?

Comments

mbleigh Sun Nov 15 05:01:48 -0800 2009 | link

I think the solution here is to make the validations more optional and flexible instead of requiring a second table for the stored Twitter information. I'll take this under consideration.

Comment
I think the solution here is to make the validations more optional and flexible instead of requiring a second table for the stored Twitter information. I'll take this under consideration.
or cancel

Parsed with GitHub Flavored Markdown
16.

-1 votes

use twitter_id as id in users table
0 comments Created 5 months ago by kykim

Title

Body
is it possible to change the migration to look like this: create_table :users. :id => false do |t| t.integer :id, :limit => 8 # force column to bigint in mysql ... end add_index :users, :id, :unique => true if this is possible, then we can have the id in the users table match the id we get from twitter. we'd have to change the GenericUser model a bit to handle this, but i think it should work.
or cancel
is it possible to change the migration to look like this:
```
create_table :users. :id => false do |t|
  t.integer :id, :limit => 8    # force column to bigint in mysql
  ...
end
add_index :users, :id, :unique => true
```
if this is possible, then we can have the id in the users table match the id we get from twitter.
we'd have to change the GenericUser model a bit to handle this, but i think it should work.
Comments

Parsed with GitHub Flavored Markdown
18.

2 votes

profile_background_tiled is not updating - Attribute name mismatch
1 comment Created 5 months ago by swards

Title

Body
The migration creates an attribute called "profile_background_tiled", but the twitter api returns the attribute "profile_background_tile".
or cancel

The migration creates an attribute called "profile_background_tiled", but the twitter api returns the attribute "profile_background_tile".

Comments

zapnap Sat Sep 26 11:26:44 -0700 2009 | link

I updated this in my fork and sent a pull request

Comment
I updated this in my fork and sent a pull request
or cancel

Parsed with GitHub Flavored Markdown
19.

1 vote

Won't log in
0 comments Created 4 months ago by cbmeeks

Title

Body
I followed the instructions here: http://intridea.com/2009/3/23/twitter-auth-for-near-instant-twitter-apps and http://wiki.github.com/mbleigh/twitter-auth/twitterauth-and-the-oauth-security-advisory When I log in, the records are pulled from Twitter and stored in the db just fine. However, I'm not logged in. "current_user" is always nil. Any suggestions?
or cancel

I followed the instructions here:

http://intridea.com/2009/3/23/twitter-auth-for-near-instant-twitter-apps
and
http://wiki.github.com/mbleigh/twitter-auth/twitterauth-and-the-oauth-security-advisory

When I log in, the records are pulled from Twitter and stored in the db just fine.
However, I'm not logged in. "current_user" is always nil.

Any suggestions?

Comments

Parsed with GitHub Flavored Markdown
21.

0 votes

oauth_callback doesn't seem to be honored by twitter
0 comments Created 10 days ago by openface

Title

Body
Even though I have oauth_callback defined for my environment, Twitter insists on redirecting back to the callback URL that they have defined for my OAuth client.
or cancel

Even though I have oauth_callback defined for my environment, Twitter insists on redirecting back to the callback URL that they have defined for my OAuth client.

Comments

Parsed with GitHub Flavored Markdown