1/ I submitted my 1st plugin to Obsidian for review. The process is nice. Not only is the dev experience good & support via the forums helpful, but the process of submitting a plugin makes you feel confident in @obsdmd leadership.
Here is the feedback I got with needed fixes
2/ You develop your plugin and then you submit it to review. Obsidian tests the plugin and then does a code review. The review is looking for a number of things that will improve the quality, reliability and secure usage of the plugin.
3/ First they make sure you are consistent with their User Interface features. This makes sure the user experience is standardized.
4/ The review the use of their object model. In the feedback I got, the adjustments will improve the reliability because I am using the right approach, and I think performance might even be better.
5/ Security - I know they are also looking at anything that might be dangerous for the user. While it is not a hardcore security audit, it is solid.
6/ I also received general feedback on how to improve the code, which is very welcome (code review by peers or the product developers is gold!)
7/ All and all, a great experience!
It just makes me feel more confident that I am investing in the future of a product moving forward.
PKM is an investment in future self, we need our tools to be future proof. I am very pleased about what I see in Obsidian's future.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ Hi folks, today I changed my twitter handle to @TfTHacker. Basically using Roam less than other tools and my bias is toward being tool neutral. So going to be discussing many tools and their benefits and not just Roam, also @obsdmd, @rem_note, @logseq.
2/ For those who have followed me because of Roam, I won’t be offended if you unfollow. Though I intend to continue to tweet on Tools for thought and PKM, including Roam. Someone has to keep them honest - assignment accepted.
3/ In my book, Roam is 2020, lots of other options out there worth exploring as they are delivering features we need today not some focus on 2060 or 2070 (40 or 50 year vision?)
I live in reality, your welcome to join me if you like.
Obsidian Mobile is not some watered-down afterthought gesture to Mobile, but a strong mobile app. In my personal experience, 95% of what I can do on the desktop I can do in mobile, including using all my plugins.
Mobile works great on mobile phone and tablet (iOS and Android)
The Sync service is amazing. It is $40 USD a year. It includes sync up to 5 vaults, all with a 4GB storage. Which is very good for markdown files, PDFs, images and such.
The sync service syncs not just documents, but all your custom CSS, plugins, hotkeys and other settings.
The idea of a digital dashboard is like the dashboard in your vehicle. It is a display of all relevant data related to driving (Vehicle speed, distance travelled, fuel status, possible engine issues).
With a quick glance you get all this information and you can focus on driving.
This would be relevant in the digital realm, a dashboard of indicators and statuses that help you get to your destination, focus your energies & avoid problems.
Today, while there are digital dashboard technologies out there, it seems their promised future has gone unfulfilled.
Over two months ago I released workBench (wB), part of roam42, now maintained by @dvargas92495. A while back I promised @cortexfutura that I would explain a little of my motivation behind it. It is an amazing tool to help you work with your graph as it grows.
workBench is complex since it is keyboard driven. We learn quicker when something visual & we use the mouse. But it is more about working with the unseen than the seen. I can’t emphasize enough that if you spend a few hours with it, it will benefit you.
In summary, wB allows you to work with parts of your graph that are not currently visible. Example 1: you are working on a block & want to move it or block ref it to another point of your graph not currently visible. Without leaving your current context, wB allows you to do this.
This requires a few tweets to answer. I do trust cloud services. You can use @Tresorit which is zero trust e2e encryption. @obsdmd also has a service called “Obsidian Sync” which allows for cloud based zero trust (you provide your own encryption key).
Of course using any program on a local computer requires a level of trust with the vendor. This is true just using Windows, or Mac OS. So I trust @obsdmd, especially on the foundation of their openness and approachability.
Plugins are not necessary to use. But I do use a few. Of course as a JS dev, I can audit the code myself, but not everyone can do that. however the obsidian model currently is “safer” (not guaranteed safe). Why do I say that?