Ever since the decline of Evernote, I've been looking for something as convenient, but been pretty much disappointed in the alternatives. For a while Qownnotes was my choice, but it's not without its drawbacks. Currenlty Joplin ( https://joplin.cozic.net/ ) is the one I'm taking for a test drive, and I'm pretty much pleased with what I've seen so far. Among the features that impressed me most in terms of personal priority are:
- Importing from Evernote (.enex files)
- Cross-platform support (Win/Lin/Mac) + Mobile apps (ios / Android)
- It's FOSS, with a number of active contributors on GitHub (https://github.com/laurent22/joplin). A good bus factor and no more dependence on the whims of private organizations.
- A command line interface
- Use of Markdown. Drag and drop support for files and media in the GUI.
There are still features of evernote I miss such as inline PDFs and audio recording
I've got my eye on Joplin as well to replace EN. The deal-breaker issue for me right now is that the mobile app (iOS) only supports Dropbox as the backend sync provider. I refuse to use Dropbox, and prefer to sync via filesystem. I use Resilio Sync (formerly btsync) for this. Until some other method is allowed, I can't make the jump.
A hyperlinked knowledge-management system for personal use, on all my computers, is essential. To achieve it, I use Emacs and Org-Mode and Dropbox.
An additional benefit of using Emacs: the personal wiki can be integrated with my task-management system, which Org-Mode handles as well. Plus I can draft and edit at warp speed, having customized the native Emacs keybindings to suit me better.
Were I going to publish my wiki to the Web for others to use, I'd export the wiki to HTML with Org. But for now it's all personal.
How do you handle images/screenshots/handwritten notes?
I am also using Org-Mode and Dropbox for the majority of my notes. I really like it. In particular, Orgzly for Android works great with this system, so check it out if you want mobile notes as well.
The problem is that I also like to take paper notes, and take videos/pictures of stuff, and scan documents, and download webpages. Org-mode kinda stinks for embedding external content that isn't text? As far as I can tell.
I can link to external content, and if I export to HTML it'll show up. But... I never export to HTML, because, as you probably already know, it's way easier to read notes in an editable format. I can turn on picture rending in Org-mode, but it's not responsive, and I can't crop the pictures or annotate them with a stylus, or do any of a dozen different things that I want to do.
What I've thought about is that I really just want the ability to render HTML/CSS inside of an Org-mode buffer, and ideally to be able to set up custom CSS classes that would be applied to every snippet. Just set up a quick region, write some helper functions to compile/render the HTML, etc...
I've been thinking for a while about taking some time off of work to just try and solve the problem. Is it already solved? I know that at one point people were looking into getting webkit embedded into buffers. Did that go anywhere? I guess you can build GTK widgets for Org-mode as well? But then you lose the ability to define custom styles on the fly.
I also use org-mode as a personal wiki, combined with git version control and ripgrep search. Furthermore, my task/time management is also within the wiki, as a kanban page and as an events page. Org has tons of useful features. Especially for time management and export. But it's also quite simple.
I started implementing a personal wiki using MediaWiki long time ago, trying to replicate the concept of Zettelkasten. But MediaWiki is a bit too heavy and complex, even if you use a SQLite backend. Furthermore, it doesn't compose with my editor and version control system of choice.
I think having a wiki is essential, as the deliverable of many tasks is just a knowledge bit you really want to record. It's interesting to see personal wikis are starting to show up in GitHub and GitLab. I wish both platforms improved their org-mode support to capitalize on this trend. We can all collectively benefit from open-sourced wikis in the same way we benefit from open code.
In addition, I have an AWS lambda endpoint which listens to a SES email hook. I send emails to the SES address which the hook then appends and schedules to org files on dropbox based on email content.
I'm curious, are you (or anyone else using Org Mode) using a single org file for your entire personal wiki, or one file per major topic? In the past, I've used Markdown files with one file per language/topic for my personal developer wiki, but am looking at moving it to Org Mode now. One file for everything (developer knowledge + other subjects) seems nice, but it seems like trying to manage and navigate around a single large file would get messy.
I personally think Tiddlywiki is a fascinating project and I even used it professionally for a few years. But, these days, I think you likely do better with either a Dropbox directory full of Markdown files or installing the free tool Simplenote everywhere (mobile/desktop) and using its support for notes/Markdown. It's true that if you go with these simple schemes, you lose wiki-style linking. But, I've found that YAGNI applies here.
I personally use ZimWiki[1], with it's files synced across devices using SyncThing[2]. Setup to install both took barely half an hour and it doesn't really need any maintenance now.
For team use take a look at the open source wiki we've been working on, simple, BSD licensed, well designed and works with Markdown: http://getoutline.com
I discovered TW a few months ago and I decided to use it for our new project at work.
We use it to document our SW, one tiddler for each module.
So far, it is working great, we can quite easily merge our code and doc because everything is in one file.
I find it much easier to use than Word. My colleagues were startled by it, but they mastered it now.
The only annoying thing are:
- we need to press 2 carriage return to go to the next line
- the markup languages are never standard. we use redmine with textile which is kinda compatible with TW, but not 100%
I look at TW every couple of years or so, and there has never been either:
- a sane way to keep a wiki on something like Dropbox (at the time, the only way to have persistence was to disable browser security and allow JavaScript to write to disk directly) or
There is a server version, which you can run locally. This keeps all the individual tiddlers in separate files in a folder. You can sync this folder, run git on it etc. Currently, the server doesnt seem to notice changes made outside the server interface(like editing and saving tiddlers in a text editor) until restart, though there is probably some way to manage this.
I run a tiddlywiki server (on my server) and sync the files between all my devices. That way I always have a copy of my data, but I always do my editing through the server. Previous to this setup I tried to sync to all my devices and edit them locally, but it wasn't worth the trouble. I find that I don't mind doing all my edits through an online service.
Created an account to let you know, there's a few good apps on the website that work fairly well, and I'm working on a "unified" set of apps to clean up the experience across platforms, eta: before the heat death of the universe
A bit of a tangent, but I'm looking at the (official? shown on site) Tiddlywiki poster[0], and I just have to ask: what is that fish doing, and does this really communicate something positive about the product?
('Tiddler' is perhaps BrEng slang? I'm British, and I'd say it's slang - especially when applied not to a fish, but to something or someone small - but I don't know how widespread it is.)
The most unique thing for me is the fact that it's an .html file that you can just download and run. The data/saving mechanism is completely separate. This "unhosted-ness" seems to be a growing trend.
I tried using TiddlyWiki some years back but never really reached the stage where I felt I could definitely trust my use of it to result in it saving my notes properly. The real utility of it, I'm sure, comes with a large corpus - but I never got there.
At the time though, my only option was keeping it as a local file on a single machine - these days my home infrastructure is much more developed, and I think I might have more luck running it on a proper http server. Maybe I'll give it another shot.
I've been writing a personal encyclopedia for the last five or six years or so. I have some 1500+ articles multiple of which are 50+ pages. I think it's been really valuable. I think I get a few things out of it:
1. Perfect recall. Every little detail I read in a book/blog/article stays with me. Makes it easy to synthesize results from multiple pieces across time, which is useful when you only have a casual interest in something. (I really like downloading the cool education images/GIFs and and inserting them in articles- otherwise I don't know where I'd keep them.)
2. Reveals what I don't know about a subject. For example, whenever I start off writing a new article on some topic, the first thing I write is a definition, e.g. "A cat is an animal that ...". The process of doing that often reveals gaps in my understanding.
3. It makes me better at asking questions when I'm trying to understand something. The analogy I like to make here is that learning a second language is harder than a third language, because after learning the second you know what you need to know to understand a language. But there's no reason that should be limited to languages and couldn't apply to all things, and things themselves. Some questions I like to ask are "What is the function/uses of this thing?" "What are the parts of this thing and how are they arranged?" "How do we make this thing?" "What's the history of this thing?" "What subtypes of this thing are there?"
The downside is that it dramatically slows down my reading speed, since I now feel I need to take detailed notes, and then I often have to reconcile them with notes on other things which can be time-consuming. Considering the number of books a person could realistically read in their lifetime is limited, it's unclear if it's worth the tradeoff.
I'm curious how other people think about remembering things, and if they have a system, what tools they use. It seems unsatisfying to me to read a book and realize I'll probably forget it in four years, yet most people seem content to do so.
If anyone is interested in the specific software I use, here's the Github project: https://github.com/Ceasar/Encyclopedia. It uses restructuedText (as opposed to Markdown) for the text. I edit them using Vim. All the files are stored in Dropbox so it gets synced between my devices. A simple Flask web server renders the pages in a prettier format.
Still very primitive compared to what it could potentially be, but combined with regular Unix command line tools it's worked fine for my needs. (I like the idea of a hacker-wiki by the way, more than something like this which comes out of the box. Seems like an personal wiki designed for a power user could be way more interesting.)
I have the same fear of forgetting things and the desire to remember everything I've learned. I'm an academic, so mostly this means references to papers and books I've read, along with notes summarizing their contents.
(My PhD advisor used to say that a sign of learning isn't whether you remember something -- it's how quickly you can re-learn it. So I try to make it easy to find and re-learn things I need.)
Since I need to cite papers, I had to put together a system that can read BibTeX bibliographies and format them into references. I cobbled together a Hakyll config that uses Pandoc and KaTeX to turn Org files into HTML pages, with a simple chronological listing: https://www.refsmmat.com/notebooks/
I've found this useful for my own reference and to share with others -- if someone asks me about some topic I've read about, I can just send the notebook link with summary and citations.
I'd like a version that doesn't need separate BibTeX files (though that should be easy to solve with a couple scripts or some Emacs packages), and perhaps intelligent full-text search, but for the moment I like that it produces static HTML that will last forever.
Thank you for sharing. I have a system that is kind of like this. Except it's not meant for memory as much as analysis. And I don't consider the entries "articles" but rather refer to them as "models" as in mental models. Like a real life model, say a toy car, I try to cover enough bases that it--metaphorically--at least _resembles_ a car at first. Then as I identify needed leverage points in the model, I refine my analysis and expand the model. So maybe at that point it has a hood you can open, and an engine you can see, so to speak.
I think I'm at or near around 800 of these, and many are very short. But no matter how short they are, they are all there because they provided me or continue to provide me with needed leverage.
I keep the bulk of the information in markdown in a Dropbox folder and also occasionally try new methods. For example, for topics that will quickly benefit from hyperlinks, I developed a LibreOffice web template and a companion PHP script that indexes these files and inserts additional CSS, variables, JS, etc. when they are served up. For searching I like Regexxer a lot, but I also use grep quite a bit :-)
On my XFCE desktop are buttons for opening a random one of these files, and for opening a random journal entry to try to harvest new models, so to speak.
And there's some paper involved here too... Can't get away from it, because paper has its own special leverage points...
I'm not concerned about memory, knowing it's a special weakness of mine. If I'm working in a context where memory is super important, my energy is best spent moving to a more sustainable context. :-) Memory is a hobby for me, a side gig for memorizing pi, that kind of simple and fun thing.
> I have some 1500+ articles multiple of which are 50+ pages
Holy shit. Make it public.
The idea is fantastic. I would love to have something like wikipedia but people have separate pages on topic.
Or, in other words, if you want to find everything written by given person, why not that easy it is doable - it was more doable back when blogs were more popular.
But if you want to find everything on given topic written by different people that's not such an easy task. I feel like it should be solved soon by machine learning and evolution of search engines, but you still have the problem of which authors (or inevitably bots) do you actually want to see. This can be solved with a global web of trust.
Neither does keeping large amounts of well formatted documents privately. I can't hold myself accountable unless its public, and easily accessible with a search engine. Notes are primarily to break down topics and cement my understanding of it
Maybe this is just me but its pretty convenient to just type "name-of-article-you-made or name-of-video-you-made" on google and then get the files you've made.
Tiddlywiki's maintenance cost and learning curve / ability to create notes efficiently and effortlessly is not there to me. I've tried picking it up a dozen times in the last few year. A good notetaking app should get out of your way entirely, and only add a small cost of maintenance for the larger amounts of benefits you reap from it. Everything needs to be visible at a glance, with nothing hiding behind obscurity
Something like book reviews, you can write a review on goodreads to remember your opinions and thoughts were. You can bookmark things and use readwise to autosync and send you email reminders of things highlighted / quotes
Understanding is more important than recall. The brain does a great job
at making connections and dumping what's not important. The important
stuff gets absorbed like muscle memory. Even if it's not at the tip of
the tongue, it's part of the knowledge borg and emerges at the right
time.
Total recall might not even be possible. Information is relative. It
transmits different messages to different people. Each of us is
constantly changing, so the information also changes. Whatever thing
that the information was at one time, that thing rots as soon as it's
saved (same words, different thing.)
The rational brain likes to collect stuff and do busy work. Thank
goodness for the emotional brain which gets tired, bored and concludes
with "this is stupid" before nudging the rest of the brain to move on to
something else.
Not sure what the point of my comment is. When I want to access
information, I just Google it. Also, it's important to publish stuff.
Get the work in front of people for feedback. If it's not paying some
sort of rent (fighting off some other higher value of something to do)
then it's just cargo-culting. Much better to pass the time by going
outside to play and get in trouble like we did when we were South Park
age.
In a previous job as a presales engineer, I kept notes of prospects and customers in a TiddlyWiki. When I left, I handed the file over to my replacement. He told me after a few years that the "wiki" was of great help to him.
I looked into Tiddlywiki before but it seemed too involved to maintain easily and overkill for my use case. I have recently found https://www.notebooksapp.com/ and am in the process of converting all my desperate notes and documents into it using the internal linking to create my own kind of wiki.
Everything is plain text, has markdown support, apps on most platforms, ability to automate things for everyday use, and easier to use overall.
I was wondering if it was the same project I remembered! I used to use it in high school, with its stored on a USB stick that i'd carry around on my keys. Was pretty useful at the time, wouldn't want to carry around a USB stick now, but using dropbox is interesting.
That said, the list of literally 20 different ways of storing your Tiddlywiki data is user-hostile. Don't tell me that you have a Node server and a PHP server, just give me the easiest way to self-host, how to use Dropbox/Google Drive, or perhaps one more option. You can include a link to "other options", but don't put them front and center.
Even open-source tools that appeal to us nerds need some attention to marketing.
Once you're seeing the page you have it all. Click the "Save..." button to keep a local copy with any edit you've made. If you right-click and "save page" you'll get the original content only.)
TiddlyWiki is great, but I really need is something like Notational Velocity but everything is stored in a single html file (with .js embedded of course), so that it's very portable.
https://www.notion.so offers an excellent balance of power & simplicity. Definitely worth a try for those who prefer to visualize the connection between different projects. Shines in long-term planning & wiki knowledge collection.
After TiddlyWiki classic with tons of plugins, I used SpringPad while it lived, then Evernote but markdown was able only via browser addon (Markdown here or something). OneNote never suited for my needs and finally settled down with Quip.com. It is like TW with all fancy plugins + live editing...
A text file formatted as markdown and a text editor is an easily searchable flat wiki. After having tried _a lot_ of stuff I can say that nothing beats it on my usecas e.
[+] [-] mih|7 years ago|reply
- Importing from Evernote (.enex files)
- Cross-platform support (Win/Lin/Mac) + Mobile apps (ios / Android)
- Synchronization (Dropbox, Onedrive, Nextcloud, WebDAV, Filesystem)
- Support for encryption
- Webclipper extension (for Firefox and Chrome)
- It's FOSS, with a number of active contributors on GitHub (https://github.com/laurent22/joplin). A good bus factor and no more dependence on the whims of private organizations.
- A command line interface
- Use of Markdown. Drag and drop support for files and media in the GUI.
There are still features of evernote I miss such as inline PDFs and audio recording
[+] [-] luckman212|7 years ago|reply
[+] [-] TomDavey|7 years ago|reply
An additional benefit of using Emacs: the personal wiki can be integrated with my task-management system, which Org-Mode handles as well. Plus I can draft and edit at warp speed, having customized the native Emacs keybindings to suit me better.
Were I going to publish my wiki to the Web for others to use, I'd export the wiki to HTML with Org. But for now it's all personal.
[+] [-] danShumway|7 years ago|reply
I am also using Org-Mode and Dropbox for the majority of my notes. I really like it. In particular, Orgzly for Android works great with this system, so check it out if you want mobile notes as well.
The problem is that I also like to take paper notes, and take videos/pictures of stuff, and scan documents, and download webpages. Org-mode kinda stinks for embedding external content that isn't text? As far as I can tell.
I can link to external content, and if I export to HTML it'll show up. But... I never export to HTML, because, as you probably already know, it's way easier to read notes in an editable format. I can turn on picture rending in Org-mode, but it's not responsive, and I can't crop the pictures or annotate them with a stylus, or do any of a dozen different things that I want to do.
What I've thought about is that I really just want the ability to render HTML/CSS inside of an Org-mode buffer, and ideally to be able to set up custom CSS classes that would be applied to every snippet. Just set up a quick region, write some helper functions to compile/render the HTML, etc...
I've been thinking for a while about taking some time off of work to just try and solve the problem. Is it already solved? I know that at one point people were looking into getting webkit embedded into buffers. Did that go anywhere? I guess you can build GTK widgets for Org-mode as well? But then you lose the ability to define custom styles on the fly.
[+] [-] nextos|7 years ago|reply
I started implementing a personal wiki using MediaWiki long time ago, trying to replicate the concept of Zettelkasten. But MediaWiki is a bit too heavy and complex, even if you use a SQLite backend. Furthermore, it doesn't compose with my editor and version control system of choice.
I think having a wiki is essential, as the deliverable of many tasks is just a knowledge bit you really want to record. It's interesting to see personal wikis are starting to show up in GitHub and GitLab. I wish both platforms improved their org-mode support to capitalize on this trend. We can all collectively benefit from open-sourced wikis in the same way we benefit from open code.
[+] [-] Vekz|7 years ago|reply
In addition, I have an AWS lambda endpoint which listens to a SES email hook. I send emails to the SES address which the hook then appends and schedules to org files on dropbox based on email content.
[+] [-] iBelieve|7 years ago|reply
[+] [-] pixelmonkey|7 years ago|reply
[+] [-] as1mov|7 years ago|reply
[1] http://zim-wiki.org/
[2] https://syncthing.net/
[+] [-] tommoor|7 years ago|reply
[+] [-] snthpy|7 years ago|reply
[+] [-] anothergoogler|7 years ago|reply
[+] [-] zouhair|7 years ago|reply
[+] [-] another-cuppa|7 years ago|reply
[+] [-] Glawen|7 years ago|reply
I find it much easier to use than Word. My colleagues were startled by it, but they mastered it now.
The only annoying thing are:
- we need to press 2 carriage return to go to the next line
- the markup languages are never standard. we use redmine with textile which is kinda compatible with TW, but not 100%
[+] [-] hobo_mark|7 years ago|reply
- a sane way to keep a wiki on something like Dropbox (at the time, the only way to have persistence was to disable browser security and allow JavaScript to write to disk directly) or
- a service to sync a wiki between machines
Has that changed nowadays?
[+] [-] jimpick|7 years ago|reply
I haven’t tidied it up for a public release, but feel free to try it out:
https://dat-tiddlywiki.glitch.me
https://github.com/jimpick/dat-tiddlywiki
[+] [-] enugu|7 years ago|reply
[+] [-] siegecraft|7 years ago|reply
[+] [-] kickscondor|7 years ago|reply
The great thing about TiddlyWiki is that you can easily move it somewhere else and edit from there because it is just a single file.
[+] [-] _lbaq|7 years ago|reply
[+] [-] somkun|7 years ago|reply
[+] [-] ivm|7 years ago|reply
[+] [-] TeMPOraL|7 years ago|reply
--
[0] - https://tiddlywiki.com/poster/images/TiddlyWiki_TiddlerPoste...
[+] [-] OJFord|7 years ago|reply
the fish is a tiddler [0], it's consuming a mess [several entangled lines] and excreting something unified and cohesive [single line].
[0]: https://en.wikipedia.org/wiki/Tiddler
('Tiddler' is perhaps BrEng slang? I'm British, and I'd say it's slang - especially when applied not to a fish, but to something or someone small - but I don't know how widespread it is.)
[+] [-] techsupporter|7 years ago|reply
[+] [-] lxe|7 years ago|reply
[+] [-] kvakil|7 years ago|reply
[+] [-] catach|7 years ago|reply
[+] [-] eponeponepon|7 years ago|reply
At the time though, my only option was keeping it as a local file on a single machine - these days my home infrastructure is much more developed, and I think I might have more luck running it on a proper http server. Maybe I'll give it another shot.
[+] [-] cbau|7 years ago|reply
1. Perfect recall. Every little detail I read in a book/blog/article stays with me. Makes it easy to synthesize results from multiple pieces across time, which is useful when you only have a casual interest in something. (I really like downloading the cool education images/GIFs and and inserting them in articles- otherwise I don't know where I'd keep them.)
2. Reveals what I don't know about a subject. For example, whenever I start off writing a new article on some topic, the first thing I write is a definition, e.g. "A cat is an animal that ...". The process of doing that often reveals gaps in my understanding.
3. It makes me better at asking questions when I'm trying to understand something. The analogy I like to make here is that learning a second language is harder than a third language, because after learning the second you know what you need to know to understand a language. But there's no reason that should be limited to languages and couldn't apply to all things, and things themselves. Some questions I like to ask are "What is the function/uses of this thing?" "What are the parts of this thing and how are they arranged?" "How do we make this thing?" "What's the history of this thing?" "What subtypes of this thing are there?"
The downside is that it dramatically slows down my reading speed, since I now feel I need to take detailed notes, and then I often have to reconcile them with notes on other things which can be time-consuming. Considering the number of books a person could realistically read in their lifetime is limited, it's unclear if it's worth the tradeoff.
I'm curious how other people think about remembering things, and if they have a system, what tools they use. It seems unsatisfying to me to read a book and realize I'll probably forget it in four years, yet most people seem content to do so.
If anyone is interested in the specific software I use, here's the Github project: https://github.com/Ceasar/Encyclopedia. It uses restructuedText (as opposed to Markdown) for the text. I edit them using Vim. All the files are stored in Dropbox so it gets synced between my devices. A simple Flask web server renders the pages in a prettier format.
Still very primitive compared to what it could potentially be, but combined with regular Unix command line tools it's worked fine for my needs. (I like the idea of a hacker-wiki by the way, more than something like this which comes out of the box. Seems like an personal wiki designed for a power user could be way more interesting.)
[+] [-] capnrefsmmat|7 years ago|reply
(My PhD advisor used to say that a sign of learning isn't whether you remember something -- it's how quickly you can re-learn it. So I try to make it easy to find and re-learn things I need.)
Since I need to cite papers, I had to put together a system that can read BibTeX bibliographies and format them into references. I cobbled together a Hakyll config that uses Pandoc and KaTeX to turn Org files into HTML pages, with a simple chronological listing: https://www.refsmmat.com/notebooks/
I've found this useful for my own reference and to share with others -- if someone asks me about some topic I've read about, I can just send the notebook link with summary and citations.
I'd like a version that doesn't need separate BibTeX files (though that should be easy to solve with a couple scripts or some Emacs packages), and perhaps intelligent full-text search, but for the moment I like that it produces static HTML that will last forever.
[+] [-] themodelplumber|7 years ago|reply
I think I'm at or near around 800 of these, and many are very short. But no matter how short they are, they are all there because they provided me or continue to provide me with needed leverage.
I keep the bulk of the information in markdown in a Dropbox folder and also occasionally try new methods. For example, for topics that will quickly benefit from hyperlinks, I developed a LibreOffice web template and a companion PHP script that indexes these files and inserts additional CSS, variables, JS, etc. when they are served up. For searching I like Regexxer a lot, but I also use grep quite a bit :-)
On my XFCE desktop are buttons for opening a random one of these files, and for opening a random journal entry to try to harvest new models, so to speak.
And there's some paper involved here too... Can't get away from it, because paper has its own special leverage points...
I'm not concerned about memory, knowing it's a special weakness of mine. If I'm working in a context where memory is super important, my energy is best spent moving to a more sustainable context. :-) Memory is a hobby for me, a side gig for memorizing pi, that kind of simple and fun thing.
[+] [-] comboy|7 years ago|reply
Holy shit. Make it public.
The idea is fantastic. I would love to have something like wikipedia but people have separate pages on topic.
Or, in other words, if you want to find everything written by given person, why not that easy it is doable - it was more doable back when blogs were more popular.
But if you want to find everything on given topic written by different people that's not such an easy task. I feel like it should be solved soon by machine learning and evolution of search engines, but you still have the problem of which authors (or inevitably bots) do you actually want to see. This can be solved with a global web of trust.
[+] [-] swaggyBoatswain|7 years ago|reply
Neither does keeping large amounts of well formatted documents privately. I can't hold myself accountable unless its public, and easily accessible with a search engine. Notes are primarily to break down topics and cement my understanding of it
Maybe this is just me but its pretty convenient to just type "name-of-article-you-made or name-of-video-you-made" on google and then get the files you've made.
Tiddlywiki's maintenance cost and learning curve / ability to create notes efficiently and effortlessly is not there to me. I've tried picking it up a dozen times in the last few year. A good notetaking app should get out of your way entirely, and only add a small cost of maintenance for the larger amounts of benefits you reap from it. Everything needs to be visible at a glance, with nothing hiding behind obscurity
Something like book reviews, you can write a review on goodreads to remember your opinions and thoughts were. You can bookmark things and use readwise to autosync and send you email reminders of things highlighted / quotes
[+] [-] gexla|7 years ago|reply
Total recall might not even be possible. Information is relative. It transmits different messages to different people. Each of us is constantly changing, so the information also changes. Whatever thing that the information was at one time, that thing rots as soon as it's saved (same words, different thing.)
The rational brain likes to collect stuff and do busy work. Thank goodness for the emotional brain which gets tired, bored and concludes with "this is stupid" before nudging the rest of the brain to move on to something else.
Not sure what the point of my comment is. When I want to access information, I just Google it. Also, it's important to publish stuff. Get the work in front of people for feedback. If it's not paying some sort of rent (fighting off some other higher value of something to do) then it's just cargo-culting. Much better to pass the time by going outside to play and get in trouble like we did when we were South Park age.
[+] [-] hboon|7 years ago|reply
In a previous job as a presales engineer, I kept notes of prospects and customers in a TiddlyWiki. When I left, I handed the file over to my replacement. He told me after a few years that the "wiki" was of great help to him.
[+] [-] agentdax5|7 years ago|reply
Everything is plain text, has markdown support, apps on most platforms, ability to automate things for everyday use, and easier to use overall.
Also I just can’t stand the idea of “tiddlers”.
[+] [-] moioci|7 years ago|reply
[+] [-] jtl999|7 years ago|reply
Glad to see it's still here.
[+] [-] Milner08|7 years ago|reply
[+] [-] hyperpape|7 years ago|reply
That said, the list of literally 20 different ways of storing your Tiddlywiki data is user-hostile. Don't tell me that you have a Node server and a PHP server, just give me the easiest way to self-host, how to use Dropbox/Google Drive, or perhaps one more option. You can include a link to "other options", but don't put them front and center.
Even open-source tools that appeal to us nerds need some attention to marketing.
[+] [-] carapace|7 years ago|reply
Live demo: https://calroc.github.io/HulloWurld/Hullo.html
Once you're seeing the page you have it all. Click the "Save..." button to keep a local copy with any edit you've made. If you right-click and "save page" you'll get the original content only.)
Repo is here: https://github.com/calroc/HulloWurld
It's just a simple experiment, nothing fancy.
[+] [-] rwbt|7 years ago|reply
[+] [-] ttroyr|7 years ago|reply
[+] [-] igorp74|7 years ago|reply
[+] [-] rb808|7 years ago|reply
[+] [-] galfarragem|7 years ago|reply
[+] [-] rmu09|7 years ago|reply
This TiddlyWiki-variant stores documents in the browser (pouchdb) and can sync to a couchdb-server.
[+] [-] platz|7 years ago|reply
there is a newer version, but I think it's worse than the old one.