21–30 of 157 posts
What's wrong with using Dropbox or Github?
I had to shell out for another app[0] on the iPhone to allow for a fairly seamless GitHub workflow. Not sure if it’s changed in recent times. It works great, but I’d imagine something more tightly coupled with obsidian.md would eliminate that need? 0: https://workingcopy.app/
Should note I use Obsidian for a journal, so it's pretty much append-only.
FWIW - the sync service provided by Obsidian is really worth paying for. Dropbox / Github just aren't as slick and integrated. The mobile app doesn't work without sync (not without some really nasty workarounds), the option to "view sync version history", the fact that it's rock solid... all worth paying for IMO.
$8/month is a bit steep, but I snatched $5/month early bird pricing and I consider that to be a lot more acceptable of a price.
Edit: worth pointing out there's a 40% discount for non-profits and students: https://help.obsidian.md/Licenses+and+payment/Education+and+...
Reverse engineering is fine. It certainly is from a moral point of view, and also from a legal one in a lot of jurisdictions.
TOS depend more on the fact that you’ll behave than on whether they can actually be enforced (most have unenforceable clauses).
You're prob not violating ToS since you're not doing it for commercial use, and you're actually reinventing the wheel as a couple of options for that are already available as community plugins. I've been using Remote-save for a while with a almost free private S3 bucket and encryption to sync between my computers and phone for a while. https://github.com/remotely-save/remotely-save It supports more than just S3 (as i…
I want a durable way to edit, sync, and preserve my notes, not just a pretty interface.
I'm happy to pay Obsidian for sync, but if they PM this to only one distribution channel and subsequently enshittify it, I don't want it. Stopping acheong08 would be a bad signal forewarning what's to come.
Syncthing actually works pretty well when you have a tool that automatically resolves sync conflicts: https://discuss.logseq.com/t/automatically-merge-syncthing-c...
i use https://github.com/vrtmrz/obsidian-livesync and self-host a couchdb instance for it... this looks like it might be a bit cleaner once it's all fleshed out...
First time I heard about CouchDB was many years ago. I bought an O’Reilly book about it, even. At the time MongoDB was gaining a lot of traction, and I think because of that many people overlooked CouchDB.
I recently remembered CouchDB because I have some projects that could potentially benefit from replication between multiple machines. And in the case of my projects I think the database level would be an appropriate place to do replication. Hence CouchDB is an interesting proposition for my projects.
I installed CouchDB on my laptop for the first time in ages, and started inserting documents into it with a third party library for Rust. So far it is working nicely.
Obsidian is not able to open a local folder on my machine stored in Windows Subsystem for Linux, which for me makes it a non-starter (my personal knowledge base is stored there).
I personally prefer the Notion UI but hate being locked into their cloud, so I created an offline-first Notion alternative [1]. Offline mode is totally free (no user registration required), and aiming to add cloud syncing tomorrow or so. Still in active dev so needs a lot of work, but wondering whether others might find this useful. Goal is to make it be able to seamlessly sync across multiple data sources, and also easily to publish files/folders (eg. can currently turn folders into APIs when synced to cloud).
What's wrong with using Dropbox or Github?
> I'm probably violating the TOS, and I'm sorry. Reverse engineering is fine. It certainly is from a moral point of view, and also from a legal one in a lot of jurisdictions. TOS depend more on the fact that you’ll behave than on whether they can actually be enforced (most have unenforceable clauses).
> Reverse engineering is fine...from a legal [perspective] in a lot of jurisdictions
Sorry, what jurisdiction permits one to violate a contract against reverse-engineering?
This is a pretty big problem that can't be hand-waved away. Companies everywhere have mere copyright on some materials that they make available if you agree e.g., not to reverse-engineer the interface or distribute the materials, essentially hoisting copyright to contract. This is how Java has worked for decades.
> Reverse engineering is fine. It certainly is from a moral point of view
In this case, the server is how Obsidian funds their work, offering free and paid parts. They're clear about it up front; they don't entice you and switch terms after you're committed. So how is it morally justifiable in this case?
> most have unenforceable clauses
The "enforcement" is not that they win their case, but the threat that they can take you to court and force you to pay a lot of money to escape the contract, especially in cases where you have significant investments or income. Unless you're dedicated to being so irrelevantly small that no one cares, why waste time building IP you can't benefit from, or telling the world that you don't care?
For people starting out, I would recommend picking viable projects, i.e., relevant to others, not illegal, not on dying technologies. They can exemplify not only your skills but also your judgment, and introduce you to the whole lifecycle of OS development if they have any legs.
And it may be best to find an unoccupied niche; in this case, there are alternatives already (better to invent than re-invent). (Unless you aspire to being a giant-killer :)
That's in part why the standard young-entrepreneur pattern is to pick new applications of emerging technologies, particularly those that irreversibly disrupt old industries or build new markets.
In this case there are many note-taking applications with syncing server. The unique project today e.g., might be to update an existing sync alternative to maintain a semantic model and then publish semantic cross-references, or publish a results of AI queries over the evolving set of highly-trafficked semantic topics.