This might help with GS compatibility

This prevents the bug where if you go "back" to the UI after navigating to
another page it loads with the old set of statuses

registration API

as well as formatting of content

Added stack trace for SQL queries in development
Removed badly thought out accounts/lookup API

and atom feed generation to some extent, as well as the way mentions are
stored

relations on Status#mentions

simplify FanOutOnWriteService, add /api/accounts/lookup method

the block, even though the last line of a block is an implicit return. I am
confused to say the least

POST /api/statuses                  Params: status (text contents), in_reply_to_id (optional)
GET  /api/statuses/:id
POST /api/statuses/:id/reblog

GET  /api/accounts/:id
GET  /api/accounts/:id/following
GET  /api/accounts/:id/followers
POST /api/accounts/:id/follow
POST /api/accounts/:id/unfollow

POST /api/follows                  Params: uri (e.g. user@domain)

OAuth authentication is currently disabled, but the API can be used with HTTP Auth.