Thread by @RoamFm

ALT+D
[[@[[@Conaw]]]]
- [[Conor Priority List]] #Hmmm
- We gotta think about messaging guys
- That's some useful shit [[Network]]

https://twitter.com/Conaw/status/1400606581407076352

Relevant cc @mayfer

https://twitter.com/patio11/status/1400466955690078211?s=20

To be fair, I know @Conaw is already thinking about networks and messaging anyway - we have to overhaul that if we want comms in a knowledge graph context

For example, if you manipulate the global filter feature to only feature blocks directed at you (author) via notation = DM?

Assuming I want to go to my collab graph and see a private message, feels like it needs a notation so I can recognize it's private from a first glance
And a CSS to note that it's different (OR a namespace?)

Then it's designed as a page, with linkrefs, the big one is notifs

If we have [[roam/notif]], and that filters to only the account, maybe that's some level of privatization?

It's like, author-only [[roam/comments]], surfaces up on DNP, and it contains all mentioned/important activity INCL comments

So communication is not as mesages but blocks

Would be cool though...if I write a block and I want to /mention -> pop up list of authors on graph with small search bar, type name -> notation gets typed down -> block gets ref'd to DNP, parent block notifies destination author, anything nested doesn't overwhelm with notifs

I also like how I've stopped thinking about comms in a graph, but rather attributes of the DNP to surface up types of blocks when necessity, makes each piece of information (whether insight, comment, or DM) more atomic and equal

Maybe all we need is a UI implement for DNP