G.Ambatte

Still working on functionality, visibility will come next.

I believe that these latest changes have finished the first pass at functionality. My thinking for the process is roughly as follows, at this stage I've used the DMCA Takedown...

There's still a ton of debugging commands that will need to be removed, and some tuning of the actual lock data functions - I believe that I can probably just...

On opening a locked brew for editing:  On clicking "REQUEST REVIEW":  On the new "LOCKS" tab of the Admin page: - Lock Count:  Clicking "REFRESH" causes the...

Still need to implement some feedback from the Lock Brew method, to indicate success or failure. Otherwise I think most of the functionality is in a good place, although the...

It should work - the change to `homebrew.api:getBrew` should throw an error on any locked brew, the only exception being a valid edit attempt, in which case the lock notification...

Looks like it's getting back 503 Service Unavailable errors, possibly related to DB request timeouts. Might be a case of adding an index, or even pushing `locks` to it's own...

The addition of indexes on the database have greatly increased the speed of the lock functions.

Currently, the message and code can be set to anything - I used 1001 in my test lock simply because it doesn't get used anywhere else, so I could be...

> We should also specify what is the offending content as well as what is the specific issue. IMHO there is no point to the notification message if it doesn't...