I want to somehow use my monome grid to build out coarse vocal tract shapes for a physical model like !voc or @!(sndkitref “tract”)!@. 16 diameters with 8 steps of resolution, or 32 diameters with 4 steps of resolution. #halfbakedideas

created the compudanzas page on patreon: support us and help us achieve the goal of having this dream project as our main activity! | https://compudanzas.net/support.html

I dislike it when people use two en dashes for an em dash

I’m back on twitter, kind of. I’m only using it to mirror posts from my mastodon account: [[https://twitter.com/yesthiswaspaul]].

Surely people have thought about this, but is it so useful to include proofs in textbooks?

FOLLOW: @default@txt.sour.is from @xandkar@xandkar.net using tt/0.22.0

FOLLOW: @stats@txt.sour.is from @xandkar@xandkar.net using tt/0.22.0

FOLLOW: @twtxt@txt.sour.is from @xandkar@xandkar.net using tt/0.22.0

FOLLOW: @xuu@txt.sour.is from @xandkar@xandkar.net using tt/0.22.0

@antonio@twtxt.net @mckinley@twtxt.net @prologic@twtxt.net i did use Wireapp for a little bit. it is pretty polished and doesnt rely on phone numbers for connecting. The ownership had some shady changes but im not sure it ever led to issues in the security model.

FOLLOW: @xuu@txt.sour.is from @sdk@codevoid.de using txtnish/0.2

FOLLOW: @xuu@txt.sour.is from @reednj@twtxt.xyz using twtxt/1.1

FOLLOW: @stats@txt.sour.is from @bot@www.linguee.com using Linguee Bot

Good idea. Plan 9 sets $NPROC on boot to the number of cores, so other things can use it. mk will dispatch things in just that way.

@xuu@txt.sour.is Is this of any use? https://libretranslate.com/ – Congrats on the new job!

FOLLOW: @default@txt.sour.is from @xandkar@xandkar.net using tt/0.21.0

FOLLOW: @stats@txt.sour.is from @xandkar@xandkar.net using tt/0.21.0

FOLLOW: @twtxt@txt.sour.is from @xandkar@xandkar.net using tt/0.19.1

FOLLOW: @xuu@txt.sour.is from @reednj@twtxt.xyz using twtxt/1.1

FOLLOW: @xuu@txt.sour.is from @xandkar@xandkar.net using tt/0.19.1

FOLLOW: @xuu@txt.sour.is from @xandkar@xandkar.net using tt/0.15.0

Someone brought us pie for Pi Day. 💯

using a forked version of ed to do live coding #halfbakedideas

FOLLOW: @xuu@txt.sour.is from @codebalion@twtxt.prismdragon.net using txtnix/0.07

Hrm, that would’ve been csh probably, or tcsh if you were lucky. But Plan 9 uses rc, which is so lovely I use it everywhere.

FOLLOW: @xuu@txt.sour.is from @reednj@twtxt.xyz using twtxt/1.1

No, totally not useful. 🤣 I mean, the finger protocol is pretty trivial, and it’d be fun to add, but doesn’t replace anything you’re doing.

This was macOS. I don’t really use gnu. Of course, it’s also not on Plan 9, the system I know best.

I have been using Unix for 25+ years and I just learned about the status character in shells (often ^T). Huh.

Possible climate change intervention: Improve performance of widely used but neglected open source projects.

@thewismit@twtxt.psynergy.io @jlj@twt.nfld.uk in old school terminal jargon the ^H means control H or the sequence used in some terminals to indicate backspace. The “joke” is that the term failed to interpret it correctly and you can see the partially typed word before they changed it.

feels good to be using tmux again more regularly. ansi-term in emacs is well, special.

Hey @xuu@txt.sour.is another mention that didn’t render ☝️

@thewismit@twtxt.psynergy.io Hey! It’s easy. Just install the twt CLI with something like:

go get github.com/jointwt/twtxt/cmd/twt/...

Then use it in some hooks/scripts to post some content to your Pod.

The keys that have some use would be nick, url/feedurl, avatar, lang

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

trying to get myself to reach for !links browser instead of firefox for locally testing my wiki. For the most part, it really doesn’t need the heft of firefox. When links -g is used, it really really doesn’t need firefox.

💁‍♂️ If you’re ever on a UNIX machine of some kind without any useful networking utilities like ip or ifconfig, fear now! You can view the network topology of the Kernel by just doing:

cat /proc/net/fib_trie

😲 #Linux #Tips

FOLLOW: @xuu@txt.sour.is from @hxii@0xff.nu using picoblog/0.1.1

@jlj@twt.nfld.uk “Wow. I think much of what drew me to zettlekasten – and then letting it languish :-( – really belongs in Anki.” i have only used SRS for ~3 months now, so I’m not sure how long i’ll continue

new algorithm in @!(ref “sndkit”)!@: @!(sndkitref “phasor”)!@ generates a normalized periodic ramp signal, typically used for table-lookup oscillators.

@hxii@0xff.nu There is another twter that uses !<wikiword wikiaddr> or !wikiword for their wiki intigrations.

Mirroring my private sites on the IPFS network. Generating my static site using 11ty

FOLLOW: @xuu@txt.sour.is from @thewismit@twtxt.psynergy.io using twtxt/0.1.0@6379df1

FOLLOW: @xuu@txt.sour.is from @asdf@0.0.0.0 using twtxt/0.1.0@51889ee2021-01-26T21:02:50Z FOLLOW: @xuu@txt.sour.is from @asdf@::1 using twtxt/0.1.0@0b6d6822021-01-27T18:29:57Z FOLLOW: @xuu@txt.sour.is from @asdf@0.0.0.0 using twtxt/0.1.0@bea2d23

added recipe I use for brown sugar cinammon poptarts: !poptarts #food #breakfast #baking

FOLLOW: @xuu@txt.sour.is from @asdf@::1 using twtxt/0.1.0@174baf7

FOLLOW: @xuu@txt.sour.is from @asdf@0.0.0.0 using twtxt/0.1.0@174baf7

FOLLOW: @xuu@txt.sour.is from @asdf@::1 using twtxt/0.1.0@174baf7

FOLLOW: @xuu@txt.sour.is from @asdf@0.0.0.0 using twtxt/0.1.0@9b57da3

FOLLOW: @xuu@txt.sour.is from @alice@twt.nfld.uk using twtxt/0.1.0@0f0603f

I’m finding the microblogging format to be really useful for working out ideas.

@prologic@twtxt.net @thewismit@blog.thewismit.com () Ya I get that error a lot. I mostly use the web on mobile as a result.

@prologic@twtxt.net @thewismit not sure.. im using Caddy instead of nginix

FOLLOW: @xuu@txt.sour.is from @thewismit@blog.thewismit.com using twtxt/0.1.0@b7f7c09

FOLLOW: @twtxt@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@6987434

FOLLOW: @stats@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@6987434

FOLLOW: @xuu@txt.sour.is from @asdf@::1 using twtxt/0.1.0@90d1c09

@prologic@twtxt.net that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM.

but having a federation of IRC servers would be interesting for realtime twt propagation.

US declining quickly, europe slowly?

FOLLOW: @xuu@txt.sour.is from @jlj@ctrl-c.club using twtxt/1.2.3

FOLLOW: @xuu@txt.sour.is from @adi@46.23.94.13 using twtxt/0.1.0@7098fcf

FOLLOW: @stats@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@9d7b86c

@prologic@twtxt.net sounds about right. I tend to try to build my own before pulling in libs. learn more that way. I was looking at using it as a way to build my twt mirroring idea. and testing the lex parser with a wide ranging corpus to find edge cases. (the pgp signed feeds for one)

@prologic@twtxt.net yeah it reads a seed file. I’m using mine. it scans for any mention links and then scans them recursively. it reads from http/s or gopher. i don’t have much of a db yet.. it just writes to disk the feed and checks modified dates.. but I will add a db that has hashs/mentions/subjects and such.

I just built a poc search engine / crawler for Twtxt. I managed to crawl this pod (twtxt.net) and a couple of others (sorry @etux@twt.u53.us and @xuu@txt.sour.is I used your pods in the tests too!). So far so good. I might keep going with this and see what happens 😀

@felixp7@twtxt.net “Yo, crypto-heads. Encrypted communication doesn’t protect your privacy. Laws …” I guess crypto-heads are often happy with acknowledging this, but also arguing that e.g. deniable crypto is a useful way out here (and, of course, just doing illegal stuff if it gets really rough).

FOLLOW: @xuu@txt.sour.is from @niplav@niplav.github.io using txtnish/0.2

@prologic@twtxt.net I am trying to cut costs, so I deleted all my Digital Ocean droplets. For a month I will be using a free s390x VPS, so I needed to adapt some of my Docker images, scripts and configurations for that architecture. Also took another chance with Traefik Proxy, I ditched it long ago for nginx-proxy, but this time I made it work. #h5nn5tq

@prologic@twtxt.net sure. I don’t use signal much because I have to disclose my personal phone. Telegram? https://www.t.me/xypheri

FOLLOW: @xuu@txt.sour.is from @lyse@lyse.isobeef.org using twtxt/1.2.3

@adi@twtxt.net @prologic@twtxt.net using regex. which can be a rather inexact science ;)

the !zet I have written for my wiki is probably going to end up replacing what I’ve been using twtxt for these past few months. this means less spam here. you’re welcome.

If you’re an average man, my calculation tells me that freezing your sperm & getting a vasectomy is worth ~ in expectation (https://niplav.github.io/notes.html#Vasectomy–Sperm-Freezing-CostBenefit) (in the US, caveat caveat caveat)

Used bash to remove the timestamp of the just -posted tweet to twttxt.txt and passed that to twt to re-post to the configured pod

Using twt as a post_tweet_hook for txtnish to re-post to a twtxt “pod” https://github.com/jointwt/twtxt

Can one encode if-statements by using modulo?

I am loving how organic this !zettelkasten is in !weewiki. the key value structure I’m using is so simple and allows for many structures to emerge from it.

@prologic@twtxt.net I see them is why I ask. like here #cwqmygq they use both hashtag and bangtag?

@prologic@twtxt.net have you tried using the macos github build environment? looks like they have a windows one too.

more or less. :D
what are you using to ci/cd? i dont see a travisci/circleci/etc in the repo.. i can put something together to bump the patch level on master branch merges.

@prologic@twtxt.net I use https://key.sour.is/id/me@sour.is

I would need an out-of-band way to verify your public key’s fingerprint though 🤣

@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 def would be a wider discussion on preventing the pod from adding its own key to a users device list. Or using device keys to authenticate instead of user/pass.

@prologic@twtxt.net device gets the cypertext and uses it’s device key to decrypt one of the keys and then decrypts the cypertext.

i am guessing you are using some form of webmention to notify the target of the DM? which loads it into a store for the user to read?

@prologic@twtxt.net I see.. so using an ec25519 key as identity? and some kind of certificate to define the location of a feed? or maybe a DHT like Kademlia? TwTorrent ;)

@prologic@twtxt.net My thoughts on it being if they switched from a different way of hosting the file or multiple locations for redundancy..

I have an idea of using something like SRV records where they can define weighted url endpoints to reach.

@prologic@twtxt.net just an off the wall question about hashes. why not use the time+message as it was in the original twtxt.txt file? is it because it’s just not store anyplace?

also how set in stone is using user+url? vs user@domain? the latter would mean the url could change without invalidating the hash.

@lyxal@twtxt.net @prologic@twtxt.net yah. the service can have a flag for allowing non-TLS for development. but by default ignores.

are there some users that use alternative protos for twtxt? like ftp/gopher/dnsfs 🤔

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.

FOLLOW: @xuu@txt.sour.is from @vain@www.uninformativ.de using twtrd/latest

@prologic@twtxt.net looking through the drafts it looks like it actually used SRV records as recently as 2018 😵

@prologic@twtxt.net Web Key Directory: a way to self host your public key. instead of using a central system like pgp.mit.net or OpenPGP.org you have your key on a server you own.

it takes an email@address.com hashes the part before the @ and turns it into [openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>

@xuu@txt.sour.is With SRV you can set what hostname to be used (and port/priority/etc)

@xuu@txt.sour.is Not too happy with WKD’s use of CNAME over SRV for discovery of openpgpkey.. That breaks using SNI pretty quick. I suppose it was setup as a temporary workaround anyhow in the RFC..

@adi @prologic@twtxt.net One reservation about using it with a small community would be the expectation that the discussions at some level stay within the circle as opposed to the internet at large.

Scuttlebutt is an interesting space. I’m using the Patchwork client and so far it works great!

smoothstep is a stateless smoother function commonly used in computer graphics. could be interesting in the audio domain as well (parameter smoothing, phase warping/distortion synthesis, etc): [[https://en.wikipedia.org/wiki/Smoothstep]] #links #halfbaked

@prologic@twtxt.net Yep! installed it yesterday. I like the simplicity of twt. I am quite happy with how little memory the pod seems to use. Mastodon and the “lightweight” Pleroma don’t work well in small VMs.

@prologic@twtxt.net it is some interesting work to decentralize all the things.. tricky part is finding tooling. i am using a self hacked version of the go openpgp library. A tool to add and remove notations would need to be local since it needs your private key.