445100+ entries in 0.243s
williamdunne currently has a neck
that looks like Cheetah fur, lovely patterned bruising
williamdunne: I would also like
to learn Spanish, on my
to do list
mod6 has
to ramp up on espanol for c4
williamdunne: ;;later
tell gabriel_laddel was checking my rates, out of interest what is my association with gamingfurry.tumblr.com?
☟︎ BingoBoingo: But still,
that isn't
the complete
type. It's
the entire shape of
the face: very, very Anglo
trinque: why do all
the chimos have a certain look about
them?
mod6: lemme
try
this out :]
mod6: read your readme... so yeah, months and months ago I was able
to build a dynamic bitcoind on openbsd, but
that was
the exact issue after statically linked: seg fault.
phf: mod6: yes,
though
they are conceptually similar
to
the one from dpaste
mod6: ok, so I should just use your patches just posted
then
BingoBoingo: phf: It sync'd and so far it hasn't forked outside of
the ways other Bitcoins have
BingoBoingo: <mod6> phf: i built on 5.6 but I can't seem
to get mine
to be be statically built :( << First
thing
to understand about OpenBSD is
that it is a weird unix. Not as weird as Linux, but differently weird.
phf: BingoBoingo:
that's a good idea, i decided
to punt on it, because i don't fully understand
the reasoning behind
the whole 1.0.1g freeze
mod6: it was from a patch, but not from
the email you just sent in...
phf: mod6: is
that with
the patch i posted
to ml?
BingoBoingo: phf: No, not yet. On OpenBSD I'm running an 0.7.2 derivative with LibreSSL 2.0 just
to see how it behaves.
mod6: phf: i built on 5.6 but I can't seem
to get mine
to be be statically built :(
phf: BingoBoingo: have you
tried making static build on openbsd? i seem
to recall you were running a bunch of openbsd boxes
BingoBoingo: Yeah, it was necessary
to keep up with 0.8 normal. May need a still bigger boost for reorgs
though.
mod6: for
those who don't remember, we used
to get stuck at block 252`450 before with only 10000 locks set
BingoBoingo: <mod6> here's something I missed: log.bitcoin-assets.com/?date=04-07-2015#1187292 << May have
to increase locks limit (why it must be
there idk) for reorg robustness
shinohai: Good find mod6, I hadn't got
that far back yet
mats: it doesn't look like bitcoin is ready for prime
time
mod6: i'll have
to see when i get
there i guess.
shinohai: I have a stator build working, just waiting on my pogo
to get here first. Using
the 0.5.3 RELEASE on my shell
BingoBoingo: shinohai: My stator
testbed is lucky it is
too slow
to have been anywhere close in
time
to
that having been an issue,
though
that is still an enduring issue.
shinohai: I made
the sync fine until
that orphaned block on
the 4th
shinohai: I switched my config
to addnode, got unstuck
then stopped it
ben_vulpes: <mod6> i seem
to remember asciilifeform switching over
to -addnode after he got stuck. but let's see what he says about it. i'll probably hit
the same issue myself. << i don't
think he did
shinohai: It's always in
the name of lulz BingoBoingo
BingoBoingo: Well, not really re-create. Just fucking up
the version strings in
the name of lulz
BingoBoingo finally
trying
to recreate my OpenBSD 0.7.2-ish qt build. Must have lost
the original sources
that worked somewhere down
the line
shinohai: I'll give
that a shot mod6, been using -connect
mod6: i seem
to remember asciilifeform switching over
to -addnode after he got stuck. but let's see what he says about it. i'll probably hit
the same issue myself.
shinohai: I wish my node would sync
to either IP, as it is I'm stuck atm.
trinque: better yet, rather
than death, a life of moving heavy objects
trinque: the ritual should be arranged such
that imitating someone else without reflecting on
the outcome first results in death
trinque: these earth humans need a ritual which
tests for mindless imitation in children
trinque: BECAUSE YOU KNOW,
THIS IS HOW
THINGS ARE DONE
TODAY
trinque: presumably
to help work on
their vast wad o cpp
ascii_field: this is
the output of a proggy
that can
take any cpp
tree ?
trinque: so perhaps if I can find where it stores
the symbol
table, I can get
the data out of
this vast piece of mozilla
danielpbarron: in 2010 a very similar conversation was being had over on
the forum
danielpbarron: i have read it all; just happened upon
this relevant
thread coincidentally
ascii_field: danielpbarron: if you missed
the
thread - it was about how we have no clock on pogo
mats: i wonder why it failed
to build on OS X
ascii_field: it is possible
to develop for winblows and remain sane if you
treat it like a 'nintendo'
ascii_field: (and before anyone chimes in with 'of course vs' -
this is empirically false. can build arbitrarily complicated crapware for winblows with gcc)
BingoBoingo: querying at all is problematic. If it must be queried
though best
to make
the
timing of queries less predictable.
ascii_field: mats: read
that last night. notice how it wants you
to build with microshit vs!!!
ascii_field: BingoBoingo: querying it at all is problematic. see
today's
thread.
BingoBoingo: <ascii_field> danielpbarron:
this is correct and unsurprising, and blows up
the 'ntp once on powerup'
thing << query
timeserver every modulo(rand) seconds?
ascii_field: likewise,
the 'bubbles' ought
to be sized proportional
to
their connectivity degree.
☟︎ ascii_field: but gotta minimize
the crossings of
the paths.
ascii_field: the callgraph
thing is a straight 'travelling salesman' problem
ascii_field: which means
that it is severely pushed off course by events outside of its control
ascii_field: danielpbarron:
this is correct and unsurprising, and blows up
the 'ntp once on powerup'
thing
jurov expects a discovery
that satoshi cast and called functions from void*
danielpbarron: on
the
topic of
time and
the pogo, I should point out
that I recently had
to update
the
time on my blue pogo (the one i'm using as a web server / irc client) because it had drifted from
the real
time by as much as a quarter hour in
the few months it had been running continuously
ascii_field: the graph flabkebab_ showed does not even attempt
to place symbols ~anywhere near~ even one of
their links !!
trinque: but
the ebnf I was modeling wasn't convoluted inward on itself
this haphazardly
trinque: I wrote a
thing
that did a force directed graph for an ebnf once
ascii_field: if
the answer is no - what makes you
think ~i~ could
ascii_field: look at your picture. would you, personally, get any use out of
this ?
ascii_field: trinque:
technically, packets are diddled in room 641a. room 101 is where
they put rats in your face
jurov: mircea_popescu: is
the ftp server in
the vicinity of your bitcoin node? it went full speed for minutes,
then it suddenly
throttled
to 6kbps
☟︎ trinque: gephi will shake
the graph out for ya with various plugins
flabkebab_: Edges
too close
together and was also unreadbale
flabkebab_: I also
tried something less... ball-yarny
trinque: yeah well
the call graph itself is
tangled
trinque: I mean an interface
to
the dot
trinque: I was using "gephi" for
this
trinque: ascii_field: it's gonna
take something where you can grab a node and have it
trace only
that one
ascii_field: my patience for 'help
the mouse find
the cheese' ran out when i was four
☟︎ ascii_field: that still doesn't look like ~all~
the unique symbols in
the
tree
trinque: looks better
than my rat-king
flabkebab: So I've been having a go at
the callgraph
thing
danielpbarron: i have not noticed
the "network
test" except
that my actual full nodes sometimes differ by (sometimes rarely) as much as a few dozen blocks before eventually settling in on
the
true height. My
transaction sending has been uneffected.