Next features

[Erik Pukinskis]

Things to work on:

Security model
----------------------
- At the moment all of the apps run within the forkolator.org domain,
so apps should be able to basically just pop up an iFrame to
forkolator.org/auth, which gets the user logged in, and stores a key
in a cookie. Then the apps can send the key along to Couchdb, which
would authenticate on a per-document basis as needed.
- Apps also need to be owned, github style, so that random people
can't just come in and change your app.

App chrome
------------------
- The only way to edit/fork apps right now is to know that you have
to go to /edit/the_app_name to do so. There probably needs to be some
sort of topbar/bottombar/page curl that gets added to pages that has
those links. We could forcibly add it to pages as they get served,
but probably the first step is just to have a javascript library that
people can choose to include in their apps that does it.

Version control
----------------------
- Right now when an app is saved, it just overwrites the file. We
also need to be checking those files into version control (git). The
next step after that is to allow people to roll back changes, fork old
versions, etc.

Social features
---------------------
- The whole point of Forkolator is to make it easier for people to
work together on code, so there should be basic social features, at
least the big few that GitHub already has... user pages, news feeds,
network, and pull requests.

Anyone who is interested in any of these, speak up, or just grab the
code (https://github.com/erikpukinskis/forko3) and start hacking!

Erik