log☇︎
16600+ entries in 0.151s
asciilifeform: but as we discussed in old thread, the single most serious problem of ada, is that it is quite difficult to implement an adatron. esp if you actually go for standard compliance.
mircea_popescu: gcc or w/e you use as a compiler,. for instance, also not an ada proggy. ada dun even try what lisp tried and failed to obtain, ie, a full universe.
mircea_popescu: if the convention can be "you'll need a serial capable machine", as it HAS to can be, then convention can also be "you'll need a cpu with ror/rol implemnented". whether it is decided to make it so has no bearing on whether it could be decided to make it so. that's a 1 : it could be.
a111: Logged on 2017-11-16 15:29 mircea_popescu: tbh, this item aside (it was just given as an ~example~ anyway), i do not expect that on the medium term we will be able to avoid "and here's the special asm library, links at link time with the rest of compiled shit" situations.
asciilifeform: ( and is made of junkyard parts, given as the actual FG stock is s.nsa inventory, lol )
mircea_popescu: tbh, this item aside (it was just given as an ~example~ anyway), i do not expect that on the medium term we will be able to avoid "and here's the special asm library, links at link time with the rest of compiled shit" situations. ☟︎
mircea_popescu: "rotation can be directly an opcode item linked as such", how about that.
asciilifeform: returning to http://btcbase.org/log/2017-11-16#1739533 , i will point out that inline asm is ~likewise~ a gcc-specific syntax. so if you're marrying gcc you may as well use the existing ( as seen in ffa ) rotate intrinsic. ☝︎
mircea_popescu: just as reference implementation will bake in FG, and users of others are responsible for others' quirks.
asciilifeform: imho if you're gonna have asm, may as well write whole thing in it
mircea_popescu: as a forinstance.
a111: Logged on 2017-11-16 15:01 asciilifeform: exactly same nonsense as the carry flag thing
asciilifeform: diana_coman: the sad fact re gnat is that it is in fact the only ada. being as the 'alternatives' are, without exception, closed winturds.
asciilifeform: ('use asm' is not an answer, i want, as diana_coman wants, a PORTABLE proggy )
asciilifeform: exactly same nonsense as the carry flag thing ☟︎
asciilifeform: diana_coman: how do you propose to rotate without it ? as i see it, the language standard simply has a rotate-shaped hole in it
asciilifeform not much into eccism, regards its presence in btc as a bug
mircea_popescu: or consider something as simple as phuctor, that already has a lot of "special" primes, however you define special (small, common, whatevewr)
a111: Logged on 2017-11-16 11:27 apeloyee: http://btcbase.org/log/2017-11-15#1739374 << can you enlighten us about why you believe there's no way to use information about range of factors (because you say so?), and about the http://btcbase.org/log/2017-11-15#1739371 as regards the number field sieve, as this doesn't seem to be published (or perharps for quadratic sieve). elliptic curve does benefit from smaller factors, but if the...
mircea_popescu: it may appear beneficial to instead produce larger sets, such as of 4096 bits. the UPPER BOUND of the gain from this process is known ; the lower bound of losses from it is not known, because yes if you allow 4096 bit p, q and test, an acceptable N can be composed of the product between 17 and 2^4092 - 177 or whatever it was.
a111: Logged on 2017-11-14 15:01 mircea_popescu: http://btcbase.org/log/2017-11-14#1737387 << this is alternatively a perfectly acceptable approach ; expensive as all fuck though. prolly should be the standard for homemade keys.
mircea_popescu: as far as anyone knows, something closer to 450 bits is what's actually needed.
mircea_popescu: yes, in about 6% of cases the N will come out as 111..., in which case you know that both p and q are actually 1111 1111 led, ie you'll have 2 bits of each. and in 0.001% of cases N will led by FF and have the next bit set, so you'll know both p and q have the first octet set. if you have an extension attack allowing you to parlay 8 leading bits into the prime exposure, you can thereby crack rsa in 0.001% of cases.
mircea_popescu: factors that are very small are trivially a vulnerability, as the 17 example shows. what is "small enough" is somewhat of an open question, but 512 BITS does conceiovably qualify.
apeloyee: http://btcbase.org/log/2017-11-15#1739374 << can you enlighten us about why you believe there's no way to use information about range of factors (because you say so?), and about the http://btcbase.org/log/2017-11-15#1739371 as regards the number field sieve, as this doesn't seem to be published (or perharps for quadratic sieve). elliptic curve does benefit from smaller factors, but if the... ☝︎☝︎☟︎
BingoBoingo: Figure subject to change as more tax law is digested
BingoBoingo: Calculated as 2*{[(monthly rack with 22% VAT)/(40 Salable RU)]*(12 Months)}/(52 weeks)
asciilifeform: sooo they are also fraudulently pushing bch' ( or what it was) as a fork of bch ?
a111: Logged on 2017-07-18 03:17 mircea_popescu: the notion that bitcoin can somehow by stolen by name is so ridoinculous as to betray its ustardian origins. bitcoin is not a name.
mircea_popescu: in other "obscure attempt at http://btcbase.org/log/2017-07-18#1685850 fares as well as could be expected", https://futurism.com/bitcoin-classic-shuts-down/ (evidently, 100% http://trilema.com/2016/and-they-wont-fucking-yield/ mode, "here's our next pick" bs) ☝︎
asciilifeform: mircea_popescu: it's a pretty good olympiad problem, actually, to show why PeterL's scheme is still a bad idea even though '17' scenario is ruled out given as he capped the lower bitness at 512
mircea_popescu: http://btcbase.org/log/2017-11-15#1739375 << the first factor found will necessarily be the smallest of p, q. therefore if your q is 17 and p some 4094 bit prime, you're fucked as the N will fall over within microseconds. ☝︎
PeterL: anyway, I have to go take care of the kids, as always I keep an eye on the logs.
asciilifeform: there is no such thing as 'bad value' for individual p or q
PeterL_: hi, missed the 30 second window to identify as PeterL
lobbes: http://btcbase.org/log/2017-11-15#1739265 << My ultimate goal with the thing would be to use trinque's ircbot and try and rebuild lobbesbot off of that. As it stands now, lobbesbot is nothing more than a suite of 'supybot modules' I wrote ☝︎
asciilifeform: ( rms, sad as it may be to say, is among these. )
asciilifeform: 'Anyone who held Bitcoin at the time Bitcoin Cash Plus was created became owners of Bitcoin Cash Plus. This means that Bitcoin holders as of block 501407 ' << apparently, contrary to appearances, is NOT a fork of bch
asciilifeform: 'The price of the cryptocurrency in the Southern African nation jumped as high as $13,499' but in which $ ?
trinque: I proposed that as a better solution to portability a while back
mircea_popescu: trinque so you'd rather keep it as two separate items is the idea here ?
mircea_popescu: but as they stand right now, they're not separate.
a111: Logged on 2017-11-15 18:43 diana_coman: and re peterl's keccak implementation trouble is that thoroughly testing it looks atm as much work as writing a new one in the process anyway so whatever version ends up with tests and everything is the one that will make it into v too I would say
mircea_popescu: diana_coman some bits of code, such as heavily linked against standard hash etc would normally take a zillion reimplementations rereads etc anyways.
mircea_popescu: inasmuch as logbot (bv item) has a genesis, it is not a branchoff. yes it imports from a different line.
diana_coman: and re peterl's keccak implementation trouble is that thoroughly testing it looks atm as much work as writing a new one in the process anyway so whatever version ends up with tests and everything is the one that will make it into v too I would say ☟︎
diana_coman: I get the feeling that v is not really seen as versioning in the sense of these are the steps I took, still mulling a bit on thiw
mircea_popescu: diana_coman so what's your call, rather write as mpi branch or rather stand alone ?
mircea_popescu: anyway. my conclusion is ima do the eu-crypto as a new genesis, because really most of the koch crap in mpi (esp the prng crap) got dirtched
asciilifeform: because it was , as you can probably see, done barbarically
asciilifeform: you can produce this mechanically. the unfortunate bit is that it gives same problem as basing trb on original 5.3.1 tarball contents did
mircea_popescu: this as described could work splendidly well.
mircea_popescu: what exactly did happen ? phf wrote a fine v parser ; jurov sweated white hairs getting an email system into alf-tip-top shape only for it to not be used as soon as it was got to work...
asciilifeform: the current item, as i understand it, doesn't interoperate with wp ( or otherwise blogotronic )
phf: mircea_popescu: no, publish meaning put relevant parts into patch visualizer, i otherwise haven't published anything. log/patch visualizer is presented as a service, as far as log is concerned the philosophy has been "write your own" and there's not been much interest in the v part until now
phf: http://btcbase.org/log/2017-11-15#1738923 << the underutilized part of patches visualizer is the tree view, it shows what specific file will actually look like when pressed with a specific patch, e.g. http://btcbase.org/patches/programmable-versionstring/tree/bitcoin/src/crypter.cpp as you can see formatting is not particularly good, but it supports highlighting various languages including Ada. so given a normal v-based workflow (is there one?) can get ☝︎
mircea_popescu: and b) correct linkage. such as above displayed, arbitrary byte, such as so on.
asciilifeform: i'd even settle for a very low-tech, orcish thing, that lives as emacslisp and shits out a wp post .
mircea_popescu: neverfmind artistic. it's as functional as a hammer in a pot of soup.
asciilifeform finally dug up link to what asciilifeform sees as state-of-the-art wwwtronic ada viewer : http://unzip-ada.sourceforge.net/za_html/index.htm ( they're auto-generated per project )
mircea_popescu: which is why it's even interesting to have one as an intellectual activity.
asciilifeform: trinque: not necessarily, could even store the lines individually, rather than as single text string, and generate the html soup in variants depending on number in url
trinque: thing'd have to know the code's AS
mircea_popescu: there'\s as you can see 100s of diff variants
mircea_popescu: imo this is the correct usage of html, make the code line as long as it needs.
mircea_popescu: but this aside : adding the code as text files, linked from the post is perfecty acceptable.
asciilifeform: as it is, it's a sisyphian labour
mircea_popescu: now, 4 can flow to 1 as it can flow back to 3, and 3 can flow to 1 as it can flow to 4 and so on and so forth. but the important point re these four phases is that they must be explicitly followed, for great personal as well as republic-wide gains of productivity and GDP.
mircea_popescu: phase 3, when you are done writing code FOR NOW. this is traditionally the "refactor break". this is also when you publish, explaining other than the code what you did and why, in detail. this included "i tested so and so -- i didn't test so and so" as it includes "i asume so and so". countrary to patently false subjective intution, this is the MOST valuabler of all the phases.
mircea_popescu: coding has four phases. as follows :
mircea_popescu: at which point i feel teh urge to also link http://www.dianacoman.com/2017/06/12/o-brave-new-code/ as it's such a perfect dialectic expose of the differences. code-about-code vs code-about-coder.
asciilifeform: as it is , 100% of the thing is in may-theoretically-change form.
mircea_popescu: a snipped of code IS NOT SUFFICIENT. you gotta say ALL SORTS of things. such as this, yes, how it was tested and for what. and so following.
mircea_popescu: meanwhile if you DO cash it out as you get it, you cash it out as you get it (missing out on a along with your customer).
mircea_popescu: b) btc goes to $1. you're now on the hook for the same 3.5k, but if you didn't change the BTC to cash as you received it, you have no way to cover for it. this possibility makes just like a, people not want to pay long term.
mircea_popescu: wer perhaps another user from before used the same nickname too << yes. someone else registered the nick, but didn't set enforcement on it. as a result you can use it (you don't get kicked by nickserv) but can't register it yourself. ask in #freenode if they're willing to move it over to you ; if not, find a diff name and register that.
trinque: could be as simple as billing monthly in advance, calculating bill as u*$operatingCost*1.15/40 or whatever margin atop you think is reasonable. $operatingCost denominated in BTC should be going down all the time
trinque: curious what happens to the price when btc buying power increases, as it likes to do.
a111: Logged on 2017-10-22 05:20 mircea_popescu: your cost basis is ~200 per server. you can rent them for 3-400 as such, or can give out vpsen, which are more productive. perhaps even "shared" if particularily interested into it.
BingoBoingo: For trinque and other parties interested in shipping their own boxes, considering the current cost basis and exchange rates to get a server homed for the first year is looking like ~0.57-0.6 BTC per rack unit (minding that especially power hungry servers may count as multiple rack units despite their physical footprint)
BingoBoingo: <asciilifeform> i've not worked as a caretaker of the profoundly retarded, neh, so can't say i experienced directly << Do you want to come visit before we depart for our seperate ventures? I can make introductions. Maybe even get you some shifts at the BingoBoingo store.
asciilifeform: gotta wonder, how many other 'hey it's soo cheap and available!' technomarvels, on examination would turn up to be exactly same as this
mircea_popescu: just as sheep as the sheep.
mircea_popescu: shall we now do the incomprehensible seed ? all the way to the witch doctors, just as good as medicine ?
asciilifeform: i've not worked as a caretaker of the profoundly retarded, neh, so can't say i experienced directly
davout: "Let's as X to accept buttcash donations"
mircea_popescu: the problem with "tide lifts all boats" is that where boat is comes as function of boat not function of "tides".
davout: the thing that amuses me, is that they seem to be rehashing exactly the same nonsense as proper bitcoin reddit was doing 3 or 4 years ago
asciilifeform: and it isn't as if there is nonchinese equipment for sale somewhere. unless you count the for-usg 'weight in gold' nonsense
phf: hehe, somehow i read every single thing that BingoBoingo wrote about the girl as some form of double entedre
BingoBoingo: <mircea_popescu> is this code for "bb got laid" << Nah, she's a white girl. Practically has a Cherenkov glow of warning signs, but is making an effort to stay sober. Is however a source of entertainment watching the petite weapon of mass destruction operate. Much as the BingoBoingo is a valuable customer service lab, driving this kitten around is valuable wmd development lab.
BingoBoingo: mircea_popescu: Girl I've been driving around as favor for her sponsor.
mircea_popescu: asciilifeform is one guy as far as anyone knows.
asciilifeform: ( in further continuation of the microscopy q : what the everliving fuck happened to the beta ray microscope ? theoretically can do ~same thing as sem, but no need for massive electron gun, million volt power supply, or the vacuum pumps. where is it ?? )
asciilifeform: ( as in , discrete items )
mircea_popescu: the pacepa nutteries with assassinations etc -- footnote, if present. then, as now, ~nobody gave a shit.
asciilifeform: as illustrated by kurt tank in argentina
mircea_popescu: it was that a) it didn't know what to steal (as per above re lisp) and b) it couldn't steal fast enough.
asciilifeform: he describes the usa trips as specifically for the purpose of building cred, to get access to semiconductor goodies
mircea_popescu: defected as a 50yo. a 50yo ready to claim oswald worked for kgb.