timeline VS TiddlyWiki

My timeline thing. It gathers all my crap and puts in onto a timeline. It's a more fine-grained version of scrolling to a specific date on my photo stream.

https://github.com/nicbou/timeline

It serves no purpose, but somehow it attracted one contributor.

It's pointless on purpose. It's the thing I work on when I want to forget about work, and build purely for myself.

Google Drive as a first line of defence. It's been solid for a really long time.

I also run hourly rsync backups to my home server, and propagate them to a Hetzner file storage server. This is done by my timeline thing [0]. The timeline thing backs up files from multiple devices, but also geolocation, social media posts, and other data I consider valuable. It's extensible, so I can add new inputs/outputs as needed.

Whatever your backup strategy is, consider the following threats:

- Your files are held hostage by ransomware, and the damage spreads to your backup

- Your house is destroyed by fire

- You lose your 2FA device

- You are locked out of your Google/Apple/Microsoft account

- You are incapacitated, and someone needs to take over

I have 4 of those factors covered. I am working on the last point.

[0] https://github.com/nicbou/timeline

My own timeline thing.

It hosts all of my data plus my personal diary. I update it at least once a day. My photos, backups and geolocation are automatically uploaded to it.

https://github.com/nicbou/timeline

My home server gets a lot of use too. It's mostly my own code, plus Transmission.

https://github.com/nicbou/homeserver

I also have a few lines of code that take my browser's search queries and routes them according to keywords. Browsers do this natively now, but old habits die hard. Every search query goes through it.

I added RSS to my websites, because my timeline thing (https://github.com/nicbou/timeline) uses them to retrieve posts from my websites.

However, I see the death of RSS as the symptom of a larger problem: when platforms get big enough, they restrict access to their data. RSS feeds disappear, but so do other machine-readable endpoints. If it wasn't for GDPR, there would be no way to export that data. GDPR gave us clunky one-time exports, but even those are often incomplete.

The industry has a strong incentive to kill RSS, since the readers can strip the valuable bits (content or data) from the business bits (analytics, monetisation). RSS users are hard to count or monetise.

This is a battle worth fighting, but it's not one you should expect to win.

https://github.com/nicbou/timeline

It regroups my personal data, and displays it on a timeline. Sort of like if Google Photos also included reddit posts, personal journal entries, text messages and other slices of life.

I do it both as a way to back up files and photos, and as a way to keep an enhanced journal.

> 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....