Pageforest UI is getting closer. The dialog box is flying in from the right and is draggable (with PF script - not using jQuery to minimize impact on host application pages).

Sung did this floating dialog box design for me for PageForest - I just worked out the HTML/CSS implementation today. It's not yet "integrated" into PageForest but this was a big hurdle to get to this point.

I slapped a jQueryUI draggable method on it so you can move the box around the page.

Here's a sample PageForest application. I just implemented the "app bar" at the top of the page. The Save command does work (though you get wonky input boxes to enter a username and password).

The 1,000 blocks application is basically working too - just needs some UI tweaking.

A Wordle visualization of my "todo" list for pageforest...just for fun

Just a nice photo (could use in our slide puzzle application for pageforest).

I'm building a PageForest application based on this art piece called "1,000 Blocks" at the Seattle Art Museum.

Sample PageForest app, inspired by a physical block table at the Seattle Art Museum.

The protocol I use in PageForest is essentially challenge/response. It is susceptible to (online) dictionary attacks (intruder tries all possible passwords) - but I could de-activate accounts after a small number of authentication failures.

Evesdropping does no good if per-request authentication is used (the high-secure mode of the pageforest protocol).

If the server is compromised, the secret keys will be disclosed (not plaintext passwords, but hashes H(user, pass)).

It seems to me this paper compares itself to the paper tiger of really poor plaintext protocols and storage. I wish they would have analyzed other good (non PK) systems like the one I'm using.

Quoted: The Secure Remote Password Protocol