Updates intro to Obsidian

This commit is contained in:
Marcin Czenko 2025-05-13 02:51:05 +02:00
parent 7c4f3517f9
commit 94a3a4a403
No known key found for this signature in database
GPG Key ID: 33DEA0C8E30937C0
2 changed files with 5 additions and 1 deletions

View File

@ -1,6 +1,10 @@
Here a short intro to Obsidian and *Personal Knowledge Management Systems*.
I currently, document some of the Codex/BitTorrent stuff in the vault you already can use to see how does it feel for you. The vault is available on GitHub: [https://github.com/codex-storage/bittorrent-codex-docs](https://github.com/codex-storage/bittorrent-codex-docs). You can just clone the rero, and open the cloned folder in Obsidian. That's it. This is you local copy - anything you do is only visible to you. GitHub is used for a more controlled syncing. Normally, when you work on your own content, you will put your vault on some shared network drive (end-to-end encrypted of course! :yum: ), and then you can conveniently open it on any other device. Syncing is done by the network drive, Obsidian has nothing to do with it in this case. You content keeps the same structure (including folders) as you see it in your local (shared) folder - thus, everything is transparent and extremely portable. Myself, I have a paid subscription to Obsidian Sync service (not that I really need it, but I wanted to try it and to support the Obsidian team a bit). It costs me $96,00 per year (see the picture). Obsidian also provides publishing service, which I use for our Codex/BitTorrent documentation and which costs me around $10,- monthly: here you can see how it looks like: [https://publish.obsidian.md/bittorrent](https://publish.obsidian.md/bittorrent). You can also just as easily create an empty vault to play with the settings and plugin. The BitTorrent vault has some basic set of plugins included. For a more active collaborative vault, perhaps using Obsidian Sync and then try to [Collaborate on a shared vault](https://help.obsidian.md/sync/collaborate). It requires a paid subscription, but perhaps $96,- per user per year will not break the bank (limit is 20 users currently). Paid Sync service also includes versioning of the content.
I currently, document some of the Codex/BitTorrent stuff in the vault you already can use to see how does it feel for you. The vault is available on GitHub: [https://github.com/codex-storage/bittorrent-codex-docs](https://github.com/codex-storage/bittorrent-codex-docs). You can just clone the rero, and open the cloned folder in Obsidian. That's it. This is you local copy - anything you do is only visible to you. GitHub is used for a more controlled syncing. Normally, when you work on your own content, you will put your vault on some shared network drive (end-to-end encrypted of course! :yum: ), and then you can conveniently open it on any other device. Syncing is done by the network drive, Obsidian has nothing to do with it in this case. You content keeps the same structure (including folders) as you see it in your local (shared) folder - thus, everything is transparent and extremely portable. Myself, I have a paid subscription to Obsidian Sync service (not that I really need it, but I wanted to try it and to support the Obsidian team a bit). It costs me $96,00 per year:
![[Pasted image 20250513024925.png]]
Obsidian also provides publishing service, which I use for our Codex/BitTorrent documentation and which costs me around $10,- monthly: here you can see how it looks like: [https://publish.obsidian.md/bittorrent](https://publish.obsidian.md/bittorrent). You can also just as easily create an empty vault to play with the settings and plugin. The BitTorrent vault has some basic set of plugins included. For a more active collaborative vault, perhaps using Obsidian Sync and then try to [Collaborate on a shared vault](https://help.obsidian.md/sync/collaborate). It requires a paid subscription, but perhaps $96,- per user per year will not break the bank (limit is 20 users currently). Paid Sync service also includes versioning of the content.
### Personal Knowledge Management Systems

Binary file not shown.

After

Width:  |  Height:  |  Size: 89 KiB