TiddlyWiki es más complejo de usar pero puede tener más utilidad para diseños de sitios web,
De acuerdo, considero que las posibilidades de TiddlyWiki son un poco mas versátiles para la lectura y la escritura.
TiddlyWiki es más complejo de usar pero puede tener más utilidad para diseños de sitios web,
De acuerdo, considero que las posibilidades de TiddlyWiki son un poco mas versátiles para la lectura y la escritura.
porque siento que podría ser muy útil para alojar los productos de investigación-creación de mi tesis de doctorado.
Conozco dos estudiantes de doctorado y una de pregrado que lo están usando para los productos audiovisuales de sus tesis. Pero efectivamente requiere tiempo, revisión de videos, tutoriales y otra literatura. Habitualmente hacemos eso en talleres extra en el hackerspace, pero este semestre están muy limitados (los estudiantes que profundizaron en dichas plataformas lo hicieron en tiempos extra clase). Sin embargo, tendremos un proyecto que incluye un periodo intersemestral en el que usaremos TiddlyWiki intensivamente.
In the mid-1600s, Gottfried Leibniz devised a notation for integrals and derivatives (the familiar ∫ and dx/dt) that made difficult ideas in calculus almost mechanical. Leibniz developed the sense that a similar notation applied more broadly could create an “algebra of thought.” Since then, logicians and linguists have lusted after a universal language that would eliminate ambiguity and turn complex problem-solving of all kinds into a kind of calculus.
Bret Victor, en Media for thinking the unthikable, compara a Leibnitz con Steve Jobs, diciendo que el primero era un gran inventor de interfaces de su época, en la forma de nuevas notaciones.
Cardumem, de hecho, empezó como un ejercicio mental pensando una nueva notación para expresar "álgebras hipertextuales" que pudieran ser embebidas en un motor wiki (al comienzo vía Lua en JavaScript y luego del lado del servidor, con sistemas hipermedia). Y dicha notación fue concebida en la medida en que las herramientas externas para manipular hipertexto, como TiddlyWiki Pharo generaban mucha fricción en los miembros de la comunidad de Grafoscopio, al punto que su uso era marginal. Una nueva herramienta con una nueva notación alentaría usos y personalizaciones compartidas que con herramientas separadas eran muy esporpadicos y más bien solitarios, entre un puñado de personas, a lo sumo.
Dado que las piezas para armar el wiki (Djot y YueScript) ya estaban integradas al ecosistema Lua, y que originalmente se pensaba en integrarlo directamente a TiddlyWiki, del lado del navegador web, en lugar del servidor, Lua este fue elegido en lugar de Pharo para los procesos de prototipo, dando muy buenos resultados iniciales hasta el momento.
Cardumem is proposed, in the context of the Grafoscopio community, where we have experimented with digital metatools and the notion of interpersonal wikis as a way to collect and care for personal and community knowledge and memory. Because of the connections of members in the Grafoscopio community with places in other communities and academia, our practices and infrastructures has been tested in different contexts
Encuentro muy interesante el tomar a TiddlyWiki como una inspiración por su facilidad de uso y alta customización y transformarla a partir de las necesidades de una comunidad, siempre es bueno tomar una formula que ya funciona y potenciarla, por lo que aprecio que le den crédito a esta plataforma. Ahora bien, se destaca la necesidad de portabilidad entre plataformas como uno de los motivos para crear Cardumem, lo que me parece más que justificado cuando se menciona que la comunidad objetivo trabaja para proteger la memoria y el conocimiento comunitario. Sin opciones para la portabilidad es difícil construir conocimiento colectivo que permita la trazabilidad hacia el contenido original y su creador, por lo que hacer una wiki que, por medio de Lua/YueScript logre solventar este problema, me parece una excelente iniciativa.
Simply stated, Luhmann’s Zettelkasten structure was not dynamic or fluid in nature. Yet, it was not rigid, either. Examples of a rigid structure are classification systems like the Dewey Decimal Classification System or Paul Otlet’s massive notecard world museum known as, The Mundaneum. These types of systems are helpful for interpersonal knowledge systems; however, they’re not illustrative of what Niklas Luhmann’s system was: an intrapersonal communication system. Luhmann’s notebox system was not logically and neatly organized to allow for the convenience of the public to access. Nor was it meant to be. It seemed chaotic to those who perused its contents other than its creator, Niklas Luhmann.
Nuestros wikis interpersonales son pensados para ser utilizados por otras personas. Sin embargo, los identificadores únicos vía NanoID, podrían tener también una jerarquía de contadores arborecentes, similares a los de Luhmann.
Había pensado en esos contadores únicos en cada wiki para TiddlyWiki por si queríamos algún tipo de enlace corto local de ese wiki y el NanoID para los indicadores únicos entre wikis, dadas las bajas probabilidades de colisión. Son ideas que se pueden combinar con otras como el control de versiones.
El carácter dinámico del wiki no tiene por qué sacrificar la trazabilidad histórica y una cierta memoria visual de los enlaces y sus conexiones. Lo clave es que el wiki sea programable con curvas progresivas entre creación de contenido y de funcionalidad, como lo hace TiddlyWiki y lo propone Cardumem
Don't rely on an inbox, comprehensive indexes, or backlinks When writing notes for your Zettelkasten, it's natural to feel some anxiety about whether you're just writing into the void, or whether you'll actually stumble across those notes again in the future. To relieve this anxiety, there are at least three tempting solutions that seem to make sense on the surface, but which tend to fall apart in the long term.
Mis blikis me permiten reencontrar la información fácilmente y los consulto/referencio con frecuencia. En particular para ofrecer información que solicitan una y otra vez, como hojas de vida y portafolios de proyectos.
Si bien a veces creo índices con otros tiddlers, en general confío y uso los sistemas de etiquetados y de búsqueda que ya vienen incorporados en la herramienta para reencontrar la información y el sistema de filtros y operadores para ofrecer vistas específicas de la misma a terceros, como mi portafolio o mi perfil.
No reorganizo la información en publicaciones más grandes y lineales como artículos o libros, como lo haría Luhmann, básicamente por dos cosas:
Lo anterior requerirá otras métricas, en las cuales vamos trabajando lento.
The Zettelkasten: When there's something that I want to rediscover later, but forget about in the meantime, I add it to the Zettelkasten. This includes not only research notes and snippets of writing, but also ideas for future projects, interesting bookmarks and articles that I haven't yet read, and anything else that I want to find again but which isn't in itself critically important. To increase the chances of finding something again, try distributing it throughout the Zettelkasten – for example, instead of having a big list of bookmarks about some topic, sprinkle in a link here and there, where you might end up clicking on it again in the future when you stumble upon it.
De esta manera venía usando mi vieja instancia de TiddlyWiki (desde 2010) y también la nueva, (retomada en 2020) incluso antes de descubrir el Zettelkasten entre estas dos décadas.
El autor luego refiere dos herramientas para recordoar, una lista grande, inspirada en GTD y la bitácora diaria inspirada en el bullet journal. En mi caso, yo también usé TW para agendas y proyectos (es decir combinando GTD y actividades diarias), pero con el tiempo me decanté por Taskwarrior, porque estaba siempre convenientemente a la mano en mi ubicua y privada consola de comandos, en lugar de estar perdido en alguna de las desbordadas solapas del navegador, requiriendo autenticación y permisos y con el temor de que el estado de una nueva solapa sobreescribiera cosas importantes que tenía en la solapa ya abierta (en algún momento coloqué en MiniDocs una utilidad de agenda que se conectaba con Taskwarrior, llamada Acrobatask y le proveía una interfaz web, pero no avanzó mucho y quizás se integre mejor con Cardumem).
Ahora Taskwarrior en la consola se ocupa de los proyectos y los listados de tareas personales, mientras que para lo colectivo estoy probando NocoDB
Take Wikis as an example. Most of them have two different modes: The reading mode. The editing mode. The reading mode is the default. But most of the time you should create, edit and re-edit the content. This default, this separation of reading and editing, is a small but significant barrier on producing content. You will behave differently. This is one reason I don’t like wikis for knowledge work. They are clumsy and work better for different purposes.
Los blikis (blogs + wikis) son formas de pensar en público y tener modos de lectura y escritura está bien, pues no todos los que se aproximan al wiki lo van a editar y la mayoría de internautas sólo lo va leer.
Además sistemas tipo TiddlyWiki (y en el futuro Cardumem) alientan en buena medida la reedición de unidades de contenido (wiki refactoring). Lo clave es que las unidades sean pequeñas y se puedan usar para organizar otras unidades (es decir usarlos como etiquetas).
El primer problema implica que el software no es tan accesible ni liviano como se promociona, pues necesita de la instalación de programas que parchen su compatibilidad y que distancian el supuesto uso descomplicado. El segundo problema implica que, con actitud de modulor moral, es necesario entrar en las entrañas del código para reemplazar las palabras en inglés por palabras en español, hacer ajustes a los vacíos de documentación o personalización, y eso requiere conocimientos en programación o recursos para rediseñar interfaces o hacer localización.
Desde la comunidad de Grafoscopio, hemos encontrado en la metaherramienta TidddlyWiki esta adaptabilidad extrema y facilidad de uso multiplataforma y multilingüe, incluso para procesos de catalogación y memoria viva.
También hemos acuñado lo que he llamado "programación intersticial" que permite extender las infraestructuras y, en general los sistemas sociotécnicos pequeños, no desde sus entrañas, sino desde los intersticios con otras infraestructuras, comunidades y sistemas. Así, cuando TiddlyWiki no tiene una funcionalidad particular, la conectamos con Grafoscopio/Pharo o con Fossil para tener las ventajas de todas sin las desventajas particulares de sólo una de ellas.
They are tools we created and used as part of our development, and they allowed us to replace reading as the main means to figure systems out, the largest cost in software development. The implications do not stop here. For example, these tools compress communication which then unlocks new ways to discover and create value.
Por lo pronto usé:
> Click secundario > Send it to Pocket
para retomar estos enlaces con los que estoy familiarizado, en caso de que quiera anotarlos. (enviarlos a Omnivore no funcionó)
Sería interesante que Hypothesis también soportara funcionalidades de "read it later", incluyendo quitarle el "blink" a ciertas páginas (aunque quizás esto último les quitaría el foco, siendo una ONG pequeña). Lo mejor sería tener funcionalidades de lectura anotada/agendada en plataformas propias flexibles, tipo TiddlyWiki
Example of a public Zettelkasten using TiddlyWiki by Soren Bjornstad. https://zettelkasten.sorenbjornstad.com/
He's open sourced portions of it for use by others who are interested.
TiddlyWiki is free as in freedom. Unlike proprietary tools like Evernote, Roam Research, and OneNote, you have complete freedom to use TiddlyWiki for any purpose you want, share it with others, and modify it if you need or want to. You will never lose access to your notes because a company decided the service wasn't profitable anymore. If you're planning to write a lot of notes, this should be non-negotiable.
This is the key feature you should consider before deciding how to implement your ZettelkastenIsForLifeNotJustForChristmas.
Most notes systems fail at the seemingly elementary requirement of matching the way you think.
This makes me want to create RoundPegRoundHole. But then I'm not sure whether this should be in h. or tw. I would lean towards a public tw which has the feeling of TV Tropes in that it's a database of patterns. Perhaps that's the use case of publishing a subset of a tw/Zettelkasten.
The other (meta) thought this generated was how the decision of whether to be public or private interrupts the pleasant flow that comes from knowing exactly where to put a note and how to divide a thought. This is what experience tiddlywiki fluency is trying to capture.
Categories and hierarchies are sometimes unfairly maligned. In reality, they are powerful supplemental tools for thinking; sometimes, in order to think about a topic, we need to add additional order to a set of ideas to reduce them to a level of complexity we're capable of thinking about, and these tools give us that ability. But as a general-purpose organization method, these tools are terrible: they prevent ideas from being effectively used outside their original context and force us to collapse distinctions that we might prefer to maintain. For notes to reach their full potential, we need to allow them to relate in a greater variety of ways. Further, we don't naturally think in hierarchies except when we are tackling a specific problem; we think in links and webs of ideas.
Grok TiddlyWiki
Takes a while to grok without a guide. Maybe this is that guide!
For those who have been interested in my public Zettelkasten wiki in the past (or might be interested in it now), I've just put up an extensive discussion of Zettelkasten and how I've implemented it in my TiddlyWiki on my YouTube channel
Origin story of TW implementation.
Introduction to tzk (Zettelkasten in TiddlyWiki)
Route 1 to pragmatic Zettelkastening!
Zettelkasten example using my preferred toolchain.
Possibly the quickest way to get the technique under your fingers by browsing the author's example.
You can’t do this so easy in the digital version.
In TiddlyWiki this just means having > 1 tiddler visible.
To make the most of a connection, always state explicitly why you made it. This is the link context. An example link context looks like this:
Doable in TiddlyWiki as it's just guidance on how to write tiddlers.
In practical terms, he's talking about structure notes which consist of an outline of links to other existing notes.
Structure notes is a technical term. They're "meta-notes" in that they're notes that point to other notes containing content.
This seems to be what Ahrens means by a "sequence". I guess there's one explicit sequence defined by notes and their forward/back links, but structure notes can create used to arbitrary sequences.
This also seems to be the key mechanism by which a linear narrative is created.
I've tried to keep a Zettleksaten several times now with no real luck. My most recent try was using TiddlyWiki, with each Tiddler being an entry, usually containing a single piece of information. Perhaps it's the way TiddlyWiki is laid out, but I didn't particularly find the filing system to be of any real benefit to me. After my 30 day experiment I had nearly 1,000 Tiddlers and the majority were interlinked. When I would click through the hyperlinks I wouldn't necessarily have any particular 'a-ha' moments that these articles on Zettlekastens typically try to convince you will happen when you use this filing system.Perhaps I went about it all wrong, but I loved the theory but didn't find the particular application useful. I also found absolutely no examples of a real life Zettelkasten online anywhere.
Here's a real-life example using Obsidian. I suspect the success is in the use rather than the tool, and I would go for TiddlyWiki.
I’m edging towards a new book, which is pretty formless at the moment, so I need a better solution for keeping my writing ‘chunks’ organised. I started playing around with a new piece of database software called Obsidian after recording an episode about it for the On The Reg podcast with my co-host Dr Jason Downs. Obsidian makes your notes more useful by ‘linking your thinking’. Basically, any word in an Obsidian note can become a link to another note, so, over time, your notes become like your own personal wikipedia. Obsidian also makes a cool visualisation of all the links between your notes, so you can surf through them, visually. Pages are represented as nodes; pages which have a lot of incoming links become bigger in the visual graph, literally showing you where an idea is ‘growing’:
I'm not sold on Obsidian. I think TiddlyWiki has equivalent (and more) features (albeit requiring plugins for graphing), a more robust architecture, and a more open license.
Horses for courses I guess, but depending on Obsidian's evolution, I suspect other writers might end up looking for alternatives.
how was I ever able to organise my thoughts without atomising them
Yes! This is the killer feature of TiddlyWiki. I think of it as some kind of intrinsic reward associated with cognitive outsourcing/offloading. Don't hear this mentioned often.
These "atoms" also seem like the fruit of the insight process, e.g. the moment when Leo Szilard conceived nuclear fission whilst waiting to cross the road near Russell Square. Oh! I just noticed the atom pun! Entirely accidental.
The "atomising" aspect is also key to making "molecules".
This whole rabbit hole that led to discovering hypothes.is originated because I wanted to suggest TiddlyWiki to an Obsidian user. It seems all roads lead to @chrisaldrich!
in 2023, I find myself missing the seeming constancy of the old "gang":
Among the many packages I’ve used, stroll has definitely changed the way I interacted with Tiddlywiki. It allowed me to focus more on the note-taking process by dividing the screen into 2 columns. This allowed me to work on different tiddlers simultaneously. Still it took me hours to process my notes and digitize them into Tiddlywiki. I guess the UI kind of slowed me down, mostly because I’m a keyboard-centric user and don’t use the mouse that often.
I share the advantages of having more the one visible tiddler. In my case, I have been using a multicolumn layout like the one in our TRPG wiki particularly in my tablet. I don't get the fluent edition experience I will like, and the panoramic+detailed view I can get with (meta) editors like Leo Editor or Doom Emacs. But TW has several important advantages over them: it is pretty multi-device, self-contained and over all easier to introduce to non-programmers, as extensive teaching/facilitating experience (700+ hours) in workshops, since 2015 has shown trying to introduce meta tools/systems to non programmers, which is a main concern of my practices and research.
While I initially started using just one single HTML file for my tiddlers, I soon switched over to the nodeJS installation. This still has better benefits like: you can run the instance in Docker install tiddlywiki and its dependencies without messing around with your system you’ll get multiple “flat” files (.tid files are in plain text) you can apply sed, awk, bash foo to extract/modify data even if Tiddlywiki will be discontinued some day, you’ll still be able to import your notes in whatever note-taking syntax
For this advantajes regarding flat files and their programmability, we are using our custom build package TiddlyWikiPharo which allows us to have the single file approach while not using NodeJS (so, keeping at bay its incidental complexity). Our flat files are STON files, serialized from the live representation of the tiddlers objects from the Smalltalk image to the filesystem.
And while is still possible to use Unix tools to extract/modify data over those plain files, we prefer to manipulate the tiddlers lively/directly inside the image, with all the advantages of a emergent DSL that give us to have the tidllers represented as a collection of live objects, as shown in the Malleable Systems Wiki data narrative. Also, instead of just plain text Unix scripts, we can build, share and publish complete interactive data narratives involving the import/export and manipulation of tiddlers (as the afore mentioned one).
Xememex is a tool for building tools for collecting, curating and composing fragments of information.
Appears to be a TiddlyWiki farm, possibly for collaborative work?
TiddlyWiki's philosophy now is that the purpose of recording and organising information is so that it can be used again. To maximise the possibilities for reuse, write or slice information into the smallest semantically meaningful units, and weave them together into narratives.
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>TiddlyWiki's philosophy now is that the purpose of recording and organising information is so that it can be used again.<br><br>To maximise the possibilities for reuse, write or slice information into the smallest semantically meaningful units, and weave them together into narratives.
— TiddlyWiki (@TiddlyWiki) September 20, 2022
The first demo of TidlyWiki from 2004 took the ideas of wiki and applied them to fragments rather than entire pages. The hypothesis was that it would be easier to write in small interlinked chunks that could be gradually massaged into a linear narrative
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>The first demo of TidlyWiki from 2004 took the ideas of wiki and applied them to fragments rather than entire pages. The hypothesis was that it would be easier to write in small interlinked chunks that could be gradually massaged into a linear narrativehttps://t.co/v2v6dyL3Oy pic.twitter.com/MJO7tyopr2
— TiddlyWiki (@TiddlyWiki) September 20, 2022
TiddlyWiki was inspired by @WardCunningham's glorious idea of wiki – more than anything by the way that wiki makes linking be part of the punctuation of writing.
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>TiddlyWiki was inspired by @WardCunningham's glorious idea of wiki – more than anything by the way that wiki makes linking be part of the punctuation of writing. https://t.co/pLPfYcCJY2
— TiddlyWiki (@TiddlyWiki) September 20, 2022
Pol Baladas https://batou.xyz<br /> Fermat<br /> https://fermat.ws/<br /> https://app.fermat.ws/
I'm a [[TiddlyWiki Maximalist]]. —Boris Mann
Paul Shen https://twitter.com/_paulshen<br /> Natto<br /> https://natto.dev
Does anyone else work in project-based systems instead? .t3_y2pzuu._2FCtq-QzlfuN-SwVMUZMM3 { --postTitle-VisitedLinkColor: #9b9b9b; --postTitleLink-VisitedLinkColor: #9b9b9b; --postBodyLink-VisitedLinkColor: #989898; }
reply to u/m_t_rv_s__n https://www.reddit.com/r/Zettelkasten/comments/y2pzuu/does_anyone_else_work_in_projectbased_systems/
Historically, many had zettelkasten which were commonplace books kept on note cards, usually categorized by subject (read: "folders" or "tags"), so you're not far from that original tradition.
Similar to your work pattern, you may find the idea of a "Pile of Index Cards" (PoIC) interesting. See https://lifehacker.com/the-pile-of-index-cards-system-efficiently-organizes-ta-1599093089 and https://www.flickr.com/photos/hawkexpress/albums/72157594200490122 (read the descriptions of the photos for more details; there was also a related, but now defunct wiki, which you can find copies of on Archive.org with more detail). This pattern was often seen implemented in the TiddlyWiki space, but can now be implemented in many note taking apps that have to do functionality along with search and tags. Similarly you may find those under Tiago Forte's banner "Building a Second Brain" to be closer to your project-based/productivity framing if you need additional examples or like-minded community. You may find that some of Nick Milo's Linking Your Thinking (LYT) is in this productivity spectrum as well. (Caveat emptor: these last two are selling products/services, but there's a lot of their material freely available online.)
Luhmann changed the internal structure of his particular zettelkasten that created a new variation on the older traditions. It is this Luhmann-based tradition that many in r/Zettelkasten follow. Since many who used the prior (commonplace-based) tradition were also highly productive, attributing output to a particular practice is wrongly placed. Each user approaches these traditions idiosyncratically to get them to work for themselves, so ignore naysayers and those with purist tendencies, particularly when they're new to these practices or aren't aware of their richer history. As the sub-reddit rules indicate: "There is no [universal or orthodox] 'right' way", but you'll find a way that is right for you.
The reason these apps are great for such a broad range of use cases is they give users really strong data structures to work within.
Inside the very specific realm of personal knowledge bases, TiddlyWiki is the killer app when it comes to using blocks and having structured, translatable data behind them.
https://www.youtube.com/watch?v=bWkwOefBPZY
Some of the basic outline of this looks like OER (Open Educational Resources) and its "five Rs": Retain, Reuse, Revise, Remix and/or Redistribute content. (To which I've already suggested the sixth: Request update (or revision control).
Some of this is similar to:
The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web. #osb11 lunch table. #diso #indieweb [Tantek Çelik](http://tantek.com/2011/174/t1/read-fork-write-merge-web-osb110
Idea of collections of learning as collections or "playlists" or "readlists". Similar to the old tool Readlist which bundled articles into books relatively easily. See also: https://boffosocko.com/2022/03/26/indieweb-readlists-tools-and-brainstorming/
Use of Wiki version histories
Some of this has the form of a Wiki but with smaller nuggets of information (sort of like Tiddlywiki perhaps, which also allows for creating custom orderings of things which had specific URLs for displaying and sharing them.) The Zettelkasten idea has some of this embedded into it. Shared zettelkasten could be an interesting thing.
Data is the new soil. A way to reframe "data is the new oil" but as a part of the commons. This fits well into the gardens and streams metaphor.
Jerry, have you seen Matt Ridley's work on Ideas Have Sex? https://www.ted.com/talks/matt_ridley_when_ideas_have_sex Of course you have: https://app.thebrain.com/brains/3d80058c-14d8-5361-0b61-a061f89baf87/thoughts/3e2c5c75-fc49-0688-f455-6de58e4487f1/attachments/8aab91d4-5fc8-93fe-7850-d6fa828c10a9
I've heard Jerry mention the idea of "crystallization of knowledge" before. How can we concretely link this version with Cesar Hidalgo's work, esp. Why Information Grows.
Cross reference Jerry's Brain: https://app.thebrain.com/brains/3d80058c-14d8-5361-0b61-a061f89baf87/thoughts/4bfe6526-9884-4b6d-9548-23659da7811e/notes
https://maya.land/technicalities/hypothesis-python/
python to grab hypothes.is annotations and put them in a tiddlywiki
¿Cuáles son tus primeras impresiones?
Desde el texto, es claro con la idea que desea comunicar. No se si de esta forma el texto sea la mejor forma de por hacer llegar la información de su uso. Esto al poder aprovechar la virtualidad y sus recursos como el video donde puede condensar mucha información de forma grafica, un poco mas inteligible para las personas que puedan querer iniciar en el tema.
https://www.youtube.com/watch?v=GjpjE5pMZMI
Nice overview of using TiddlyWiki for an online zettelkasten. Some obvious influence by Andy Matuschak in here.
Some of the work looks a little bit Wiki like, but seems to stay within bounds. Would have been nice if he showed how he used it as a tool once he's got the pieces together, especially if he actually does it this way.
When sending links to a page by email consider following links from the beginning to the page of interest and sending the whole sequence to provide context.
Interesting to see this same sort of contextual background here as in TiddlyWiki which calls the space a "river". TiddlyWiki does this in a vertical scrolling space where as Federated Wiki does it horizontally.
The motivation behind TiddlyMap is to combine the strengths of wikis and concept maps in the realms of personal knowledge management in a single application.
Build a mind map from wiki topics using Vis.js.
Exporting references from Zotero to Tiddlywiki https://www.rousette.org.uk/archives/exporting-references-from-zotero-to-tiddlywiki/
A recipe for doing just that ^^
http://tw5.scholars.tiddlyspot.com/
Some clever UI affordances in this version.
Thedor Holm Nelson.
Me gusta que algunas de sus ideas, a pesar de no ser tan populares, están dispersas y han persistido en el desarrollo de algunas tecnologías, como la transclusión que es posible hacerla en herramientas como TiddlyWiki
Tuesday, August 17, 2021 9:00 AM
AlexHoughunread,Dec 26, 2014, 5:12:35 AM12/26/14Reply to authorForwardDeleteYou do not have permission to delete messages in this groupLinkReport message as abuseShow original messageEither email addresses are anonymous for this group or you need the view member email addresses permission to view the original messageto TiddlyWikiDear All,TiddlyWiki is like a card index, and a tiddler like an index card. Zettelkasten is German for card index box. The term is closely associated with German sociologist Niklas Luhmann whose text about his Zettelkasten has been recently translated into English by philosophy academic Manfred Kuehn. Manfred Kuehn is a long time user of electronic note-taking technology and he describes his journey to is tool of choice, Connected TextI found out about Zettelkasten on this TiddlyWiki list. Luhman recommends that ones zettelkasten should have the inbuilt capacity to surprise, the same coud perhaps be said for a social system dedicated to the design and application of a personal non-linear note bookAlex
Reference from 2014 connecting the ideas of Zettelkasten and TiddlyWiki
This is pretty slick and looks pretty in its published form. Great to see others are using clever set ups like this as posting interfaces.
I have a feeling that other TiddlyWiki users would love this sort of thing. While TW may not seem as au courant, it's still got some awesome equivalent functionality and great UI which is what most of the users in the note taking space really care about.
I do still wish that there was a micropub set up for Hypothes.is to make this sort of thing easier for the non-technical users.
persiste el error PYWB error
esta es una nota para probar si funciona el Visit annotations in context con los html estaticos de tiddlywiki
Para tener enlaces reversos (back links), con lo cual se puede implementar enlaces de doble vía.
yo estoy utilizando el plugin TWCrossLinks para gestionar backlinks
The students in Raphael Folsom’s Spanish Borderlands course read primary sources on a weekly basis. Rather than taking notes on 3×5 index cards as we did when I was a kid, the students take the same type of note in the Drupal system. They fill out some basic bibliographic information about the source, write a short summary of the source, and then take a note about an interesting facet of the text.
I've been trying this sort of thing out with a TiddlyWiki for a while and have got a reasonable sort of workflow for doing it. The key is to reduce the overhead so that one can quickly take notes in a manner that interlinks them and makes it seem worthwhile to come back to them to review and potentially reorganize them. Doing this practice in public has a lot of value as well. I'll have to come back and look at some of how this was built at a later time.
I have one system for the stream, and one for the garden. It's a bit 'manual til it hurts' at the moment combining the two - but not a big deal. If I had a choice, I'd go for moving the stream to org-mode too. But WordPress is so full featured for now with IndieWeb stuff, it'd take a long time to recreate all that in org-mode (there is Arcology though if only could get the source…)
I too would give my left arm to have a fully featured IndieWeb capable wiki. TiddlyWiki is pretty close to the sort of tool I'd love, but it's missing some of the IndieWeb capabilities and it may be difficult to build them into the system.
Breaking the card into more atomic pieces turned a question he routinely got wrong into two questions he routinely got right.
This sort of atomicity is exactly that of platforms like TiddlyWiki and Zettlekasten.
In mnemotechnic,brevitasrefers to the creating ofsuch ‘‘rich’’ if necessarily ‘‘brief ’’ units. Because there is in principle no limiton the number ofdivisionesa person may have in memory, readers could beencouraged to make ‘‘brief and compendious’’ summaries of materials theyhad learned.
This is very similar to the idea in TiddlyWiki or Zettlekasten of writing down and storing the minimal amount of information on a card to capture an idea.
Re-collection is not passive, but rather an activity involvinghuman will and thought; it is often defined as a form of reasoning. One mayconveniently think of this activity in spatial terms, as if memories have beenstored in a variety of places and must be called together in a common placewhere we can become aware of them, where we can ‘‘see’’ them again andknow them in the present.
I don't use it frequently (enough perhaps), but TiddlyWiki has the ability to open multiple cards (tiddlers) in one view (using a permalink) as a means of giving disparate small pieces of thought a commonplace. Very few other note taking systems do this without relying on a taxonomy mechanism.
What’s the difference between a digital garden, a note-taking app, and a blog? You can see the digital garden sitting between the former and the latter. It’s a place to share your evergreen notes—not raw notes you may have stored in your note-taking app, but not quite the level of polish you would expect on a blog. Creating a digital garden is a great way to receive early feedback on your ideas. Over time, several posts in your digital garden may be combined to create longer essays to post on your blog, but it won’t necessarily be the case.
Anne-Laure defines a third "thing" known as a digital garden sitting in between a private note-taking/thinking tool and a blog. She calls it here a digital garden.
The idea is interesting, but requires some additional work to create the third thing, which is okay for those who'd want it.
In some sense, I'm more likely to create just a single thing that does all three functionalities and not worry too much about the public/private portions. I'm not opposed to maintaining all three, though it will require a tool that has the pre-built UI to make maintaining them all simple. Otherwise, I'm not sure the manual work would work for me.
Maybe of interest for some readers here: With your plugin, it's also straightforward to import the "tweets.csv" file from the official Twitter archive, which contains all the tweets (and a lot of metadata) from one's personal account. Still don't know what to do with this in TiddlyWiki, but there is certainly potential...
“Where have you been, you young monkey?”
Testing out annotations on Hypothes.is with a TiddlyWiki published book.
Your machine is a library not a publication device. You have copies of documents is there that you control directly, that you can annotate, change, add links to, summarize, and this is because the memex is a tool to think with, not a tool to publish with.
I can't help but think about Raymond Lull's combinatorial rings which he used as a thinking tool. Or Giordano Bruno's revision of Lull's tools as described in De Umbris Idearum. Given their knowledge of the art of memory stemming from rhetoric in combination with his combinatorial tool, he was essentially sitting on top of an early form of a memex.
I also can't help but think about Kicks Condor's Fraidyc.at reader tool that pulls in wiki content from TiddlyWikis and which have the potential to also make wikis publishing tools as well.
Here’s how you currently reuse something in WordPress, for example. It’s a pretty horrific process. Log into the WordPress source site Open the file, go to the text editor. Select all the text, cntrl-c copy it. Go log into your target WordPress site Create a new page and name it. Go into the text editor, and paste the text in. Save Draft. Go back to the source site. Right click on the images in the post and download them. Go back to the target site. Open the Media Gallery and upload the images you just downloaded. Go through you new post on the target site, and replace the links pointing to the old images with links pointing to the images you just uploaded. Preview the site, do any final cleanup. Resize images if necessary. Check to make sure you didn’t pull in any weird styles that didn’t transfer (Damn you mso-!) Save and post. You’re done! Oh wait, you’re not done. Go to the source post and copy the URL. Try to find the author’s name on the page and remember it. Go to the bottom of your new “target” page and add attribution “Original Text by Jane Doe”. Select Jane Doe and paste in the hyperlink. Test the link. Now you’re REALLY done! It’s about an five to ten minute process per page, depending on the number of images that have to be ported.
One of the things I love about the idea of using TiddlyWiki for OER. Drag, drop, done!
Of course it would be nice if the metadata fields of Tiddlers included links to the permalinks of the original as well as their Creative Commons license.
The purpose of recording and organising information is so that it can be used again. The value of recorded information is directly proportional to the ease with which it can be re-used.The philosophy of tiddlers is that we maximise the possibilities for re-use by slicing information up into the smallest semantically meaningful units with rich modelling of relationships between them. Then we use aggregation and composition to weave the fragments together to present narrative stories.TiddlyWiki aspires to provide an algebra for tiddlers, a concise way of expressing and exploring the relationships between items of information.
This also seems like a great underlying philosophy for open educational resources.
wikis and concept maps
TiddlyMap = wikis + concept maps
PartTiddlerPlugin
Looks like a really useful plugin. Possibly some advantages over use of extraclusion as it keeps all the content in one place but allows no-linear use of the parts.