\nError following feed @<reednj http://twtxt.xyz/u/reednj.txt,>: error: request failed with non-200 response\n/sbin/init like what uLinux uses? :)
--max-cache-ttl and --max-cache-items limits meaning that you can't "arbitrarily" show nested or even flat conversations as far back as you want. Replies/Posts eventually fall off active caches into the archive. This is why content addressing / hashes are so important as it is the only way to bring up the matching root of a conversation -- even if that conversation is long gone, it could get "re-sparked"...
gopher://, http://, https:// or even ftp:// 🤣 (_but really we only support http/https at this time_)
shop is the best name I could come up with at the time...
xxx is a simple command-line tool written in Go\nthat helps you simplify the way you manage configuration across a set of\nmachines. xxx is your configuration management tool of choice when Chef,\nPuppet, Ansbile are all too complicated and all you really want to do is\nrun a bunch of regular shell against a set of hosts.
http.ServeContent() to effectively io.Copy()...
test.yml config looks like this:\n\n\n---\nversion: 1\n\nitems:\n - name: Ensure /root/foo exists\n check: ls /root/foo\n action: touch /root/foo\n - name: Check Uptime\n check: false\n action: uptime\n\n(⎈ |local:default)\nprologic@Jamess-iMac\nSat Feb 20 12:24:53\n~/Projects/shops\n (master) 0\n$ ./shops -f ./test.yml 10.0.0.50\n10.0.0.50:22:\n Ensure /root/foo exists ✅ -> /root/foo\n Check Uptime ✅ -> 02:24:56 up 18 days, 42 min, 0 users, load average: 0.00, 0.00, 0.00\n