Currently we embed the User object into the MediaEntry field. Bad, bad bad! This means all sorts of terrible things, but especially that we'll be keeping potentially out of date information. We should be referencing it instead.

See: https://groups.google.com/group/mongokit/browse_thread/thread/50c0c9ab4a313010

It looks like the indexes feature in mongokit is acknowledged as not well implemented for production. We should figure out a nice way of doing this ourselves, possibly via a command to ./bin/gmg and then adding / removing indexes later via migrations?

Alternately we could keep some value in the database about whether indexes have ever been set up, and if not, set up the current indexes, and then handle all subsequent ones via migrations? We don't want it to be hard to have new users have migrations from the get-go without having to run an extra command, maybe.

Asheesh Laroia has rightly pointed out that talking about "owning your own data" is misleading, esp if extrapolating free culture from free software, "data shouldn't have owners". Think of better phrasing, update http://mediagoblin.org/about/

"Also, people should be able to own their data." to something nicer.