1100+ entries in 0.464s
Framedragger: i recall someone attempting an implementation /
spec of this 'everyone has their own currency' thing. just with wot being less central to it, perhaps
mircea_popescu: why would i have to prevent it ? there's specific space in the design
spec for third-party developed maps. they run by whatever rules third party comes up with ; player doens't have to enter it. if he does enter it, client loads up more data.
mircea_popescu: so then say "sorry, i couldn't maintain my bot to
spec" not "bickering. truth helps.
mircea_popescu: Framedragger then stop lying to yourself and draw the design
spec correctly.
phf: right timing attacks with gpg as backend i get. i assumed that attacker being able to discover topology is a given (with
spec as written)
phf: apparently it's even in the
spec a111: Logged on 2016-08-26 14:15 phf: particular transport. never the less when the conversation about current
spec comes in you are eager to point out how
spec is useless. it's a significant effort to drone you out long enough to actually attempt the implementation, and since in my experience attempting the implementation is a significant step in grokking, i think you repeating the same point over and over again actually lowers overall snr.
phf: particular transport. never the less when the conversation about current
spec comes in you are eager to point out how
spec is useless. it's a significant effort to drone you out long enough to actually attempt the implementation, and since in my experience attempting the implementation is a significant step in grokking, i think you repeating the same point over and over again actually lowers overall snr.
☟︎ phf: asciilifeform: going back to gossip conversation, my issue is that the gossip you talk about exists exclusively in your head, where's mp got a
spec. there are aspects of gossip functionality that can be explored with current
spec despite the underlying tcp transport. and like i said broken transport doesn't invalidate the application functionality. it will leak in practice through tcp shenanigans, but that's the nature of this
phf: but that's a very minor detail of the
spec!
phf: current
spec doesn't do that
phf: come to think of it sybil is not the right word in this case, on application level there's no psuedonymity and you only talk to people in wot. on transport level an attacker can construct a valid looking (struct layout wise) pgp packet, which in my naive
spec implementation is handed over to gnupg. now you have a bunch of potential attack vectors here, but assuming there's no memory attacks in gnupg, race conditions in gpgme,
Framedragger: i won't argue the point, sorry for any frustration caused. the thing i have in mind is probably not the "current
spec" anyway!
a111: Logged on 2016-08-26 01:10 phf: adlai: i think gossip
spec is fine, just nobody took it to release. asciilifeform has significant changes to the
spec, but if you ignore those you can still build a working implementation. in fact, unless you're ascii, i think it's better to ignore further discussion and just stick to what mp wrote. i also think it's one of those ideas you don't want nailed down at protocol level. mine for example slings gpg packets
Framedragger:
http://btcbase.org/log/2016-08-26#1529496 << just curious - does the gossip
spec as it is place any trust in ip addresses? this iirc was one of the points criticized by asciilifeform, i would think it to be a valid one. sorry if this, too, was extensively discussed in the logs.
☝︎ phf: adlai: i think gossip
spec is fine, just nobody took it to release. asciilifeform has significant changes to the
spec, but if you ignore those you can still build a working implementation. in fact, unless you're ascii, i think it's better to ignore further discussion and just stick to what mp wrote. i also think it's one of those ideas you don't want nailed down at protocol level. mine for example slings gpg packets
☟︎ a111: Logged on 2016-08-23 21:41 asciilifeform: znort987: rather, yes, there was provision for it in the original openpgp
spec, but it is a bogus concept because it entails a global repository of revocation messages and a universal agreement re what time it presently is.
phf: i'm trying to remember what the current name is (which is where community retardation comes from) but yeah, aclocal is where you
spec out just the things that you need for project
mircea_popescu: asciilifeform his argument is that it fits the
spec for performance. which it does.
mircea_popescu: yes, but i suspect we solve all that through not including idiocy in the
spec.
mircea_popescu: asciilifeform the difference between your
spec and my
spec should be obvious. is it ?
gabriel_laddel: on my dead harddrive there is a bunch of half-implemented useful things like clim-
spec-in-clim, the "navigator" which is a reflective search apropos, I've taken climacs and made it usable for day-to-day work...
mats: fun fact, the usb smart card reader
spec defines a control request for eating cards instead of returning them
mircea_popescu: ok. so the reasonable move here would be to
spec this to transport 10kbps from client to server ; in chunks no longer than 2048 and no shorter than 32.
a111: Logged on 2016-08-06 00:37 mircea_popescu: asciilifeform so im thinking here, without a byte/sec sort of idea of what messaging is liable to look like, we can't really
spec anything anyway.
mircea_popescu: asciilifeform so im thinking here, without a byte/sec sort of idea of what messaging is liable to look like, we can't really
spec anything anyway.
☟︎ mircea_popescu: hm. im guessing we'll get together with diana_coman and write a
spec ? unless you want to propose one ?
mircea_popescu: in fact, the heavy machinery industry is today very much a "designer item" sort of thing, pretty much any large mine will order machinery to
spec for its own particular use.
Framedragger: (maybe i just described a
spec that i should one day implement, heh)
a111: Logged on 2014-07-27 19:05 asciilifeform: mircea_popescu: in 2010 i concocted a variant of the test that could be carried out for approx. 50k USD, from scratch. schwartz answered that, in his estimation, the test would work to
spec, but results would not be accepted by the field unless carried out on one of the two existing eotvos balances. one - adelberger's, one - chicom.
mircea_popescu: next time that guy comes in that was trying to fix qntra, i guess we get him to make you a special wp 2.7 theme to
spec ?
phf: as a
spec to how a node within a wot graph is going to operate by default in relation to text
BingoBoingo: Yeah he hasn't made it that far yet. Just has
spec Framedragger: asciilifeform: is there a 'stable' algorithm /
spec for deriving phuctor's hash / permalink? you'd mentioned before that it "includes the entire key - names, emails, ~all~ subkeys."
mircea_popescu: it is perhaps notable that universe does not provide
spec of itself, and so "we're stuck doing basic science on it".
mircea_popescu: how you distinguish between "
spec" and "things that emerge from constraints" ?
Framedragger: (ahahaha re bassett disaster.. yeah i would view 'cache' as an inevitable result of *constraints* (finite c).. i think it was a confusion of terms (
spec / things that emerge from constraints), and i suppose the point of confusion itself is possibly an interesting object to discuss, etc)
mircea_popescu: honestly it doesn't seem anyone has a better idea of what a
spec is than "correct metaphora", which is ridiculous, ironic, scandalous and not much to go on simultaneously.
mircea_popescu: asciilifeform anyway, your definition of a
spec is amply vulnerable. take the time issue : what, ddr can't be specified ? fingering a girl neither ? what happens if the
spec asks for a 10 followed by a 11, and ytou get the 10 and silence ? now you got a whole halting problem on your hands.
mircea_popescu: then variant and unequivalent implementations of the same
spec may exist ?
mircea_popescu: and
spec may not discuss internal state, only inputs and outputs ?
mircea_popescu: "don't steal" can not be a
spec, only "if you steal you go to jail" ?
mircea_popescu: so a
spec is purely descriptive, and in no sense prescriptive ?
mircea_popescu: instead, he made one. by hand. to
spec as his project needed.
BingoBoingo: But yes, 80 col wrap is out of
spec for qntra's actually adaptive layout.
a111: Logged on 2016-06-10 01:15 phf: but you can easily upgrade open access service to a custom service and charge for the extra work too. if you want your ads injected on all machines, you don't get to put own exe, needs to
spec out the problem and give it to botnet owner to develop. also means that particularly losery owners will rapidly transfer their botnets to smarter crowd
phf: but you can easily upgrade open access service to a custom service and charge for the extra work too. if you want your ads injected on all machines, you don't get to put own exe, needs to
spec out the problem and give it to botnet owner to develop. also means that particularly losery owners will rapidly transfer their botnets to smarter crowd
☟︎ phf: mod6: if you want i can
spec it out for you, but that's the direction i want to take my some miniserver, that i would put on top of my znc logs
a111: Logged on 2016-05-31 19:04 asciilifeform: eh iirc mircea_popescu flies these in and reprogramms them to
spec in days.
trinque: phf: right, I would prefer not to account for
spec violations
phf: but you also have to account of all kinds of other
spec violations. like having non-blank ids that are also non-unique
trinque: because the
spec says it's unique
trinque: were that unique as per (iirc) the
spec of atom it'd not be skipping posts
mircea_popescu: 4. convert the phuctor key db into a sks as per republican
spec. the strategy being that we will confiscate all public key crypto just like we confiscated bitcoin from the fucktarded zombie horde.
mod6: actually, i'd bet there are folks, even here, that would do small
spec'd out work for .50000000
mircea_popescu: asciilifeform can you explain the concept of "contiguity" as seen in this ada
spec discussion ?
phf: that's also an idea from "when everything had a
spec, and everything was written to
spec, and things just fit into each other neatly" decades
phf: you need to
spec your problems better :>
phf: main reason gpg is turd, because was written for dos and frozen into
spec that way. provided functionally is composite and doesn't "do one thing well". instead of freeform key annotation has explicit "name, email, comment" fields, instead of easy way to spawn many keys, has a convoluted key hierarchy, etc.
mircea_popescu: ie, the win98 item is 100k in cash + 4,5mn in fixing it to
spec ; this is 340k in cash + 0 etc.