Laverna sync code#
Laverna sync free#

Solution in RS: OAuth 2.0, so app developers can decide what part of the storage they need access to, and users can easily see which part that is, and decide to grant access in a simple dialog. Authorization of certain folders to access doesn't exist. Permissions have to be handled server-side and per account in WebDAV, as there's no such thing built into the protocol. Solution for plain WebDAV/Laverna: Any ideas? 2. Also, discovery is handled via Webfinger, where the user address can return all configuration info, but also where extra capabilities of the server can be announced. Solution in RS: the protocol requires CORS out of the box. Also, it has to be explained to the user what exactly could be the cause and that they might have to switch servers in order to use the app.

Laverna sync code#

Problem: even if one would not care about those servers being incompatible, how would an app detect if support is there? This is actually made much more difficult by browsers intentionally not giving JS code details about why the connection failed, so there would need to be some kind of discovery mechanism.

So a lot of WebDAV servers would be incompatible with Laverna out of the box. This carries with it the restriction, that the server must offer Cross Origin Resource headers for all requests and support OPTIONS pre-flight requests for HTTP verbs that can manipulate data, like e.g. The way browsers work is that an unhosted app like Laverna connects directly to the server from JavaScript. In fact, RS was using WebDAV in the very beginning, and the authors decided to remove it in favor of a simpler REST API, based on real-world testing and experience with that): 1. (These are basically the very reasons why the remoteStorage protocol was created in the first place. Here is a (probably incomplete) list of the problems I can think of, that would need to be solved for WebDAV to be integrated. So, let's look at the viability of WebDAV objectively then. If these are all devs and tech-savvy people, surely someone can contribute WebDAV support, if it makes sense?

Laverna sync free#

I don't see how providing an open-source software, free of charge, is strong-arming anyone. Instead, you aim to strong-arm them into something they don't want to do Let's all be nice to each other, because this is unpaid voluntary work for all of us! This is certainly the right place to voice them as far as I can see, and I'm not sure why your first comment in this thread is so hostile. Maybe it's not clear, that my trying to help people here (I never tried anything else, if you carefully read the history) is not the same as telling people to go away, because their opinions aren't valid or heard by someone else. The I'm not speaking for the Laverna devs, but as a remoteStorage.js developer. Reply to this email directly, view it on GitHub You are receiving this because you were mentioned.

Hence, I think it'd be great if you would ask/vote for, or contribute RS OwnCloud support to their apps, then all remoteStorage-enabled apps wouldĪutomatically also work with ownCloud acting as the remote storage server. To support remoteStorage, instead of developers having to add special This app already supports remoteStorage, so if ownCloud were Support ownCloud, if ownCloud were to support an open protocol for per-userĭata storage. It would be much easier for app developers (not just of this app) to May I suggest something to all the ownCloud users in here: On 25 July 2016 at 14:22, Sebastian Kippe wrote: Following this conversation for a few years already, I have to 's latest remark.