103300+ entries in 0.03s
mircea_popescu: o wow look at this, etymolone.com has it! "Rare 17c., revived from late 18c. in sense "to strive (alongside another) for the attainment of something" and regarded early 19c. in Britain as a Scottish or American word. Market sense is from 1840s (perhaps a back-formation from competition); athletics sense attested by 1857." is exactly correct for once.
mircea_popescu: hence why it's even fucking called "competition", from latin for "to strive together", competere. same com as in commune.
mircea_popescu: fall behind them" version of mutual driving would historically be what competition meant. this mutual-inhibition style of competition where "we all try kissing girls when we're 7, then those who don't manage having been outcompeted by those who did manage retire to kiss playstations" is novel.
mircea_popescu: i suppose in a forgotten sense this is actually what "competing" means ; walk is "leg competitive" in the sense that the movement of one drags/forces/impels the movement of the other ; tissue growth is competitive in the sense that conjunctive growth drives medular growth and medular growth drives conjunctive growth ; the very chinese (these days) "barracks area B planted roses, can we from barracks area C allow ourselves to
mircea_popescu: hardly competing. just because item b depending on item a for part of its job may end up having to implement a doesn't mean b competes with a.
mircea_popescu: ben_vulpes i r guess in some cases trilema titles are too trite.
mircea_popescu: !~google Slavery : the best thing for you. No, seriously.
mircea_popescu: Framedragger you're going towards the republican dns / unified name registry thing
☟︎ mircea_popescu: ie, if P uses 8 boolean flags and 31 one byte settings then e can be a 32 byte value
mircea_popescu: in principle the e, N part can be arbitrarily lengthy, with the semantizating convention that "e" represents "settings" and N represents "values". should be perfectly possible to describe any future key in these terms irrespective of cryptosystem.
mircea_popescu: (if "userstring" is redefined to be for eg "a";"b" items nothing breaks.)
mircea_popescu: would work. moreover the scheme is flexible enough to allow for later extension
mircea_popescu: note that because of alf's more complex hashing scheme you actually get closer to "permanent" urls than the imperial key servers can get.
mircea_popescu: incidentally, patches currently can be arbitrarily renamed with no visible effects is it ?
☟︎ mircea_popescu imagined everyone knows about that owing to his constant usage.
mircea_popescu: the judge ate it, of course, but let it be pointed out this is so fucking ridiculous as to defy any reason. there is NO information privy to the USG that is secret from the world, except by case of obscurity.
mircea_popescu: the usgians of course don't want him to be released, so they have this parole thing where he can't leave the us "for five years" and "can't use internet or give interviews" etc. the stance was challenged a few months ago on the correct basis that "nothing he stole or could have stolen 30 years ago is still secret today". nevertheless clapper chose to perjure himself by swearing for the judge that on the contrary, the usg actu
mircea_popescu: and in other lulz : jonathan pollard, a guy who stole and sold (to israle, and to others) all sorts of holies of the usg (including the nsa's utterly ridiculous 5k page manual on "how to conduct signals intelligence" - no part of which is actually useful in practice much like satoshi's bitcoin miner code is not used by any actual bitcoin miners) was released in 2015 (with much gnashing of teeth, because back whgen he was conv
mircea_popescu: in other news, holy shit the white house interiors are an abomination. there's flea markets more tastefully arranged by the process of randomly unloading vans what the fuck.
mircea_popescu: then they wonder why the barriers in front of them are only going up. because seriously, who could POSSIBLY not want anything to do with idiots this idiotic. who! who!
mircea_popescu:
http://btcbase.org/log/2016-12-26#1590742 << and in typical fashion of the utterly imbecile "average joe", the idiots wish to opine about the viability of mpex, where no issuer EVER diluted, and say nice things about pure and simple scams with free dilution a la twocan exchange.
☝︎ mircea_popescu: pete_dushenski you know ftr sourdough is supposed to be made at home.
mircea_popescu: (in principle the off-bits versions, 299, 511, whatever monkey numbers should be merely truncated versions of the immediately above hash. but who even knows by now.)
mircea_popescu: also if they "publish" it in klyngon, or in cuneiform, or etcetera. published means it works on computers.
mircea_popescu: check that out, there's no actual fips 180 past 1 published online. because why the fuck would there be. anyway, i can't source this "The SHA512/384 spec says that the final bit length of the message is to be stored as a 128-bit (!) integer at the end of the message." assertion. as best it can be determined the blocks are either 512 (for sanity) or 1024 bits (for 384 hmac etc)
mircea_popescu: h of a padded message a multiple of 512. The SHA-1 sequentially processes blocks of 512 bits when computing the message digest. The following specifies how this padding shall be performed. As a summary, a "1" followed by m "0"s followed by a 64-bit integer are appended to the end of the message to produce a padded message of length 512 * n. The 64-bit integer is l, the length of the original message. The padded message is the
mircea_popescu: "The SHA-1 is used to compute a message digest for a message or data file that is provided as input. The message or data file should be considered to be a bit string. The length of the message is the number of bits in the message (the empty message has length 0). If the number of bits in a message is a multiple of 8, for compactness we can represent the message in hex. The purpose of message padding is to make the total lengt
mircea_popescu: i see the link. i suspect variant sha512 implementations.
mircea_popescu: i have nfi why it was even specified other than a love of bloat. all the bs 224 384 blabla does not belong. either you word allign or go away.
mircea_popescu: Framedragger nah, it's in the logs, have an auto dld of links
mircea_popescu: imagine, to go in trying to fight "world problems", to be fucked raw by putin and eventually defeated... by fucking israel.
mircea_popescu: "I knew Obama was looking to take sweet revenge against Israel and Netanyahu. Since he was elected in 2009, he was hostile to settlements and Netanyahu. He revealed his true face with an anti-Israel decision but Netanyahu and Israel will defeat him." << they very likely will, too.
mircea_popescu: Framedragger we do also have a scheme whereby we save the plain data and deedbot under consideration, but meh.
mircea_popescu: the problem of saving html soup well is hard ; phf announced working on it some time ago but i dunno how it goes.
mircea_popescu: anyway the jewish thing is proceeding nicely, israel no longer funding un bodies ; israel ministers no longer allowed to visit countries or meet officials from 14 list.
mircea_popescu: now, there's entirely nothing "promisetronic" about people providing seals named as their patches are named. if they fail to do this - their patch won't work.
mircea_popescu: anyway, the idea is maximum power for the user. a scheme whereby i am forced to check all seals for each patch dispowers me ; a system whereby i can always resolve each patch in at least 1 checks or however many i feel like doing empowers me.
mircea_popescu: (and please don't tell me your idea is that the reason room-fulla-puppies isn't how maternity wards are ran is because cunt runs on perl and most kids therefore fit to most teats.)
mircea_popescu: i dunno how either the current method adds complexity (show this ?) or the alternative isn't rank insanity. why should i have to look at >1 seal to verify a patch ?
mircea_popescu: i don't get it. suppose you ran a maternity ward, would you go "adding nametags to the kids adds complexity, just send the mothers naked in a room fulla puppies let them pick which fit to their teat" ?
mircea_popescu: ben_vulpes just have it silenty discard all patches that aren't sealed properly for the narrow definition of properly neh ?
mircea_popescu: ben_vulpes to my eyes "the situation" ie, the developer's own private choice, illustrates the natural tendency of one to cruft up his workbench.
mircea_popescu: anyway alf has it - there's no need to handle what you list other than by not using them
mircea_popescu: it's hard out there for a cuck when tryina make da money for da lulz
mircea_popescu: anyway, it's mildly amusing to watch internet people act under a very earnest notion that the portion of any one thing that they ran across has, grace to half a minute's meditation, formed a complete and useful image in their heads.