230500+ entries in 0.146s
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!
a111: Logged on 2016-12-26 06:07 pete_dushenski: naturally,
the deal is being sweetened : ""All
those who invest in Bitstamp on
the BnkToTheFuture platform before midnight 1 January (UTC -12) can now get 12 months of anti-dilution protection on
their investment!"
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.
☝︎ pete_dushenski: naturally,
the deal is being sweetened : ""All
those who invest in Bitstamp on
the BnkToTheFuture platform before midnight 1 January (UTC -12) can now get 12 months of anti-dilution protection on
their investment!"
☟︎ pete_dushenski: holy fuck are
they cheap
too. boxes
that were $8k a decade ago are now cad$100. basically free.
pete_dushenski: this is only partially disappointing because i) no one ever said macs were computers anyways, and ii) who doesn't like new
toys ?
pete_dushenski is also spending holiday
time shopping for boxen on which
to run eulora because mac hack is more hassle
than it's worth.
pete_dushenski: they're often either
too sweet or
too buttery but can be made
to be quite
tasty by savvy bakers.
pete_dushenski: mircea_popescu: i guess
too busy making lasagna and quiche (like rest of
tmsr!). homemade nanaimo bars
too.
mircea_popescu: pete_dushenski you know ftr sourdough is supposed
to be made at home.
phf: (i remember
there being a standalone sha256 (?) version for sbcl, but i can't find it now. everything crypto
that's coming up re lisp is ironclad.)
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.
phf: re "liberty with whitespace"
there's something else going on. it's doing everything
through unsigned-byte 8
phf: asciilifeform: for
the record
there's not a single line of ffi in ironclad. we've had
this conversation before
ben_vulpes: well
that'd be in stark contrast
to
the claim i remember
Framedragger: (and don't use 'adopted storage' in android in
the future. it's stupid.)
a111: Logged on 2016-12-25 15:51 Framedragger: i don't suppose anyone here has messed with android 'adopted' storage? (use sd card as internal encrypted android storage.) i'm
trying
to recover files from a half-broken 32GB sd card which has weirdo android-internal partitions and encryption.. oh god
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.
Framedragger: mircea_popescu are you referring
to
the
time-honoured "put some irc logs into deedbot" practice? :D (that i'd seen)
mircea_popescu: Framedragger we do also have a scheme whereby we save
the plain data and deedbot under consideration, but meh.
BingoBoingo: links are a courtesy, if html soup dies
then it dies
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.
Framedragger: unrelated; such heavy reliance on archive.is by qntra, irc forum et al. scares me. it seems
to be doing ~fine and i like
the owner's attitude (
http://archive.is/faq), but 'someone' should make another one
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.
ben_vulpes: it is a small but worth-noting difference between "put yer patches in
this here directory, your signatures in
this other, and your pubkeys in
this
third".
☟︎ 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.
ben_vulpes: in which i realize
that
to get code review in
tmsr you have
to paste it into irc one line at a
time
ben_vulpes: the naive o(n^2) calculation is
to say "there is a signature for
this patch" and not giving a shit about which signature, provided it corresponds
to a key in .wot .
ben_vulpes: look i'm pointing at a promisetronic bit of v and saying "hey look i
think
this is a bit floppy"
ben_vulpes: also
that mothers know which baby is
theirs and a signature can't
tell me which patch it belongs
to
ben_vulpes: i was holding
that one in abeyence for lols
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" ?
ben_vulpes: it costs in complexity, yes. could be argued
that it is a very minimal cost, but i would still prefer
to "pick any signature from .seals
that verifies" instead of
the by my read promisetronic "pick any signature whose filename contains
the filename of
the patch under verification"
ben_vulpes: i suppose
there's no practical way around
the patches and signatures sharing a prefix.