tmsr - Search: "in the log"

800+ entries in 0.146s

mircea_popescu: as far as mostly 1 is concerned, there's significant interest in shortwave, which is why it's a recurrent thread in the logs.

asciilifeform: ( also in the log )

mircea_popescu: i've engineered hell for myself here, "it's either in the log or on the blog" yes tyvm

mircea_popescu: kinda why i even bothered putting it in the log / why i look for weird in the mega webfilter that is trilema. you never know when a magical packet pops up, they're like tachyons these things.

trinque: I reported this in the log

trinque: I already put it in the log, what

trinque: http://btcbase.org/log/2017-12-21#1755798 << this does *not* explain what I put in the log, though it is also a problem. ☝︎

asciilifeform: btw some very large share of 'no can haz trb, plz help' in the logs to date, feature shituntu

mircea_popescu: there was some discussion as to the history of typographical ideas in the log somewhere

diana_coman: in "only 2 years later" but since I did not find otherwise in the logs an answer to mod6's question at http://btcbase.org/log/2015-05-20#1139680 : that is simply the number of limbs, so a matter of size; since p and q are same size, it is fine there although arguably not helping the reader ☝︎

mircea_popescu: i clearly remember gushing in the log many years ago, but can't seem to find. anyway : difficulty worked.

asciilifeform: there was a version given to mod6 , should be in the log somewhere , that had all of the basic arithmetic (+,-,*,/)

mod6: ya. it's in the logs. i can dig it up if needed. but i believe my problem to be environmental and somehow to related to adacore.

fromloper: this seems to be Symbolics' internal docs for the Ivory. are they sufficient to develop a clone? I've tried to find previous discussions of this particular subset of docs in the logs but didn't find anything.

mod6: <+trinque> would probably be useful to say which restrictions. << it's in the logs.

asciilifeform: now i recall also that phf had some trouble at first eating the thing, http://btcbase.org/log/2017-11-15#1739113 and elsewhere. but i can't seem to find in the log whether he ever said what the problem was, and how fixed. ☝︎

asciilifeform: made originally ( as amply described in the logs , at every step of the way ) for universal numbertheoretical ciphrator.

asciilifeform: it is in the log

asciilifeform: subj was beaten to death in the logs, neh

shinohai: I feel happy to be a part of such a grand institution that goes out of the way to be so all-inclusive in the logs.

gabriel_laddel: Finally figured out how to score meth tho. Tis the bomb diggity & works exactly as I noted here in the logs prior to finding it.

mircea_popescu: whoa, THAT is in the logs ?

mircea_popescu: at significant cost, twas in the logs.

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-13 20:35 diana_coman: I can't seem to find in the logs any discussion re duplex construction/duplexing the sponge i.e. keccak's authors own proposal of using keccak for authenticated encryption; did anyone look into this?

diana_coman: I can't seem to find in the logs any discussion re duplex construction/duplexing the sponge i.e. keccak's authors own proposal of using keccak for authenticated encryption; did anyone look into this? ☟︎

asciilifeform: listed most of what's worth talking about, in the log.

concernedscaling: Thanks. I guess I am just trying to make sense of all of this, and couldnt find it in the logs. Instead of bcash forking from bitcoin, what was stopping them from just mining and rejecting segwit transactions on the the real BTC?

asciilifeform: may be in the logs.

a111: Logged on 2017-06-14 15:42 mircea_popescu: so i was gonna quote this story with my grandfather regretting the time of stalin, except apparently it;'s not in the log ? and there's even attempts to find the shit, like http://btcbase.org/log/2016-03-15#1433159

lobbes: http://btcbase.org/log/2017-10-22#1727791 << this whole time I figured I just missed something in the logs ☝︎

phf: diana_coman: did you also explain the logo?

mod6: might be in the logs

erlehmann: i noticed recently, looked a bit in the logs, then did something else

mircea_popescu: asciilifeform we had the fx 9500 ecc discussion like three times in the logs. they are.

trinque: it's already in the logs.

mircea_popescu: http://btcbase.org/log/2015-11-21#1329338 << guess what, it's in the logs. ☝︎

phf: well, i've been getting that error for the past two months. while there was still a heavy archive.is exchange in the logs, os i thought it's something to do with russia. i'm still getting it in u.s. though :o

asciilifeform: it was in the logs

mircea_popescu: it's all in the logs you know. see http://btcbase.org/log/2017-09-14#1714183 http://btcbase.org/log/2017-09-14#1714212 and so on. ☝︎☝︎

asciilifeform: was this in the log?

trinque: then it's both in the logs, and the logger can do something interesting with it, if it can.

asciilifeform: if it dun belong in the logs, it possibly dun belong anywhere

asciilifeform: ( are there any extraneous ffa's ? in the log )

diana_coman: asciilifeform, I'm currently looking at eulora rsa and I'm a bit foggy (I know and followed the bits posted in the logs but it's a long trail): what is available/ready to use atm?

asciilifeform: grrr it WAS in the log somewhere

mircea_popescu: and as tempting as it may be TO THE NAIVE, this "oh, i found an actually workable one" is what we've been doing for years. there's people in the logs vouching for cherry servers, the FUCKTARDS who outlook.com their email and so following.

mircea_popescu: yes, but putting that in the log is like putting the goop in the woman. so much fun to do you keep doing it.

mircea_popescu: anyway, since nobody apparently got the faberge egg bait, let's put it in the logs. so yes on the substance front i asked alf if he knows what it is because it is in fact stained glass, except with gold instead of lead and porcelain instead of glass, ie just like his properly cast key, piston-and-typeface in metal, bulk in porcelain.

ben_vulpes: fromloper: it's allllll in the logs

mircea_popescu: eh wtf, we don't have the koans in the logs now ?!

ben_vulpes: can't be nyooz, much less old unless it's in the logs

ben_vulpes: shinohai: his selling of it was in the logs already?

mircea_popescu: http://btcbase.org/log/2017-09-01#1709154 << seems the correct solution is the layer of indirection. you do have actual information, which is immutable, and which can be served as urls ; and you have indexing etcetera, which yes is mutable, but which also best lives as an alias layer on top of urls. so in this sense : each line in the log is an url ; the query for "give me the by-day list of archives" just like the query for ☝︎

mircea_popescu: consider : when i put http://trilema.com/2017/the-life-and-times-of-fna/ in the log earlier, the bot archived it, so now it's at http://archive.is/L1Up3

asciilifeform: sageprobes: plenty in the logs

mircea_popescu: kanzure in the log dir.

mircea_popescu: actually, let's put this in the log.

mircea_popescu: there's some work in the log re creating mechanical-mp, but mostly at the lulz stage.

asciilifeform: kanzure: the alternative is amply illustrated in the logs : effort of actual people, without any trace of http://btcbase.org/log/2017-04-07#1640325 ☝︎

kanzure: about to get unvoiced i think. could someone offer mircea_popescu a link to the right place in the logs for the eugenics war.

asciilifeform: dh in the logz is... 'dieharder'

mircea_popescu: http://btcbase.org/log/2017-08-22#1701674 << this is actually in the logs. in short, badly written "p2p" ☝︎

asciilifeform: ( several cases documented in the logs, by mircea_popescu and others )

mircea_popescu: btw, incredible enough how the borz is not in the logs! pot metal smg yo!

mircea_popescu: r0nin- it was in the logs, http://btcbase.org/log/2017-08-14#1697556 ☝︎

ben_vulpes: while i'm on the topic, can confirm that 'modern' asdf is all sorts of royal pita as well, although that thread has been well hashed in the logs

asciilifeform: http://btcbase.org/log/2017-08-06#1694638 << iirc i even mentioned it in the logs ☝︎

asciilifeform: http://btcbase.org/log/2015-07-23#1210108 << afaik this was never actually resolved in the logs ☝︎

mod6: ah, right. all .ro. i used to just translate the stuff. however, it was mentioned in the logs, since im not sure what exactly is being lost in such translations.

mod6: Also, f1maze, you'll find countless examples of people going through the motions on this in the logs if you need.

asciilifeform: can't seem to turn it up in the logz

ascii_modem: http://btcbase.org/log/2017-07-30#1690897 << lol, you did, it was in the logs ☝︎

mircea_popescu: expand, let's have the story in the logs.

mircea_popescu: good thing you two decided to put it in the log, sounds exactly what the baked-in "reasonable" move would be, who knows how many souls it claimed.

mircea_popescu: and i guess the next round of these idiots will not "know" how to find the previous round in the logs.

mircea_popescu: hmmm i never put this in the logs ?!

asciilifeform: ... the connects and disconnects? 'cause everything else, you can read in the logz

mircea_popescu: and this is my point here : yes, bitcoin corrupts. i mean specific things by this term of art, they're in the logs.

mircea_popescu: amusingly i also put it in the log earlioer today. so what of it ?

sina: I mean I can picture reading it in the logs

mod6: there've been a bunch of threads on it in the logs.

asciilifeform: erlehmann: didja ever read the pernicious-standardization thread in the logz ?

mircea_popescu: the finer points of forum scheduling still elude me. but nevertheless -- let it be said each dog wil lget his day in the sun and nothing will remain buried in the logs, forgotten. so.

mircea_popescu: http://btcbase.org/log/2017-07-10#1681164 << amusingly this was discussed a coupla times in the logs, naive "owner" in thailands. ☝︎

phf: asciilifeform: literally five lines lower in the logs

mircea_popescu: i think i even mentioned this in the logs at some point. perpetual connections are unsanitary.

mircea_popescu: did you see the economic discussion of the matter in the logs ?

mircea_popescu: see the early discussion re it in the log, http://btcbase.org/log-search?q=UCI it's well described

asciilifeform: sina: it is in the logs

sina: asciilifeform: btw I was going to ask you about your feelings on this https://github.com/cforler/Ada-Crypto-Library ...obviously hasn't been impl for constant time/space but regardless. may be possible to ctgrind it using that valgrind patch I linked in the logs

mircea_popescu: aha. was even lulzed vaguely in the logs last year iirc.

mod6: sina: if you wish, you can always ask your question, and im sure it'll get read in the logs. someone will get back to you eventually.

asciilifeform: ( at one point i derived how to do ~fixed-joules~ rsa, and it is in the logs, but needs peculiar silicon, don't expect one yet )

a111: Logged on 2017-06-09 17:43 asciilifeform: !~later tell Framedragger do you perchance remember where in the logs i posted phuctor's key parser ?

mircea_popescu: so i was gonna quote this story with my grandfather regretting the time of stalin, except apparently it;'s not in the log ? and there's even attempts to find the shit, like http://btcbase.org/log/2016-03-15#1433159 ☝︎☟︎

phillipsjk: Your solution in the logs is to replace unix with DOS to avoid that problem.

phillipsjk: maybe I can find it in the logs...

mircea_popescu: asciilifeform yeah i saw trims of that in the logs lol.

mircea_popescu: in fact, deedbot was intended to be federated from the get go... or in fact no. the item deedbot replaced because the operator got syphilis (ie, assbot) was created specifically because failure of previous item (operator travelled unexpectedly, thing went down -- tis all in the logs) and was intended to be federated from the get-go