Camo only proxies images hosted somewhere else, so it doesn't make sense
to add the proxied versions to search engines. It only creates traffic
for camo when /camo/* urls are in search results.

closes #7726

Squashed commits:
[d5001fe] Refactor
[8d8a23f] Add test for when authorization is denied
[659fc56] Adjust password flow integration test

So we can correctly reference the images

This allows us to reuse any CSS we have, unify
their look and unify their look with the regular
page design.

This works by instantiating ActionView and rendering
templates in a rake task.

Inspired by the errgent gem.

It allowed Flash apps on any domain to make requests on
behalf of a signed in user.

Thanks to Oliver Beg for the hint.

I moved 404 to the assets to avoid loading font and images from joindiaspora.

 #- Can I move the design to a 404-style.css file which will be in the public repository too ?
 #- This pull request proposes to insert the two font files and the cat image, do you agree ? Depend of amazon seems really bad for me.

Changing 404 message to no longer use Joindiaspora's media on S3

clarify comments and update permanently moved URL

this changes profile background colors to be dark, and sets up the groundwork for uploading user-selected background images for their profiles.  all the styling is in place; what remains is creating a new image uploader and (possibly) a new controller action.

for information on what command to use to darken the background image that's uploaded, see line 11 in `_profile.scss`.  the current image tests in the public folder are results of the convert command noted.

made favicon sexier; extracted form-block into its own custom class; made the title of pages less caps-lock.

I think possibly "https://github.com/diaspora/diaspora/issues" better than "http://bugs.joindiaspora.com/"

add some assets which are for bootstrap which seem to need them to be in public.  bootstrap-sass should deal with this

heroku and asset sync, which puts the S3 config vars in from your app
config.

fix for the stream not loading;  we were creating status_message objects that were simply wrappers around posts.  in the lastest codebase, status_messages in js are what we are using for the new post form, so we need to just tell our post collection to stop making status_messages directly