Rather than keep "poorly titled" and "poorly tagged" as reasons for
flagging, make the user do the work of suggesting new ones.
At some point, suggested taggings will flip to real taggings once
they reach a certain count (to be determined later). This also has
to take into account tagging sets that don't contain current tags,
for when they need to be removed.
For titles, I'm not yet sure how to handle this in an automated
fashion except for the (probably rare) case of multiple users
submitting the same exact thing, but at least collect them for now.
Issue #207
Highlights username in a different color and says "authored by"
instead of just "by".
Move html class printing into a method in Story to use in the future
for friends, admin posts, etc.
Closes#171
Instead of hard-coding the scheme and host everywhere, use _path
methods to show relative URLs.
Except that our previous setting of
Rails.application.routes.default_url_options in
config.after_initialize made this moot because Rails inserts that
host into all _path helpers for some reason. So revert that
setting.
But then anything that wants an absolute URL doesn't know the
hostname and the root_url helper throws an exception. So make a
Rails.application.root_url shortcut to pass the per-app settings in
Rails.application to root_url.
Now we can just use _path helpers most places but still use _url
ones where we need them, such as in RSS views and e-mail templates.
if there is only one error and the story has a already_posted_story,
show a custom error dialog that links to that story. if there are
other errors, show the standard error dialog.
closes#135
Private tags would allow admins to create tags that only admins could
use, and that regular users could not filter. The best example use case
for this is an 'announements' tag for site announements that all users
should see.
