Hi all,
Regarding How to stimulate User Growth of TW? - #98 by TW_Tones, Make TiddlyWiki your own - discussion - #20 by TiddlyTweeter and Essential Editions: Personal Notebook edition - development and feedback, I would like to propose some alternative approaches.
- Which kind of growth we want to get?
- How can we bootstrap the kind of experiences/tools we want as part of being a part of this community as TW users?
Regarding growth, for me is kind of strange the obsession with scale, particularly as I see it in US American culture (from food combos, to the size personal cars for everyone and so on). Vertical growth as in more and users, is usually related with more funding, as shown with Logseq comment. But I think that the main value of TW is regarding horizontal growth as in more diverse users and I think that the “architectural choices” embedded in TW made this kind of growth an already present value (but not as visible as we could made).
I think that the discussion about user growth is pretty useful in the sense that is about having more fluent experiences with TW (which help in growth in both axes: horizontal and vertical). And regarding such fluency in our local experiences, introducing malleable systems, in particular TW, with diverse people (teachers, librarians, students, activists, designers, artist, etc) what we have done is this:
-
I started with a personal (re)exploration of TW after a 10 years long hiatus, particularly guided by questions in our malleable systems workshops regarding apprentice notebooks. Then I searched for a mobile friendlier TiddlyWiki interface. My search “stabilized” so far with the customized version of Nicolas Petton’s Projectify TW variant.
-
Then I developed a workshop curriculum hosted in TW, extending my personal usage with a curricular teaching TW variant and I taught it to different groups: grassroots communities, master students on childhood and culture and undergrad students in library and information sciences. I implemented a project based learning approach, to leverage on Projectify projects support. Learning TW was to develop a set of projects with granular and recombinable activities and we tried to use the more general lessons in dialogue with personalized projects (but we need to improve integration between both in the future). I didn’t use spaced repetition and I think that @sobjornstad Groking TW is a pretty good example of a well developed book/curriculum with exercises and Take Aways.
-
Our teaching materials are online for self learning, but they also happen in events: workshops, short curses and seminars in formal and informal settings. So the learners have periodical events where they can learn together, instead of something that is there for “someday”.
-
Our projects are pretty concrete and usually with resonances in the local contexts. For example, with our Cuban hacker/maker space friends. After introducing them to TiddlyWiki and participating in several of our workshops and the longer course they’re using TW as their main web site, their hacker/makers space wiki (similar to our community wiki) their plastic recycling site. We made a prototype to introduce TW to El Paquete Semanal (the Weekly Package, think in offline Hulu/Netflix with Island wide distribution) and with the possibility to reach millions of cubans. Combining TW with leaflet Cubans are able to map themselves in social cartographies build by local communities and to overcome US Cuban embargo (because Google Maps don’t work there and connectivity is pretty expensive).
-
Several of our workshop participants use TW as their main desktop taking notes app.
-
We recently make a research proposal that uses TW (and GTookit) as bridges between a hacktivist community in Bogotá, several tribes in Amazonas and a economic solidarity and food sovereignty group in the Colombian Coffee region. (It’s under review, but I will share more details as soon as I can).
As you can see, these are pretty interesting TW use cases that showcase hopefully broad compelling reasons for TW: as they account for its flexibility and its generative nature. But they’re hardly going to get 1.5 million investment (particularly if they’re grassroots innovation happening in the Global South). So my approach would be: what we can learn about such experiences, how we can make them more fluent and visible and how they inform the bootstrapping of (inter)personal and community editions?
The key for me is that we bridge (inter)personal with community editions via educational processes that start informal but formalize overtime while keeping personal and contextual relevance. For example the same TW edition that an individual use to keep track of his/her projects (Projectify) is the same that we use for project based learning and for many community wikis that involve projects. Once a collective has learn about TW they customize even further their editions via plugins or go back to more bare editions to create future customized versions.
This educational process deals with the onboarding process and the distilled experience you need to go from the TW page (in English) to your particular combination of TW plugins, contents and storage methods (BTW our best combination so far, as tested in these educational settings, is starting with Tiddlyhost and then with Timimi).
What I try to convey here is that:
-
we can, as a community, to choose a different kind of growth that is more about diversity (horizontal) instead of the so praised scale (vertical) and, consequently, to improve on how we communicate that this is already a present value in TW. My proposal is to show more complete pictures of use cases connecting personal editions with communities and learning/onboarding processes and making this easier to find in the main page.
-
community growth and personal editions are complex socio-technical processes and usually we tend to focus in the technical part, disregarding the social part, particularly concerning formal and informal educational processes inside/between communities. Making this invisible part more prominent would help us to address a multi-dimensional problem in a more assertive way. This also would help us to visualize some tensions about how (TW) cultures and infrastructures co-evolve together (for example, what happens when your base edition stopped to be supported/developed, as happen with us and Projectify).