lrc self-hosting

a few days late to my weekly blog post but i don't care; time isn't real; in order to support media, i refactored lrcd a lil bit, and then i realized that it's been high time to start making kinds of testing environments. however, ever since i transitioned from lrc version 0 to lrc version 1 with protobuf, i haven't really had a command line client for lrc protocol to test my changes to lrcd outside of pushing changes to prod xcvr (i don't have a development environment since adding oauth....)

this, of course, has changed now that i've made tty!xcvr; instead of being totally careless pushing my changes to lrcd to prod, i can now have local or self-hosted instances of lrcd (using lrcdaemon; i don't know exactly how go modules work and i don't want to mess up imports, so i just made a separate repo consuming lrcd in a very minimal manner, forgive the stupid name)

this required some refactoring of tty!xcvr but it wasn't anything particularly special, i think most of the time last week was metabolized into my hardcore minecraft world. nevertheless, now you can dial arbitrary lrc servers (i'll make the command parser better in the future for flags and stuff, in particular use insecure websocket, and atproto event stream uri so you can manually dial a xcvr instance (xcvr instance is lrc + xcvr event stream which pushes appropriate signet records so the atproto org.xcvr.lrc.message records can be verified)) if it exists but isn't indexed by the lexview you're getting channels from

if you want to test out simple lrc servers without xcvr, you can dial lrc.moth11.net from tty!xcvr. probably it's more interesting if you do this with a friend or with me, as with all my HyperRealTime / RealTimeText / LivePosting / WhatEverEver projects if you're interested in them don't hesitate to reach out to me through any channel at all & we can have a chat, it's not soo cool when you're just talking to the void

kinda unrelated to the rest of this post, recently a silly thought that's gone through my mind is that of course lrc server can respond to lrc client with whatever it wants. ultimately the conceptual metaphor is that hyper-real-time is a text-based telephone, so my first thought in this direction is that after dialing a server, it can be like an interactive voice response system which yaps some stuff at you and interprets your response and then routes you accordingly. of course, the logical next step is a dial-up internet access. now we're getting somewhere interesting... i so badly want to make an lrc server which is a clone of WorldWideWeb/Nexus browser that runs in any lrc client, without expanding the protocol at all. there's something so crunchy about that... it's on the backburner for now, but i know i'm going to do it some day

onto upgrading lrcd to support more practical things! and then we'll revisit media

see ya around,

-rachel