Creating an alternative client that syncs with the Joplin data format for unsupported OSs

cfenollosa · 2020-10-27T10:46:06.450Z

Hello,

I use multiple systems and I'm happy with Joplin. I use it to sync notes with my Mac, Linux, and iPhone. However, I also have an OpenBSD box, and it's difficult to get the Joplin client working there.

I was considering writing a very simple alternative client which, at least, allows me to create and edit notes and sync them via the filesystem. The client would read and write from the synchronization folder (.md files, info.json, locks, temp).

After some research, I haven't found any documentation on the synchronization data format (which is the one I would use for the client) or how to parse the Joplin folder items.

The last resort is reading the source code, but I'm not very familiar with Javascript.

Is there any documentation, any starting pointers that I could work with?

Thanks,
Carlos

metbril · 2020-10-27T19:46:38.816Z

How about building;g wrapper around the CLI?

cfenollosa · 2020-10-27T20:13:06.534Z

Unless there is another CLI, the official CLI also uses Node, so it doesn't work either on OpenBSD

c0dev0id · 2024-11-01T15:06:31.866Z

I want to add a "me too" here. I'm also using OpenBSD and neither the cli client, nor the big client can be compiled. Luckily there's a rudimentary webfrontend now. But that's long not feature complete and still has a note that sais: "At present, the web client is in beta. In the future, it may change significantly, or be removed." - So I don't want to rely on it.

So... if there's any movement in porting the jopling client to something that's not an unportable beast like electron, take my vote for it.

Is the joplincloud/server API documented? The existing Data API documentation runs against a locally installed joplin service, which is part of the beast I can't install