-- Leo's gemini proxy
-- Connecting to git.thebackupbox.net:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini
repo: blog action: blob revision: path_from: veilid-6 revision_from: refs/heads/master: path_to: revision_to:
/ veilid-6
refs/heads/master:/veilid-6 # netchat => veilid-5 previous I've gotten some shell scripts with a not too terrible interface for sending messages to a group of users that can be discovered from them putting route blobs into the DHT. The scripts are pretty rough atm. I named them netchat-[stuff] and they use some hardcoded paths. All the veilid-hacks stuff has expected itself to run in ~/projects/veilid-hacks because I can't be fucked to do something like.. ~/.veilid-hacks or ~/.cache/veilid-hacks or... whatever. I also have my scripts expect the rest of them to be in the $PATH, so have fun with that. anyway, if you still want to try to use them, you can do: ``` $ cd ~ $ mkdir projects $ cd projects $ git clone git://git.thebackupbox.net/veilid-hacks $ cd veilid-hacks $ mkdir -p keys $ mkdir -p netchat_routes $ make install $ netchat-watch-appmsgs [some output, including your route-blob] ``` if netchat-watch-appmgs fails because it couldn't fetch your own DHT key, uh, wait a minute and try again I guess. maybe comment out that check. it isn't actually that important. then in a second terminal, you can try netchat-discover -g to search the DHT for anyone who has published their route-blob with 'netchat ' prepended. Once you have a coule route_blobs in ~/projects/veilid-hacks/netchat_routes named after their route_id you can actually send stuff to them using: ``` $ netchat-send 'a message' ``` It'll loop over that directory, import all the routes just in case, then send an appmessage to them. Anyway. I figured I'd at least get this out of my head before I go to bed.
-- Response ended
-- Page fetched on Sun Jun 2 15:53:36 2024