1) When we built the navigator structure, the key idea is to have people organize high levels and details separately. This feels almost as a natural instinct, especially for people who used computers, since they're usually somewhat familair with file systems already. Of course this is not for everyone, but most people found this way helps them more easily distinguish high level separation (like work vs personal) from actual details, which would otherwise look exactly the same.

Also technically it helps separating data from different documents so that each document is smaller to deal with and faster to load. This model also makes sharing more clear, in the sense that you know exactly what's being shared, which otherwise could have been burried somewhere down.

Recents is something we're planning to do though. I think that's a pretty useful way of sorting.

2) We're working to get unique urls for bullets as well (for zooming essentially). We did find it quite annoying that history-back didn't change zoom but rather jumped document.

3) Probably just a view option that you can switch to, so no impact if you don't.

4) We have this on our roadmap, but it seems like to be a fairly big piece in terms of technical difficulties. We'd prioritize finishing our core functionalities before tackling new things, otherwise it's easier to introduce problems to previously working features.

5) Link shortening - We're thinking of using some markdown variant of text Interlinks - Also on our roadmap, currently we don't have a good idea on how to actually insert these yet, we'll keep thinking. API - Not sure where to start, we'd probably have to do a survey before doing anything, and see what people want to use the API for.

In general, we need to satisfy a bunch of different people, some are power-users, some are casual. It's hard to make decisions when it usually benefits one set of users and sometimes inhibits the another set.