punkman: "Over the last 60 years, Visa has built a collection of historic commerce artifacts - from early paper credit cards to the zip-zap machine. Today, as we enter a new era of NFT-commerce, Visa welcomes CryptoPunk #7610 to our collection."
thimbronion: $ticker btc usd
busybot: Current BTC price in USD: $49762.15
PeterL: !s update
dulapbot: Logged on 2021-08-22 07:40:14 cgra: PeterL: by me, you may add it to the scoopbot roll, http://cgra.net/feed
dulapbot: Logged on 2021-08-22 12:41:24 thimbronion: asciilifeform: in your scheme is there a field in the packet that indicates whether or not it should be relayed?
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-22#1053343 << still haven't tried this item, but fully intend to!
dulapbot: Logged on 2021-08-22 12:34:50 scoopbot: New post on Thimbron: Alcuin 9996: Testnet and Bugfixes
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-22#1053348 << ftr asciilifeform still suspects that 'lolcatvids' could just as effectively be served via a torrent-like mechanism, with 0 centralized cachefarms etc req'd
dulapbot: Logged on 2021-08-22 23:57:42 bingoboingo: And if it isn't clear "consumers have come to expect" is driving the decision to record the video in a vertical format.
dulapbot: Logged on 2021-08-21 19:13:16 shinohai: Good to be back home.
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-23#1053349 << wtf is a 'cryptopunk' here ?
dulapbot: Logged on 2021-08-23 07:18:03 punkman: "Over the last 60 years, Visa has built a collection of historic commerce artifacts - from early paper credit cards to the zip-zap machine. Today, as we enter a new era of NFT-commerce, Visa welcomes CryptoPunk #7610 to our collection."
asciilifeform: $ticker btc usd
busybot: Current BTC price in USD: $49423.18
asciilifeform: !w poll
watchglass: Polling 17 nodes...
watchglass: 220.127.116.11:8333 : Could not connect!
watchglass: 18.104.22.168:8333 : Could not connect!
watchglass: 22.214.171.124:8333 : Could not connect!
watchglass: 126.96.36.199:8333 : Alive: (0.081s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=697216
watchglass: 188.8.131.52:8333 : (172-6.core.ai.net) Alive: (0.141s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=697216
watchglass: 184.108.40.206:8333 : Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=697216 (Operator: whaack)
watchglass: 220.127.116.11:8333 : (172-4.core.ai.net) Alive: (0.153s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=697216
watchglass: 18.104.22.168:8333 : (ns562940.ip-54-39-156.net) Alive: (0.171s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=697216
watchglass: 22.214.171.124:8333 : Alive: (0.150s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=697216 (Operator: asciilifeform)
watchglass: 126.96.36.199:8333 : Alive: (0.234s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=697216
watchglass: 188.8.131.52:8333 : Alive: (0.220s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=697216
watchglass: 184.108.40.206:8333 : (ns3140226.ip-54-38-94.eu) Alive: (0.331s) V=88888 (/therealbitcoin.org:0.8.88.88/) Jumpers=0x1 (TRB-Compat.) Blocks=697216
watchglass: 220.127.116.11:8333 : Alive: (0.389s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=697216
watchglass: 18.104.22.168:8333 : (terebe.ns01.net) Alive: (0.614s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=697216
watchglass: 22.214.171.124:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.897s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=697216 (Operator: asciilifeform)
watchglass: 126.96.36.199:8333 : Violated BTC Protocol: Bad header length! (Operator: jurov)
shinohai: asciilifeform: A cryptopunk is where you sell .jpg copy of a head from a 1988 Nintendo game for thousands/millions in ETH
watchglass: 188.8.131.52:8333 : Busy? (No answer in 100 sec.)
punkman: in 2014 terms, cryptopunks are an implementation of "colored coins"
punkman: with people pretending a jpg is equivalent to painted canvas and can be owned/traded
asciilifeform: aa these
asciilifeform: punkman: any idea what made that liquishit return ? ( or -- never entirely disappeared at all ? )
billymg: weren't the "cryptokitties" in 2017 the same thing too? i think they just rehash it during each hype cycle to distract from btc and divert funds from btc into eth
asciilifeform: billymg: pyramids, i suspect, 'will be with us always'.
dulapbot: Logged on 2020-05-05 19:32:50 asciilifeform: sergey mavrodi of 'mmm' was at 1 pt richest man in orcistan. and even sat in parliament. still died broke and folx came to shit on his grave.
asciilifeform: a possibly moar interesting observation is that the 'stupid will lose their coin to the smart' prophecy of mp et al did not (detectable) come to pass.
asciilifeform: 'smart' may be a null set.
asciilifeform: (or at any rate among bitcoinists...)
punkman: asciilifeform: is passing just fine
punkman: we can see coins parked at "cold" addresses at increasing rate
asciilifeform: punkman: how wouldja distinguish this from the commonplace 'luser loses his keys' ?
asciilifeform: ( or the also not uncommon 'dies capt.kidd-style w/out sharing key with heir' )
punkman: I'm talking about kilocoin addresses
asciilifeform: punkman: how does mass enter into it ?
asciilifeform: plenty of kilocoin addrs w/ lost (by all indications) keys, incl. likely shitoshi's
punkman: because "microstrategy" is quite less likely to lose key than derp in 2014
asciilifeform: punkman: that microstrategy ? did they publish their addrs ? (why would do this?)
dulapbot: Logged on 2021-07-07 19:35:18 mats: microstrategy llc, has the biggest btc stash among public corps https://bitcointreasuries.net
dulapbot: Logged on 2020-10-27 13:54:19 thimbronion: asciilifeform: the claim is that the btc is now in cold storage, in the posession of Microstrategy. They haven't published their storage scheme.
punkman: I'm seeing the addresses accumulate, seeing the news of "microstrategies" buying kilocoins, perhaps the correlation is imagined.
punkman: but my bet is that big players are indeed accumulating
asciilifeform: punkman: imho is interesting to contemplate the q of the theoretical limits of (any) organization's seekrit-keeping capacity.
punkman: the derp that lost 500 btc to "pirate", is losing maybe 0.5 btc to "pirate2021"
asciilifeform: arguably prior to bitcoinism, absolutely no bitstring was of a 10k-2021-btc 'bearer instrument' worth.
asciilifeform: (not even a hypothetical 'pill for rsa' kept at ft meade underneath pillow of lizard hitler's throne, perhaps)
asciilifeform: punkman: re pirate -- probably factual, but presupposes that 'pirate' himself will not lose to anyone
punkman: the derp of integer btc, is not derp of integer bitcent
punkman: pirate can lose to usg or whoever else, and a bit later it's in hand of "microstrategy" that doesn't play dice or throw away usb key
asciilifeform: punkman: right; so q is, whether microstrategy et al are qualitatively different kinds of organization with somehow infinite secret-keeping ability
asciilifeform: and 100% airtight electronics
asciilifeform: and 100% loyal employees; etc
asciilifeform: ( the song & dance w/ 'multisig' and its pre-btcism equivalents is just that -- for one thing, often enuff a privkey physically exists ~somewhere~ prior to being 'split' ; for other thing, just about erry organization uses some form of 'unprincipled exceptions'; or else 1 or 2 plane crash -> total loss potentially )
asciilifeform: ... there's, imho, an inherent 'engineering contradiction' b/w the traditional 'organizational continuity' of an item like microstrategy or nsa, and the approach req'd to hold on to coin on a decade+ timescale.
punkman: for organization of many people, could say btc is quite like storing physical item worth millions, with the added downside of being much easier to sneak out the building
asciilifeform: ... and impossible to return
asciilifeform: ... and virtually impossible to say (if it were done with even half a brain) who did it or how.
asciilifeform: not to mention that traditional 'xyzmillion dollar items' (e.g. rembrandts) were NOT bearer instruments
asciilifeform: and generally ~useless to steal
asciilifeform: (try fence a rembrandt for anywhere close to its Official value)
asciilifeform: whereas a 10kbtc privkey is worth 10kbtc.
asciilifeform: other interesting aspect (if obvious one) is that the circle to whom a btc privkey is useful, is of almost planetary width ( janitor finds -- he can use) unlike the proverbial h-bomb plans , seekrit formulae etc
punkman: we'll see how the big stashes of 20/21 fare, maybe chinese spies get them like all those "trade secrets" they've been stealing
asciilifeform: punkman: maybe 'we find out', maybe not
dulapbot: Logged on 2021-08-09 06:14:47 punkman: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-08#1050664 << good example of "didn't find out, after all". what did we "find out later" about 9/11? even talking about it 20 years later, sort of makes you a weirdo
asciilifeform: (for the thick readers -- just because coin 'moved' does not mean that it changed hands; and conversely, simply because ~hasn't~ moved, does not prove that there is not a second party in possession of privkey... )
punkman: when loss happens, there will be the SFYL
punkman: conversely, if there was no SFYL, did loss even happen
asciilifeform: 'the bezzle'(tm)(r)
asciilifeform: (happened, but 'lazy-evaluated')
punkman: doesn't that guy make the point that "hasn't actually happened before point of evaluation"
asciilifeform: galbraith ?
asciilifeform: was his contention, yes
asciilifeform: (imho sophistry. it 'happened' when it happened, just like yer shot when shot, not when fall down)
asciilifeform won't be surprised if eventually reich mandates and attempts to enforce key escrow for 'organizational' (i.e. reich-registered orcs) held coinz
punkman: a utxo visualization https://utxo-stats.com/
punkman: if I'm reading the blue part correctly, it's concentrating
asciilifeform: punkman: 'Updated August 03 2019, 16:18 at block height 588457' << rip ?
punkman: seems like I might have to make my own
asciilifeform: ' Each pixel represents a block, where each row is 300 blocks (~50 hours). The orange image displays the number of unspent transaction outputs per block, and the blue shows the combined value in BTC of those outputs.'
asciilifeform: ^ not clear from this that 'concentrating' (at least, per the picture)
asciilifeform: seems opposite -- dispersing ?
asciilifeform: if 'number of unspent outputs per block' -- increasing (as the graphic implies)
asciilifeform: punkman: perhaps whaack could easily make a similar graphic, iirc he recently completed a wwwistic trb block browser
punkman: https://www.blockchain.com/charts/utxo-count from 8mil utxo in 2014 to ~80mil now
punkman: yes the previous visualization is kinda useless
asciilifeform: soo, then where's the 'concentrating' ?
asciilifeform: ( can't deny that it may be happening from avail. evidence -- but cannot say that it is, necessarily, likewise )
dulapbot: Logged on 2021-08-23 14:11:20 asciilifeform: (for the thick readers -- just because coin 'moved' does not mean that it changed hands; and conversely, simply because ~hasn't~ moved, does not prove that there is not a second party in possession of privkey... )
asciilifeform: if anything -- seems entirely opposite
asciilifeform: wb bingoboingo
billymg: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-23#1053423 << this property of bitcoin seems like cause for optimism (if you can survive long enough). it would also undermine these kinds of schemes by the reich
dulapbot: Logged on 2021-08-23 13:56:08 asciilifeform: ... there's, imho, an inherent 'engineering contradiction' b/w the traditional 'organizational continuity' of an item like microstrategy or nsa, and the approach req'd to hold on to coin on a decade+ timescale.
dulapbot: Logged on 2021-08-23 14:33:24 asciilifeform: won't be surprised if eventually reich mandates and attempts to enforce key escrow for 'organizational' (i.e. reich-registered orcs) held coinz
asciilifeform: billymg: 1 caveat is that only ~actual~ bitcoin has this property; papercoin, otoh, behaves similarly to erry other previously known type of paperism
billymg: asciilifeform: right, but this concedes there's an advantage to the individual vs. the organization
billymg: asciilifeform: unrelated, i'm trying to configure dulap with xorg and dwm but one of the deps for xorg isn't found on your repo, 'app-eselect/eselect-mesa-0.0.10-r1'
billymg: i can't remember if dulap is meant strictly as a headless distro or can be configured with dwm
asciilifeform: billymg: there was a box 'with head' among the machines which collectively went into that repo; but it had ancient x
asciilifeform recently completed a gentoo box w/ xorg and using circa-2021 packages strictly, save for gcc (where 4.9) and w/out any systemdisms which crept in since the '16 cut date of dulap-gentoo ; so can confirm that it is possible. but sadly no time to document the process atm
asciilifeform: there was a considerable amt of manual fiddling w/ USE flags for individual builds. and mesa defo was on this list.
asciilifeform: here's 1 link re subj; will eventually post the rest
dulapbot: Logged on 2021-08-05 15:41:05 asciilifeform: 'Get ride of systemd-tmpfiles'
asciilifeform: ... the process took 2+wks of nights/weekends ftr.
dulapbot: Logged on 2021-08-01 21:26:37 asciilifeform: blew days on trying to transplant 'AMDGPU' to dulap-gentoo. so far w/out success.
billymg: asciilifeform: https://g3ngr33n.github.io/systemd-openrc/index.html << this is for excising any remaining traces of systemd from "stock" 2021 gentoo?
billymg: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-23#1053471 << also if the output of this effort is ~= to a "2021 dulap" i'd pay to have a copy
dulapbot: Logged on 2021-08-23 15:13:39 asciilifeform: recently completed a gentoo box w/ xorg and using circa-2021 packages strictly, save for gcc (where 4.9) and w/out any systemdisms which crept in since the '16 cut date of dulap-gentoo ; so can confirm that it is possible. but sadly no time to document the process atm
asciilifeform: billymg: i'ma repeat the exercise 'from 0' a la 2016 when i get a chance (if lucky -- december!) and make a new repo w/ the resulting /usr/portage/distfiles and instruction.
asciilifeform: ( if someone beats me to this -- will not be sad, quite opposite )
billymg: asciilifeform: looking forward to it, i really like dulap for its ease of installation
asciilifeform: fwiw contrary to asciilifeform's expectation -- did not need to resort to gcc5 or later for any package (tho is possible to eselect and use evil gcc if req'd; evil-gcc's do build w/ godly one )
asciilifeform: billymg: if you consider disk image as 'easy installation' lol
billymg: asciilifeform: regarding the css for your logger theme, what was the goal for the table? have it always stretch to full width rather than size of elements and centered?
dulapbot: Logged on 2021-08-20 15:34:20 asciilifeform: ( to be clear -- is asciilifeform's 'fit width' kludge which turns to soup, rather than billymg's css fix from yest. )
asciilifeform: billymg: wanted to fill width, but to cleanly spill to N rows if req'd
billymg: seems to sort of be working that way, at least in chromium
asciilifeform: seems to work on e.g. x86 chrome ; but on crapple pnojes etc -- crumples into wreck
billymg: and what are the reqs for lynx rendering?
asciilifeform: that all links are legible, elementarily
asciilifeform: under all browsers.
asciilifeform: imho is not overly ambitious for simple item like this.
asciilifeform: legible and without horiz. scrolling.
asciilifeform: horizontal scrolling is to be killed with fire and sword.
billymg: asciilifeform: right, but iirc it was also a requirement of yours that the channel links be displayed in a horizontal row in lynx
asciilifeform: one or more horiz rows.
asciilifeform: as req'd to fit'em all.
asciilifeform: (this currently only concerns 'show all' mode obv.)
billymg: ok, i see the problem in ios now lol
billymg: kind of an amusing result
asciilifeform: atm asciilifeform has 1) no idea why breaks on crapple 2) not remotely the time to try to find out. but if anyone does -- plz write in.
asciilifeform: i suspect that The Right Thing there would be to actually crank out multiple tables, w/ say 3 entries each max. and that nuffin short of this will cover 100% of possible browser idiocies.
billymg: asciilifeform: going back to lynx, i can't think of how you'll ever achieve something different than what you have now, since all CSS is ignored
asciilifeform: cssism is arguably bogus approach
billymg: so it's gonna render based off your <table> tag structure only
asciilifeform: billymg: lynx wraps lines tho
billymg: iow works as you want out of the box?
billymg: if so, that's good
asciilifeform: hrm now looks like in lynx -- 1 chan/line
asciilifeform: so no, not as it oughta be
asciilifeform: (in fact entirely wrecked under lynx -- there are not correct line breaks b/w the last-change times and chan names)
billymg: asciilifeform: i think that was a result of your latest css changes, see http://logs.bitdash.io in lynx
billymg: (i switched it to the classic theme with <table> chanlist layout temporarily to test this)
billymg: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-23#1053516 << sorry, i meant a result of your latest html changes (CSS has absolutely 0 effect on lynx)
dulapbot: Logged on 2021-08-23 15:55:06 billymg: asciilifeform: i think that was a result of your latest css changes, see http://logs.bitdash.io in lynx
billymg: looking at the patch though it looks like you tried a similar approach to what i attempted back when i was working on these themes
billymg: where you keep the channel together with their last active timestamps together in respective table cells (which imo is semantically and ordinally the right approach)
billymg fought with this for quite some time actually, until eventually gave up and provided two separate chanlist templates, one based on <table> to work with classic.css and to asciilifeform's specs in lynx, and one based on <ul> which renders as a stacked list in lynx (and however you want in graphical browsers, depending on the css)
asciilifeform: billymg: i suspect that the Right Thing would be to throw out 'table' and simply hardcode N (e.g. 3) chan/time per line, with paragraph markers, and styled to fit screen width.
asciilifeform sadly does not have the cycles to experiment atm
billymg: asciilifeform: i'm happy to help with this
asciilifeform: why ty billymg
asciilifeform will try out patch if billymg comes up w/ one
billymg: asciilifeform: not sure how that hardcoded approach would help with lynx though
asciilifeform: billymg: it does seem to faithfully render paragraph breaks. so i expect it would
billymg: asciilifeform: right, but does it send e.g. "viewport width" to the server so the server can calculate the right number of lines to send back
billymg: i was assuming your solution was a server side solution
asciilifeform: billymg: correct -- notion would be to simply stuff e.g. 1st 3 chans/times into a para, then 3 more, etc. generated on server end.
billymg: is 3 arbitrary?
billymg: or based on width of client (if server can somehow know this)
asciilifeform: billymg: conservative guess of 'how many would fit in every known horiz screen width w/out spillage'
billymg: that makes it easy at least
asciilifeform: at this pt i'm convinced that there is not a clean, cross-browser solution to this or to anyffin else, that doesn't reduce to 'pretend it's 1993'
billymg: ok, gonna switch my logger back to its default theme
asciilifeform: cssism tricks ALWAYS, seems, break ~somewhere~
asciilifeform: and unpredictably.
asciilifeform: and if not today, then tomorrow.
asciilifeform: whole concept of 'web standards' is a malignant crock of shit.
billymg: asciilifeform: not disagreeing, but i do know (as a result of being paid to know) how to work around most of these issues
billymg: asciilifeform: i switched mine back to my theme, take a look in lynx and see if you still hate the vertical stacked chan list
asciilifeform: right, but the workarounds have a strong flavour of voodoo -- they consist of incantations which are tested empirically, via brute force, and when they fail -- no rational explanation for why fail (or conversely -- when do not fail) appears to exist anywhere
asciilifeform: billymg: still stacked. (but now -- correctly paired chan/time , at least... )
billymg: asciilifeform: yup, this is my personal preference for lynx. would you be opposed to that for your theme? (if so can nuke chan-list-table.html and users only need to switch css file to go between themes, not also the template file)
asciilifeform: billymg: is improvement over previous. (so long as not changes how graphical browsers display)
punkman: unspent coinbase outputs quite stable around 2mil BTC https://checkonchain.com/btconchain/minerbalance_pricing_usd/minerbalance_pricing_usd_light.html
asciilifeform: punkman: linked graphic seems to concern specifically block reward addrs, neh ?
billymg: asciilifeform: wish you would've told me that months ago when i was working on it! lol
asciilifeform: billymg: i thought q was re porting the lynx fix to asciilifeform's theme
asciilifeform: ( asciilifeform does not like sidebarism in any form and will not use it in his logger instance )
billymg: asciilifeform: it is, i had baked a classic.css theme that worked with this html
asciilifeform: right, my current item is based on same
asciilifeform: billymg: my vpatches are built on top of your item, i thought this was clear
billymg: asciilifeform: yes, was clear, but my patch had two html variants for the chanlist: 'chan-nav-table.html' vs 'chan-nav-list.html'
dulapbot: Logged on 2021-08-23 16:05:46 billymg: fought with this for quite some time actually, until eventually gave up and provided two separate chanlist templates, one based on <table> to work with classic.css and to asciilifeform's specs in lynx, and one based on <ul> which renders as a stacked list in lynx (and however you want in graphical browsers, depending on the css)
billymg: your theme works with the table-based, mine works with the list-based
asciilifeform: billymg: a hm, i thought the list-based piece only worx w/ the sidebaristic 'dark' theme
billymg: this was because i assumed the vertical chan list in lynx was a hard req, and due to lynx's limitations could not get timestamps to sit under chan names without doing two rows (and having a weird tab order of chan, chan1, chan2, chan_ts, chan1_ts, etc...)
asciilifeform will have to reread whole thing
billymg: asciilifeform: nope, in fact had a css ready to go that would render in graphical exactly the same as you had on your theme prior
asciilifeform: hmm i thought this ~was~ 'classic.css'
billymg: asciilifeform: it is. two separate considerations: graphical rendering and lynx rendering
asciilifeform: btw asciilifeform must confess that he does not actually use lynx with any serious frequency. simply insists that any wwwtronic item of his ~must~ behave sanely in it, because in practice this ensures reasonable behaviour across graphical browsers.
asciilifeform: it is a kind of procrustean bed for www crapola.
billymg: to keep that 100% 1:1 with your previous theme (in lynx), had to keep the table. in graphical browsers, can switch to <ul> based and render exactly how you had it (and even make the improvements you want, such as auto wrapping)
asciilifeform: billymg: i.e. different browsers would get different html ? ( that's specifically not what asciilifeform wants )
billymg: asciilifeform: no, same html, always
billymg: asciilifeform: the lynx/graphical differences are just a result of lynx completely ignoring any and all css
asciilifeform possibly confused re what in the current vpress corresponds to the item in question
billymg: asciilifeform: your latest patch, style_fixes, did away with the two-row chanlist (where, roughly: <tr> chans... </tr> <tr> timestamps... </tr>)
billymg: which is what broke the lynx styling
billymg: i saw you added <br> tags, but lynx ignore those if used inside tables
asciilifeform: billymg: correct. so far i've not found a way to make a multi-row table 'wrap'
asciilifeform: anyways if billymg has an alternative variant, i'ma test it (reasonably quickly)
asciilifeform must bbl
billymg: asciilifeform: and in lynx you probably never will, lynx table rendering appears to be meant strictly for tabular data, not for layout tweaking
billymg: asciilifeform: my alt variant that i recommend is what you can see currently on my logger (in lynx, in graphical would be identical to your current theme but with properly wrapping rows)
billymg: asciilifeform: end result would be: 1, in lynx: what you see now on logs.bitdash.io, 2, in graphical: what you see now on logs.nosuchlabs.com. all clients (lynx, chromium, phones, etc.) would receive the same html, no server side tricks
vex: i'd guess the institutional bc keys are under a mountain. where the 556 shells come with extra paperwork
vex: lloyds prolly has a stack just in case. no need to report it
vex: asciilifeform's dream of $1 bc seems less likly than another 1.5 zeros on the exchange raTE
vex: my mathematics may be vexatious, but it's worth considering that these corporate structures also use legal frameworks to prtect their holdings
vex: I wonder whether asciilifeform has more distain for fluffypony or notoshi
vex: prolly both over 9000 on the hate-o-meter
vex: when did visa hire their blockchain dept? surely they have something better than "buy a cryptopunk"
vex: it's even a shitty troll if they've got something good... alibaba are doing intellectual property rights on chain, now that's epic
vex: later tell bingoboingo love the gardening show; healthy roots is healthy toots
vex: can't wait till you get the yt money and start doing punnet squares
vex: 35th parallell doesn't fuck about. put uy on the map
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-23#1053587 << the 'your favourite # of zeroes' thing is ~guaranteed~ to happen, eventually.
dulapbot: Logged on 2021-08-23 21:26:02 vex: asciilifeform's dream of $1 bc seems less likly than another 1.5 zeros on the exchange raTE
dulapbot: (alethepedia) 2020-10-11 asciilifeform: thimbronion: the altcoinists -- sure . but i was speaking of the fact that the exch rate prolly aint growing another 0 -- or rather, not w/out the dollar price of archaetypical sandwich also growing a zero.
asciilifeform: i.e. you'll read about 1e6$ btc -- while eating a 1e3$ sandwich.
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-23#1053588 << lol, y'mean like this ?
dulapbot: Logged on 2021-08-23 21:39:33 vex: my mathematics may be vexatious, but it's worth considering that these corporate structures also use legal frameworks to prtect their holdings
dulapbot: Logged on 2021-07-10 18:42:37 punkman: top kek "As part of regular monitoring of the network by the Bitcoin SV Infrastructure Team, the Association has been made aware of an illegal attack against the Bitcoin SV network. A malicious actor has recently been carrying out block re-organisation attacks on the Bitcoin SV network, which appear to be intentional acts in an effort to illegally
asciilifeform: much prtection..
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2021-08-23#1053589 << from my pov they're all 1 person
dulapbot: Logged on 2021-08-23 21:56:40 vex: I wonder whether asciilifeform has more distain for fluffypony or notoshi
asciilifeform: y'know, rather like 'dindus' are 1
asciilifeform: and all policemen. etc