https://learn.microsoft.com/en-us/openspecs/office_file_form...
{
"nodes":[
{"id":"6c711bf8c24c4f5b","x":-226,"y":-62,"width":400,"height":400,"type":"file","file":"testin/2022-10-14.md"},
{"id":"4dd7d04cdd0b379c","x":-530,"y":-209,"width":250,"height":60,"type":"text","text":"this is a note"}
],
"edges":[
{"id":"0c589a4d6bbb06aa","fromNode":"4dd7d04cdd0b379c","fromSide":"bottom","toNode":"6c711bf8c24c4f5b","toSide":"left"},
{"id":"eda9f3edb3ec232a","fromNode":"6c711bf8c24c4f5b","fromSide":"top","toNode":"4dd7d04cdd0b379c","toSide":"right"},
{"id":"abf404722ba48c3b","fromNode":"4dd7d04cdd0b379c","fromSide":"top","toNode":"6c711bf8c24c4f5b","toSide":"right"}
]
}
[1] https://interoperability.blob.core.windows.net/files/MS-ONE/...On the other hand, this has also caused some headaches around using it on mobile.. but so far this has been a worthwhile tradeoff. Thanks for all the hard work!
And it has 15 GB free forever, just like Google Drive.
Mega sync has native clients in MacOS, Linux, Windows, iOS, Android.
[0] https://developer.android.com/guide/topics/providers/content...
But you can always tweak settings to run the 3rd party sync app always in the baclground, and override the battery optimization setting for that particular app.
Syncing by merging changes and resolving possible conflicts is a much harder task. Theoretically git has all the right bits, including the pluggable diffing and merging. In practice, I haven't seen it seriously used in this capacity.
This is to say nothing about files you only want on one node but not on another (heavy stuff lives on server and laptop, but not mobile, etc.)
This is why special-case syncing tools that know how to sync semantically are indispensable.
What do you mean? What is preventing you from using git to sync your notes?
The thing is that you should not expect a user to explicitly host a git repo somewhere to for a grocery list app. Most apps are designed for users who are unwilling to do that, and are actually ready to pay to avoid whatever technical hurdles.
OTOH I see a niche for an app geared towards more technical users, chich would, among other things, allow you to point at a git / hg / whatever repo to use as the synchronization point.
Obsidian sells a first party syncing solution, which I hear works well:
I do git syncing on Android via termux (It works most of the time, except when git decides to shit itself every now and then on my tablet):
https://forum.obsidian.md/t/guide-using-git-to-sync-your-obs...
I can't vouch for it because I don't have any iOS devices new enough to support it, but supposedly you can use Working Copy to sync via git on iOS:
https://forum.obsidian.md/t/mobile-setting-up-ios-git-based-...
So far it has worked absolutely flawless. If I change a file it's changing on my connected device in seconds. Not exactly like working on a shared google doc but close enough that I would even use it as a hack to quickly share links between my mobile and my desktop
I don't think that's the intended use case of Sync or anything they've ever said it could be used for.
- Obsidian Sync is pretty slow.
- Obsidian Sync doesn't happen in the background, at present. That means, if you just made a bunch of updates in Obsidian, or you haven't opened the Obsidian mobile app in a while, you're in for a wait.
- Obsidian Sync occasionally has sync errors that involve manual interaction.
That said, it's fine and the overall Obsidian experience makes it worth it (well, if you can swing a discounted price).
More realistically, I used to use a custom sync setup with a WebDAV server I set up and Goodsync software. You can set it to sync in file change, and it was fast, with changes replicating in a few seconds.
As it is, the Obsidian sync takes a few minutes. And if you edit the file on another device before sync goes through, you’ll lose the changes from one device or the other.
Clearly we have had very different experiences. I have mainly markdown notes, PDFs, and screenshots and it syncs everything continuously as I work. As for "losing" the changes, I'll have to push back on that. You have full version history, so while you might have to look at an old version, you won't lose anything. There's certainly nothing unique to Obsidian with respect to conflict resolution. If version history isn't working, you'll have to talk to the developers because there's a serious bug.
This has been my biggest fear using sync. So far I haven't had any issues, but I just get a" feeling" (maybe it's the lag between syncs) that this could definitely happen.
Can you explain in a little more detail how it might actually occur? Maybe so I can prevent it from happening.
If you are transferring from desktop to mobile, make sure the .obsidian folder inside the vault is copied also
Caveat: not an obsidian user (although I am a big step closer after this)
> I am guessing this let's you set coordinates for how to lay the canvas out but this is exactly why I'd never use it.
You wouldn't like a text editor that automatically rearranges source code or sections of a document without you having a say in it, and for the same reason I find manual layout for this graph feature absolutely necessary. And beside that it's very likely you'd want some other metadata that just have no place in standard Markdown. Maybe a viable alternative would have been generating graphviz dot code and embedding it in Markdown code blocks, which would make it compatible with other tools as well - that could still be added via plugins.
Photoshop is proprietary software with a well documented file format anyone can read and write.
So is this software. "Open source" is not branding, it means something.
It's okay to make and promote and sell proprietary commercial software. That's what you are doing, be proud and clear about it. Pretending your efforts have anything to do with free software is deceptive.
Photoshop/PSD on the other hand is a closed proprietary format: https://en.wikipedia.org/wiki/Proprietary_file_format
> The Canvas format is MIT licensed in the same way that Markdown uses a BSD-type license.
In no sense are these two things comparable. "Markdown uses a BSD-type license" is a true statement because "Markdown", in the context where it makes sense to say this, is a Perl script—a program, licensed in a way that is not uncommon for open source programs to be licensed. Your canvas format is not a program. It's a 70-line TypeScript interface definition, going by your own link:
<https://github.com/obsidianmd/obsidian-api/blob/master/canva...>
To call this "open source" (let alone open source "in the same way that Markdown" is) is a very odd choice. It's less odd for anyone who recognizes that it follows a common pattern, where folks with something to sell often openwash what it is that they're selling based on the (not unfounded) perception that having it be thought of as more open than it really is tends to confer certain positive benefits. It's why Steve Jobs lied about FaceTime being an open standard, for example.
Whether or not you're giving any explicit permission to build apps, scripts, plugins, etc. is largely moot—to be frank, you don't have the power to dictate otherwise. On the other hand, if you're saying that you're aiming to steward and participate in a (hopefully) vibrant ecosystem built on a common format, then that's cool. But say what you mean, though. Calling it an open format or an open standard would be fine; "open source", however, this is not.
> Thus, “Markdown” is two things: (1) a plain text formatting syntax; and (2) a software tool, written in Perl, that converts the plain text formatting to HTML.
What we have done so far is shared an open spec for the .canvas file format, with a type definition that helps developers understand how to create properly formed Canvas files. We also are giving permission to people/companies to use this format with the freedoms that come with the MIT license. In addition we're also putting forward the intention that there should be a free and open format for this type of canvas data, with some similar properties to Markdown. Perhaps in the future there will be more open source tooling fitting into definition (2).
The goal here is simply to help people feel more comfortable that the canvas files they create are their own, and can eventually accrue longevity as more tools get built around the format. I hope this will lead to a rich ecosystem outside of Obsidian. We're committing to keeping it an open format, and hope to collaborate with other people who might want to adopt it.
The same can't be said about the PSD format, so I do think there is a difference in the level of openness that we're aiming for.
Obsidian on the other hand uses open formats with open standards. The difference is NIGHT and DAY.
And if the goal is taking freedom away from the people who are using your product, or to artificially keep people using your product because you know you are making the world a worst place to live in, making that type of propriety software is not OK, even though there are plenty of misguided organizations and people who do it.
It can borrow a few things from OneNote e.g.
- cards resize automatically with text.
- OneNote starts with a cursor, clicking anywhere on canvas and writing is a single click operation.
- There are no hard borders around cards in OneNote.
- OneNote is WYSIWYG which this canvas isn't currently.
This is not a definitive list and I know its too early to ask for new features and stuff. Good things to consider IMO.
Not that this should impact Obsidian much, since I assume the canvas thing is optional there, just a data point.
Related to infinite canvas _do_ checkout “The Humane Environment” [1] it has a few interesting takes
As for a more semantic approach to layouting, I think Flying Logic[2] makes a decent job of it
[1] https://www.goodreads.com/en/book/show/344726.The_Humane_Int...
If I sign up for the Sync or Publish plans, do I still need to pay $50 per year to use it at work? Or is that included?
Make a private repo, and git commit / push / pull your obsidian notes and canvases just like you would any other shared repo
I know the plugin, but it seems to work only for Github hosted repos. I want my notes to be elsewhere.
That's against their license. You're essentially pirating it.
The MIT license is a license about copyrighted software, allowing people to use/modify/publish that software. But a file format isn't a piece of software.
Are you open-sourcing the specification document for the file format? (people are still free to write software that reads+writes the file format even if the specification document isn't open-sourced).
Are you open-sourcing your particular library for reading the file format? (I'm confused here, because you stressed that the file format was so simple, so I'd have expected it easy and maybe even desirable for many people to come up with libraries for reading+writing the file foramt?)
Anyone is free to write software that modifies a file - there is no copyright law protecting that. This is one of the reasons why many large corporations are pushing hard towards cloud - they can protect the format AND the platform then monetize it at will. End users lose control.
I will give them points for putting it in a readable file format. But placing it under an MIT license and "open sourcing" it, doesn't do anything - and they know that. It's just fluff to market their new features.
Edit: Re-reading what I posted, In case it's taken the wrong way, I am not disparaging the team at Obsidian in any way:
I think they do good work and make great software.
IANAL
> The file itself is considered instead to be an idea or a system and is therefore not protected by the laws of copyright. So the description of a file format is copyrightable, but the format as it exists in its medium is not.
So? The actual tool is closed source.
For all we know all your cute notes app is backdoored for CCP.
Does this look OK? https://i.postimg.cc/4ymyHWxF/window-border.png
https://github.com/obsidianmd/obsidian-api/blob/master/canva...
Just like all other files in Obsidian, canvas files are your own and local to your device. You're still linking to your own Markdown files which are just as future-proof as ever.
We decided to create the .canvas format because there wasn't any pre-existing canvas-type format we could find that fit our priorities around longevity, readability, interoperability and extensibility.
The .canvas format is designed to be as easy to parse as possible. We've already seen a few plugins take advantage of it, and we hope that more tools will become available that can use the .canvas format.