a decentralized community !zet. individual zet feeds could be managed using something like git/git submodules, then built locally into self-contained SQLite files. zet items would be referenced by their zet nickname and UUID. #halfbakedideas

SQL(ite) and zettelkastens as a medium for non-linear story telling. #halfbaked

user-defined order in SQL [[https://begriffs.com/posts/2018-03-20-user-defined-order.html]] #sql #links maybe something that can be adapted to !sqlite?

with the addition of crate in weewiki, I finally found an opportunity to add some words to the !sqlar page #updates

plans for weewiki: a zettelkasten-like interface, a microblogging platform inspired by !twtxt, and some utilities for managing collections of SQLar archives. #updates #halfbakedideas

huh. it seems that dumping + gzipping a SQLite database can sometimes have better compression than gzipping the SQLite database directly. cool. #sqlite

A fragment of my !monolith program has been woven to a !weewiki from !worgle using !sqlite. Find it for now at [[/proj/monolith/wiki/][the monolith project page]].

Testing @!(ref "weewiki_sql" "page markers" "iterate_over_values")!@.

!worgle -> !sqlite -> !worgmap -> !weewiki is kinda working?

It turns out that fts5 is enabled by default on SQLite! My twtxt2sqlite generator has been updated to use fts5. Now I can do full text search on all my twtxt tweets. I have implemented a related-tweets box in the !twtxt_playground as a proof-of-concept. More info on fts5 can be found at [[https://www.sqlite.org/fts5.html]].

here is the script I use to convert my twtxt feed into a SQLite database: !twtxt_sqlite

a unique thing I do with my twtxt feed is convert it to a SQLite database. This, combined with the Janet + SQLite scripting abilities available in SQLite, could provide interesting metrics and insights over time.