This is the error when deployed on heroku:

This is the error locally:

The herokuapp link takes me to the "Authenticate with your Twitter" page. Instead of opening a pop-up or OAuth in the background, it takes me to "please check your logs" page.

Hi, I don't know rails at all so that may be my problem.

I followed the Installation and Usage directions on the Readme. I created a new Twitter app and entered the consumer keys.

I get an unauthorized error when I try to log in.

Here is the dump.
https://gist.github.com/ondrae/8588754

Not an issue, but a feature (maybe?). It would be nice to see exactly who you are about to follow prior to following a list of some indeterminate number of users.

I'll submit a pull request if this attracts any interest.

This could just be a matter of preference, but is there any opposition to using RSpec to test this app (as opposed to Test::Unit)? I'm open to using Test::Unit, but I find RSpec's syntax a little cleaner. @sferik what was the design decision behind the testing framework? Do you prefer Test::Unit? I'll defer to you. Obviously, changing the framework for a single contributor wouldn't be justified.

After following the deployment instructions, I can select a list and click the 'Follow all members of this list' button but then I get the following:

Running heroku logs results in this output, with the key line appearing to be:

Twitter::Error::Unauthorized (Read-only application cannot POST.):

Changing the permission to read+write seemed to fix that (after also updating the config vars with the new consumer key and secret).

What was the 'team' list? CfA appears to not have it anymore: https://twitter.com/codeforamerica/lists

@Jaime-Alexis do you know what happened to it?

Trying to follow that list via http://follow-all.herokuapp.com/list results in an error.

I think the fix for this would be to change 'team' to 'staff'. We have a staff list.

Follow-all is great for Twitter! Can we extend it to follow all for github also? Cheers!

Currently the lists generated for fellows is 2011 (FIRST_YEAR) through the current year (see sessions_helper.rb. That works usually, but when the fellows for the following year (2015) are announced in late 2014, they won't show up as a list.

The simplest 'fix' is adding +1 after Date.today.year but we'll probably also want a way to ensure that the list actually exists (otherwise, in January we'd have a 2016 list before the fellows have even applied).

More of a question than an issue, but would there be value in adding an input for following lists not hard-coded into the application?

the app is down
error in the console is 503 service unavailable