asciilifeform: !!ticker btc usd
deedbot[asciilifeform]: $30,972
awt_akris[asciilifeform]: Happy new slave owner day!
asciilifeform: ty awt_akris
asciilifeform 'picking cotton' even today, lol
lobbes[asciilifeform] likewise
lobbes[asciilifeform]: awt: btw, my peering info, if you'd like: http://paste.deedbot.org/?id=HRKm
unpx[asciilifeform]: Found this amusing https://www.youtube.com/watch?v=4To-F6W1NT0
awt[asciilifeform]: ty lobbes will peer
billymg[asciilifeform]: which is why i put e.g. nav into the right column instead of in the header
billymg[asciilifeform]: (but switches to header on "phone view")
asciilifeform: billymg: a, see, asciilifeform uses vertical displays exclusively
asciilifeform: hence wai never bothered with these
asciilifeform: ( and given that these displays only available in 9:16, there's moar or less 0 win from horiz. margins on'em )
asciilifeform: billymg: fwiw even on asciilifeform's vertical display, there's a massive deadspace on the right where (on top of pg) chan list
asciilifeform: would make some kinda sense if it were 'frame' and could switch chans from it at any pt along the page, but still gotta scroll to top... so wainot have'em at top of pg like in asciilifeform's
asciilifeform: billymg: the chan list occupies chunk of right hand all the way along the scroll
asciilifeform: 2160
asciilifeform: and in e.g. emacs, asciilifeform uses from 0th pixel to the last.
asciilifeform: width.
asciilifeform: 2160 width, 3840 height .
asciilifeform: actual pixels
asciilifeform: ( what kind didja think )
asciilifeform not knows how many 'css pixels' it ends up
asciilifeform: billymg: rly? seems like epic waste
asciilifeform: why would it, if fonts config'd correctly ?
asciilifeform: i've simply set the dpi in xorg to the correct #
billymg[asciilifeform|asciilifeform]: it's similar to how in printed text books there is typically a generous margin
billymg[asciilifeform|asciilifeform]: there is an ideal target for reading comfort, measured in number of characters per line
billymg[asciilifeform|asciilifeform]: asciilifeform: i took that into account too. thought to myself "alf and probably others read on narrower displays, so should be sure to adjust layout accordingly". at 989px the timestamps are hidden and the nav goes to the top, and at 766px the handle and payload columns collapse into one
billymg[asciilifeform|asciilifeform] still sees layouts all over the web where the "desktop" margins are maintained in the "mobile" view, resulting in text columns with 2-3 words per line
billymg[asciilifeform|asciilifeform]: asciilifeform: dead space on right while the chan list is on top? not sure i follow
billymg[asciilifeform|asciilifeform]: when the chan list moves to the top, there shouldn't be any extra margin on the right
billymg[asciilifeform|asciilifeform]: ah, right, that's intentional
billymg[asciilifeform|asciilifeform]: asciilifeform: what's your viewport width, in pixels?
billymg[asciilifeform|asciilifeform]: width??
billymg[asciilifeform|asciilifeform]: asciilifeform: ok, so 2160 actual pixels
billymg[asciilifeform|asciilifeform]: "css pixels" lol
billymg[asciilifeform|asciilifeform]: people usually run high dpi displays at some ratio, like 1.5x, 2x
billymg[asciilifeform|asciilifeform]: otherwise everything would require a magnifying glass to read
awt_akris[asciilifeform|asciilifeform]: !!ticker btc usd
deedbot[asciilifeform]: $30,813
awt_akris[asciilifeform]: !!ticker btc usd
deedbot[asciilifeform]: $30,813
awt_akris[asciilifeform]: Wow. Just discovered that blatta's netchain tracking is utterly retarded.
awt_akris[asciilifeform]: For example, while syncing, it will just use whatever the latest getdata message hash was for the netchain when an operator sends a message. Could be anything.
asciilifeform: lol! might explain the oddly unfetchable historic msgs