Show Idle (>14 d.) Chans

← 2022-11-26 | 2022-11-28 →
asciilifeform: $ticker btc usd
busybot: Current BTC price in USD: $16558
phf[asciilifeform]: << this line lands particularly well, because i'm reading unixhaters guide at the moment
bitbot[asciilifeform]: Logged on 2022-11-25 23:44:37 asciilifeform[jonsykkel|deedbot|crawlerbot]: it worx ok for editing a config on remote box. asciilifeform uses it (for ~20y nao) to upload items to www.
phf[asciilifeform]: feels like one of those mp moments when he discovers that some core tool that he uses is an utter pos, loses his shit, and starts calling for lynching of the specific programmers and the programmer's in general, etc.
phf[asciilifeform]: *programmers
phf[busybot]: i'm also reading unixhaters, and there are some passages there that makes one despair not just for the field, but the humanity in general
phf[asciilifeform]: like the whole section of nntp hate, one the grounds that it's just gigabytes of noise. what will authors say about modern™ internet
phf[asciilifeform]: << the braindamage is inherent to fish protocol,
bitbot[asciilifeform]: Logged on 2022-11-25 23:41:17 asciilifeform[jonsykkel|deedbot]: phf: 'fish' is a horrendous hack -- iirc pisses the file over base64, and at snail's pace (and satan help you if you have over9000 files, there's a sometimes ~1s overhead per)
phf[asciilifeform]: “#RETR /some/name Server sends line with filesize on it … then it sends binary data … Note that there's no way to abort running RETR command”
phf[asciilifeform]: which means that a copy of a 10gb file is just that, a 10737418240 followed by control message followed by 10gb worth of firehose
phf[asciilifeform]: so apparently it try to run a start_fish_server script, if it's available, otherwise it sends these shell snippets on each command
phf[asciilifeform]: actually it sends shell snippets every time, but fish server, if it's there and it runs, is supposed to ignore them
phf[asciilifeform]: of course there's no start_fish_server or anything remotely resembling a server (or anything online either) in the mc package
phf[asciilifeform]: “Let's forget about the compatibility with FISH command formats. Let's just send shell scripts with arguments that are convenient for us to the remote host and get results of script work. The part of FISH protocol relative to remote host answers will be used as is.
phf[asciilifeform]: this is utter trash, because even for a simple connection, during handshake, at baseline, mc sends a shell command, that doesn't have corresponding fish annotation
phf[asciilifeform]: LANG=C LC_ALL=C LC_TIME=C; export LANG LC_ALL LC_TIME;
asciilifeform: phf: precisely as summarized by asciilifeform neh
bitbot[asciilifeform|busybot]: Logged on 2022-11-25 23:45:28 asciilifeform[4]: prolly could be made faster, but not easily (iirc it uploads a shell turd that decodes the text piss errytime)
phf[asciilifeform]: asciilifeform, not even like that, because your summary is more similar to how emacs tramp does it: upload a perl script, and then let interactions all go over perl
phf[asciilifeform]: not the case here. instead it supposed to send #CMD ARGS\ncmd equivalent raw shell code\n
asciilifeform: barfalicious
phf[asciilifeform]: so it's a fish command "#LIST /${FISH_DIR}" followed by a script with all the shit inlined
phf[asciilifeform]: fish_list_perl ()
phf[busybot]: FISH_DIR=$1
asciilifeform: pretty disgusting, but interestingly does work 100% even with embedded toystore boxen (e.g. 'pogo' with asciilifeform's 5MB incl. trb hand-sewn linux etc)
phf[busybot|asciilifeform]: well, yeah, "works"™
asciilifeform[busybot]: 'light duty worx'
asciilifeform did wonder, wai not at least ~try~ caching the thing (see if it's still in /tmp) b/w files
asciilifeform: why it sends errytime.
phf[busybot]: refer to unixhaters handbook to understand the brain damage
asciilifeform: normally asciilifeform would immediately nod, but on surface seems like generic braindamage, rather than unix braindamage
phf[asciilifeform]: i mean don't even need to cache: you can just send perl -e '...' as a first command, which sets up a mainloop server, that responds to your commands
asciilifeform: sumbody simply didn't bother baking a separate case for >1 file
phf[busybot]: nah, i'm not even going to nod along. this is not "simply", this is fundamentally retarted on multiple levels
asciilifeform: retarded in the usual way where author: 'it worx for me, all i ever do it edit /etc/apache configs' etc
phf[asciilifeform]: send perl -e 'while(my $cmd=<>) { if(cmd=='list') { ... } ... }' as first command, and then send commands one after another. this way also not stuck with idiotic protocol, because if you want to extend ("getchunk /file <start> <end>"), simply add command and add it to your perl script. still overhead, but at least it's per
phf[asciilifeform]: -connection overhead
phf[asciilifeform]: but that requires more than a second of thinking
asciilifeform: well and relies on having perl on the other end
phf[asciilifeform]: sh -c '...'
asciilifeform: oughta be doable with plain sh
phf[busybot]: oddly enough there's sftp file system, but i don't have that in menu. i imagine that runs directly of sftp commands?
phf[asciilifeform]: and sftpfs uses libssh2
phf[asciilifeform]: …except it doesn't want to use config/ despite the fact that this claims its implemented
phf[asciilifeform]: and that's because sftp vfs includes its own ssh/config parser, that uses regular expressions, and expects you to have your configure in a particular format
phf[busybot]: asciilifeform, you might want to look into that, sftp vfs once configured works somewhat better than fish
phf[asciilifeform]: at least large file interrupt is instantaneous
phf[busybot]: there's still ложка дёгтя though: when getting the directory list it inexplicably does echo in the modeline "sftp: (Ctrl-G break) listing... <filename>". where i suspect the terminal i/o actually slows down the listing more than the listing itself being slow. what utter idiocy
asciilifeform not infrequently uses (raw, rather than via mc) sftp
← 2022-11-26 | 2022-11-28 →