What are the competitive NS features?

General
#1

So, I’ve set up a kind of guide to help people decide on what kind of back-end setup they want for their TW. NoteSelf is, of course, one of them - even if it is also much more. Please take a look at:

http://backend.tiddlyspot.com/

@danielo515 - how would you say NoteSelf performs on the criteria given there? And what criteria are missing that NoteSelf features (or depends on) that are relevant in this matter?

Here are the criteria listed (so far)

auto-backup
browser
data-storage-location
dependencies
encryption
file-or-folder
format
mobile-first
multi-user
os
type-of-backend
versioning
works-offline

Thanx

<:-)

#2

Hi Mat, I’m not Danielo (obviously) but I have set up several different Tiddlywiki back-ends. In my experience, the following applies for your list:

Note Self using self-hosted CouchDB
Auto backup - no (but can be set-up on server)
Browser - pretty much all (must support PUT)
Data-storage - on server and browser cache
Dependencies - CouchDB server (that’s what Cloud Ant’s back-end is/was)
Encryption - TLS in transit (if setup on CouchDB)
File-or-Folder - neither (stored in a database)
Format - json (CouchDB native)
mobile-first - no
multi-user - yes (per tiddler opportunistic locking)
OS - any
Portable - what do you mean?
type-of-backend - a CouchDB server
versioning - yes, per tiddler
works-offline - yes

WebDAV
auto backup - no (depends on your WebDAV back-end; can be set-up on server)
browser - pretty much all (must support PUT)
Data-storage - on server
Dependencies - a web server (IIS, Apache, possibly Nginx) with WebDAV support
Encryption - TW native (in storage), tls in transit (if setup on web server)
File-or-Folder - single file
Format - .html (TW native)
mobile-first - no
multi-user - poor (uses opportunistic locking)
OS - any
Portable - what do you mean?
type-of-backend - a web server
versioning - depends on WebDAV implementation (probably not)
works-offline - no

PHP
auto backup - yes: store.php creates a backup every time you save
browser - pretty much all (must support PUT)
Data-storage - on server
Dependencies - a web server (IIS, Apache, possibly Nginx) with PHP support
Encryption - TW native (in storage), tls in transit (if setup on web server)
File-or-Folder - single file
Format - .html (TW native)
mobile-first - no
multi-user - poor (uses opportunistic locking)
OS - any
Portable - what do you mean?
type-of-backend - a web server
versioning - via backup
works-offline - no

NOTE: opportunistic locking is where the client (browser) checks to see if the file/data has changed since it last got a copy, if it hasn’t changed, your updates are saved. if it has changed, you get an error message.

1 Like
#3

@thelostadmin - appreciated!

I will transfer your info to backend wich, btw, has been somewhat improved since I posted the above.

However, some of the criteria were poorly explained here by me so I’ll have to come back on some of them. Actually, it is unlikely that I’ve assembled the relevant criteria to begin with; what would you say I’m missing / misunderstanding? What other areas should be there and which ones are either not relevant or merely less interesting for someone looking to “set up a good TW system”?

Thanx!

<:-)

#4

@Mat

I didn’t see a change to the categories in your list. I like the ability to select criteria and links to the various back-ends.

As for what criteria is relevant; I honestly don’t know. The relevant criteria is heavily dependent on the goals of the reader.

For example I use Tiddlyspot to host content that I want other people to be able to read (somewhat like a blog) whereas I use Note Self more like a self-hosted EverNote/OneNote that doesn’t need a special program to access. My needs between the two are very different. Most of the info I have on Tiddlyspot was created from notes I wrote in Note Self, so I don’t much care about backup in TiddlySpot but do in Note Self.

#5

Wow, thanks @Mat for taking NoteSelf in account and many many thanks to you @thelostadmin for your detailed explanation and you support to several users. I’m very grateful.