tmsr - Search: read the log

580 entries in 1.007s

lobbes: I was going to hop on to state this very point, but alf beat me to it so I will simply underline and point to trilema article referenced twice above. My own trust for various people (read: cryptographically backed identities) in here was not immediate, but evolved over the 4 years I've spent interfacing with said people. >> http://btcbase.org/log/2018-04-12#1797719 ☝︎

a111: Logged on 2018-04-11 10:14 spyked: anyway, I'd be happy to read a version of http://btcbase.org/log/2018-04-11#1796038 (or better yet, a blog post/series) that explicitly references or otherwise explains all the priors and provides an actual proof, not just "we model this in tamarin, gtfo, install it and read the proof it generates". I want to be able to find out precisely what "symbolic reasoning/analysis" means in their universe, wtf is a "message deduction theory"

spyked: anyway, I'd be happy to read a version of http://btcbase.org/log/2018-04-11#1796038 (or better yet, a blog post/series) that explicitly references or otherwise explains all the priors and provides an actual proof, not just "we model this in tamarin, gtfo, install it and read the proof it generates". I want to be able to find out precisely what "symbolic reasoning/analysis" means in their universe, wtf is a "message deduction theory" ☝︎☟︎

mircea_popescu: anyway, there's a lot for you to read wrt to why specifically segwit is a usg-driven attack against bitcoin, and not supported by the bitcoin foundation. perhaps the recent http://btcbase.org/log/2018-04-11#1795944 is a good starting point ; but generally the logs are your friends, search them. ☝︎

asciilifeform: http://btcbase.org/log/2018-04-11#1796063 << the most important documents are ~not there~ for him to read : i.e. the wholly-absent proofs of strength for any of the symmetric poppycock ☝︎

mircea_popescu: read the log, they had a whole thing recently with like 100kgs worth of various shit.

mircea_popescu: http://btcbase.org/log/2018-04-06#1793484 << basically the "girl gets restless on farm, joins gypsy caravan to get pregnant" story retold, in up to date terms. i suppose the slice of about-read-to-great-again us as the third world shithole it ~actually~ is has some documentary value. ☝︎

asciilifeform: going by the log in #asciilifeform-test, d00d 1) still refuses to actually read the proggy 2) continues to think that it remaining standing has something at all to do with 'sanitizing' or anticipating whatever attack

asciilifeform: tho the moar likely explanation is that trinque read the machine log, and, laughing, went to look at what was in yer intended payload url

phf: http://btcbase.org/log/2018-03-30#1791228 << i'll publish the relevant patchsets on btcbase this saturday; i've read the relevant specs and the issue seems to be straightforward, what is annoying though is that for whatever reason it's not uniform across platforms. ☝︎

asciilifeform read the log just nao, and can't quite figure out whether ave1 was attempting to implement a mechanism similar to asciilifeform's ch8 ( http://www.loper-os.org/?p=2175 ) or something entirely else

mp_en_viaje: http://btcbase.org/log/2018-01-30#1778242 << nah, for one if you set up her bouncer you can read her logs, and for the other it breeds bad habits. she can do it herself once i get around to putting it on her menu ; meanwhile if enough folk complain ima just have her not chan till then ☝︎

a111: Logged on 2018-01-24 17:07 lobbes: http://btcbase.org/log/2018-01-24#1775207 << impressive. Makes me think about the self-referential nature of logs. As time moves forward, being able to say "I read x unit-of-time worth of logs" will require more and more reading to comprehend same unit-of-time due to growing "webs of threads"

a111: Logged on 2018-01-24 05:42 mircea_popescu: in other shit you never heard before, new slut claims to have read the previous month's worth of logs ~last night~. i think i'm moving the bar to "a minimum of 65 years' worth of log reading" on the basis of this one datapoint.

lobbes: http://btcbase.org/log/2018-01-24#1775207 << impressive. Makes me think about the self-referential nature of logs. As time moves forward, being able to say "I read x unit-of-time worth of logs" will require more and more reading to comprehend same unit-of-time due to growing "webs of threads" ☝︎☟︎

mircea_popescu: in other shit you never heard before, new slut claims to have read the previous month's worth of logs ~last night~. i think i'm moving the bar to "a minimum of 65 years' worth of log reading" on the basis of this one datapoint. ☟︎

mircea_popescu: http://btcbase.org/log/2018-01-23#1774921 << amusingly i read it as a "well, gotta put best foot forward and don best suit", kinda unconvinced of why or what the fuck subjhectively, "but what can you do". which is why i just ignored it, triggered none of my tripwires. while apparently hitting TWO DIFFERENT!!! immune system protein pathways in two different people. ☝︎

asciilifeform: http://btcbase.org/log/2018-01-16#1770914 << this is a classic piece and i recommend for all of the folx here, to read it, if they had not already read it. ☝︎

BingoBoingo: <mircea_popescu> jurov iirc it was briefly discussed. the risk of doing such a thing in orc (read : http://btcbase.org/log/2014-03-17#563333 ) is that you acquire debt you don't know about, and can't properly verify afore the fact. << And the ask here for shelf corps starts at 3k -6k USD with that risk ☝︎

mircea_popescu: jurov iirc it was briefly discussed. the risk of doing such a thing in orc (read : http://btcbase.org/log/2014-03-17#563333 ) is that you acquire debt you don't know about, and can't properly verify afore the fact. ☝︎

asciilifeform: http://btcbase.org/log/2018-01-07#1766213 << d00d freely conversed in the langs of europe, had classical education, read his frege, etc and was no more 'neet' than e.g. mircea_popescu , socrates, et al ☝︎

PeterL: http://btcbase.org/log/2018-01-06#1766126 << so I was like "how hard could this be?" and I am trying to wrap my head around what this comes from, so I open up the gpg source code, and bleh, code is sooo much easier to read when it is written in ada by asciilifeform! ☝︎

asciilifeform: PeterL: so to find how it is broken, you will have to ask the folx who believe that it is broken, when they wake up. or at the very least, to read the log.

mircea_popescu: http://btcbase.org/log/2018-01-05#1765119 << this is actually the most cogent critique of phalocentrism in computing i ever read. ☝︎

mircea_popescu: http://btcbase.org/log/2018-01-05#1765028 << lmao this guy. YOU PUT IT THERE! and moreover... what is the logic of "begins to suspect that ~nobody actually read ch5" when "it survived nearly a week of asciilifeform rereading whole thing every day." ? DID YOU NOT READ IT ? ☝︎

mircea_popescu: http://btcbase.org/log/2018-01-05#1765023 << sadly, not in this language. but otherwise, the german school is the canonical introduction ; read ye yer kant, then proceed to http://btcbase.org/log-search?q=frege (not the other fucking way around ; english is a liability to the thinking man, and the latter's accessibility a burden). ☝︎

mircea_popescu: for instance when i linked you to http://btcbase.org/log/2017-12-31#1761560 i specifically meant you to read the whole thing lol. it explains why "why an enterprising individual hasnt come along and made it more accessible, or rather go for the volume game". ☝︎

danielpbarron: mostly asked because someone will probably wonder the same and now they have something to read in the log. i'll give it a look when it finishes

mircea_popescu: specifically because http://btcbase.org/log/2017-12-31#1761851 ; i have the lingering suspicion i have read something like say "The key management stream is not distinguishable from the rest of the stuff, be it noise, or plaintext." stated in other hands before. ☝︎

mircea_popescu: http://btcbase.org/log-search?q=rms << this may be interesting, but read it from the bottom up

asciilifeform: http://btcbase.org/log/2017-12-29#1760637 << hilariously, i had previously read the whole thing... on fcc's www. ( they have a public pillory of all citations/fines/complaints/etc ) ☝︎

mircea_popescu: if you signed it, then you read it. what matters what you edited ? moar of the same http://btcbase.org/log/2017-12-05#1746388 ☝︎

mircea_popescu: http://btcbase.org/log/2017-12-22#1756414 << the original slashdot.com was composed deliberately so that people COULD NOT read it to a dork. "oh man it's aiche te te pe colon slash slash slash dot dot com" "it doesn't work". ☝︎

mircea_popescu: o hey, so here's a deal, read out the log to them. i'll pay you say a bitcent for an hour.

asciilifeform: ate: i recommend to read the logs also. http://btcbase.org/log and see subj line of this chan.

mircea_popescu: http://btcbase.org/log/2017-12-03#1745783 << my read is that he was genuine lee kuan yew, except not nearly as intelligent (nor fortunate) ; eventually collapsed under the pressure of the pointless maggot herd wanting what it wants rather than what it needs aka "democracy". ☝︎

mircea_popescu: and no further than ONE DAY BACK in this log which seemed very respectable snr-wise on the basis of my hsaving read today, there's a PILE of "how to lisp on windows" and "how to utf-8 unicode etc".

a111: Logged on 2017-11-21 19:38 phf: http://btcbase.org/log/2017-11-20#1741179 << you can just ignore the whole "string" question in first version, McCarthy's lisp used symbols instead of strings (that's why early nlp code, like eliza all come out as DOG SAID, HELLO) and the only operation you could do at some point was read and eq.

phf: http://btcbase.org/log/2017-11-20#1741179 << you can just ignore the whole "string" question in first version, McCarthy's lisp used symbols instead of strings (that's why early nlp code, like eliza all come out as DOG SAID, HELLO) and the only operation you could do at some point was read and eq. ☝︎☟︎☟︎

a111: Logged on 2017-11-20 03:40 pete_dushenski: http://btcbase.org/log/2017-11-19#1740754 << am i the only one who can't read "dex" without thinking "dexedrine" ? phf ?

a111: Logged on 2017-11-14 18:50 phf: http://btcbase.org/log/2017-11-14#1737529 << that doesn't sound right, read and eval are distinct phases, by the time you get to eval you shouldn't be operating with strings when but instead with interned symbols (i.e. things that can be eq'd in lisp and pointer equivalent on c machine level)

pete_dushenski: http://btcbase.org/log/2017-11-19#1740754 << am i the only one who can't read "dex" without thinking "dexedrine" ? phf ? ☝︎☟︎

Ingolfr_Arnarson: any recommendable log to read with more detail on the advance of the project?

phf: i resent the "sorta works" bit, i've been responsive with any feedback related to log and patch visualizer. i've not read todays log so maybe i missed how /patches fits into greater scheme of things

asciilifeform: generally noobs are advised to read the log for a spell, before considering whether they have something to say

phf: http://btcbase.org/log/2017-11-14#1737529 << that doesn't sound right, read and eval are distinct phases, by the time you get to eval you shouldn't be operating with strings when but instead with interned symbols (i.e. things that can be eq'd in lisp and pointer equivalent on c machine level) ☝︎☟︎☟︎

mircea_popescu: http://btcbase.org/log/2017-11-14#1737536 << this was part of the original speccing of "unequal length p, q" etc. that line of thought withered and died, see the whole thing in the log it's worth the read. ☝︎

a111: Logged on 2017-11-14 11:09 apeloyee: http://btcbase.org/log/2017-11-08#1734517 << not quite. for encryption, if I get your modulus, and you actually want to read my messages, I can generate a public exponent between M/2 and (say) 3M/4, and attach it to the message in plaintext.

apeloyee: http://btcbase.org/log/2017-11-08#1734517 << not quite. for encryption, if I get your modulus, and you actually want to read my messages, I can generate a public exponent between M/2 and (say) 3M/4, and attach it to the message in plaintext. ☝︎☟︎

spyked: http://btcbase.org/log/2017-11-13#1736972 <-- I did follow in read-only mode. (and unfortunately suspecting that I will continue to do so until upcoming vacation, when I can start doing ~actual productive work) the principle being, I either read daily, or logs pile up and I fall continuously out of sync. (almost happened last weekend!) ☝︎

mircea_popescu: http://btcbase.org/log/2017-11-07#1733356 << for completeness i originally read "largest prime factor", and intuitively thought i see the proof, but meanwhile that also collapsed. ☝︎

mircea_popescu: http://btcbase.org/log/2017-11-03#1732656 << you should read the "seo expertise/information products" stuff sometime. ☝︎

asciilifeform: read the log.

a111: Logged on 2017-10-14 18:38 apeloyee: http://btcbase.org/log/2017-10-14#1725293 << lulzily, it mentions http://btcbase.org/log/2017-10-14#1725240 method on page 9: "we load the entire table into registers and perform the selection via arithmetic". wonder how you have read that paper if you didn't notice that.

apeloyee: http://btcbase.org/log/2017-10-14#1725293 << lulzily, it mentions http://btcbase.org/log/2017-10-14#1725240 method on page 9: "we load the entire table into registers and perform the selection via arithmetic". wonder how you have read that paper if you didn't notice that. ☝︎☝︎☟︎

asciilifeform: can speak now, and he'll read the log & maybe answer

asciilifeform: !~later tell midnightmagic http://btcbase.org/log/2017-10-03#1720099 << if you want to read, e.g., the phuctored page, i refreshed it on archive.is a few days ago. but if what you're aiming for is to embrace&extinguish phuctor itself, you're on yer own ☝︎

mircea_popescu: for log completeness : http://btcbase.org/log/2017-09-15#1714731 should read "but look at the idiotic pieces krugman used to shit out before getting preet'd on the quiet" ☝︎

asciilifeform: http://btcbase.org/log/2017-09-13#1713808 << i did assume that d00d read the current coad ☝︎

asciilifeform: http://btcbase.org/log/2017-09-01#1708199 << i'ma read this catalogue ! but if it ain't posted before the leaves fall in benighted shitmordor , back to -1 quisling inquire within ☝︎

jackdaniel: sorry, I'm quite busy now. I've read the log – yes, bounties are arbitrary, or as someone nicely put it "pulled out of ass" by me

a111: Logged on 2017-08-29 20:21 phf is mildly curious is mp is doing his "once i found a thing, i read the whole archive" thing on 5gb or whatever it is of their log..

phf is mildly curious is mp is doing his "once i found a thing, i read the whole archive" thing on 5gb or whatever it is of their log.. ☟︎

mircea_popescu: http://btcbase.org/log/2017-08-29#1704898 << well i was going to read that after the log, but since you put spoilers in there ima go read it first and continue later. ☝︎

mircea_popescu: kanzure i'll tell you, i read the log every day, first thing, chiefly because it's the higherst snr item i know of. so not really noisy, no.

asciilifeform: kanzure: as for why you won't read about it in the lugenpress, http://btcbase.org/log/2017-07-20#1687903 << n00b review ☝︎

phf: "intelligence" "humans are idiots" "kurzweil" "working memory" "genetics" "yudkowsky". it's funny at some point you don't even need to read the log, you can figure out the particular, previously observed failure mode of a person by keywords that stand out

danielpbarron: i did get a pm on tardtalk recently but i didn't log in to read it; just saw the notification email

asciilifeform: i'ma save log space, and invite PeterL to read what i observed re the last d00d's gossipd prototype.

mircea_popescu: i suppose the moral being, we're going to see ever more waiters who read the log for i-log-ical purposes in teh futures. and, the imbecile (aka narcissist in ballas' terminology) being more dedicated to the preservation of the malfunctioning "self" he already has, they'll just run off the moment that dun work, to either try [the same stupid shit] again later or not dare to try again [ie, proclaim some sort of incomprehensible

a111: Logged on 2017-08-06 12:58 asciilifeform: anyway if you actually read the log, would see sig verify failing repeatedly.

mircea_popescu: http://btcbase.org/log/2017-08-06#1694478 << i did read the log you pasted. ☝︎

asciilifeform: anyway if you actually read the log, would see sig verify failing repeatedly. ☟︎

mircea_popescu: http://btcbase.org/log/2017-07-22#1689201 << nonsense, read napoleon's letters to the j-slut. ☝︎

a111: Logged on 2017-07-18 20:00 floog: http://btcbase.org/log/2017-07-17#1685787 <<< blue book is going to take 3 weeks to ship. any tips of what to read up on/learn in the meantime?

floog: http://btcbase.org/log/2017-07-17#1685787 <<< blue book is going to take 3 weeks to ship. any tips of what to read up on/learn in the meantime? ☝︎☟︎

BingoBoingo: <andreicon> but i take pride in being an above-average thinker so i'm sure i'm in the right place. just don't know why until i read the 22mn lines of logs << Recommend reading Trilema the blog from transition to English in 2012 through 2013 alongside log

a111: Logged on 2017-07-13 16:03 asciilifeform: http://btcbase.org/log/2017-07-13#1682555 << some time it would be interesting to read what means 'sanity' here, other than the somewhat circular 'not what the pantsuits do'

asciilifeform: http://btcbase.org/log/2017-07-13#1682555 << some time it would be interesting to read what means 'sanity' here, other than the somewhat circular 'not what the pantsuits do' ☝︎☟︎

asciilifeform: http://btcbase.org/log/2017-07-07#1679878 << i'm curious, what's the non-blue alternative? read all?! then no time to eat, sleep... read 0? state-of-the-art solution, practiced by many. but sometimes crackpot proofs are novel in some entertaining way. hence 'triage' ☝︎

a111: Logged on 2017-06-26 16:32 asciilifeform: http://btcbase.org/log/2017-06-26#1674428 << fwiw i carefully read all of it. asciilifeform's verdict: very much a gabriel_laddel-ization of gossipd. does 0 of the necessary work, and drags in 5+GB of liquishit deps (python, sql, some derp's crypto lib.) the amount of this that would have to be rewritten, from the ground, is 100%. not even useful as illustration of anything, because NONE of the actually complicated moving parts of a

asciilifeform: http://btcbase.org/log/2017-06-26#1674428 << fwiw i carefully read all of it. asciilifeform's verdict: very much a gabriel_laddel-ization of gossipd. does 0 of the necessary work, and drags in 5+GB of liquishit deps (python, sql, some derp's crypto lib.) the amount of this that would have to be rewritten, from the ground, is 100%. not even useful as illustration of anything, because NONE of the actually complicated moving parts of a ☝︎☟︎

erlehmann: i'll read the log again to maybe get a clear picture

mircea_popescu: the schmuck above, http://btcbase.org/log/2017-06-20#1672451 like so many equal schmucks before him, thought "read logs and get into tmsr ? THAT MEANS NEVER!!!! LOG TOO LONG!!!" etc. ☝︎

erlehmann: have you read the paper i linked? » http://btcbase.org/log/2017-06-14#1670094 ☝︎

mircea_popescu: !!later tell sina a) dun need to msg me the day's log, i always read it anyway and b) yeah, the prototype actually implements an older spec. trivial to revise if one cares to, was published.

shinohai kicked girl out of house when she said "Why do you read that boring log every day, can't you just facebook like the rest of us"

a111: Logged on 2016-10-03 13:35 asciilifeform: mepian: http://btcbase.org/log/2016-10-03#1551507 << please read the xilinx threads .

Framedragger: http://btcbase.org/log/2017-05-31#1663689 << i believe you misquoted out of context. the purpose of that was to (as you can see if you read till end of para), "The challenge here is to show that secure multi-user RSA key generation can becarried out more efficiently than one-user-at-a-time RSA key generation" ☝︎

asciilifeform: http://btcbase.org/log/2017-05-12#1655022 << i can only picture the frustration of gabriel_laddel_p -- he read the l0gz and went off to get subj b00k and presumably tried to eat it -- but never afaik learned ordinary classical electromagnetism ☝︎

a111: Logged on 2017-05-08 10:04 phf`: http://btcbase.org/log/2017-05-08#1652797 << i don't get it. i'd say i could get rid of about 20% of my books, but the rest i read or consult regularly. i had the bulk of my books in storage last year, and it was inconvenient (unlike say clothes or random "useful" junk that i have, that, once it goes into storage i don't even remember i had)

phf`: http://btcbase.org/log/2017-05-08#1652797 << i don't get it. i'd say i could get rid of about 20% of my books, but the rest i read or consult regularly. i had the bulk of my books in storage last year, and it was inconvenient (unlike say clothes or random "useful" junk that i have, that, once it goes into storage i don't even remember i had) ☝︎☟︎☟︎

mod6: <+asciilifeform> http://btcbase.org/log/2017-05-04#1651852 << i'ma have to do a likbez when i get home. mod6 did you even split the ads and adb pieces? ( i pasted them into same paste, for ease of reading ) << yup. that was the first thing I encountered. but indeed, much easier to read. ☝︎

mod6: this is built from this line in the debug.log, for example: "ProcessBlock (res == 1) took : 2901ms; db write wait: 313ms; db read wait: 155ms "

a111: Logged on 2016-11-10 17:10 mircea_popescu: no, actually, it concerned an isp which, like any other isp, can't afford to actually pay a lawyer to read all the legalse spam being thrown their way. the guilty party here is the state of california, as per http://btcbase.org/log/2016-08-18#1524561

mircea_popescu: http://btcbase.org/log/2017-04-20#1646560 << #trilema being possibly the only place in the history of letters that takes sensibly longer to read than it takes to write. ☝︎

mircea_popescu: http://btcbase.org/log/2017-04-07#1640078 << are you sure this is equiv to select * where something=something and if nothing is selected insert, ie, does the insert take read locks while it looks for the where ? ☝︎