1. The backend is graphql/django/postgres and yes, the notes are currently being preserved indefinitely. At some point I might add a cron job to remove the empty ones
2. I'm thinking of adding a notebook option eventually, but still considering the best way of doing this in terms of not compromising the current look and feel, which I like the simplicity of
3. for these three points - the markdown editor itself is an open source solution () and not my own creation, so these issues are limitations of this library. I may fork it and make some fixes at a later date, although some of these issues may be fixable with simple css
4. good point, i'll try to implement some kind of a lock here
1. I don't see details of retention anywhere, are you just storing indefinitely at the moment?
2. No sign-up is nice, but have you considered even just using cookies for 'my past notes'?
3a. ```Code blocks``` render as `inline code` in editing mode, which looks worse than not doing any 'preview' of them in edit mode at all IMO.
3b. ```lang hints (in the manner of Github flavour) are ignored, though some syntax highlighting is done with or without them.
3bi. This seems to mean that keywords from other languages are highlighted as if a keyword in the language used.
3bii. The syntax highlighting colour scheme used is not very colour-blind friendly.
4. Two users (uh, tabs) can concurrently edit, but each others' edits are not seen until refresh; so last to stop typing (=> save) wins.