Notes:

currently comment blocks have ids and follow the same pattern as documents. so linking to a comment block should work the same:

hm://<ACCOUNT_ID>/<TSID>#BLOCK_ID[start:end]

With this URL we should be able to resolve the comment and only show the particular comment, or range.

the entity id function must comply with this, although I believe they already do it.

embeds should also know how to resolve this. we might need a different design for comment block embeds or not? @Gabo H Beaumont @Untitled Contact

selecting the comment block currently is all working only on documents. and we can make it work on comments. the issue is that the code that construct the copied link needs to know the comment URL that its being clicked to create the correct URL.

we might also need to add a hover state to comment blocks so the hovercard makes sense when appears. I believe we might need to change how users create this links, because the hover buttons do not work super well. and sometimes we get double buttons appear and is confusing.

we also need to support get the mentions for a particular comment block, the same way we do for document blocks @Untitled Contact @Untitled Contact . we need this because this way we can list all comments or citations of a particular comment/comment section. This is related to listEntityMentions vs ListEvents

[NICE TO HAVE]: it would be nice to also consolidate both discussion panel codebases into one. now that we have a comments service we can merge those two and just use one commenting code to render the discussions, and the focused panels (block focus and comment focus).