2/ Example one: Project Xanadu (Structuring data, bidirectional links) first hypertext project in 1960 by @TheTedNelson
+ nonsequential writing (writing with block refs, no folders)
+ zippered lists (Roam Multiplayer)
+ tumblers: any part of a file to be referenced (Block UID)
3/ Example two: (1960's, 70's) Graph databases (Roam under the hood)
+ Nodes (Blocks)
+ Edges (Bidirectional links/block refs)
+ Properties (Creation/edit dates, user, block characteristics: open, closed, heading)
4/ Why now? If so many concepts were already previously explored, why is there such a strong movement today for them? To summarize a complicated subject, I give two reasons:
REASON 1) Every day users are finally ready for these advanced (but intuitive) concepts, not just us geeks
5/ REASON 2) Foundation technologies needed are finally in place. (Ex: infinite processing & storage, timeless db's, structural sharing). Geek out on @richhickey lecture -don't watch for Datomic, watch to understand how the way we think of data has changed
6/ The problems we want solved looks simple on the surface, but there are a lot of problems Roam is solving for us & will solve.
What do you think: Can we learn from the past? Is it time to bring these ideas into the present and beyond?
This is the journey (Roam) we are on.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ @Conaw thank you for giving Roam42 a try, its a work in progress.
I want to turn this around on you though & say we are really thankful to @RoamResearch for supporting community, giving us tools, encouragement & freedom to mod Roam. #roamcult
2/ I became a believer the day you announced roam/js. For those not in development, it probably wasn't clear what signal this sent. I have used many tools, but never seen a company so genuinely engage with public & make such an early commitment to devs (that wasn't lip service).
3/ I don't know everyone in the Roam Research team, but have enjoyed all my interactions so far with the few I have met: @thepericulum, @MamanLunettes, @filipematossilv. Always helpful & supportive, never judging. A testimony of good things to come.
This is a tweetstorm mostly for new users of Roam, but something I take to heart as an experienced Roam user (Experience in Roam? Not sure what that means, we are all Roam babies).
[[2/19]] Roam is a very powerful tool. Roam is feature rich & has MANY MANY hidden gems. Because of a lack of documentation & onboarding many users barely scratch the surface of Roam's potential. This will improve. Team RR has this on their radar.
[[3/19]] Roam requires time, practice & experience to master. There is a tendency at the start for the perfect system, to understand it all in depth before we really engage in using it. But this is not the right approach. With Roam, JUST START & use it as much as possible.
Beautifully composed visual explanation to Zettelkasten from @e_thomas_v. Lots of insights. Only 11 minutes. Many best practice concepts from Zettelkasten that can be mapped to Roam, without having to do Zettelkasten.
Zettelkasten - Position of the note in the slipbox is not important
Roam: don't worry too much about a top down structure. Just make sure to create references (tags, page links) to other notes, or providing context of the current note
Zettelkasten - Quality comes from the network of links between notes, not necessarily the content of the note.
Roam: Big picture is to insure unexpected insights through the network. We don't know yet what we don't know, just know that you don't know & eventually you will know.