Note history or blame log

[jackycute]

To review note changes and revert.
It's necessary to have change history or blame log.

[janniklorenz]

What about saving every delta in the persistent database? So we can go back to every state.

The size shouldn't be a problem, it shure courses an overheat, but also big advantages.

[jackycute]

Do you have any experience of the persistent database?
Can you explain a little bit? I'm not quite familiar with them.

And I've been very busy for previous two months, but I'm back now 😄

[jackycute]

I think ProseMirror (by the same author of CodeMirror) might help this.
http://prosemirror.net/demo_track.html

[jackycute]

Note history (revision) supported in dbc126b

[almereyda]

For a quick improvisation of an annotation and discussion layer with the help of hypothes.is, versioned static URIs allowed for integrating their client. Unfortunately from the revisions menu it is not obvious if each have a content-addresable hash or UUID et al. associated. I would like to be able to visit a https://hackmd.instance/s/`UUID`/ URI to annotate quick and dirty.

• dbc126b#diff-f808d078baf2f737acae5485915be4daR7

---

lastContent then probably only ends up to be a pointer to the previous revision id, as the previous pointers in git #114 or other Merkle-DAGs like #175.

[jackycute]

@almereyda Thanks for giving this idea, it looks great.
There isn't any way to access certain revision in publish page, they all in json for now.
But this seems a possible approach though.

[Himura2la]

When should we expect this feature to appear on the main website? Our team started using hackmd and we consider the absence of authors not convenient

[jackycute]

Hi @Himura2la, We already provide note revisions which is in the "Menu" -> "Revision".

This issue is left for blame log and other related todos.

[Himura2la]

I see the revisions, but there is no authors of each revision. I thought this ticket is about authors

[jackycute]

No, that's another issue #312

[ccoenen]

related to #443 and #123