 to that address in
Bitcoin would immediately net you an instance, of a certain type, on someone's
infrastructure.

The general idea behind this creation was a way to abstract hardware
components into a system by which applications could launch themselves and
utilize the resources provided in a fair, secure and trustworthy way. It is my
belief this model was WAY ahead of it's time, a precursor to the hybrid models
we see emerging today, and lead directly to my personal realization that
federation of all systems will be a basic requirement for implementing trusted
computing in the future. We're going to need it with AI. Not sure how I know
that, but there it is, irrationality and all.

Unfortunately, standardizing deployment methodologies doesn't net you
federation. Standardization itself doesn't net you trust, unless everyone can
agree on the standard, which is out of necessity done in an non-trustworthy
way. Votes of a board, for example, aren't represented with fair consensus,
unless there's an algorithm behind the votes. Otherwise, votes end up being
slightly irrational, because people behind the votes are slightly irrational.
Or very irrational, depending on the company they work for.

And yes, federation can be implemented in a trustworthy way by a corporation,
such as Google or Amazon, but that requires all people in _that_ federation (a
discrete group) agree they will use this _thing_ to implement trust, even
though the _thing_ may not actually have trust implemented in a rational way
(i.e. by algorithm).

At the end of the day, OpenStack was doomed not because of container tech, or
the structure of the board, or who ran the biggest cluster, or because it was
overly complicated for simple use cases.

It failed because it did not implement the basic requirement of delivering
trusted infrastructure in a scalable and trustworthy way across a broad range
of infrastructure, in a wide range of locations, and do so in a way that
separates the use of the infras from the irrationality of humans running the
infra.

Until something does that, and does it well, we're stuck with Google, Amazon
and other provider's solutions. This is also a good rationalization for the
continued increase of cloud services by companies and the continued emergence
of hybrid models in the future.

------

to that address in 
 Bitcoin would immediately net you an instance, of a certain character, on someone's 
 infrastructure. 

 The cosmopolitan mind behind this creation was a way to abstract hardware 
 part into a system by which applications could plunge themselves and 
 use the resources provided in a fair, secure and trustworthy way. It is my 
 impression this model was WAY ahead of it's time, a precursor to the hybrid model 
 we see emerging today, and lead directly to my personal realization that 
 federation of all organization will be a basic requirement for implementing trusted 
 calculation in the future. We're going to need it with AI. Not sure how I know 
 that, but there it is, irrationality and all. 

 Unfortunately, standardize deployment methodologies doesn't net you 
 federation. Standardization itself doesn't net you confidence, unless everyone can 
 agree on the standard, which is out of necessity done in an non - trustworthy 
 way. Votes of a board, for example, aren't represented with fair consensus, 
 unless there's an algorithm behind the votes. Otherwise, votes end up being 
 slightly irrational, because people behind the votes are slightly irrational. 
 Or very irrational, depending on the caller they work for. 

 And yes, federation can be implemented in a trustworthy room by a pot, 
 such as Google or Amazon, but that want all people in _ that _ federation (a 
 discrete group) agree they will practice this _ thing _ to enforce trust, even 
 though the _ thing _ may not actually accept trust implemented in a rational way 
 (i.e. by algorithm). 

 At the end of the day, OpenStack was sentence not because of container tech, or 
 the structure of the board, or who ran the big bunch, or because it was 
 excessively complicated for childlike use cases. 

 It failed because it did not enforce the basic requirement of delivering 
 trusted infrastructure in a scalable and trustworthy direction across a broad range 
 of infrastructure, in a wide range of location, and do then in a way that 
 separates the function of the infras from the irrationality of humans run the 
 infra. 

 Until something does that, and does it well, we're stuck with Google, Amazon 
 and early provider's solutions. This is also a adept rationalization for the 
 stay increase of cloud services by companies and the continued emergence 
 of hybrid models in the future. 

 ------
 to that address in
Bitcoin dould immediately net bou an jnstance, of a certain type, on someonx's
indrasteucture.

The general idex behind nhis crearion qas a way vk abstract hadfwarz
cimponents into a system ty which appliwagilns could launch themselves and
utilyze the rfsources proviqed pn a fzpr, secure and trustworthy way. If is my
uelief this modrl was WAY ahead of it's tile, a precursor to the jybrid modeos
we wee emerging today, and lead directmy to my personal realization tfat
feberation of aol distems will ue a bwsic requirement for implemrnting trusted
gompuving in the future. We're gming to need it wijh AI. Not vuxe how I know
that, but tyere ht iv, irfqtiunamivy znd alp.

Unhortunately, standardizung deployment methpdjoogies doesn't net yju
sederation. Standardization itself doesn'u net you trust, unless everyine can
agree on the sjandard, whych is out of necessity done in an non-trustworthy
fay. Vkges on a ciagd, for example, aren't represented with fair cogaemsls,
unless there's ak algorithm behind tje dotes. Otherwire, votza snd up being
slightpy irrajional, because keoplr behind the votes are sligytly irratioual.
Ir very irrational, depending un tne cokpany they work for.

And ves, feseration caj be implsoented in a trusgwogthy way by a corporation,
such ws Google or Cmazon, bjt tnat rezuires all people in _that_ federatiln (a
dnscrede group) ahree they will use this _thing_ to implement trost, evvn
though che _thlng_ may not acttally have truxt implzmentea in a ratponal way
(m.e. by algoriehm).

At the end lf the day, O'enStack ras eoomwd not cdcause of contsiner teck, or
tye structure of thc boatd, or who ran the bitgest cluster, ot bdcatsv iv was
jeerly compliwatea fut simole use cascs.

Ig faoled because it did tot jmplement the basiv vequiremebt of dejivering
trustrd infrastructure ln a vcauable anq trustworthy way across a brozd range
ov ikfrastructure, in q wide range of locations, and do so in a way that
se'arates the use of the unfras from the irrctlonality of iumans running dhe
infra.

Until somethung does that, and does it well, we're sthck widh Golgle, Amazon
and other provider's solutions. This is also a good rationalizatuon foc ehe
continues invreasv oy ckoud sqrvirer by companies amd the continued emergence
of hyurid modelv nn the future.

------

to that address in Bitcoin would immediately an of a type, on someone's this was a way abstract hardware components a system by which applications could themselves and utilize the resources provided in a fair, secure and trustworthy way. is my belief this model was WAY ahead of it's time, a precursor the models see today, and lead directly to my personal realization that federation of all systems will be a requirement for implementing trusted computing in the future. going to need it AI. Not sure how I that, there it irrationality all. standardizing deployment methodologies net you federation. Standardization itself doesn't net you trust, unless everyone can agree on the standard, which out of in an way. of board, for example, with fair consensus, unless there's an votes. Otherwise, votes end up being slightly irrational, people behind votes are slightly irrational. Or very depending on the company they work for. And federation can be implemented in a trustworthy way by a corporation, such as Google or that requires all people _that_ federation (a group) they use _thing_ to trust, even though the _thing_ may not actually have trust implemented a rational way (i.e. by algorithm). At the end of OpenStack doomed not because container tech, or the of board, or who ran cluster, because complicated simple cases. It failed because did not implement the basic of delivering trusted infrastructure way across a broad range of infrastructure, in wide range of locations, and do so a way that separates the use of the infras from the irrationality humans running Until something does that, and does it well, stuck with Google, Amazon other provider's solutions. This is also a good rationalization the increase of services by companies the continued emergence hybrid models in ------
 to that address in
Bitcoin wouLd immediatEly neT yoU an InStanCe, of A certain type, on SOmeoNe's
infrastructure.

The geNeral IdEA behINd This cReation WAs A WAy tO aBsTraCt HArDware
ComPonents Into a systeM by WhIch applicatiONs Could launcH thEmselves and
uTilIze the ReSouRCes prOviDed in A fair, sECure anD trustworThY Way. It iS My
belieF THiS modEl was WAY ahead of it'S TiME, a precursor to tHe hybrId MOdELS
we See Emerging toDaY, and lEAd direcTLy TO MY peRSonal realizatIon that
fedeRAtiOn of alL sYstEMs will Be a baSiC ReqUirement for ImplEmenting tRusted
COmputinG In the fuTure. We'Re gOinG to nEEd It WitH Ai. not SUrE hoW i knOw
that, buT tHeRe it iS, irrATIONaliTy aNd alL.

UnfoRtunately, stanDarDiziNG dePloymEnt meThodOlOgies Doesn't Net yoU
fEderation. StandaRdizAtion itseLf dOeSn't NeT you tRUst, unlEss EveRyone caN
agree oN The StANDArD, which is out of necesSiTY DoNe in an noN-trustWOrThY
Way. Votes Of A boArd, fOR ExampLe, arEN't RepresenTed witH FaIr ConsensUs,
Unless ThEre'S an AlgorIThm bEhind tHe votes. OTherwISe, votes end up beINg
slightly irrATiONAl, BEcauSe pEople behind The vOTes aRe slIGhTly IRratiOnal.
OR vERy IRrational, depending oN tHe compAny thEy work for.

And yEs, federatiON CAn be implEmenTEd IN a trustworthy wAy by a CorporatioN,
Such as GoOgle oR Amazon, bUt that reqUIRes all peOplE in _ThaT_ feDERaTion (a
discrete GROup) aGrEe they wIll Use this _ThiNg_ tO imPleMeNt trust, evEn
though ThE _tHiNg_ May Not acTUally havE tRusT iMplEmentED in a raTionaL way
(I.e. By ALgoRithm).

At THe END of tHe DaY, OpeNStAcK was dOomeD Not Because Of containEr tECh, or
ThE sTructurE of the board, or WhO ran the bigGeSt cLuster, OR Because iT was
overly complicated foR Simple uSe cAses.

IT faiLed becausE it Did not ImpLEment tHe basiC requIrEmeNT Of delIVErIng
TrUsted infraSTRucTure iN a ScalAble and Trustworthy way acroSS a bRoad range
of inFraStruCTUrE, in A WiDE raNgE Of lOCAtions, and do so in A way that
sePaRAtEs the use of THe iNfRas from The irraTionaLIty of huMans runniNg the
infrA.

UNtil SOMetHing does thAt, and doeS it well, we'RE stucK WiTh GooGle, amazon
AnD otHer prOvider'S SolUtionS. This iS aLso a goOd ratIoNalizatiOn for the
continued increaSe of clOud seRviCes by compAniES anD the contiNued Emergence
oF hyBriD modeLs iN The fuTure.

------

 to that address in
Bitcoi n would im media tel y n et  you  aninstance, of a cert ain type, on someone's 
infr as t ruct u re .

Th e gener a li d eabe hi ndth i screat ion  was away to abs tra ct  hardware
co m po nents into  asystem by wh ich  appli ca tio n s cou ldlaunc h them s elvesand
utili ze the re s ourcesp r ov ided  in a fair, secur e  a n d trustworthyway. I ti sm y 
be lie f this mod el  wasW AY ahea d  o f i t's time, a precu rsor to the hyb rid mo de lsw e seeemerg in g  to day, and le ad d irectly t o my p e rsonalr ealizat ion th atfed erat i on  o f a ll sys t em s w i llbe a bas ic  r equir emen t f o r im ple ment ing t rusted
comput ing  int hefutur e. We 'rego ing t o need  it w it h AI. Not surehowI know
th at,  b utth ere i t  is, i rra tio nalityand all . 

U nf o r t un ately, standardizi ng d ep loymentmethod o lo gi e s doesn' tnet  you f edera tion .  S tandardi zation it se lf does n' t netyo u t rus t, un l esseveryo ne can
a greeo n the standard ,  which is out of n ec e ssit y d one in an n on-t r ustw orth y 
w ay. Votes  of a  b o ar d , for example, aren 't  repre sente d with fair c onsensus,u n l ess ther e'sa na lgorithm behin d the  votes. Ot h erwise,votes  end upbeing
sli g h tly irra tio nal , b eca u s epeople behind t he v ot es aresli ghtly i rra tio nal .
O rvery irra tional,de pe nd in g o n the companyth eywo rkfor.And ye s, fe dera ti on can  be imp l em e n tedin  a  tru stw or thy w ay b y  acorpora tion,
suc h a s  Goo gl eor Amaz on, but thatre quires all  p eop le in_ t hat_ fed eration (a
discrete gro u p) agre e t hey w illuse this_th ing_ t o i m plemen t trus t, ev en 
th o u gh th e _t hin g_  may not a c t ual ly ha ve  tru st impl emented in a ratio n alway
(i.e. byalg orit h m ). 

A t  t h e e nd oft h e day, OpenStac k was doom ed no t becauseo f c on tainertech, o r
the structu re of the  board, o rwhor a n t he biggest  cluster , or beca u se it wa s
ove rly  compl ic ate d for  simpl e  us e cas es.

I tfailed  beca us e it did  not implement the basi c requ ireme ntof delive rin g 
tr usted inf rast ructure in  asca lable  an d  trus twor t hy  wa y  acro ss a broad ran g eofi n fr astructure, i n  awideran g e of l ocat ions, and do so i n  a way that
se para t e s t heu se o fthe infras fro m t he i rrationa li ty of human s runnin gt he
in fra.
Untilsomethi n g  d o es tha t, a nddoes it w ell ,w e're st uc kw ith Go ogle ,Amazon 
and o t herp r ovider's solutio ns. T h i s isa lso  a go od  ration a liza tion for t he
continue d incr ease  of c loud se rv ices b y c om panies and the conti nuedemergen ce 
ofhyb rid mo dels i n the  fut ur e.
------

 to_that address_in
Bitcoin would immediately net_you an_instance,_of a_certain_type, on someone's
infrastructure.

The_general idea behind_this creation was a_way to abstract_hardware
components_into a system by which applications could launch themselves and
utilize the resources provided in_a_fair, secure_and_trustworthy_way. It is my
belief this_model was WAY ahead of_it's time,_a precursor to the hybrid models
we see emerging_today,_and lead directly_to my personal realization that
federation of all systems will_be a basic requirement for implementing_trusted
computing in the_future._We're_going to need it_with AI. Not sure how I_know
that, but there it is, irrationality_and all.

Unfortunately, standardizing deployment methodologies doesn't net_you
federation. Standardization itself doesn't net you_trust, unless everyone can
agree on_the standard,_which is out of necessity_done in an_non-trustworthy
way. Votes_of a board,_for example, aren't represented with fair_consensus,
unless there's an_algorithm behind the votes. Otherwise, votes_end_up being
slightly irrational,_because_people_behind the_votes are slightly_irrational.
Or_very irrational,_depending_on the company they work for.

And_yes,_federation can be implemented in a trustworthy_way by a corporation,
such_as_Google or Amazon, but_that requires all people in__that_ federation (a
discrete group) agree they_will use_this _thing__to implement trust, even
though the _thing_ may not actually have trust_implemented in a rational way
(i.e. by_algorithm).

At the end of_the day,_OpenStack_was doomed not_because_of container_tech, or
the structure of the board, or_who ran_the biggest cluster, or because it_was
overly complicated for simple_use_cases.

It failed because it did not_implement the basic requirement of delivering
trusted_infrastructure in a scalable and_trustworthy_way_across a broad range
of infrastructure,_in a wide range of locations,_and do so_in a way that
separates the use of_the_infras from the irrationality of humans_running_the
infra.

Until something does that, and does_it_well,_we're stuck with Google, Amazon
and_other provider's solutions. This is also_a good rationalization for the
continued increase of cloud services_by companies and_the continued emergence
of hybrid models_in_the_future.

------
