It uses the database on the Clibu server.

-nevf (September 12, 2019, 05:04 PM)

That means it does call somewhere to register, correct?  It just happens to call to you.  Am I parsing that correctly?

-wraith808 (September 12, 2019, 05:46 PM)

Clibu consists of a Browser App and a Cloud Server app which communicate back and forth. User registration is handled back on the server, so yes it calls our server.

-nevf (September 12, 2019, 06:51 PM)

So even with the following feature from your prior post:

This stores all data locally, and will have offline support with synchronization to other devices should you wish to use that.

You will still need to be connected to your servers to use the software?

-wraith808 (September 12, 2019, 11:36 PM)

Apologies there is some confusion here. Clibu currently stores all data on the server, with some duplicated in the Browser.

The new app I'm developing, which I have written a bit about on the Clibu blog (along with live demos) and have mentioned here, stores all data locally.  It will eventually be able to run entirely in the Browser, even without any Internet connection. In order to get the full benefits of automagic sync across devices, secure cloud backup etc. then connection to the server would be needed. This will be optional. I hope that clears things up.

If you haven't tried Clibu yet, I'd welcome any feedback.

-nevf (September 11, 2019, 04:59 PM)

Does it use the same sort of registration as Surfulater, i.e. dial home instead of just inputting a code?

-wraith808 (September 11, 2019, 10:14 PM)

Clibu registration is entirely in the app, no third parties involved. It uses the database on the Clibu server.

If you haven't tried Clibu yet, I'd welcome any feedback.

Clibu has the same functionality and UI across Smartphone, Tablet and Desktop adapting the UI to suit each device. All updates are synced to all devices in real time.

Clibu was my first Web application and borrowed quite a bit from Surfulater. However it lost some of the more desktop app capabilities which help speed up workflow, like lots of keyboard shortcuts and keyboard navigation. And the UI is a bit cumbersome.

I'm now rewriting Clibu from scratch with a heavier emphasis on usability, more powerful UI components such as the new Tree (blog)  (demo) a new and far better WYSIWYG editor with the ability to switch to using Markdown, both Tree Folders and Tags like Surfulater had, local database (with import/export), offline support with both real time sync and eventual updates when back on line and much more.

The next demo will include the new content editor, with basic functionality, new Home content, Archive and Trash collections along with various bug fixes.