Thank you forwarded to me you're solving discussion, I just try to
modify the HOSTS in the number of connections from one into two, but
then was broken,,,, I will try to find other ways to break the blockade.
hosts:
0.0.0.0 xiaolan.me
0.0.0.0 twister.net.co
0.0.0.0 tuiku.me
0.0.0.0 wyc.tuiku.me
0.0.0.0 wyc2.tuiku.me
0.0.0.0 seed.twister.net.co
0.0.0.0 seed2.twister.net.co
0.0.0.0 seed2.twister.net.co
0.0.0.0 192.241.250.189
Marian Smith 於 2016/7/27 14:20 寫道:
Ok then how about the client picks a user at random to source the data
from with possible opt in, or give me a module that tracks the chain
and I'll drop it on my server, 10 gig a month is nothing. Build an ARM
variant so people can drop it on low power C1/C2/RPI devices so I can
put it in the closet and forget about it.
On Wednesday, 27 July 2016 04:26:20 UTC+10, Miguel Freitas wrote:
On Mon, Jul 25, 2016 at 2:59 AM, Marian Smith <[email protected]
<javascript:>> wrote:
Why don't you just maintain a github/sourceforge repo with the
blockchain and update it at least weekly/monthly and have the
client pull from that during initialization, pulling date a
week or month behind is nothing, it's the "since the dawn of
time" thing that is the issue.
Yes, you are right! This would be the best alternative.
However I can't be the only responsible for maintaining these
things. There is this idea called "bus factor", and we must
increase ours ;-)
--
You received this message because you are subscribed to the Google Groups
"twister-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
