“Everyone who had serious philosophical conundra on that subject just, you know, died, a generation before. The Bitchun Society didn’t need to convert its detractors, just outlive them.”
@prologic@twtxt.net Ok.. so using NaCL boxes. yeah its just a combo of using secretbox with a generated key/nonce. and then using the pubkey box to encrypt the key/nonce for each device.
@prologic@twtxt.net sender generates an AES key encrypts message. gets the device list for user and encrypts key for each device. sends the encryptedkeys+cypertext.
@prologic@twtxt.net for encryption. we can have browser/app generate ec25519 keypair. store the private on device and add pub to list of devices for the user on pod.
with some scripting, I could probably use my upcoming !weewiki !zettelkasten as a drop-in replacement for !twtxt, and then generate the twtxt file. however, I think I am going to keep them separate for the time being. let them both grow to serve different purposes.
finally finished all the initial ugen documentation. everything now has a sentence or two. the generated page can be accessed from the ugen wiki page [[/proj/monolith/wiki/ugens]] #updates #monolith
I’m hoping to build a phasor-to-clock signal generator, which divides up a phasor into an arbitrary number of ticks. Using a global phasor as a global clock would allow for interesting polyrhythms, as well more flexible precision in sequencers. It’s also closer to how human-based conducting works. #halfbakedideas
the fe language by rxi would make for a great frontend for generating txtvm code maybe #halfbakedideas
This morning I had this really weird notion of building a generative podcast complete with musical interludes and asemic speech using a speech synthesizer. It’d be interesting to have “interviews” with two distinct vocal characters. #halfbakedideas
asemic script done in contextfreeart: [[https://www.contextfreeart.org/gallery/view.php?id=945]] #links #generative #asemic #graphics
generative bad handwriting: [[https://avinayak.github.io/programming/art/2020/09/18/p5-strokes.html]] #links #generative #asemic #graphics
randoma11y is a color generator that generates two colors and scores them using WCAG system for accessibility: [[https://randoma11y.com/]] #links #color
automatically generated #TeX equations implemented in !sndkit
thinking about implementing some noise generators for !sndkit. A chaos noise generator that leverages numerical instabilities in IEEE floating point, and a 1-bit linear feedback shift register noise generator based on NES audio. #sndkit #halfbakedideas #dsp
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]].
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.
statically generated my twtxt feed here: https://pbat.ch/wiki/twtxt.html. learning how to be social on this thing comes next.
testing out auto-generation of twtxt wiki page now
@kas@enotty.dk the only thing I can think is that people are finally re-figuring out that static sites are really fast because the content doesn’t need to generated on the fly. I noticed there were a lot of static content generators out there.
@nblade@nblade.sdf.org I could probably put something together, but I went this route originally because existing generators felt like they took too much control from me over the exact output. I want very small, static pages I can throw behind nginx, and I want to know exactly what the contents are. My current mess of spaghetti Racket is getting hairy since I’m halfway through an unfinished rewrite I started a while ago and forgot about, but at least I know exactly what it’s doing.
I’m trying to decide whether soldiering on with the messy codebase of my homegrown site generator is worth it or if I should redo my site in a more established tool.
@phil@philmcclure.duckdns.org I actually just started a new job working on a frontend for Hugo (and other static site generators).