84200+ entries in 0.459s

shinohai:
I mean
I usually just don't voice them until they actually produce a key.
trinque:
I don't see a problem with people coming to the forum to announce their existence as a person.
shinohai: asciilifeform: when the tardstalk people come in, just have them msg me or something and
I'll point them to the guides
veter2601: Tell me how
I can (Earn 0.01 BTC (one bitcent) per two hours doing computer stuff.) pls
Framedragger: asciilifeform: ah, so 'private key' is purely 'station key' -
i guess like in latest gossipd discussion
shinohai: neat asciilifeform ...
I haven't sourced one of the others yet :/
Framedragger: PeterL: ah, good point. and regarding first packet,
i wonder if some very light lighthouse version would make sense, a pre-shared sequence of whitelisted nonces between two given nodes, whatnot. in the beginning, interchangeable over internet. and later, updateable over same radio channel ("here's my payload, and also please add to your whitenoncelist this encrypted sequence of nonces for future channel initiations.")
burnsd03: nope,
i stay clear of hyips etc
shinohai: Exactly who
I thought of PeterL lol
Framedragger: asciilifeform: you mean an initial packet after a period of silence? hm yeah; one way would be to have a scheme in place which
i think you may have suggested anyway: to have stations constantly stream packets at some rate, 24/7.
Framedragger: maybe
i'm not getting the picture how quickly entries in the buffer can expire, though
Framedragger: asciilifeform: ah, right,
i forgot everything's signed, lol. nice!
i guess enemy could replay for a (choosably) small window of time, some degree of flooding possible? but this could be minimized and that's the point, right?
Framedragger: asciilifeform:
i wonder, could this not be predicted by the enemy? (value of nonce - say the enemy is aware of the (likely) packets received by the receiving end.)
i'm not sure, just trying out all possibilities in the head, because otherwise sounds nice
Framedragger: asciilifeform: buffer is a rolling window (or how do you call it),
i.e. last N messages? hmm
Framedragger: nice. what of DoS via replay, asciilifeform ? or should this get ignored?
i.e. enemy just floods with identical packets (so both checksum and sig ok), and those get redistributed
thestringpuller: "The main cost in the initial synchronization is disk
I/O when seeking for transactions in the blockchain. Default cache size (dbcache) is 100MB, and it is too low.
I always set it manually depending on the amount of RAM in the system (5GB for dbcache on a 8GB system)." << re: discussions of using SSDs on initial sync.
mircea_popescu: word ;
i was thinking of proposing exactly this but then
i got distracted.
Framedragger: need to minimize energy expenditure at $job. "go home tired" sort of case, it's sad.
i'd like to, e.g., among other matters (incl mkj log etc of course), write a very initial very to-be-criticized gossipd for udp/ip, using (kill me now) python twisted.
i guess many live like this, savouring free time, with personal projects falling behind. [
i rant today, because exhaustion + coffee infusion => wee bit psychedelic]
Framedragger: mircea_popescu: the sad part is that by "battling out" ideas in this wordspace, one gets a bit of serotonin rush, to feel *as if* they have actually done something material.
i know
i get this, at least. evolutionary side-effect, this whole "curiosity -> completion" gap used to be much larger, not it short-circuits easily. it sucks, need to make conscious effort to resist sinking into nihilistic bliss,
i think. </rant>
PeterL: oh, yeah,
I think it just lapsed
Framedragger: myeah,
i know. but
i also think it's only a matter of degree of effort: if
i'm not important enough in their eyes,
i'll be fine. if on the other hand
i am, then they'll find a way to link me to station and will pay a visit. a.k.a. binary "are you important?" security model.
Framedragger:
i'd risk getting a visit from the spooks here, honestly been interested in viability of low bitrate (plain-encrypted, in my mind) radio exchange for a whole.
PeterL: mircea_popescu at one point
I demonstrated a script to do that, asciilifeform scoffed at it as useless
mircea_popescu: and
i do recall it ; which proves that they aren't eh ?
Framedragger: mircea_popescu: and those will of course not have much bandwidth capacity. but
i maintain that to usefully PoC the thing, you don't need much at all. jeebus, having a radio-based key server would be amazing already
Framedragger: (consider a true radio relay, by which
i mean a relay which sends, receives, and *passes on* messages received from one end to the other)
Framedragger:
i still don't understand why the hell you need them 100kW
Framedragger:
i mean personally, to be able to exchange pgp-signed sha512 hashes would make me super happy already - maybe premature ejaculation, yes, but it'd be a *useful facility*.
Framedragger: yeah
i wouldn't transmit encrypted shortwaves from usa, that indeed sounds like doom
Framedragger: (
i know that ideal lighthoused would have much higher throughput.)
Framedragger: that's the way it works,
i guess. talk is easy
Framedragger: that's the thing,
i wonder if a few points around the globe wouldn't be enough, in principle!
Framedragger:
i mean ideally, it'd be a p2p radio station network. antenna + dongle + stuff can be real cheap.
Framedragger: btw regarding "there is no sane NIC out there" problem and appreciating the fact that designing a whole proper NIC may not be an efficient effort ("ip stack should be eventually abandoned", lots of work, economies of scale at work in semiconductor production, whatnot),
i wonder why asciilifeform hasn't considered investing time not in seeking a sane nic, but rather designing / using a sane transport protocol via *radio* (
i don't mean shi
Framedragger: but
i guess that's what's effectively happening anyway :)
Framedragger: yeah for a sec
i thought this was new. but totally should be done
Framedragger: (
i mean, polling and re-polling later to check status etc)
Framedragger:
i'll prolly do this and make use of vc's cockbox. his /dev/null attitude to abuuuuze complaints is appreciated.
ben_vulpes: asciilifeform, phf:
i'm giving up on variable length binary-types for now. my personal pons asinorum for this library is the task of defining either a type or a class whose value could be either u8, u16, u32 or u64, plus the headaches of entirely arbitrary-length scripts.
mircea_popescu: yeah. and
i meant, "probably a realtek clone made in south korea".
phf:
i think are behind the "Killer" brand