K closest nodes empty

[cjb]

K closest nodes empty

[cjb]

Ah, this is actually a syntax problem: you can do:

git clone gittorrent://github.com/cjb/gittorrent

or

git clone gittorrent://81e24205d4bac8496d3e13282c90ead5045f09ea/gittorrent

But you can't use the shortest syntax yet, 'cause the blockchain stuff isn't running. Seems like we have two bugs, one to reject the short syntax, and one to make the blockchain scanning work (probably by integrating https://github.com/blockstack/blockstore).

[retrohacker]

Oh nice!!! I'm connected to the torrent network now!!! This is sweet!!!

Though I'm getting a lot of timeouts for queries, is that normal?

(also, thanks for responding so quickly!)

Do you have open issues for either of those? I'd be interested in tackling at least the first one.

[cjb]

Nope don't have open issues!

That's odd, it looks like my machine is emitting internal (10.*) IPs and they're (obviously) failing, that's a third bug :)

[retrohacker]

If you give me some code smells to follow, I can try and debug some of this stuff 😄

I'm trying to glue this work to https://github.com/creationix/js-git/ for github-pages style hosting over bitorrent in the browser.

[retrohacker]

I'm going to try running the daemon locally to see what IP addresses it pulls.

[cjb]

Ahh that is SO COOL

[cjb]

I haven't had any more ideas on this, just wanted to mention that the 10.* is a red herring -- you do find one peer, the 192.34.86.36:30000, and that should be good enough. So the real question is why the bittorrent-protocol handshaking doesn't end up doing a download. (Any chance your network blocks BT somehow?)

[retrohacker]

Ah, you are right.

I'm pretty sure that my network is doing something weird somewhere. I can download torrents via gtk-transmission but I can't get the webtorrent cli tool to work (assuming over TCP/UDP).

Even stranger is that instant.io does work (over webrtc).

I'm triaging the issue with webtorrent now 😄 Will document my findings.