asciilifeform: oduct that they will come to see as inadequate.
asciilifeform: http://logs.nosuchlabs.com/log/trilema/2019-10-23#1947784 << will say this : several folx expressed interest. but presently i do not know if will have ~any~ takers: for instance mp & diana_coman have very specific reqs that i dunno if can in fact fill. they might have to make own, heavy-industrial hosting system. all depends there on outcome of the costs-draft-then-flame process. i do not want to somehow bamboozle folx into buying pr
asciilifeform: ladies & gentlemen, please welcome back the designated ddos magnet, snsabot .
asciilifeform discovered today -- similarly to earlier find -- that his new ip range once housed a (long-dead) 'nudecelebritease.com' .
asciilifeform: ( 'do you expect me to...' 'no, mr. bond! we expect you to DIE!!!!'(tm)(r) )
asciilifeform: and incidentally, if asciilifeform cannot actually supply the service mp_en_viaje needs (e.g. if he needs a 24/7 staff of 4 working in shifts ) would rather know about it sooner than later.
asciilifeform: mp_en_viaje: re those '200 hrs' , if there are actually 200hr/mo required for any part of this, i'ma have to hire ( BingoBoingo ?? ) an assistant. i dun have 200h/mo hidden up sleeve.
asciilifeform: will detail this in rewritten piece .
asciilifeform: ( concretely : 4 'dulap'-style units , while (w/ mp_en_viaje-corrected set of constants) putting op +240 in +ev, in fact exhausts the energy allotment (not overruns, but leaves room only for rk plant.) and there already were requested, counting everyone who answered, tentatively 4 dulap's worth . (5 if counting shared-box) . )
asciilifeform: mp_en_viaje: not done w/ the 2nd set of numerics yet, but seems i may have ~opposite~ problem atm
asciilifeform: ( all folx considering emplacing ~anyffin~ in asciilifeform's rack -- plox to write in. no commitment is implied, would like to simply gauge the immediate prospects. )
asciilifeform: w/ the new philosophy of tmsr iron being spread out worldwide, i dunno what kind of occupancy can expect in the immediate term. which is why began with dwarf rack rather than shelling out for the full orchestra immed.
asciilifeform: for intervals of expansion : would also help if had any way to gauge demand. ( atm i have 1 ~maybe~ dulap-install being considered by diana_coman & mp. anyone else ? )
asciilifeform wonders if he's thinking about this backwards, and oughta instead model the upper half of (expanded) tower as a separate numeric system, w/ same constants but Te == 200.
asciilifeform: ( and right in re rk in draft 1 being catastrophically underpriced )
asciilifeform: BingoBoingo and mp were right, btw, it appears that a well-populated rk fixture (and, possibly, shared-machine) are the only way to actually cross that bridge w/out further raising subscriber colo charge.
asciilifeform: ( ^ in the simplest formulation, a full occupancy that brings in net >200 $ (the added expense of upgraded tower) w/out eating into irons amort. budget. )
asciilifeform will post in #2 example scenarios for 'full occupancy' and what is required to permit expansion of plant.
asciilifeform: ( elementarily, the irons ~must~ amortize in the given time spans, to cover cost of maintenance/replacement )
asciilifeform: i'ma have to recalculate w / machine-amort. as separate figure.
asciilifeform: ( in the black revenue-wise, that is; to cover the outlay for the machines per se would take at that rate 10y, supposing an improbably static btc exch rate )
asciilifeform will begin proper rework of costs draft #2 tonight. prelim. spreadshit however suggests that w/ 45% margin, three leased 'dulaps' already would bring in enuff to upgrade the tower (+20u, 10x pipe, 2x amperage) ~and~ remain in the black...
asciilifeform: DanielBTC (~macaxeira@unaffiliated/danielbtc) has joined #trilema << anyone know whothefuq that is ?
asciilifeform found that there ~remain~ 'microshit quotes' in certain posts, where text had evidently been pasted from wp output. will have to write a sqlism to remove'em, but prolly not today an' not this week.
asciilifeform: when moved, will finally have that static ip...
asciilifeform: fwiw it has never been detectably vandalized, to date.
asciilifeform: BingoBoingo: my wp is squarely a 'legacy system', analogous to e.g. 'mpb'. i dun propagandize its use, nor intend to separately genesis it, imho mp has the wp question 100% covered .
asciilifeform: it's a manually gardened wp (if not as elaborately cultured as mp's) .
asciilifeform: hell knows. seems to remove the mutilation tho, w/out breaking anyffin (if anyone sees a breakage from this patch on my www, or remaining mutilated quotes -- plox to write in)
asciilifeform: BingoBoingo: ty, that actually worked. ( tho, funnily, i had to correct the author's own piece, on ~his~ wp evidently did NOT work, his contained microshit-quotes!! )
asciilifeform: the human-readable urls thing in particular, in mpwp, is quite appetizing.
asciilifeform: BingoBoingo: i expect to move entirely to mp's wp when i get to moving www finally. but atm hands quite full. ( it'll be somewhat tricky, will have to port the coad printer extension thing to it, and various other things i changed over 12yrs+ of my www)
asciilifeform: tangentially, other mp_en_viaje point -- anyone readily recall how to banish mutilation of quotes from wp? ( aka 'microshit quotes' )
asciilifeform: diana_coman & mp_en_viaje are the king/queen of the prospective customer base, by weight, and so if no one adds anyffin in next few hrs, i'ma work w/ what's been given so far for draft 2.
asciilifeform: would like to accumulate all possible nitpicks of 1 before setting out tho.
asciilifeform: diana_coman: moar in brief re expansions (will address pedantically in draft 2) -- they will have to be financed by actual revenue, and BingoBoingo-style auctions, i do not have massive capital (and what i have, is earmarked for physical irons, already ordered 'dulaps' and will be purchasing yet-moar of'em once it becomes clear that asciilifeform won't live alone in the rack)
asciilifeform: on top of this, i have a gentoo for'em; an automated system for provisioning; and rk is 'most cpu for the watt' box that i'm currently aware of, is imho excellent fit for a wattage-constrained initially small tower.
asciilifeform: diana_coman: re rk -- i included rk plant from the following logic : 1) it was best-selling product in era of piz 2) i am sitting on a crate of brand-new rk that did not get invoiced to piz or get to fly 3) pre-existing interest ( e.g. diana_coman's ) in inexpensive www mirrors.
asciilifeform: diana_coman: 'fully populate' i expect will happen quickly when l1 finds prospectus satisfactory. e.g. 4 'dulap'-type boxen and 1 shared-www per BingoBoingo's schematic already exhausts the energy supply. at which pt i'ma expand to full tower. and diana_coman is right imho, this oughta be detailed in 2nd draft.
asciilifeform: the 'solvent' part imho is satisfied by even draft 1. the 'expand' i think deserves more space.
asciilifeform: 'this is rubbish, not a proper plan' is not an eggog that i can work from, diana_coman . need detailed 'why, idjit, didntcha explain x?'
asciilifeform: but will have to be specific crit, like mp_en_viaje's.
asciilifeform: diana_coman: if it wasn't clear from thrd, i intend to give the askers what they are asking.
asciilifeform: diana_coman: it's simple logical consistency. why apply 1 standard for rack where park 0.1btc of box, and an entirely diff for wallet where park dozens of btc ?
asciilifeform: if it takes 5 writes -- than 5 writes.
asciilifeform: i'ma rewrite that thing until it actually satisfies all of the prospective inhabitants, would like to start the commercial life of the thing asap.
asciilifeform: that being said, if diana_coman has specific 'what about x', plox to comment, i'ma address in 2nd draft along w/ mp_en_viaje's crit.
asciilifeform: and typically elaborate biz plans are written for ~investors~ rather than customers, afaik. imho it is reasonable for folx considering to park expensive irons to ask for 'how you plan to remain solvent', hence this thread. but 'how you plan to become rockefeller' is imho tall order. esp. since i've atm no plan to become rockefeller via this work.
asciilifeform: http://logs.ossasepia.com/log/trilema/2019-10-22#1947558 << i considered pre-ordering ( it'll be 62, 14 for 1us and 48 for rk plant, i.e. a /26 ) but that'd be 200/mo vs the current baseline 25, and hesitated to do this until rack actually populated by paying customers, it is steep cost for an empty-for-indefinite-time rack.
asciilifeform: http://logs.ossasepia.com/log/trilema/2019-10-22#1947552 << imho this is a+++ idea. tho as i understand all of the prngism applies strictly to /dev/urandom and so not particularly important how it is wired, no one in his right mind will use urandom for anyffin serious
asciilifeform: other omissions in the draft include FG -- i dun presently have a 'equip erryone who asks' supply of'em here. can equip mp_en_viaje & co, but others will have to wait for wat-do re recovery of FG from piz crater
