https://tiddlywiki.com Is a single .html wiki app that store all its data in that single .html, including markdown notes and plugin javascripts.
According to https://tiddlywiki.com/dev/ , seems it’s core is a js called Microkernel. If change the behavior it save content, from “save to .html file” to “save to Solid POD”, I think it will be a powerful SoliDApp.
Then there will be a non-linear wiki in the Solid world.
I am infact working on a tiddlywiki-SOLID integration right now. There is a JS-only database called PouchDB (in-browser CouchDB) and I trying to modify the noteself plugin called tiddlypouch to enable synchronized notebooks, Evernote doesn’t stand a chance.
So tiddlypouch is a Syncadaptor that can connect to a SoLiD Pod? This seems to be a project started 2 years ago, but is lacking doc so I can’t be sure.
User data is scoped by so-called categories, which are essentially base directories, for which you can give apps read-only or read/write permission. Apps will use OAuth scopes to ask for access to one or more categories.
In the example screenshot, Litewrite is asking for read/write access to the “documents” category, using the OAuth scope documents:rw. If you allow access, the app will retrieve a bearer token, with which it can read and write to your storage, until you revoke that access on your server.
Data Storage & Sync: HTTP REST
remoteStorage defines a simple key/value store for apps to save and retrieve data. The basic operations are GET/PUT/DELETE requests for specific files/documents.
In addition to that – and the only special feature aside from plain HTTP – there are directory listings, formatted as JSON-LD. They contain both the content type and size, as well as ETags, which can be used to implement sync mechanisms. The files and listings themselves also carry ETag headers for sync/caching and conditional requests.
Very near with Solid for our needs except directory listings (do not exist in Solid)
Remote Storage choices made for data storage
The orignal implementation of Tiddlywiki stores the wiki as a simgle .html document.
some implementation have chosen to store each tiddler individually.
This is the choice made by the RemoteStorage plugin. This choice could help reuse pieces of data and should improve performance
Tiddlywiki SyncAdaptorModules (https://tiddlywiki.com/dev/static/SyncAdaptorModules.html)
SyncAdaptorModules encapsulate storage mechanisms that can be used by the SyncMechanism. Two examples are:
. The TiddlyWebAdaptor interfaces with servers compatible with TiddlyWeb’s HTTP API, such as TiddlyWeb itself and TiddlyWiki5’s built-in ServerMechanism.
. The LocalFileAdaptor interfaces with file systems with an API compatible with Node.js’s fs module
SyncAdaptorModules are represented as JavaScript tiddlers with the field module-type set to syncadaptor.
Just the meaning i wanted, not the coding technical side of it.
So is it like a notebook that a user can upload/store all the personal information such as photos,videos,notes, other documents etc ?
Solid is very good for quickly adding “Save As” functionality to existing Single Page apps. Note how dokie.li does something similar with its annotations functionality.