unpx[asciilifeform]: Hello there, let's see if things get syncd now
phf: http://logs.nosuchlabs.com/log/pest/2023-06-06#1027185 << correct, it is though one of those 90% there situations, and the q is what superset of pest is enough to support extended usecases, and what those usecases are. i'd like to be able to use pest as the only interface to messag
dulapbot: Logged on 2023-06-06 21:41:19 asciilifeform: phf: unless i misunderstand, this (i.e. asking a bot to send a privmsg on some other net, but 'pestronically') aint sumthing that pest protocol per se is a tight fit for -- you'd need to layer some command lang on top of direct msgs to $bot
phf: es from various sources, and extending to telegram proxy should cover the scope
phf: foo
asciilifeform: phf: seems like a deedbotesque use case, i.e. you'll have a bot with a defined command lang, perhaps a '!!help', etc. and directmsg to it, it then does various things on heathen net, potentially msgs you back, etc
asciilifeform: ( for that matter, other side of such bot can be just about anyffin you like, even e.g. a shell )
asciilifeform: for such thing, you only need a ~subset~ of pest, given as you aint concerned with broadcasts at all there
phf: http://logs.nosuchlabs.com/log/pest/2023-06-07#1027192 << sort of, but i'd rather avoid deedbot-style interaction as much as i can. instead proxy has a flag enabled, and operator client has a flag enabled on proxy's station entry, and it just works™
dulapbot: Logged on 2023-06-07 12:03:37 asciilifeform: phf: seems like a deedbotesque use case, i.e. you'll have a bot with a defined command lang, perhaps a '!!help', etc. and directmsg to it, it then does various things on heathen net, potentially msgs you back, etc
phf: but the flag should preferably also not enable/disable too large chunks of functionality
phf: telegram is the only other 100% heathen technology client that runs on my machines, and i basically just want to get rid of it. there's nothing clever going on
phf: it's also pretty easy to isolate. its c++ library has a mode that lets you sling json back and forth about the state of your client. wrap that in ffa, attach it to pest, and you can isolate it on some remote machine
asciilifeform: phf: 'just worx'(tm) in the sense that on ui end, oughta look as if you had $heathennetpeer as a directmsg session ?
asciilifeform pictures that this is entirely doable, but could be almost as gnarly as simply baking a multiprotocol chattron that actually speaks $heathennet protocol in addition to pest
asciilifeform: you'd potentially get uptime win, tho, similarly to 'znc'
awt[asciilifeform|cgra] realizes short buffer no longer necessary, belatedly checks updated spec and sees it's gone
asciilifeform considered similar application , 'slave mode pest'
asciilifeform: awt: indeed
asciilifeform: phf: does 'telegram' support group chats? might be rather gnarly to interface
awt[cgra|asciilifeform]: it does
awt[cgra|asciilifeform]: http://logs.bitdash.io/pest/2023-06-07#1026791 << brings back memories of Adium
bitbot[cgra|asciilifeform]: Logged on 2023-06-07 13:18:16 asciilifeform[6]: pictures that this is entirely doable, but could be almost as gnarly as simply baking a multiprotocol chattron that actually speaks $heathennet protocol in addition to pest
asciilifeform recalls 'pidgin' (used well into 2010s, when ye olde 'aol messenger' finally kaput)
awt[asciilifeform]: ✅ GetData working on new station
awt[asciilifeform]: *on new