CouchDB was already established when I started TiddlyWiki 5 in 2011, and
I'd been following it with interest. Not only did it have solid
synchronisation functionality, at the time it had intriguing features for
hosting JavaScript applications, long before Node.js.
I think there were a few reaso
That was it for me too. In the space of a month, it went from this
friendly, reasonably understandable thing, to this borg-like
mega-corporation thing. HAL* doesn't really cater to "little people" --
that's not their mission statement.
* Advance each letter one step
On Thursday, November 25,
@Jan
I was quite keen on noteself, had it set up and everything but then after
the takeover, Couch DB moved past my tolerance for banging my head against
software and it killed it for me. I suspect that was true for others.
On Monday, 22 November 2021 at 20:06:16 UTC cj.v...@gmail.com wrote:
>
That would be very cool.
*Comments*
Other than technical coolness, what would be the advantage of it? From
just a user perspective (i.e. forget technical stuff) what reason would I
have to want that?
You're talking technological "wowness", but bring it back to "in the
trenches" "daily usage"
Hi V,
this is a very important topic...
I also would like to have the browser storage plugin play a more important
role, because for some first-time users it is a deception that their
changes are not saved when they return - couchDB could heal this.
One setback for noteself was that the service
I can't speak for everyone, only myself. When I picked TiddlyWiki several
years ago, I imposed the following constraints on myself (brief reason in
square brackets):
* Lightweight text markup that included hyperlinking [these are among the
things that separate the solution from text-only]
* Sea
6 matches
Mail list logo