76800+ entries in 0.021s
mircea_popescu: where the fuck is that tmsr-standard-rsa-key discussion
mircea_popescu: asciilifeform no. one needs multiple planets, the other exceeds matter.
mircea_popescu: not so. why i said do the math : cracking 4kb key the hard way exceeds the universe. this is a categorical argument, substantially different from "i could compute 2 bit key by enumeration on napkin"
mircea_popescu: asciilifeform well there is that. nor should you. butwhat happens to 8kb keys is of ~0 interest nevertheless.
mircea_popescu: and not even 4096 bits, there's a whole speccing discussion re this in teh logs
mircea_popescu: and this nonsense of offering faux meaningless choice a la kochpgp is unwelcome and shouldn't be perpetuated. keys are 4kb and forget about it.
mircea_popescu: do teh math, if 8kb rsa key is preferable to 4kb rsa key, there's fundamental problems with rsa that make it useless anyway.
mircea_popescu: what's a 4kb keygen, gotta look for the primes, say a few hundred emults ?
mircea_popescu: and yes, both gerousia and roman senate come off the first branch.
mircea_popescu: (for the anthropocurious : there's three types of primitive civilisation known to either theory or practice. all three had a female hut, where the women did their woman shit. one of them had a male hut where they got drunk and dragged unwilling sexual partners by the hair. another had a male hut where they mostly sat idly about. the final one had no male hut at all, like the chimps, and thereby is very dubiosly a civilisation
mircea_popescu: direct calque off the inept old woman "oh, tell all the young women not to go to the rape hut!!!" except , of course, the sort of girl that'd listen nobody wants there in the first place.
mircea_popescu: moar win-win has scarcely ever been seen in the history of human stupidity.
mircea_popescu: it's exactly how it goes, too. and the funny thing is, the braindead vat dwellers actually go by that.
mircea_popescu: "that weird cult that calls everything by unprintable names inexplicably because we try to run off with any other names they use hur durr"
mircea_popescu: i also do not expect we will ever call anything outside of the "pussygraber" "yesmeansanal" etc antipantsuit set
mircea_popescu: i eagerlyexpect the imperial "fuckgoats" bowdlerization
mircea_popescu: dat hipocrisy hunting, and its remarkably directional application.
mircea_popescu: funny how nobody from the "concerned" peanut gallery is there on the congress floor uninvited every day, "hey guise, remember that time when oyu decided to rechristian french fries ? what happened to that ??? I THINK THE USD IS WORTHLESS!!!"\
mircea_popescu: lemme guess, it conveniently makes fries on the side ? LIBERTY fries ?
mircea_popescu: in the same vein, the early 1900s investigations into the meaning and structure of number resulted in a correctly complicated notion, from riemann functions to cantor's sets and so on. this is at great variance with non-fields like "artificial intelligence" or say alf's favourite, postmodern qm (say string theory or w/e) -- which evidently are incorrectly complicated even if it's not always evident where exactly.
mircea_popescu: "if you're going to complicate -- complicate like latin, don't complicate like puritan society or any other barbarian non-people"
mircea_popescu: and re latin : it should be noted that it was by no means a maximally simple, or a maximally adequate-to-human-experience language. it was however ~correctly~ complicated, which to date is its foremost value.
mircea_popescu: anwyay, perhaps best historical example of the "problem -- ill posed" bit is the history of the sewing machine.
mircea_popescu: yet obviously swiss-army knife wrong bitsize for every problem!
mircea_popescu:
http notably gets this half-right : there's no such thing as an error message the server ever expects to see from a client, such as i dunno, "this page has porn on it, unacceptable, send me another version" or whatever.
mircea_popescu: i am ok with chunks of machine word size, ie, quantify data by n bits rather than by 1 bit.
mircea_popescu: phf i would be friendly to the notion of a machine word yes.
mircea_popescu: i don't care if it's a "gui" or a telex or whatever it may be.
mircea_popescu: or to put this belaboured thing in different words : if your data exchange protocol includes the concept of "error message", you do not in fact have a data exchange protocol.
mircea_popescu: and if asked for "bitcoin block", i do expect to be asked a number according to that exact type.
mircea_popescu: but the problem becomes really complex when you consider "bitcoin block index" is as of right now "positive integer under 474974", and won't stay that way for long.
mircea_popescu: so more like all-exposed-functionality) -> ((gossipd:all-message-since "give me all the gossipd message since a certain timestamp") ((timestamp fixnum positive "timestamp (in seconds since epoch) since which messages") ...))
mircea_popescu: moreover, and here's where it gets biting : if we go with
http://btcbase.org/log/2017-07-09#1681006 ; which i expect we should, you can end up with implicit types. "you asked me for the 999999th bitcoin block, fucker". what about that ? you will need bounds adnotation yes ?
☝︎ mircea_popescu: what happens if i do data like "1 byte|fff|2bytes|fff" ?
mircea_popescu: what happens if i do data like "1 byte|ff|2bytes|fff" ?
mircea_popescu: "o look, it also has #. in it, gotta load #.parser on top of + parser now".
mircea_popescu: ah i thought you were just loading a parser spuriously.
mircea_popescu: asciilifeform different sort of problem, that's for data entry this is for proper outputs.
mircea_popescu: and moreover, and perhaps most importantly, "(+ 1 1)" is NEVER 2. because 2 is 2 and fuck you.
mircea_popescu: for the curious : yes, i also have this problem in speech, especially when discussing complicated things with complicated women, and the solution THERE is the sort and short rule. which in relevant part says here that "(1 #.(+ 1 1) 3)" could NEVER be interpreted as "(+ 1 1)" because "(+ 1 1)" was a shorter statement of that and it wasn't used.
mircea_popescu: phf serialization can at best be a packaging. the issue is, can i say "here's a function that takes a parameter and outputs "your mom's a python" and the data payload is function(is that you daddy)" in order to convey the string "your mom's a python" ?
mircea_popescu: if you;'re going to have adnotated data and the adnotations are macros and who the fuck knows what goes on, you've got a miserable protocol.
mircea_popescu: phf this is like saying "this website prevents xss by using base64".
mircea_popescu: but nevermind the processor for a second. the discussion here is data interchange.
mircea_popescu: i need someone hacking on my bitcoin like i need someone feather-tickling my spleen.
mircea_popescu: the best and handiest way to illustrate this folly is, "imagine if your vlc tried to mpfhf every film you played"
mircea_popescu: phf and the reason for this is that it tries to take it as code.
mircea_popescu: but i can say you not merely should, but absolutely must. the cornerstone of wire protocol is a firm, protocol-derived guarantee of there being no such thing as bad data.
mircea_popescu: phf i don't know if you can or if you can't, not sufficiently experienced with the thing.
mircea_popescu: everything sucks where there can be such a thing as "this is the table of possible inputs and these are the three that set it on fire".
mircea_popescu: the very possiblity of even having such a thing as "broken data", by eg naming your kid "-- DROP table students;" is why i agree with the sql sucks sentiment.
mircea_popescu: phf but that is, for the needs of this mental model, a broken machine. not broken data.
mircea_popescu: and this is fundamental and won'[t go away nor can it with money and reputations involved.
mircea_popescu: i STILL don't want my number five to have the capacity to really be four.