800+ entries in 0.271s
mircea_popescu: anyway, in other advantages of living in tiny
spec of a country : i went for that steak i was considering yest. across from my table, laura chincilla (ex president)
a111: Logged on 2017-10-18 15:19 mircea_popescu: in other items of republican interest : eulora is at a stage where we have to set down what we'll use for sensitive data encryption (such as for instance the privkey files). i don't particularily wish to use aes ; anyone wants to contribute to this emerging
spec ?
mircea_popescu: asciilifeform there's no difference. artists dun wanna work, ie ON TIME and TO
SPEC and ON WHAT THEY'RE TOLD TO just like erryone else.
diana_coman: ofc; but idiotic keccac "reference" implementation goes about reading *bytes* although
spec clearly talks of bits and at most of z-dimension long array of bytes and as a consequence madness necessarily ensues
ben_vulpes: are these stylistics part of the
spec or what
phf: asciilifeform: how where do you source your cat5e? i've been using a leftover roll from my contracting days, but it finally ran out. went on amazon, not only are prices somewhat suspect (300m for $40?), but comments say that they cable doesn't actually conform to
spec (wrong insulation, wrong conductor, etc.)
mircea_popescu: ben_vulpes hey, how hard would it be to add a flag (=lisp) to bpaste, make it highlight and shit as per #lisp folk
spec ? ("<|3b|> mircea_popescu: links to
spec in particular, + interactive paren highlighting")
mircea_popescu: asciilifeform right you are, it's in the... 2006
spec.
a111: Logged on 2017-11-17 06:37 trinque: for the simple webhosting and bothosting cases, of which there oughta be many, max-
spec'd machine is not necessary
trinque: for the simple webhosting and bothosting cases, of which there oughta be many, max-
spec'd machine is not necessary
☟︎ BingoBoingo: <mircea_popescu> trinque better idea is that we have to figure out what boards/etc we're buying. a "standard box of the republic". << AHA, this is why cost of dedi box hosting not yet
spec'd
BingoBoingo: trinque: Racking 1u will give more freedom to
spec box, get ECC RAM
mircea_popescu: and second off, do the foxybot trade module. let me fish out the
spec mircea_popescu: asciilifeform in my
spec the comment in e, N, comment is arbitrary ~to storer~, not to originator.
mircea_popescu: the only problem in all this is that i'm not willing to put "use archive.is" into the logger
spec ; nor am i willing to go "write html-decrufter or die". so... we're FOSSing about.
hanbot: anyway having spent a few years fulfilling copywriting specs i'll admit a fair amount of the work was absorbed in weighing whether a given
spec-producer seemed likely to pull the penny-revision stuff
mircea_popescu: in other items of republican interest : eulora is at a stage where we have to set down what we'll use for sensitive data encryption (such as for instance the privkey files). i don't particularily wish to use aes ; anyone wants to contribute to this emerging
spec ?
☟︎ mircea_popescu: i am loath to put "and load this website" into the eg log bot
spec.
mircea_popescu: experience convinces me that anchor-first is correct way and the url-first html
spec a kludge./
mircea_popescu: evolvospec, for the record, is not a
spec, exactly in the manner a bad girl may be great fun to be with but notrly a wife.
lobbes: !~later tell mircea_popescu ^^ 'help sexpr' and 'help json' also working. lobbesbot has been brought up to
spec a111: Logged on 2017-10-05 18:20 mircea_popescu: ok so results of audit : Framedragger, shinohai, phf : your bot has no help implemented whatsoever, in spite of
spec. trinque Framedragger you don't follow the json/sexpr portion, bot simply puts out the same help.
a111: Logged on 2017-10-05 18:20 mircea_popescu: ok so results of audit : Framedragger, shinohai, phf : your bot has no help implemented whatsoever, in spite of
spec. trinque Framedragger you don't follow the json/sexpr portion, bot simply puts out the same help.
apeloyee: per
spec the bitness is a power of two
mircea_popescu: the part what's under discussion is the ~why~ nobody implemented the json/sexpr part of the
spec./
ben_vulpes: and what, a machine-understandable description of what each extra-
spec command does? i didn't think anyone here operated machines that /thought/.
mircea_popescu: well yes. the part where the
spec should be followed is not under discussion.
ben_vulpes: the response from the bots to what they can do. either they're all
spec-compliant, respond the same way to the same set of commands, or they don't.
ben_vulpes: should be binary, #t-
spec compliant or not.
mircea_popescu: exactly like the original url worked, in practice the
spec never delivered this magical ability to query servers for resources to the end user.
mircea_popescu: ok so results of audit : Framedragger, shinohai, phf : your bot has no help implemented whatsoever, in spite of
spec. trinque Framedragger you don't follow the json/sexpr portion, bot simply puts out the same help.
☟︎☟︎ mircea_popescu: but your original claim, that "to demonstrate, here's a design for an object that meets the described
spec , if p!=np :", crumbled under scrutiny.
mircea_popescu: the problem with the
spec as-is is that you can't actually have a message of the same bitsize as the key, but must make it -1 ; this appears to be mentioned exactly NOWHERE, which is moderately concerning.
mircea_popescu: side beenfit of selecting for stupid. ftr, i know of no other nazism that actually put idiocy in the
spec for aryanism.
shinohai: Notice that happened after nist.gov declared their
spec gabriel_laddel_p: It seems rather strange to me that you’re assigning bounties to “bugs” when it is clear that in many cases you have read neither the
spec, nor the code, nor have the slightest idea what is even WRONG in the proposed bug.
a111: Logged on 2017-08-22 15:40 valentinbuza: as you can see on the
spec, it is not concerned with PKI or your authentication methods, it's up to you
valentinbuza: i don't find the word 'standard' in the description or in the
spec. it's not a standard and should not be seen as one
valentinbuza: as you can see on the
spec, it is not concerned with PKI or your authentication methods, it's up to you
☟︎ a111: Logged on 2017-08-21 15:21 asciilifeform: now it is ~possible~ that the
spec is disinfo, and in basement of kgb there is a rewritten alteratronic chain. but imho unlikely.
a111: Logged on 2017-08-21 15:06 phf: pff, russian tech.
spec is produced by kiril after sit in room with 2 fpga (such luxury, whole two!) and bread for three months
phf: pff, russian tech.
spec is produced by kiril after sit in room with 2 fpga (such luxury, whole two!) and bread for three months
☟︎ phf: sure, but chinual is extremely detailed and the ~architecture~ can be improved incrementaly. for example brad's cpu is, yes, implemented as an emulator for a discrete circuit. but at the same time it can be isolated from the bus, put into a determenistic harness, and rewritten from the cpu
spec in chinual.
mircea_popescu: spyked see, the thing with orc lands is that they have this. borz, chechen made smg. the egyptians made engine parts to VISUAL
spec, by hand. i saw this. guy here offered to produce a replacement pressure hose for me, by visual inspection.
mircea_popescu: spyked was it a cartpenter you hired, ie, a guy who worked in wood, or was it an ikea clonal system you hired, ie a guy who went to a central warehouse where they cut some glue-dust planks to his
spec ?
a111: Logged on 2017-08-16 16:03 mod6: my question is then; with regards to the tmsr-rsa rough-sketch
spec, do we then entertain the idea of other key-lengths, no just 4096 as currently outlined?
mod6: my question is then; with regards to the tmsr-rsa rough-sketch
spec, do we then entertain the idea of other key-lengths, no just 4096 as currently outlined?
☟︎ mircea_popescu: first question, of course, being whether there's value in changing the
spec for key primes from "2048" to ">2046" bits.
a111: Logged on 2017-07-13 15:18 phf: for the longest time i thought that common lisp
spec is a magic paper against modernization. not so, and you can see it with the recent evolution of sbcl. for example they made it an error to locally shadow cl package symbols, e.g. (flet ((first (...))) ...) will fail, breaking a lot of reasonable old code. many historic idioms likewise produce compilation warnings, etc.
mircea_popescu: you can not call your
spec "scalable" while it has magic numbers in it.
mircea_popescu: in the process discovering that a) they diverge from the
spec and b) in no particular or ennumerable way.
mircea_popescu: this is ALSO good : breask the ip-box bijectivity, as was intention all along transparently throughout
spec docs.
BingoBoingo: <trinque> there's going to be no fixing the generation that took psych meds throughout puberty << plenty of possible fixing. Back to '
spec' likely never. Into something possibly.
phf: but i figure i'll try pushing a binary file through (which wasn't the
spec anyway, just wanted to see what actually happens)