Forum Posts Feed
"Roam Research" -- New web-based personal wiki
< Next Topic | Back to topic list | Previous Topic >
Pages: ‹ First < 5 6 7 8 9 10 11 12 >
Posted by Dr Andus
Mar 14, 2020 at 03:03 PM
“Rudimentary Roam replica with Org-mode”
https://github.com/jethrokuan/org-roam/
Looks very cool, I’d love to have something like this but I can’t see myself going into the trouble of learning Org-mode etc., as I just haven’t got the time…
Posted by Luhmann
Mar 17, 2020 at 02:10 AM
I finally tried Roam and am really impressed. What I really love is that you don’t have to move items to file them away. This is a big problem with outliners and task managers, where you constantly have to monitor and sort your inbox. Roam’s ability to generate pages related to any keyword or tag means that you can move something just by tagging, while it still remains in its original location. This is important because items always remain their context: whether that context was a document you were reading, a journal entry, meeting notes, whatever. And it shows you that context as well as the linked text. For me this is the real genius of it all - the way context is preserved. If I tag a quote from a book, when I look at the page for that tag I’ll see the title page for that item which is the name of that book. So not only do I not have to move my quote from the book page to a new page of selected quotes related to the topic and then copy all the meta data over as well, I can just add the tag and see the item on the new page along with the metadata! It is really a much better way of doing things. It basically is a zettelkasten without having to do all the annoying work that makes it impossible for most people to maintain a zettelkasten.
Right now the biggest problem for me is that the mobile version of the app doesn’t work well on the iPhone’s mobile safari web browser. (I couldn’t delete a node, I couldn’t upload a photo, the page always defaults to a quick entry screen instead of the page I was last using, etc.) But if that were all to be fixed, I could really see myself jumping ship and moving a lot of my Dynalist data (or all of it?) over to Roam. Right now though, Dynalist remains a much more polished product. Their mobile app is not great, but compared to Roam it is far superior. Also, Dynalist’s sharing interface is much more advanced which makes it better for collaborative projects or just making individual outlines public. I’m glad to see the active discussion of Roam on the Dynalist forums and I hope they can figure out a way to capture some of what makes Roam so revolutionary.
Roam is so different from anything else it really takes some time to explore, but I really think it is a new paradigm. I look forward to not only seeing it develop, but also seeing how other developers get inspired by this approach. It would be great to see something like VoodooPad be developed which could bring Roam’s approach to a native app for Mac and iOS. This would allow for more secure data storage, offline access, and tighter integration with other apps…
Posted by Nomatica
Mar 17, 2020 at 08:09 PM
Edu Nv wrote:
TiddlyBlink sounds very interesting! My biggest issue with RoamResearch
>is that it doesn’t have offline access or local sync. I always thought
>TiddlyWiki is an open source ancestor to RoamResearch with similar
>capacities plus offline access. Where RoamResearch is different, and
>more optimised than TiddlyWiki is in the database backend, which is a
>graph database. I presume that once the databse starts getting really
>big, performance would be much better in RoamResearch.
Have you tried to use tiddlywiki for anything large? I have barely explored it, but it has quite a following. I am curious if people have used it for large projects and how it has responded to the growth.
>
>Nomatica, have you tried TiddlyMap? You could install it as a plug-in to
>your TiddlyBlink (or any TiddlyWiki) and you’d also get the graph
>visualisation. In live view you can see all the tiddlers that link to
>your selected tiddler, like Roam’s graph visualisations. In addition,
>you can create and save custom views to focus on some
>relations/connections that you can then embed into other tiddlers. It’s
>very flexible, with a very sleek infinite zoom.
>
>Thanks for sharing your TiddlyWiki adaptation!
>
I am familiar with TiddlyMap, but have not explored it. The whole tiddly ecosystem seems very interesting.
It is not my adaptation. I was posting quickly and decided to copy text from the TiddlyBlink’s website to help provide some context. While that might have been helpful. It also makes it look like I was the creator. I am not. Just a fan. Sorry for the confusion.
>Nomatica wrote:
>>TiddlyBlink is an adaptation of TiddlyWiki with
>>the goal of helping you see connections between your ideas, and move
>>quickly from one idea to another. It was inspired by the bi-directional
>>linking found in Roam (https://roamresearch.com/), but built with
>>capabilities already available in TiddlyWiki (https://tiddlywiki.com).
>
Posted by Edu Nv
Mar 18, 2020 at 02:00 PM
Thanks, Nomatica, for the clarification.
I haven’t used TiddlyWiki with a very large collection. It handles 2000 tiddlers without any problem, but I have no idea how it would be with hundreds of thousands of tiddlers for example. Since everything is contained in a single html file, I anticipate it would hit performance issues sooner than Roam’s graph database backend. On the other hand, having everything on a portable html file makes it very durable and accessible.
Posted by Chris Thompson
Mar 18, 2020 at 02:17 PM
TiddlyWiki is no longer limited to a single HTML file, though you can still run it that way. These days it seems to be more common to run it in a configuration where each tiddler is stored as an individual file.
—Chris
Edu Nv wrote:
Thanks, Nomatica, for the clarification.
>
>I haven’t used TiddlyWiki with a very large collection. It handles 2000
>tiddlers without any problem, but I have no idea how it would be with
>hundreds of thousands of tiddlers for example. Since everything is
>contained in a single html file, I anticipate it would hit performance
>issues sooner than Roam’s graph database backend. On the other hand,
>having everything on a portable html file makes it very durable and
>accessible.