11700+ entries in 0.091s

a111: Logged on 2019-05-31 11:59 diana_coman: asciilifeform: fwiw
I enjoy your non-programming output
mircea_popescu:
i didn't delete them off the site, just took 'em out of rotation is all.
mircea_popescu: in other news of little consequence,
i added 4 more headers and deleted like a dozen or so (older, shittier ones), leaving the grand total at 57.
phf: asciilifeform: right, snabb doesn't have some of our restrictions,
i.e. they accept all kinds of modern gnarl in exchange for the ability to send raw packets.
i'm not sure their approach even works on old cards
phf:
i'm not sure that's particularly useful. at the time
i was still switching between running btcbase on hunchentoot in prod and on alisp/aserve in development
a111: Logged on 2019-05-29 08:42 spyked: in particular,
I saw trinque, phf and ben_vulpes have been using it in the past, so
I'd appreciate any input you have on the matter
mp_en_viaje: indeed.
i had sluts live illegally for years, didn't even get fined.
mp_en_viaje: asciilifeform, well, meanwhile since
i'm here put a little more weight into the network and so on.
mp_en_viaje:
i thought it's a little weird, /me throws
a small bone, dog studiously pretends to not notice while tryna get all sorta typically needful "projects" off ground, like writing books and makign tv pilots.
mp_en_viaje:
i think by now they use a sort of auxiliaries that are allowed to marry.
mp_en_viaje: closed two days later
i wonder ? probably... ALSO the investor's fault ? it's not like "everything the government makes IS shit", not at all ?
ave1:
I'm currently reading May, next April...
BingoBoingo: However
I am curious how the cheapest model on the local market failed.
a111: Logged on 2019-05-29 09:06 spyked: the weird part is that the linux tcp stack ~works~ for the most part.
I imagine the maintainer of that particular subsystem must be a neckbeard with 20+y experience in tcp (because sure, it's not only the implementation, the protocol itself is a mountain of complexity)
spyked: the weird part is that the linux tcp stack ~works~ for the most part.
I imagine the maintainer of that particular subsystem must be a neckbeard with 20+y experience in tcp (because sure, it's not only the implementation, the protocol itself is a mountain of complexity)
☟︎ diana_coman: by now
I suspect most code out there is the fungus sort as that's how things "naturally grow"
a111: Logged on 2019-05-22 21:36 lobbes: As it stands
I have two full pages of hand-written notes with various c and apache-stack likbez, and that was just so
I could understand up to line 152 of
https://github.com/mbattyani/mod_lisp/blob/master/mod_lisp2.c (only 900 or so lines left to eat).
I most likely will publish these notes as a blog post once all is said and done
spyked: and
I guess
I'd prefer starting from code already battle-tested by L1 (in the form of a tarball + ksum?) rather than shithub, and turning _that_ into a genesis. although
I suspect
I'll have to dig deeper into the heathenpits of git commits anyway.
spyked: in particular,
I saw trinque, phf and ben_vulpes have been using it in the past, so
I'd appreciate any input you have on the matter
☟︎ spyked: so far
I've been looking at
the project changelog and the
patch history and the patches seem like a mixed bunch, with (perhaps) some useful things and breakage a la sslism. so before going further,
I'd like to get some idea of what version of hunchentoot the lordship and the L2 are using
mp_en_viaje:
i recall at least a half dozen of these "nope, nm, mp was right"
mp_en_viaje: so, real chain weighs 1bn and block #2 weighs 1,
i make fake chain with block alt-#2 weigh 2 and total chain weigh 10mn, in 1mn blocks.
mp_en_viaje:
i do not need to match difficulty block by block, see.
mp_en_viaje: then
i could continue this way to block 620k. just as long as
i have both a) longest chain and b) a more difficultuous block sometime early on, my chain is technically, by protocol rules, the true chain.
mp_en_viaje:
i could (in principle) produce an alternate block #2, very cheaply, but of higher diff than the true block #2. this then ~should~ be accepted by syncing node.
a111: Logged on 2018-10-22 22:37 asciilifeform: mircea_popescu: unrelated to anyffing:
i have a tentative thing that eats a
http://btcbase.org/log/2018-10-20#1864354 and gives trb option of replacing 'checkpoints' with it (
i.e. on boot, tests all already-stored blox against it, and if any blox in the tape are not yet present, then it requests & accepts them and only them, 1 at a time ). do we want this for field use ? (if so
i can put on conveyor for cleanup)
mp_en_viaje: 80% similarly. and so on. just pick one -- by which
i mean, expose knob in config, let any user pick his hairdo"
mp_en_viaje: what
i'm sayng here is, that a trb w/o the rainbow tables is shipped defective, like a car without wheels or w/e, toys without batteries.
mp_en_viaje: "cogentco doesn't give me ip" "ever wondered why ?" "you mean there's a government conspiraci ?" "no.
i mean there doesn't need to be one."
a111: Logged on 2019-05-28 16:22 nocredit: another question: if
i run core without using segwit features (so sticking with the 1 starting addresses) am
i actually protected from an eventual attack on segwit?
I know that here is not core support, but there is a way to tell core to dump the segwit part?
a111: Logged on 2019-05-28 16:11 nocredit: first of all
i'd like to ask what is a sane time for sync from zero to 100%
mp_en_viaje: this design permits fallback ("
i want to see dynas but if absent gimme joes" sorta setting)
diana_coman: ugh, last time the rough sketch sounded as
I said above though, lolz
diana_coman: iirc it was specifically not a list of meshes but at most a list of overall graphical profiles as it were;
i.e. each thing then at any time has only one option
mp_en_viaje: and so
i suppose all this can go in config file.
diana_coman: (re files and access time
I need to look if
I can get it, hopefully, via Ada.Directories)
mp_en_viaje: it's only the user whocan decide "
i don't want any sounds" or "no videos" or "no meshes only icons" or anything like this.
diana_coman:
I said "server did inform" not didn't, lol
mp_en_viaje:
i mean, if client doesn't know wtf it is, how is client to use it ? obviously it informs.
diana_coman: fwiw
I'll clearly have to hack my own client at the very least for making it text-only since there's no point in asking for all the graphical parts just because server did inform that those objects have this and that graphical part
diana_coman: from my pov
I'm fine to switch perspective and go then with this approach, so basically there are no "client/cpp demands" anything since Ada-part directly handles it on the principle "if
I saw it and it's not there, then
I'll ask for it"; how is any limit re space or anything of the sort to be defined and handled in this case?
diana_coman: (and this thing that "doesn't keep everything" is why
I went with the different approach aka ask when needed, not when heard of it)
diana_coman: is at all clear that there is this separation between the client-part that uses/needs some data on one hand, the one
I kept calling "client" or c/cpp and on the other hand the lower layer that is protocol aware and actually "asks what is x"?
diana_coman: honestly, as a player,
I'll then have to hack my own client, lolz
diana_coman:
I don't think
I get it and
I'm not sure whether it's because some things are still not right (for starters there is no fixed duration as it's dynamic basically)
mp_en_viaje:
i have NEVER seen this shitty internet in my fuckign life jesus
diana_coman: then
I don't get it; because if it is the client's decision to ask immediate refresh then sure, what's the problem? it's their decision and it still is the minimum traffic resulting
diana_coman:
i.e. client comes in the shop and asks 100 times for the same thing while shopkeeper is working on delivering it so what
diana_coman: move those three IDs*
I should have said; not the objects themselves
mp_en_viaje:
i am not saying "there is no difference".
i am saying "you are proposing to produce a mechanism to resolve a problem you imagine exists, such that the solution's parameters are populated by guesswork and the imagined problem is not eliminated"
a111: Logged on 2019-05-28 11:47 diana_coman: mp_en_viaje:
I suspect it's again one of those things where there is no disagreement at the core but we are not yet fully in sync re various bits and pieces;
nocredit: ok perfect. Will update here when
I complete the sync
nocredit: but yes,
i've learn the lesson. Only bare metal at my home
BingoBoingo: <nocredit> and last: if
i tar gz everything synced as far as now on the VPS and dump it at my premise,
i'll be able to restart at block height 300k in the future? << As long as you cleanly shut down the daemon before dumping
nocredit: and last: if
i tar gz everything synced as far as now on the VPS and dump it at my premise,
i'll be able to restart at block height 300k in the future?
diana_coman: nocredit: for that matter if running own trb is too big a pain/expense,
I suppose you might be better served by getting in the wot and using deedbot's wallet for that matter.
nocredit: correct,
I appreciate TRB as it removes the bloat. But 3 weeks to sync is really a pain
BingoBoingo: It takes time, but
I can also but a blockchain on a drive.
nocredit: another question: if
i run core without using segwit features (so sticking with the 1 starting addresses) am
i actually protected from an eventual attack on segwit?
I know that here is not core support, but there is a way to tell core to dump the segwit part?
☟︎ nocredit: thanks, yes physical colo is too much,
i hope that ssh tunnel is stable enough for 3 weeks of sync
diana_coman: nocredit: re provider
I warmly recommend talking to Pizarro and in particular to BingoBoingo in #pizarro.
nocredit: my problem is that
i don't have a static ip at my premises, so at home it's a pain with the myip parameter.
I was trying with a pico vps to bypass this by set up a private vpn, but as now
i'm stuck