My logseq-inspired edition of TW: Lithic.uk

Showcase
, ,
#1

Hello All,

I recently fell down the tiddlywiki rabbit hole after exploring various options in the PKMS software sphere; I was using these software’s to help organize my studies as an Electrical Engineering Student. I first ran into Notion.so and Microsoft Loop in the wild but didn’t adopt them, I started using Affine 2 years ago, then Logseq; but kept wishing things worked a bit differently in each case.

Then I stumbled upon tiddlystudy a few weeks ago and realized it was like 95% of what I wanted out of a PKMS, so I started playing around seeing if I could get in the final 5%.

The result of this tinkering is Lithic PKMS

lithic.uk

It’s still rough around the edges and still needs a good bit of polish and also I haven’t fully adopted the TW ‘way’ of doing things yet; but I am fairly happy with it’s current state and wanted to share it with you all.

I’m looking for any suggestions or feedback you may have, as I am very new to using and hacking TW.

Eventually I would like to do a refactor and use a more programmatic ‘package-based’ approach to building out the Lithic base edition instead of just manually cobbling stuff together; but this will also take a bit of effort on my part to learn the tooling.

Thanks in advance for taking the time to read my post and provide any feedback you may have.

-Xyvir

2 Likes
#2

It’s looking great to me. I love the storage options. I’m going to have to dig in to see how you did that. I don’t really use TW (or anything) as a generic note-taking app. So I’m probably not in the intended audience. But I can still appreciate it.

I noticed only one bug: I was just poking around opening and closing things, and ended up with a RSOE (“red screen of embarrassment”) with this message:

Uncaught Error: Minified React error #409; 
visit https://react.dev/errors/409 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

It only happened once, and I can’t tell you even approximately what I did. I know I was trying to figure out how to get the Whiteboard node back from edit mode to view mode (which I did eventually figure out) but I had resorted to some random clicking. Something went wrong. I’ve tried to replicate this and haven’t been able to. Sorry.

If you’re anything like me, that “eventually” may be long off. There’s always some new feature to incorporate, which is always more bright and shiny than clean-up work! But good luck to you; I know that when I do finally get to it, it makes me feel much better about my project.

1 Like
#3

Thanks for the comments!

So I ‘cheated’ that part by using TiddlyStow; which is basically a small wrapper web app that uses Chrome’s Filesystem API access to inect a saver that can get per-session browser permissions to modify your local tiddlers.

So lithic.uk/index.html serves a branded version of TiddlyStow which then can retreive and load a fresh lithic.uk/lithic.html tiddler into it.

I had added that ‘revert’ button playing around earlier with local webrowser storage plugin (which i liked but found annoying i couldn’t easily clear out temp changes), but it also served to get back to the launcher so that was kind of a serendipitous design lol.

Thanks for checking it out!

1 Like
#4

I want to apologize in advance for some of the branding choices, specifically referring to the downloaded wikis as ‘Liths.’

To be clear: I am not doing this to plagiarize or dilute TiddlyWiki’s own brand. I absolutely love the TiddlyWiki architecture, but I admit that coming from other tools, the convention that ‘literally everything is a tiddler’ was mind-bending for me at first.

Since Lithic targets people migrating from Logseq, I have been toying with retooling some of the jargon. My goal is to make the immediate experience less abstract for new users and lower the barrier to entry.

Finally, regarding the name ‘Lithic’: A lot of modern PKMS tools come rolled up with paid, hosted syncing. While that is fine for some, I built this for users like myself who prefer to own their data locally and distribute it across devices exactly how they see fit.

I wanted to tie the branding directly to that concept of a solid, standalone object, while also solving a semantic overlap. In the standard convention, ‘TiddlyWiki’ is often used interchangeably to refer to both the software ecosystem and the specific HTML file. I am using ‘Lithic’ to refer to the system/environment and ‘Lith’ to refer to the local file—the distinct artifact that you actually own.

1 Like
#5

Attractive appearance. Good feature set.

I also encountered a red screen and temporary unresponsiveness. After saving, the issue resolved itself.

1 Like
#6

Yeah I think it has to do with the whiteboard plugin, it isn’t playing 100% nicely with streams yet