World: r3wp

Yes, same here.

I must leave. Sorry.

yes, I must go to sleep too.

just met: [#{EB1415D4333962F3E0846C3F04EB658CC8A82BB4}  maybe he's 
an ewok

Myself: [#{8AFE771BF1EBD74BEF561678804F431020356D81} ahttp://69.154.214.143:2222]

but you can call me #{8AFE} for short.  My friend call me "8"

I only use all 160 bits with my customers.

hi 8A, nice to meet you, I'm 69

did you know 69 hex = 01101001 which is also symmetrical?  I use 
that for a maybe flag.

a geek T-shirt could be "Wanna 01101001?" but only Selma would understand...

70726F746F636F6C206572726F723A206D65737361676520646F6573206E6F74206D616B652073656E73652E

(I know that's ascii...was just downloading the chart...but guess 
I should write a script...)

not the alpha please

this uses the old async-modes

i'm sorry but i need it to work with the sdk :)

protocol ...

Gabriele - what is the bug in UDP you mentioned earlier?

port/awake gets called endlessly

... is it present even with new async Core?

yup

...error:...

crashed here too now

ah, maybe someone enetered an unvalid url. ok something to fix since 
it's too common :)

(of course nothing of this would be needed on the final version)

message...

I am only decoding Anton...mine is still running.

the bootstrap node seems to be still running

(ok i think i found another bug)

but it self-healed which is good

I guess I am not sure if it is running.  It was printing a message 
periodically, but now I don't see activity...but no error message...no 
not sure how to tell it is alive.

i think i still have you as my predecessor

anyway it's going much better than the last time... though i'd prefer 
to have it running on udp (it's much faster)

i'll keep it running and check back later. looks like i can have 
it working soon :-)

the problem is, that most ppl are today behind firewall or nat ...

UDP is used quite often in cell phone data for the same reason.

It is still running...I drag selected text...maybe printing the time 
would help tell it is alive easier for testers...

...fogs not make sense.

protocol message error: fogs not make sense.

Good to see we're coming close.... this will make REBOL shine.

(I was decoding Anton's message)

Maarten - why do you think it will make rebol shine?

... because of apps Chord will allow to build?

Yes. Distributed computing will be much more powerful, and REBOL's 
dialecting puts it apart. Enhance the networking part with P2P and 
nothing can match that.

Once Gabriele has this working we'll port it later this year to Rebservices. 
Then you can do stuff like lightweight grid computing, presence, 
file sharing, signaling for other applications (I am thinking of 
ad-hoc VPNs) in just a few lines of code. With NAT/firewall traversal 
out of the box.

how will you do NAT/FW traversal?

Yes, I have NAT at home as well. No chance to change it. Do I just 
enter my "local" IP adress? Doesn't seem to make sense to me.

I can change it, I did so for Azureus for e.g., but it requires me 
to enter local network IP. But what if I want to have two users using 
Chord? How do I tell the NAT which computer it should contact on 
2222 port? Or should I use different port for each user?

Simpler: if you are under NAT or firewall you'll poll to another 
node that acts as your relay. Network wise, you're only a client, 
but you'll do anything logically

yes, that is similar to DC++ and Bittorrents ...

Except that this is a library, allowing you to build applications 
of your own that ar eless trivial then filesharing.