asciilifeform: !!ticker btc usd
deedbot[asciilifeform]: $30,396
awt_akris[asciilifeform]: Ok akris now uses the latest message in the log for setting net_chain.
awt_akris[asciilifeform]: I don't anticipate puttion out a patch for blatta.
awt_akris[asciilifeform]: *putting.
awt_akris[asciilifeform]: Perhaps this has already been discussed, but for multipart messages, would it be possible for every assembled message to attempt to decode say image, audio, whatever, and if it succeeds display it?
shinohai[asciilifeform]: http://logs.bitdash.io/pest/2023-07-03#1027764 <<< I've been having fun with the nostr tire fire btw, got myself blacklisted from 4 relays so far for rapid-fire posting. So much for "muh decentralized twitter!". xD
bitbot[asciilifeform]: Logged on 2023-07-03 14:35:50 awt: Meanwhile from someone running nostr: https://twitter.com/thetractatus/status/1675675859217432577
awt_akris[asciilifeform]: lol shinohai I've been wanting to do something like that.
awt_akris[asciilifeform]: as far as banned goes, can't you generate a new key or something?
shinohai[asciilifeform]: Yeah you can generate new keys but I'm too lazy for that. A lot of relays I've noticed filter content, naturally I got a camhoe to post shit I could repost and observed about 40% of the nodes listed here won't relay pr0n images: https://nostr.watch/relays/find
awt_akris[asciilifeform]: Wow a public DoS target list
shinohai[asciilifeform]: Yeah and it's trivial to load 'em all up in json array in client config and fire off posts that hit 'em all using nothing but a bash script since - unlike twitter - nostr dun give af if you post same message over and over.
awt_akris[asciilifeform]: Everything is actually a WoT (tm)(r)
shinohai[asciilifeform]: DM's are atrocious - while you can't decrypt 'em without proper key they flow over the relays just like any other "note" so you can see which folks are talking to each other.
shinohai[asciilifeform]: Lame.
asciilifeform: http://logs.bitdash.io/pest/2023-07-05#1027840 << >> http://logs.bitdash.io/pest/2023-05-15#1026132
bitbot[asciilifeform]: Logged on 2023-07-05 11:57:24 awt_akris[awt]: Perhaps this has already been discussed, but for multipart messages, would it be possible for every assembled message to attempt to decode say image, audio, whatever, and if it succeeds display it?
bitbot[asciilifeform]: Logged on 2023-05-15 09:53:01 asciilifeform[5]: http://logs.bitdash.io/pest/2023-05-15#1026119 << for 'file', the notion was to luby. for lolcats, iirc no one yet suggested precisely how to mark'em ( would strongly prefer not to roll in the 'mime' traditional idiocy or anyffin like it. prolly best to have a single flag som
asciilifeform would rather not see mime in a pestron but sumthing roughly equiv. is prolly unavoidable
asciilifeform: imho lolcat markings dun belong in the wire protocol per se ( tho wouldn't object to including'em in spec, once awt et al figure out what they oughta be )
asciilifeform: http://logs.bitdash.io/pest/2023-07-05#1027844 << lol they default to rebroadcast unless blacklisted pubkey?! ( thought the thing used explicit wots )
bitbot[asciilifeform]: Logged on 2023-07-05 12:13:26 awt_akris[awt]: as far as banned goes, can't you generate a new key or something?
awt_akris[asciilifeform]: asciilifeform: proposed mechanism involves no mime types.
asciilifeform: awt_akris: plox to post algo when you've the cycles
awt_akris[asciilifeform]: It is simple and mirrors the mechanism at the heart of pest - except decode instead of decrypt. If it decodes to *something*, render it.
awt_akris[asciilifeform]: Feed bytes to png lib, then jpg, then mp3, etc.
awt_akris[asciilifeform]: Would have to be careful as legend has it there are "executable jpgs".
awt_akris[asciilifeform]: Honestly don't know much about image encoding.
awt_akris[asciilifeform]: By convention, the first part of a binary multipart could be assumed to be the caption/description.
asciilifeform: imho ideally would be a) png b) 'file' (mp3, djvu, whatever) that opens up in external proggy (if such exists)
asciilifeform: supporting over9000 embedded turds is traditionally how chat proggies pwned
shinohai[asciilifeform]: "Just install via `curl http://myawesumthing/pwnd | sudo bash` !!!!!"
asciilifeform: lol
asciilifeform: software glory hole
shinohai[asciilifeform]: 8====================D
signpost[asciilifeform]: nah this is not a scalable solution. parse with all parsers blows up the (hopefully) fixed cost of processing a packet
asciilifeform: signpost: it could be a bad idea, but this probably aint why -- presumably awt was thinking of the sort of parse that'd fail early (i.e. when not sees the magick header bytes, and only try when sees the 1st msg of multipart)
asciilifeform sees 'bad idea' for diff reason entirely -- rolling in wtf knows what libs for image-eating
asciilifeform nominally in favour of 'support display of lolcats' but with caveat 'pick one format plox' so at least hypothetically adaizable into 100% airtightness
bitbot[asciilifeform]: Logged on 2022-12-28 12:05:30 asciilifeform[4]: it's expensive, in the 'blockchain' sense. send a lolcat? nao erry new station has to sit for whoknows how long fetching rest of chain + that lolcat
bitbot[asciilifeform]: Logged on 2022-12-29 08:15:42 jonsykkel[deedbot|awt]: puting them inline in chain seems like annoying way to force evryone to store 5000 lolcats or nothing. then when disk full u gota start deleteing evrything from old end rather than just the cats
bitbot[asciilifeform]: Logged on 2022-12-29 11:28:28 phf[awt]: but that of course means that /somebody/ has to keep the entire log at all times, which is when you run into the whole 10GB of log with all kinds of lolcats
asciilifeform in spec allowed for 18,874,080byte multiparters but this may be a folly (lolcats or not)
asciilifeform: ( in particular, all of this opens up inevitable questions of 'yes protocol lets but what's considered polite behaviour'
bitbot[asciilifeform]: Logged on 2022-12-28 18:21:37 asciilifeform[jonsykkel|awt|deedbot]: phf: entirely similar. except that most folx wouldn't send 18MB of txt spamola, whereas typically people think nuffin of throwing in a 18MB cat
asciilifeform: http://logs.bitdash.io/pest/2023-07-05#1027863 << thinking further re subj, imho may even be worth it to bake a reasonably-performant but optimized-for-simplicity bitmap compressor (e.g. 'pnm' + simple run-length encode)
bitbot[asciilifeform]: Logged on 2023-07-05 14:49:43 awt_akris[awt]: Honestly don't know much about image encoding.
asciilifeform: libraryism is poison imho.
signpost[asciilifeform]: sure, what `file` does sounded like the proposal, but I'm skeptical all formats can be detected this way efficently
signpost[asciilifeform] could be wrong
signpost[asciilifeform]: what's gained from not saying what's in the payload?
asciilifeform: signpost: 1 way or anuther you gotta say wat's in the payload. the q is where you say it.
asciilifeform: ( a protocolic 'this aint human-readable text' flag could make sense. q is whether this is needed )
asciilifeform: ... arguably needed, ~somewhere~, if only to keep text clients from spewing 18MB of lolcat into console as txt