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

a copy of the btprnt program can be found at the !btprnt_program page

while eventually I hope to get all of literate org parts of !monolith posted online as a self contained !weewiki, I’ve decided to post little pieces as self-contained documents. here is a copy of !trigvm, the toy VM used to power a rhythmic computer-sequencer controlled entirely from the !monome_grid

some example graphics added onto my !btprnt page.

this rhythm machine I’m working on for !monolith has finally given me an opportunity to crack open and use Hacker’s Delight. This morning I needed to find a way to count the number of active bits, and there’s a whole chapter dedicated to it :)

The Content Creator at Innsmouth Trail #lovecraftian #halfbakedideas

penning out the structure of my current !music_software_ecosystem

a microblogging creative coding platform like dwitter, but for sound. users would be encouraged to remix, the output of one persons code would become the input of the new code. only text would be stored on the server, with audio rendered client-side. to save on time, there could be caches of frozen audio for remixes. #halfbakedideas

the natural color system: when in doubt, these are some pretty good functional colors. [[https://en.wikipedia.org/wiki/Natural_Color_System]].

a music sequencer, but for producing continuous gestures instead of discrete steps. have it be clocked with an external source so it can play well with others. perhaps build a notation system around it. #halfbakedideas

!txtvm, a text-based toy VM, used to run tiny domain-specific bytecode programs using only printable ascii characters. #halfbakedideas

a 1-bit synthesizer and sequencer for the !arduboy #halfbakedideas

I really want !btprnt to be integrated into !weewiki somehow. Both can speak !janet, and I already figured how to embed PNG images inside of an HTML document. In small doses, it could be fun. #halfbakedideas

collecting my half-baked ideas over at !halfbaked

the idea would be to build and share tiny 6.5 bit programs encoded as printable ascii characters. this could then in turn be read by a virtual computer to do things like paint a picture or compose a piece of music. #halfbakedideas

a 6.5 bit fantasy computer, whose bytecode representation can be represented entirely as printable ascii characters. The first 6 contain standard data space, with the 7th bit used to represent one of 32 values. #halfbakedideas

links web browser is surprisingly good, especially when you can get it in graphics mode: !links_browser

@eli_oat@txt.eli.li thanks for reading my wiki! janet is pretty cool right? happy noodling.

goodbye blogging? hello wiki-ing and micro-blogging? [[/blog/posts/2020-07-27-goodbye_hello.html][a new blog post suddenly appears]].

built a little script for looking up IDs in twtxt tweets: !twtxt_search. Going to use it as a way to look up and reference specific tweets in my wiki.

parsing expression grammars coming in real clutch right now. punctuation can now exist after wiki reference tags. Thanks !janet!

I’m so close to being able to get my literate programs written in !worgle converted into a self-contained !weewiki. #literateprogramming #worgle #weewiki

testing #hashtags

I’ve been actually thinking about introducing a ‘#+RELAX’ tag in !worgle that would explicity turn off strict mode, allowing literate programs to be written more casually.

weewiki uses a custom org markup parser written in ANSI C to render the HTML. No emacs needed! my hope is to introduce a user-defined callback that can process these to allow for custom meta-commands.

a new fix to !weewiki will ignore all org-mode command strings by default. Now things like PROPERTY tags won’t show up in the output.

some future plans for my !norns

first night on the new tatami mat + futon was a success. very comfty.

@hjertnes@hjertnes.social are you using emacs as twtxt client or something? does it render the org markup for you into links?

@lucidiot@tilde.town very cool idea! may have to try something like that at some point…

updated the print style of the feed. date + message are no longer on separate lines.

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

attempting masto verification @!(prin “with this link”)!@.

updating my wiki index, so some pages are not going to be featured there anymore: !MIDI_sucks !sample_curation !howyousay !sixtycolumnrule

documenting my experiments with twtxt/weewiki integration at the !twtxt_playground

Inline Janet means I should be able to make calls to functions defined in the config file. For example, the =ref= function is how I usually make wiki reference links. This @!(ref “wiki_index” “link right here”)!@ should take you to my automatically generated weewiki index of all the wiki pages.

Wow! Inline Janet code does work. What a happy accident. Will use with the upmost restraint.

Technically not org, but weewiki org. So this means that I might be able to run inline Janet code? @!(prin “Hello from Janet.”)!@

I actually think my org markup might work here. Testing a [[/proj/patchwerk][link]].

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

I’m using a wrapper around txtnish called !say to make it easer to tweet stuff.

a new twtxt/weewiki feature: any word starting with ‘!’ will translate to an internal weewiki reference in my HTML renderer. Example: here is my !wiki_index

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.

there are also things like using #hashtags, which could be a useful tool to coordinate with weewiki somehow.

in particular, twtxt provides timestamps. weewiki doesn’t really track the passage of time. it only wants to be a key/value database with org markup.

my hope is that I’ll be able integrate this more with my wiki somehow. I think they are a good pairing.

all I have to do is hit “say”, write a few bits of things, and then hit ENTER. much easier than using txtnish directly.

made a script that simplifies making twtxt entries. let’s see how well it works…

building a http server into weewiki has been more useful than I initially expected

coss a toin to ur witchr