#LAVERNA DROPBOX HOW TO#
#LAVERNA DROPBOX SOFTWARE#

This is basically more or less what is today. fully managed: UI, signal server, and database all run on a server somewhere.The three obvious configurations with this scheme that you could choose one of any of: This takes laverna and lets you turn it into anything you want. In addition, we build an adapter for the signal server to be able to handle sqlite3 connections. We include configuration allowing you to start a UI, a signal server, or both. Notes, notebooks, backup configuration files, everything except the private key. We process all data through the signal server to the database. In addition, we build electron versions of this merged package. We merge the signal server and the UI together into one package.

#LAVERNA DROPBOX HOW TO#

If it IS fully complete somehow, I couldn't figure out how to use it, which means that it's probably way too complicated. The multi-user / multi-device implementation looks incomplete though based on my cursory tests. This means that it would be possible for a user to run a laverna 'gui' (laverna in electron as an example) and connect to a public laverna 'server' / db. All the signal server does (that I'm aware of) is decouple the database from the component that handles the ui. Currently all mongodb does is store user names and what I think are public keys. The user-facing component talks to a signal server, which in turn talks to mongodb. That's an unreasonable expectation to put on a user. Laverna is two components, three if you count the UI, four if you count mongodb (currently a requirement). Here's what I'm initially thinking will be the most flexible and maintainable compromise: I feel like the client/server really is the quickest and mostly likely route to the next release, but the further we move toward that, the harder a standalone desktop application is going to be to implement. I was toying around with trying to find a way to provide it any way you want it with a hosted version, a Bring Your Own Server version, and a standalone Desktop version, but that sounds like it's going to be incredibly difficult to support.

#LAVERNA DROPBOX SOFTWARE#

If one person or group owns the software and the database such as within a client/server model, it solves a lot of the headaches necessary, but, how do you prove your data really is being properly protected? Public api that you can push already encrypted messages to would be one such way, but that's the furthest thing off in the distance. The dropbox method is kind of similar, but I can at least look at my notes and see they are encrypted. For whatever reason, I never had the dropbox sync issues I hear everyone complain about and I like the fact that there's no central server. I strongly encourage anyone who feels a vested interest in the project to come discuss, and I would like to warn anyone else that this project, as it exists at the Laverna organization, probably will not be updated any That's one of the things I've been grappling with. I'm going to replicate this issue on my fork at daed#1. I'd like to talk more about these problems and get recommendations / help on fixing them. Supposedly this is getting fixed someday, though the current plan appears to be to force a newer version of the natives package, which is unsupported.

gulp is pretty broken in node 10 due to ancient dependencies.

The electron-based desktop app version doesn't work.

In spite of the above, https is not enabled by default.

The signal server appears to have been put together with a multi-user environment in mind, and there is the start of some useful features (like sharing between users) but that is incomplete, and I believe actually currently inhibits synchronizing across multiple devices.

That's not a bad model necessarily for hosting, but it becomes burdensome for standalone end-users who are syncing through dropbox (or not at all).

It looks like the project was in the middle of transitioning into more of a client/server model with the addition of the signal server and mongodb.

It's honestly not in very good shape right now: I've spent the last few weeks trying to familiarize myself with the dev branch and working on minor bugs where I can. I'm going to continue with my plan to fork it and develop it independent of the laverna organization. I think his concerns are valid, but I like laverna and I think it's worth trying to make something out of. He also didn't give me access to the repo, so I can't do anything directly with it. He suggested that effort would be better spent focusing on other projects that do already. He acknowledged that laverna doesn't solve issues with synchronization and multiple devices.

Laverna dropbox