orgdown VS TiddlyWiki

There are two reasons why I call Org mode standardized.

> I imagine there aren't really various flavors of Org Mode, but that doesn't make it standardized.

All the implementations that call themselves org-mode follow the conventions set by the canonical implementation - the Emacs org-mode. While this may not sound like a good reason to call it standardized, the practical implication is a vast difference from what you get with various markdown flavors. In the latter case, the only way to make sure that your markdown is correct, is to test it with the target implementation.

The second reason is that there is an actual effort to standardize org-mode - called Orgdown [1]. Org-mode is already more or less uniform across implementations. This effort tries to write it down as a reference. Markdown has a similar effort called CommonMark. But if you want to know why it's different, you have to look at the history of why it isn't called 'Standard Markdown'.

[1] https://gitlab.com/publicvoit/orgdown

And yes, at least my setup fulfills all of your requirements and much more. For starters, I can add tags, date- and timestamps everywhere, generate "agenda" views for days/weeks/months/... which collects all those time-related items and visualizes them, I can link emails/urls/... and links to files which I tag as well, I can search through search strings or regex to find meta-data on files/notes/events/... and it's all in the most versatile file format possible: plain UTF-8 text files containing simple orgdown syntax, the most beautifully designed lightweight markup language (LML) there is IMHO.

Are you aware of orgdown?

If you want to parse Orgdown files yourself, expect to invest some time in setting up a testing environment.

I think we've got a misunderstanding here. Text files (in this case in orgdown syntax format) are files that contain the information in its original form: characters, words, sentences. So you only need a software that lets you open a text file to view it. If you want to modify the information stored in the text files, you need an application that lets you modify text files. In case of orgdown, you can find options on https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org or choose any non-syntax-specific editor of your choice.

So the links are working in Markdown? So Markdown-export is working and your issue starts with the conversion from Markdown to Orgdown?

Well, the difference is that Orgdown, the syntax of Org mode for GNU Emacs is a Lightweight markup language while HTML is a more complex markup language.

Since your notes are in orgdown format, you may use any compatible app that understands to read and probably write orgdown. One of them is GNU Emacs with its org-mode.

I'm thinking of a screen that pops up when booting Emacs that only shows the files I was working on recently in large font (maybe as buttons to click on). The file extension should be hidden, so that I may use it with Orgdown files that have long, descriptive file names (most probably within the same directory).

> What does ownership mean here?

It means owning the code and the data. With webapps, the code and data are hosted and owned, the users do not own the code, cannot run it independently. This is a clear dileneation between owner and user, and the owners can use that clear line to create artificial scarcity of various kinds. (The most popular being the subscription SaaS model). It's also easier to defend your IP since end users never see your binaries.

I like to make my software single html files whenever possible. People can just save them and run them locally. Havent met anyone who cares yet though.

I like that idea a lot, and I care. I think others care, but yes, it's a niche interest. Take a look at https://tiddlywiki.com/ for an example of a fairly successful project that uses the single html format running locally. However it suffers from limitations on File|Save which often requires a separate runtime of some kind to support.

Another project that approaches this ideal is https://redbean.dev/, @jart's tiny, performant, featureful single-file webserver. In this case the "single file" is a server executable + zip whose state must be updated on the command-line, but I think hits a sweet spot in terms of practicality, and a global minima when it comes to minimizing dependencies. (Redbean bundles SQLite and Lua so it's also possible to do through-the-web state updates as in a traditional webapp.)

My own project, Simpatico, aspires to be something along these lines. Eventually your browser tab is both a client and server process, connecting via websockets to other connected browsers, storing all state locally. I call this pattern "monomorphism", a play on the "isomorphic" javascript SPA. The server[2] is currently written in ~1 node file, but eventually I would like to port to redbean (and greenbean, the websocket version of redbean, but it isn't quite ready yet). The server grew several features to support a fast, practical BTD loop using markdown[1], and safe, performant execution on the public internet[2], but ultimately I'd like to pare it down to serving a single html file and allow the connected clients to provide all diversity of experience. I've used it to explore all kinds of browser apis, from crypto[3] to svg[4] to writing my own libraries (combine[4] and stree[5]). And it's all running locally, and easily hosted on a $5 VPS, and its all open source.

1 - https://simpatico.io/lit.md

2 - https://simpatico.io/reflector

3 - https://simpatico.io/crypto

4 - https://simpatico.io/combine

5 - https://simpatico.io/stree

I use TiddlyWiki. It's a portable editable wiki that doesn't require a web server or web hosting. You open it from your computer, edit it, and save it. You get all of the linking that you'd expect to see in a wiki, and it's super readable and easy to use.

It is a single-HTML-file TiddlyWiki instance that runs in a web browser (offline as well as online), meant to be downloaded and stored wherever suits you best. Everything that you see when working in BASIC Anywhere Machine (everything that makes "BAM" work as an IDE and all BASIC programs) exist in the one HTML file.

TiddlyWiki still works as intended: https://tiddlywiki.com/#GettingStarted but there are so many different clients to run on. Mobile or Desktop ? What OS? What Browser?

This effort https://val.packett.cool/blog/tiddlypwa/ is remarkable as the mobile side of saving is not as robust as on the desktop side of things and there is a scaling limit on performance as the number of tiddlers grows. Also the syncing between tw documents between different desktop/mobile clients can be a challenge with diffing.

Since then I've moved back to plain vanilla vim for a wiki (map gf :tabe ) but tw.html is still good for data other than plain text and TiddlyPWA https://tiddly.packett.cool/ is a great effort to revisit TiddlyWiki again.

You should check out TiddlyWiki as it’s designed around the concept that small linkable notes are the best way to organize.

https://tiddlywiki.com/

It’s html based so you can access it in the same way you would access a website but it can be locally stored. Saving is a bit tricky but there are multiple solutions detailed on their site. https://tiddlywiki.com/

Hi, you can use tw on nodejs with npm package tiddlywiki....