Public Perception of TW from the first few tiddlers

Meta
#1

I came across a surprising situation concerning TiddlyWiki and thought it might provide an worthy discussion topic.

The main tiddlywiki.com currently highlights the idea of TW being a fully conceived application. Though in concept it is it misses an opportunity to show that this is not a normal application like people expect. For me the biggest win for TW is that it is in essence only HTML in a browser. By comparison to something like Obsidian which is a focused as a desktop application with optional cloud support.

This distinction is important to me because of the job that I have. Like many who might work or be in an environment that has tight restrictions on what a computer can do it is important to manage the nuances of how a piece of technology is implemented.

For example I work in an industry that requires installed applications to be vetted. If I needed a note taking app like Obsidian I need to ask permission to install it. This approval process is on a per application basis. However because of TW unique implementation being that of a web page it does not need that same kind of scrutiny as a compiled application would. It is just a document on the machine. — or in my case a set of files served by a local bound node.js instance. Being so contained locally is a big win for such an environment.

But to those unfamiliar with TW and how it works it is not apparent that is the case. When I mention “I use TiddlyWiki” and link to the main page they understandably think it is an application that needs approval. The main page focuses on the tools external to TW such as the desktop application or Tiddlyhost and you have to dig very deep to find that under the hood it is only an HTML file.

I suspect that the vast majority of visitors to the site (potential users) need such a focus on simple application installs because we have entire generations who have been taught “apps, apps, apps.” The idea that things could be different is lost to those old generations who had to do things by hand.

I’m curious if the Quick Start section could have a top level HTML focused option instead of discovering that two levels under the “Explore” button. As even the Getting Started section it is not very apparent that the HTML implementation is the backbone to the TW system.

Having to try to explain all this every time I post an elevator pitch/link to tiddlywiki.com is quite demotivating sometimes.

13 Likes
#2

I think it would be a good idea. How would we present that?

Here’s a first pass, as an addition to HelloThere:

  • TiddlyWiki lets you choose where to keep your data, guaranteeing that in the decades to come you will still be able to use the notes you take today.
  • Tiddlywiki stores its data and runtime in a single HTML file, requiring no installs, no external dependencies, nothing but a web browser.
  • TiddlyWiki is infinitely customisable and extensible with many plugins that add new features
  • TiddlyWiki is the product of a collective of developers, part of an extensive community of users

(Minor note: If we’re in there updating this, my internal copy editor hopes that we can decide if these bullets should end in full stops. Right now the first one does; the other two don’t.)

6 Likes
#3

I used TiddlyWiki twice before when my job required much more knowledge work for exactly this reason. Even now I still use TiddlyHost since it is not blocked by web filtering. It’s a strong advantage.

2 Likes
#4

And, somewhat ironically, the first link quoted in the link above (to http://www.networkworld.com/article/3028098/open-source-tools/tiddlywiki-a-free-open-source-wiki-revisited.html) gives a 404 Page not found…

#5

That is ironic. It looks as though we should change the link to an archived version.

1 Like
#6

Looks like they changed their URLs: TiddlyWiki: A free, open source wiki revisited | Network World

1 Like
#7

I think https://tiddlywiki.com/#TiddlyWiki%20Privacy%20and%20Security uses the terms you need.

1 Like
#8

It does, but to my mind, the point here is to put it right up front: one of the bullet points in the very first tiddler many people ever see.

#9

I did create 2 DOC PRs using: TiddlyWiki v5.3.6 — a non-linear personal web notebook

2 Likes
#10

I agree it’s a key selling point and it’s what ultimately made me choose TiddlyWiki. I’ve written previously on how I see it as an essential feature that must be retained in the future, even if contributors and commercial users favour nodejs.

#11

Indeed, that’s why we need out-of-the-box software like TIDGIT. Inside there are configured TiddlyWiki files with a large number of plug-ins installed to help newcomers get started with TiddlyWiki quickly. later on newcomers can delete or modify many of the plug-ins once they are familiar with them. As well as a configured GITHUB synchronisation scheme. Just need to use github desktop, and register a github account, you can automatically synchronise the data to Github, very convenient.

At present, TIDGIT has no English introduction article, if the experience is better can write some articles recommended to more people.

3 Likes
#12

Good!

Those PRs may well help.

But TW is so FLEXY on use cases I doubt anyone will ever capture what she can do succinctly ???

Is that a plus?

A query, TT

#13

Yes it is. But we lack proper “Out of the box” editions, like Projectify was / is.
Or TiddlyPWA, which is relatively complex in its own right.

#14

Right. There lies a conundrum?

The paucity of “editions” (though many have been made) as VIABLE entrées to TW is a puzzle.

IMO a better way will still be editions, each with their own special imperatives and guidance.

TW Central is very good already.

Editions, IMO, are the best way to tweak & explain “Mother”.

Just comments, TT

#15

@sukima … The proposed changes from @Scott_Sauyet are active at tiddlywiki.com now.

Some (6) other improvements have been merged too.

1 Like