[Feature request] Nextcloud app for syncing metadata

[NoMoreNicksLeft]

When I view the md files that Joplin creates on NC, it is appending metadata to each (no doubt to make syncing work well). Would it be possible to create a basic Nextcloud app that would instead store this metadata on the backend db? If the NC app wasn't installed, defaulting to the current behavior would make sense.

PS Thank you. This is by far the best of the many notes apps I've checked out. Nothing else syncs very well with Nextcloud, very little even offers that.

[laurent22]

That wouldn't work actually. Joplin synchronises with file systems using an open format however it doesn't mean the sync files are meant to be user-editable. The format is designed to be performant and reliable, not user friendly (it cannot be both), and that won't be changed. Joplin sync directory is basically just a database.

What might be done at some point thought is some kind of web client, either on Nextcloud or elsewhere, that would provide a UI to view and edit the data in a synced directory.

[bmaehr]

Sorry, but I dont't understand why this ticket was closed.

Joplin synchronises with file systems using an open format

Unfortunately Joplin doesn't store the metadata in the .md file according to the (most common) open format https://blog.github.com/2013-09-27-viewing-yaml-metadata-in-your-documents/

The format is designed to be performant and reliable, not user friendly (it cannot be both)

There is no reason, why a guid as filename shoud be more reliable or performant than a readable filename.
And structuring the notes according to notebooks into subfolders instead of keeping them all in one perhaps makes synchronization a little bit slower. But who cares? If really a superfast sync is important, this can be made as user selectable option.

and that won't be changed. Joplin sync directory is basically just a database.

So in fact you are writing a proprietary software, not caring about connections to other systems, applications or standards. Opensource at its best...

I'm responding to this issue because I would be interested to implement the necessary changes to fix the mentioned issues with sync to nextcloud/WebDAV/filesystem/... but of course only if the changes will be included into joplin and not if it will stay another useless fork of opensource.

[foxmask]

If nothing suit your needs , you could see another project or make your own one with everything you'd like to see implemented.

[Wdavery]

I'd have to agree with the above comments, it's disappointing to see an open-source project unwilling to make changes to be more compatible, future-proof, and open.

Human readable file names would not perform any differently. I would expect notebooks being stored as folders would slow down syncing slightly, but it's in the nature of openness and usability.

I highly doubt anyone looking for an open source notes application would care about a slight degradation in sync speed, to allow them more flexibility in editors and future systems.

That's exactly why so many people choose Nextcloud over Seafile for file syncing. Seafile is faster, but Nextcloud keeps files in their original structure.

I believe you should give it a serious second look (or fourth look, with all these duplicate issues) because I truly think Joplin could become the de facto notes app for the self hosted community.

[PackElend]

the idea is to make the new API or a port of the web companion a project in the GSoC season next year, if Joplin gets accepted.
We are happy about any support, join us on
Joplin is applying for Google Summer of Code 2020