The db setup instructions in the README are out of date. We need to update them to show a user how to create a database from scratch, and how to upgrade a chirpy database to a porick database.

For the latter, I used https://github.com/kopf/porick/blob/master/migrate_db.sh in the previous incarnation of porick.

For all db upgrades in the future, alembic should be used. We should look into the possibility of porting migrate_db.sh to an alembic script.

copy of kopf/porick#48

When there are quotes, the interface should directly dump a user to /browse rather than telling them what chirpy is.

It seems as if the score attribute of Quote isn't used. It might well be a left-over from the chirpy times.

@stesh can you have a look at the qdb database and see if it's used at all?

If not, we can get rid of it here and create a db migration script to remove it from the db.

Copy of kopf/porick#46

Instead of having a link to a login page, place two text fields in a dropdown from the navbar for username and password.

• Add alembic to project

Migration path:

• Write initial db scripts (for migrating from chirpy) https://github.com/kopf/porick/blob/master/migrate_db.sh
• Change PasswordResets column key length to 36

Similar to what was there on Chirpy.

Intended use-cases: removing line-breaks, harmonizing tags, retro-fitting tags

Access: probably only for 'admins'.

The auth tokens are vulnerable to a hash-extension attack as they don't use a real HMAC function. Simple hash based tokens containing a secret are not secure for authentication.

https://blog.skullsecurity.org/2012/everything-you-need-to-know-about-hash-length-extension-attacks

• center the pagination at the bottom of the page
• browsing by tags
• search
• create a quote page
• reset password page
• handling pages displaying a single quote (e.g. random or /browse/<id>), as this breaks the pagination. this might be tricky to solve elegantly

Copy of kopf/porick#44

e.g. in the case of the following quote, with fields:

   rating: 0
    votes: 2
submitted: 2012-10-26 14:26:12
    score: 1
   status: 1

its # of upvotes is calculated as equal to votes (2) and number of downvotes equal to votes - rating (2). however we can see this isn't the case when we look at the actual votes for this quote:

+----------+---------+-----------+
| quote_id | user_id | direction |
+----------+---------+-----------+
|     1137 |       4 | up        |
|     1137 |       6 | down      |
+----------+---------+-----------+

There's a div and a ul of class pagination - one or the other probably has a CSS rule in bootstrap for a grey vertical line on the left border, and that's what's causing it. That's my suspicion, at least.