700+ entries in 0.256s
BingoBoingo: I am very tempted to price a fuckton of walmart/gas station
spec sunglasses and bring them in, sell for 1500 pesos each to foreigners
mircea_popescu: iirc we had a
spec discussion re how to populate nodes.
ave1: phf,
http://btcbase.org/log/2018-09-23#1852924, I've tried on debian and I can reproduce the problem, Unfortunately I have no solution yet (it will probably be a patch). It seems the default/internal gcc
spec defines "-isystem /usr/include/x86_64-linux-gnu
☝︎ BingoBoingo: asciilifeform: AHA, that's how you identify Argentine plasticrap! Clearly out of
spec mod6: didja
spec out the drives for an order from ben?
jurov: oh it calls decrypt to compute the checksum of original unescaped text, prolly something left from the ancient
spec mircea_popescu: i mean... so mocky makes a client, i see his client works, i allocate his binaries signatures, and now evilmocky does what ? doesn't follow server comms
spec ? can't connect. is smart enough to follow them, and puts the work in ? can connect, server will report expected hashes. does he distribute this thing, so user can see the hash of his program and the hash the program tells the server don't match ? suppose he does. what n
mod6: Perhaps we need to 1: Formally adopt the manifest
spec proposed by trinque, 2: build a V that supports it.
mod6: ben_vulpes: im trying to look at the big picture. the manifest
spec is a part of that, ya.
a111: Logged on 2018-06-25 12:20 spyked: I think there's great benefit in the ffa chapter-based approach, so I'm not sure yet what the genesis should include. maybe only the lispm piece? or only the
spec file from lispm? my sense so far is that after some discussion, at least some of the parts will be rewritten
a111: Logged on 2018-06-25 12:20 spyked: I think there's great benefit in the ffa chapter-based approach, so I'm not sure yet what the genesis should include. maybe only the lispm piece? or only the
spec file from lispm? my sense so far is that after some discussion, at least some of the parts will be rewritten
spyked: I think there's great benefit in the ffa chapter-based approach, so I'm not sure yet what the genesis should include. maybe only the lispm piece? or only the
spec file from lispm? my sense so far is that after some discussion, at least some of the parts will be rewritten
☟︎☟︎ mircea_popescu: it is about _whitelogger bot following
spec and reading out lines.
mircea_popescu: i mean, the backstop would obviously be "either follow
spec as-is or get out of chan", i suppose. i don't specifically care either way, we already have plenty of proper loggers for one thing, and the original, "Hey, maybe someone exists on freenode that's both a) not totally braindead and b) hasn't heard of #trilema yet" was thoroughly proven wrong by now ; the intelligence flow is the other way.
phf: asciilifeform: yeah, i was going by various
spec sites, but i have a dongle that handles that
mircea_popescu: and we don't even have a formally declared tmsr-html
spec.
spyked: mircea_popescu, I ended up working on a couple of new ones. a. trilema
spec subset and b. rss bot.
spyked: my thought re trilema
spec is having something along the lines of a "trilbot" that performs some of the basic scaffolding (self-voicing and command prefix parsing).
a111: Logged on 2018-05-25 12:38 spyked: so eventually I expect some of the rss bot components (e.g. command handling, self-voicing) to evolve into standalone scaffolding for #trilema bots that implements a decent subset of
http://trilema.com/2016/trilema-bot-spec/ esthlos: trinque: that's rather interesting. anyway, I'm sure you see the dilemma: everyone "successful" around me sees no fundamental problem with usg system, and when you say "this
spec is atrocious; have you ever heard of the CLHS?" or any infinite variation on that theme, the only response is incredulity. but what, somehow I have the magic sauce and everyone around me is wrong? this is my current resistance to trilema thought
a111: Logged on 2018-05-21 16:55 phf:
http://btcbase.org/log/2018-05-20#1815927 << i'll take a look, i had further comments about diana_coman's original
spec and the responses, but does this new
spec replaces the other one entirely?
Mocky: hey i'm not an evangelist of it, but at least it has an actual
spec, coherent memory model and thread model. but if i have to write one more corporate java web app imma choke
phf: there's also parts in the
spec that describe the format, and you can infer the behavior from the format, but there isn't explicit description of behavior. for example movement type a.5.23-a.5.28 is presumably for moving things and self around, but without further details it's hard to say how it's supposed to work. so i can't really say much about the internal consistency of the protocol, i.e. are the message types sufficient to perform some set of in g
phf:
http://btcbase.org/log/2018-04-24#1805075 << i did a first pass on the
spec over the weekend, but haven't had time to formulate my thoughts. it looks like enough to do a prototype short of three things: handshake process is still work in progress, i noticed that it's missing type of data descriptor values for 4.3.2 (there's a list of data types, but not the values that indicate which type it is), and there's no format description for the encapsulated f
☝︎ diana_coman: I'll eat the convo again and then update the
spec (+link to log ofc) hopefully
mircea_popescu: diana_coman, in any case strictly speaking, the helo as we
spec it does not include R pubkey ; whereas in practice it actually must. but read the whole blob, this is better compiled htan parsed.
spyked: trinque, yeah, I'm actually playing with cl-feed-parser to get an idea of what's required for the feed bot, going to
spec it and all. I grabbed it off the githubs (
https://github.com/tkych/cl-feed-parser ) and the number of dependencies is irksome, so if you happen to know a better alternative other than building my own, I'm open to suggestions
BingoBoingo: I see no need at present. I just imagine ways the board could be pimped. Since it lacks rtc clock, why not go for great rtc clock in Rockchip workstation
spec.
mircea_popescu: phf the
spec here is "have a library of good films accessible to friends" rather than "i want to watch something between blowjobs"
ben_vulpes: asciilifeform: please to
spec it out, yr the hardware guy. would this get attached to one of the rockchips?
mircea_popescu: ben_vulpes it's a low
spec computer (mostly, two huge disks, otherwiuse modest) ; but anyway, something to grow into.
mircea_popescu: which is the deep problem we reference now and again with the "original penguin" stories. "nobody told me that the men with guns can very well kill me" is not the idle protestation of a retard, but the desperate cry of a broken mind that literally DOES NOT REALISE things that weren't on the
spec sheet may indeed exist.
lobbes: as it stood, my own bot's commands on the old directory weren't even represented accurately. plus the
spec does specify each bot should have a "help" command listing all other commands
a111: Logged on 2018-03-08 17:21 phf: so ada95 only has from_c/to_ada, using char_ptrs/char_array, pointers only appear in ada2000. ~maybe~ they ran into limitations of that interfaces, that are somehow imposed by the
spec, that we're missing (but running into effects of that), so to address the issue they introduced yet another method.
phf: so ada95 only has from_c/to_ada, using char_ptrs/char_array, pointers only appear in ada2000. ~maybe~ they ran into limitations of that interfaces, that are somehow imposed by the
spec, that we're missing (but running into effects of that), so to address the issue they introduced yet another method.
☟︎ ben_vulpes: very useful feedback in nailing down hardware
spec, ty
ben_vulpes: gotta point out that this is out-of-
spec behavior as is
mircea_popescu: now, as to everyone else : today's the 6th. the plan is to continue discussing the
spec given above, for improvements/refinements/whatever until the 8th ; at which point we start ordering. there's about 15k fiats worth of gear being contemplated, and i'm more than willing to spread it around a few people who want some cheap coins.
mircea_popescu: you're like, untalkable to. "do you need pictures ?" "no, i said
spec" "ok, ima dump it in chan" "NO I SAID DO NOT DUMP IT IN FUCKING CHAN"
phf: asciilifeform: one data point is that in e.g. nginx max_ranges is a parameter, which can be explicitly set to 0 to disable ranges, and if you search for it you get "how do i disable ranges" q's presumably by people configuring web servers. you don't have an equivalent for HEAD. likewise HEAD is part of the original
spec, where's ranges is a later addition. it stands to reason that the number of times range fails would be non 0 even with "modern" setups
phf: yes, that's cause fg looks like some mil
spec shit. you just needed to put inside a cheap plastic box and stencil "fax modem" on it
diana_coman: mircea_popescu, will schedule dreaming eulora
spec machine then
BingoBoingo: asciilifeform: You failed to
spec that part. You
spec'd pehbot
mircea_popescu: imo a fabulous textbook example of how the imperial vulnerability cycle goes. 1. make a bad
spec, a la SMGL ; 2. implement some portions of it only, because
http://btcbase.org/log/2018-01-25#1776189 ; 3. discover the bad
spec is vulnerable, issue "best practices" for people to "santize". obviously this will not be made by 1 if 2 wasn't, so... 4) implement slightly more of the
spec, throw security in disarray.
☝︎ NoSatoshisHear: try and even get the hdmi
spec, I'm still looking for a "dumped" version. Love the ethernet
spec they built in...
spyked is reading the
spec (
http://archive.is/FQ7P ); until now, lived with the wrong idea that pingbacks are a wp-dependent thing. but hey, it looks pretty clear!
mircea_popescu: this turns into an interesting inverse case of "the code is not the
spec", whereby... the
spec is not the code.
mircea_popescu can't believe just how utterly shitty his 2015
spec is. anyone read that thing recently ? please don't, i'm ashamed.
mircea_popescu: incidentally, anyone wanna do a steganobot ? here's the
spec : upon receiving a link to a pastebin, the bot picks a random tumblr image, doctors it, and links it.
phf: right, platonic unicode, i think it was more aligned even with common lisp's notion of character object or somesuch, than what the
spec actually become. i think he might've ranted somewhere about ms fucking it up and such
mircea_popescu will pay 2 bitcents to the first l2 (not l1) that produces timing data, to the same standard as teh graph, + machine
spec.
phf: i had that experience when i tried implementing an older
spec of gossipd. i wrote it in C, actually CWEB, but i wasn't doing literate programming right, and after a while the whole thing became overwhelming.