446600+ entries in 0.276s
ben_vulpes: trivial patch
to apply for anyone who's vested.
☟︎ ben_vulpes: 3 say "fu
this shit is wrong and stupid", set version
to $maxint
ben_vulpes: 2 be stealthy, advertise whatever "version" is "current" with
the shitgnomes
ascii_field: ben_vulpes: i brought up
this point before. asked mircea_popescu why we insist on making it so easy for gavinists
to wall off our net from
the rubes. iirc mircea_popescu said 'fuck
them all'
ben_vulpes: mircea_popescu: it doesn't make a practical difference, but it pins a pointless magic variable at its "infinity" value, in
the zero, one infinity mapping.
mircea_popescu: if you mined and set
the block version
to maxint it might.
ben_vulpes: why advertise version instead of just responding
to network messages?
ben_vulpes: i actually
think setting version
to $maxint is a pretty great idea.
ben_vulpes: <ascii_field> also i verified
that if version constant is set
to 99999,
https://getaddr.bitnodes.io agrees
to see
the node. unless someone gives a fuck, i will set it back
to 0.5.4-beta later
today << eeeheuhe
ascii_field: mircea_popescu: it was intended
to work as you stated above
mircea_popescu: how
the fuck we ended up with
this situation where diff machiens have unequal
times is beyond me
ascii_field: also i verified
that if version constant is set
to 99999,
https://getaddr.bitnodes.io agrees
to see
the node. unless someone gives a fuck, i will set it back
to 0.5.4-beta later
today
mircea_popescu: ascii_field i have nfi why unixtime "locales" are implemented so braindamagedly anyway. all machines should have
the same exact integer for
time.
then if you wish
to localize it, localize it on
top of
that
☟︎☟︎ ascii_field: but since i refuse
to run ntp on
the box, i ended up setting date manually when i was given it
kakobrekla: >A
timestamp is accepted as valid if it is greater
than
the median
timestamp of previous 11 blocks, and less
than
the network-adjusted
time + 2 hours. "Network-adjusted
time" is
the median of
the
timestamps returned by all nodes connected
to you.
ascii_field: kakobrekla:
theoretically, epoch
time is 'one for all of us, like victory'
kakobrekla: 'your_epoch' is 'network-adjusted
time' isnt it
ascii_field: i knew
the basic fact of. but given as
the box displayed correct wall
time, did not
think of it
ben_vulpes: node has been wedged for more
than a lunch iirc
ascii_field: if |your_epoch - block_epoch| > 2hour
then lose
ben_vulpes: jesus shit. we'll have
to run our own ntp cluster next.
ben_vulpes: blee. so block validation relies on some absolute coordinated
time?
ascii_field: but what
this means is
that no,
the
thing won't correct for clock offset
ascii_field: i had
the box set
to my local
time instead of gmt
ben_vulpes: is
this a direct result of headers only mining?
ascii_field: (not
the umd box.
though betcha it belongs
to
the umd scamlab)
ascii_field: ;;later
tell mircea_popescu
turns out it was
the epoch
time
ben_vulpes: jurov:
there's a bit more
than
that. did you read my subsequent link?
ascii_field: ben_vulpes: i do not yet know
the answer
to
this
ben_vulpes: ascii_field: are blocks from headers-only miners coming out with
timestamps
too far in
the future?
hdbuck: hello mircea_popescu, just passing by
to say
thx for
the rating
ben_vulpes: ;;later
tell pete_dushenski whaddaya know about
this glynn-ward character?
☟︎ ben_vulpes: ^^
the wot at work. ridiculous numbers aside, we
tell stories of heroic deeds performed in service of
the papers we sign.
ben_vulpes: "Oh, well, I had
the contract, and I had
to fill it!" And
that was all he said.
ben_vulpes: So it was
that C. B. returned
to Hazelton afoot, limping into
the hotel one snowy night in midwinter, "broke
to
the wide", but otherwise unconcerned.
ben_vulpes: another
to feed
the rest,
they weakend and died on
the
trail.
ben_vulpes: Again he started out,
this
time with a hundred and
twenty-eight dogs, and when he came
to
the place where he had
turned back, he was able
to feed
the dogs on dead horse-meat, and so get
through
to
the cabin where
to
two men were waiting. But on
the return
trip,
the going was heavy and slow and he found
that
the worlves had reached
the cache of horse-meat and finished it up, so
the dogs were short of food and
though he killed one after
ben_vulpes: Those supplies had
to be delivered
to
the men patiently waiting for
them at
the far end of
the
trail, So he cached
the supplies, hoiseted as many carcases of
the dead horses as possible into
trees where
the wolves could not get
them, and went all
the way back
to Hazelton
to get dog-teams.
ben_vulpes: Every now and
then a horse would miss its footing and go over, sometimes into
the rushing river below,
to be lost forever.
Then it froze, and
the going was hopeless. One by one
the horses slipped and went down until it was impossible
to go onward. C. B. shrugged his shoulders and altered his plans.
ben_vulpes: all next day and
the following night without any let-up.
ben_vulpes: So C. B. at once set off north again witha pack-train of sixty-eight horses. He had no very great hope of being able
to make his destination before
the hard weather came on, but he
traveled with all
the speed possible,
to get over
the worst places on
the
trail before
ths first snow fell. But as ill-luck would have it, it began
to snow one night just as he came
to
the rock ledges where
the going was bad at
the best of
times. It snowed
ben_vulpes: supplied -- and it was getting late in
the autumn.
ben_vulpes: Story has it
that he returned
to Hazelton, once, after a
trip up
the
Telegraph
Trail, and
there he found out
that he had missed
the farthest cabin of all, over
two hundred miles away, and
there were
two men up
there left without supplies for
the winter. Either
the Government had not made
the
tale of
the cabins clear or C. B. himself had miscalculated. However
that may have been,
the plain fact remained
that
these
two men had
to be
☟︎ kakobrekla: >you won't gain much by lying
to your peers since your block won't be
ben_vulpes: ascii_field: fascinating! what gears are failing
to mesh here?
ascii_field: kakobrekla: ^ if
there were no record of
the early blocks -
then yes
ben_vulpes: The little Jap who, laughing up and down his sleeve goes cheerfully about his business in a gas-boat up
the coast, or picks out
the best small-fruit land in
the country;
the ubiquitous Chinaman, steadily cornering all
the loose cash in
the land -- of a surety
these
two know more of British Columbia
than most white men!
kakobrekla: generate one year's worth of hashes. < isnt
this one year actually 10 min ?
kakobrekla: >but I can't fake
the hashing power it needs
to
ben_vulpes: The Americans come, with plenty of money, and stay at
the much-advertised hotels, gulping down
the Rockies in predigested doses,
thenrace
through in a Pullman car
to
the next big hotel on
the coast. And how can
they know anything of
the province?
ascii_field: so i'm nearly certain
that
the
timestamp ~2h epoch
time window is
the reason for wedged 0.5.x nodes, at
this point
ben_vulpes: halls, about "great open spaces" and "the need for a population." But
they know nothing of
the real British Columbia.
ben_vulpes: "The English come out and
travel
through, knowing all about everything beforehand, as
the English always do; and, having set standards,
they compare
the Fraser
to
the
Thames (former
too wide) and
the Selkirks
to
the Cotswolds (former
too high).
They get out
to spend a day or so at Lake Louise or Jasper,
then get into
the
train again and stay
there
till
they reach Vancouver.
Then
they go back
to England and give vague lectures in
town
ben_vulpes: mircea_popescu: if you liked clements
tall
tales, you might get a kick out of Glynn-Ward's "Glamour of British Columbia"
ascii_field: anyone who sees a 'martian' version number from nosuchlabs public node, please don't be alarmed. running an experiment
today,
to determine whether we are being corralled by gavinists using advertised version constant
ascii_field: (for
the exact instruction set supported, see
the marvell datasheet posted ~6 mo. ago.)
ascii_field: the buildroot gives you
the complete
toolchain you need, independently from
that of
the box you're on
assbot: Logged on 06-07-2015 17:37:21;
trinque: anyone know offhand if armv5tel-softfloat is
the appropriate arch for pogo?
trinque: trying
to get some repeatable builds going for arm
trinque: I
tried building stator with arm-linux-gnueabi and it segfaults on
the pogo
ben_vulpes: trinque: is
that info missing from asciilifeform's post
to
the ml?
ben_vulpes: does anyone know at a high level how nginx does
the "swap binary while running"
trick?
trinque: anyone know offhand if armv5tel-softfloat is
the appropriate arch for pogo?
☟︎ ascii_field: they just happen
to write
turdware for usg.
ascii_field: gotta also love
the clean, well-commented (italian!) cpp
ascii_field: gotta love how
the morons had
their private keys
thrown
to
the wind
ben_vulpes: take your myip flag - is
that automagically a .conf file option as well?
mats: ain't
the net a grand place?
assbot: Logged on 06-07-2015 12:15:59; mircea_popescu: not unless you get amir
taaki
to "open source" it.
ascii_field: in other nyooz, my portable
test node is synced.
ben_vulpes: excellent long
term cost reduction strategy imho
punkman: ascii_field: not sure what you mean with "but not move
the local epoch
time"
ascii_field: seems like logical
thing
to do would be
to accept
the block but not move
the local epoch
time if
the block's
time is an outlier ?
punkman: ascii_field:rejects
too far in
the future because it wants
to keep "network
time" within some bounds
assbot: Logged on 06-07-2015 15:03:54; mircea_popescu: asciilifeform of course, if phuctor is
this starved for io, would it be a good idea
to move
that
thing
to ssd ? maybe even raid ?
assbot: Logged on 06-07-2015 15:03:24; mircea_popescu: danielpbarron ideally
take
them apart and send
them as parts he says
assbot: Logged on 06-07-2015 16:20:00; punkman: ben_vulpes: network needs
to know how long it's been in human
time since last retarget
kakobrekla: speed is a function of
time and distance, so you need
to know how much
time has passed in
the 2016 blocks, right?
punkman: ben_vulpes: network needs
to know how long it's been in human
time since last retarget
☟︎ jurov: ben_vulpes: yes it is, but also
time elapsed