Hi Jeremy, This post got many discussion and views! It is good to have your preliminary conclusion and see if any decision should make or not!
--Mohammad On Monday, February 17, 2020 at 7:42:44 PM UTC+3:30, Jeremy Ruston wrote: > > Just to add to Mark's comment: It has been clear for a few years that some > users find the terms "TiddlyWiki" and "tiddler" to be a barrier to taking > it seriously. In particular, while the word "tiddler" is common and > innocent enough in Britain, it appears that for quite a few North American > users it carries obscene connotations that they consider self-evident. > > There's an example in this recent tweet: > > > It's all fun and games until you pass away and your significant other > has to log into something called TiddlyWiki and browse through Tiddlers to > find your last will testament. > > (See https://twitter.com/remembersonly/status/1228729946656428032) > > I have recently been thinking through what would be involved in a name > change, and am starting to think that it might not be a terrible idea. > > In order to understand some of the issues, I made a very simple experiment > where I wrote a script that takes the prerelease index.html and applies the > following four global search and replacements across the file: > > * TiddlyWiki --> FooBarWiki > * tiddlywiki --> foobarwiki > * Tiddler --> Card > * tiddler --> card > > The result is a fully functional TiddlyWiki with no remaining references > to the words "tiddlywiki" or "tiddler". Not only is the user interface text > fixed, the `<$tiddler>` widget becomes the `<$card>` widget, and the > `<$tranclude tiddler=foo/>` widget becomes `<$tranclude card=foo/>` etc. > > That simple approach is unlikely to be the way that we'd want to approach > the name change, but it establishes the technical feasibility of changing > the name. > > We'd need to provide an upgrade path for existing users. Perhaps we'd keep > tiddlywiki.com running for 12 months with a build that uses the terms > TiddlyWiki and tiddler, and a separate build at foobarwiki.com with the > new terminology. We'd also need a conversion tool for updating individual > wikis: we could offer an online tool and a command line option for Node.js. > > There's lots of interesting questions to consider before we even try to > settle on the new name itself, and I'm interested to hear other views. > > * Is it worth the effort of changing the name? > * What are the downsides of doing so? > * Coming up with suggestions for the new name is relatively easy, but what > are the criteria that we should use to test the new name? (We wouldn't want > to have to change it again) > * Should we seek to keep things simple by choosing a name that retains the > TW initials? > > Best wishes > > Jeremy > > Best wishes > > > -- > Jeremy Ruston > jer...@jermolene.com <javascript:> > https://jermolene.com > > On 17 Feb 2020, at 15:53, 'Mark S.' via TiddlyWiki < > tiddl...@googlegroups.com <javascript:>> wrote: > > > These discussions about extending the outreach of TW always center around > some hypothetical > newby who is turned away by the complexity of TW. The reality is, that the > first time we > learn of the existence of a new comer, they're asking for advice on some > complicated, > convoluted mechanism that they've already devised. The technological > barrier doesn't seem > to keep motivated people away. > > Listen to the Podcast. What's keeping people away is the *name*. > > I know it's irrational to chose an information management system based on > a name, but > we live in an age of hyper-marketing -- everything gets marketed, branded, > recognized. > So if something is under-branded it goes nowhere no matter how good it is > because it's > up against hundreds of products with serious, professional sounding names. > > The name TiddlyWiki suggests a kid's game or plaything. It suggests > something that > someone made for fun but won't be here tomorrow. It doesn't suggest > something that > you could do serious work with or store your vital information in. It > doesn't suggest > something that will be here in 25 years. > > OneNote, Evernote, Cintanotes, Google Keep ... all have names that you're > not afraid > to say in an IT staff meeting. Names you don't have to mumble under your > breath > when you explain how you did something. And, you don't have to actually > get rid of > the name TiddlyWiki. You just make the publicly visible name something > like "TW Technology." "Wiki-T" . > > > > > On Saturday, February 15, 2020 at 10:28:06 AM UTC-8, bimlas wrote: >> >> A wave started which could make TiddlyWiki more and more famous. *Now* >> we might need to make it really user-friendly, so that new people can >> easily get over the initial difficulties and stay with Tiddly. >> >> >> https://hackaday.com/2020/02/14/it-aint-over-til-the-paperwork-is-done-test-driving-tiddlywiki/ >> > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to tiddl...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/ef02ea13-000d-4303-800c-230cbbe3ba22%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/ef02ea13-000d-4303-800c-230cbbe3ba22%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8cfc83e1-21aa-4961-9ded-972b7bbedbb4%40googlegroups.com.
