Password protection / page locking

[schollz]

I think password protection could be done like this:

In an editable page a user can leave a special line, like

<user=zack password=123 public=true>

which has the advantage of not being rendered because its not valid HTML (all invalid HTML is removed on server rendering).

When this is saved into the server, the server will no longer allow anyone to enter the edit page or /list page. Instead it will always redirect to the /view page. If public=false is set, then the /view page can redirect to a password form for login. If public=true is set, then the /view page will display normally. In both cases, once the /view page is rendered, the "Edit" button should change to "Edit (with password)", which on click, asks for a password so that the user can go back to edit their page.

[schollz]

Better alternative (no need to remember keywords):
On the editing page, have a button on the edit page that says "Lock" and a button that says "Privatize." Both buttons will ask for a password and the password will be saved for the page.

Lock

The "Lock" button will serve redirect all traffic to the /view page. Once on the /view page, clicking "Edit" will prompt a password before going to the Edit page. It will then load the Edit page as a POST request using the password as argument. If the password is wrong, it will again redirect to the /view page.

Privatize

The "Privatize" button will serve to redirect all traffic to a /login page that will then goto the view page. DIFFICULT

[schollz]

Will this remove the wiki-ness of these pages? Not sure if I want to do this, so I'm putting a wontfix on it.

[schollz]

Encryption added! e97bfb0