This is an "uber-story" that encompasses all the stuff we need to implement the metagame. Fill this out as needed.

Add RSS/Atom feeds for Hunts, Comments, and a User's Activity stream.

This will allow people to use their Google credentials to log into 1hph.

OAuth 2.0, which is the replacement for Facebook Connect

For each photo, you should be able to mark it as inappropriate, or delete it if you are the person who submitted it.

Create a good robots.txt so search engines don't crawl some pages.

The default table inserts a
between the form input and the hint text. It also doesn't add any classes to the hint text, so it's very difficult to style.

We need to do our own form layout (create an inclusion tag or snippet to do this for all forms: see http://docs.djangoproject.com/en/1.2/topics/forms/ (search for "reusable form templates")

Begin creating ads on certain screens (hunt, submission, comments)

Add captchas to comments and submissions for non-authenticated users (check out django-simple-captcha or supercaptcha, django-myrecaptcha)

1. Read user's geolocation using the Geolocation API
2. Display it on somewhere in the UI (their profile?)
3. Reverse Geocode using Twitter's API.
4. Use this as the lat/lon for submissions.

Once we have Twitter submissions, get the latitude/longitude via the Tweet.
Next, we may be able to find it in the photo.

Create a wiki page that lists all the test cases that we should begin to build unit tests for.

Currently this is unimplemented.

Make this enabled by settings, and enable it on the production server.

Current behavior:
If you submit via email, there is no reply. The user needs to go to the site to see whether or not the submission succeeded.

Desired behavior:
Reply to the email, and include a link to the photo.

This will list the top winners (based on points? XP? depends).

For now, it will be the people who have won the most medals.

Twitter users who send a picture to @1hph with the proper hashtag will be added to the hunt. Standard submission rules apply.

Big TODO: How do we extract the file from whatever twitter upload service they use? Hopefully there's some metadata we can use.

Right now it's fugly. We need better art and a cooler rules intro.

Sign-in, view current hunts, submit photos, vote. It doesn't need to be fancy.

Need to add the ability in the profile settings screen for the user to remove their photo.

For all client forms, use the jQuery form validation plugin to verify the form before the user clicks "submit."

Repro:

1. Create a current hunt (start time in past, end time in future)
2. Go to the hunt detail screen
3. See that there are 0 submissions, and that the Vote button appears

Expected:
The Vote button shouldn't appear unless there are >2 submissions.

The recent activity list is fugly right now.
Add some icons to it.
Make it look nicer.

Oh, and while you're add it, limit it to the last few days.

This needs to be finished if we ever want to make our API public.

User can upload their profile photo.

Every X hours a new hunt should be generated that expires in an hour, with voting expiring a day later.

X could be 24 to start.

MySQL is encumbered. Don't use it.

They need to have some ability to remove submissions they create.

This should be integrated with some form of "button overlay" for all images that will provide buttons for other photo-related actions, like "mark as inappropriate"

1. Implement rules around anonymous submissions (from Wave)
2. Implement rules for replacing submissions

Write basic copy for the Help, TOS, Privacy Policy, About us, and Learn More pages.

This is currently unimplemented.

1. Win an award
2. Hunt starts
3. Hunt ends
4. Someone comments on one of their photos

Repro:

1. Create a user in the normal way with a username 'X'
2. Attempt to use "sign-in with Twitter" on a new user whose Twitter screen name is also 'X'

Actual:
3. There's a TODO in gonzo.webapp.account.views.twitter_postauth because in this situation an exception would be thrown if we tried to create a new user with that screen name.

Expected:
3. The new Twitter user should get the opportunity to create a new user name to complete signup.

This could be done using an async call after they first sign in, or it could be manual.

Current behavior:
Right now if the email submission code throws an exception for some reason, this is sent back to the user as a failed email.

Desired behavior:
Send back a better response, and put the backtrace somewhere we might care about it.

This will allow us to compress CSS and Javascript.

We actually can use both -- but it's probably better to put all of this into the web server config rather than relying on Django.

Similar to Twitter's stream API, use a long-lived connection and stream Javascript callbacks for "push" notifications.

This will be enabled to profile settings. These will come from @1hph, and contain the hashtag of the hunt.

They may contain the short URL of the submission as well.

Need to set up mod_expires so our Apache-served resources can be cached. That's why we serve them from Apache in the first place.

Also, add a Cache-Control: public so proxies can cache stuff.

Current SSL is disabled. What we need to do:

1. Get our correct SSL certificates for 1hph.com and dev.1hph.com
2. Install those in Apache and create the appropriate virtual hosts.
3. Test that the account/sign in pages use HTTPS.
4. Test that we leave HTTPS when leaving the account sign in pages.

/media can be rewritten to be media.1hph.com or somesuch so that it there are no cookies on the domain.