1/ There is a lot of talk about roam/js and security concerns. Frankly, these issues exist from the first day Roam introduced roam/js. It boils down to trust. Do you trust the plugin author or not? There are some very good plugin authors who deserve your trust. #roam
2/ One of them is @dvargas92495, founder of roamjs.com. What many don't know is that Dave and I have collaborated since last summer. While we have gone different paths, we frequently talk about Roam and how to solve problems. I have always valued his advice.
3/ Dave is a very experienced software dev with an amazing vision for developing & supporting open source. His roamjs.com site focuses on Roam & is a living proof his concept works. https://t.co/qiZcl2mG3K is the biggest and most complete collection of roam plugins.
4/ He has developed a wide range of tools that solve specific requests of Roam users. It is hard to pick favorites, because there are so many good tools: attribute tables, filter embeds, mindmap, presentation, query builder & serendipity. Oh, I just scratched the surface.
5/ All these extensions are available for free and as open source for you to extend. Regarding trust, I have been through the code. What I see is solid engineering practices, good use of third party resources, and code that I trust.
6/ David sets development priorities based on community feedback and funding. He doesn't ask for much, and gives a lot. You can help with a small contribution and influence the direction of his work at roamjs.com/queue.
7/ Additionally he has started to branch out into commercial services that provide real value add to the roam experience. roamjs.com/services
8/ Bottom line, running external code is a risk and requires a lot of trust. Dave has been at this since August of last year and there isn't even one recorded incident of foul play. This is benefit of open source. Everything is available for review.
9/ But the real value is that David's DM is open on twitter & he is active on slack. I have seen him many times spend hours with users solve issues. Additionally, he is quick to fix bugs (usually within hours of being reported). He takes responsibility for his work.
10/ I use roamjs.com services, I have audited his code, and worked with him. I trust him and have no issue recommending him to you. Visit https://t.co/qiZcl2mG3K and give some of his plugins a trial run. If you have concerns, reach out to David directly.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Since last summer I have been intrigued by this quasi-no roadmap concept from Roam. But now almost a year later, I actually don't think it's a good strategy. @Conaw maybe now is a good time to lay out a plan with the public and timelines.
I see value in the "no roadmap" approach during prototyping & beta, but as the product matures & tackles larger problems, people want to understand what they are investing in. People using a product is an investment. Is the bank going go grow their money, or gain little interest?
Without a roadmap that outlines general goals, how can a team set priorities? how can they design for the future? Databases for example cannot be easily changed, especially when it comes to security, performance and optimized search.
1/ Roam announced local graphs are available to all Roam customers & many ask for best practices advice. Here are some recommendations. Thanks for help: @elaptics@zsviczian
2/ What is a local graph? It is a Roam database that you create on your computer in a browser. That database lives only on that computer & only in that browser. The data in your local graph is never transmitted to Roam's servers. Theoretically you can have unlimited local graphs.
3/ In fact, if you create a local graph on your computer in Chrome, and then on the same computer you open FireFox, FireFox can't see that local graph because that graph lives in the permanent cache of Chrome and is only visible there.
2/ When I saw this I thought "information overload", if he is trying to sell @obsdmd, he isn't helping." I was wrong again! As I say, always learning from community. I love the sidebar.
but always felt it would be useful to have more freedom.
3/ I wrote some code that "detached" sidebar window panes so I could move them and dock them into other places. It looked great and I could see value in it. However, this was a real hack and destabilized Roam. Not Roam's fault, I was "surgically repositioning their right arm".
1/ EMOTIONS & NOTES? One thing that fascinates me about Tools for Thought (@RoamResearch, @obsdmd, @rem_note & @logseq) are the deep emotional connections people make with these tools. But it isn't about the tool, it's about the "thoughts" captured in these tools!
2/ When I started using these tools, I thought people used them because of their features & that really one tool was likely better than another. The truth is they each have advantages. Let me list what I see:
+ Roam: Great graph DB outliner with strong linking
..cont'd
3/
+ Obsidian: Great Markdown editor designed for thought, leveraging speed of local hardware
+ Remnote: integrating spaced learning into its DNA with roots in education
+ Logseq: opensource tool based on graph DB & markdown. Totally unique hybrid that has a solid future.
1/ Over a year ago I tried out Obsidian. At the time I found it to just be another Markdown editor. I was actually frustrated with the @obsdmd devs because it seemed like a shift from @DynalistHQ which is a fabulous product, but needing love. Well I was wrong, they were right
2/ In recent months I have seen many dear friends move to @obsdmd from @NotionHQ, @RoamResearch and other such tools. I honestly thought they are crazy (Ok they are and they know it.) But they are so happy with Obsidian and brag about it like teenagers in love, it is irritating.
3/ But I have to say, these friends, some former Roamans, are really good, smart, hard working and caring people. I told myself, there must be something to @obsidian if these individuals are so happy. They know me, I know them. They would not waste my time.