Damus
Torlando · 27w
It's live in latest pre release
shortwavesurfer2009 profile picture
Well, it definitely works, but now I'm trying to figure out what indicates whether I'm going to have a good connection or not.

I've had nodes at two hops that load incredibly fast. I've had nodes at two hops that load incredibly slow or timeout. I've had nodes at four hops that load incredibly slow or timeout. And I've tried one node at six hops that did not load at all.

I am on a TCP interface.

I wonder if, for some reason, my propagation node has something to do with it. By default, when I first used the app, it chose a propagation node that was 4 hops away from me, and I manually set another propagation node that was only 2 hops away from me. But perhaps I should not have done so.

The reason I did so is because I figured fewer hops would mean better latency.
Torlando · 27w
I have noticed this too, even on other clients, but it does seem to happen more frequently with Columba. It seems related to path request. If you have heard a node announce since you started the app, and the node is still online, it always works from my experience. If you haven't heard an announce...