This allows the portals to connect way faster. In Portal.connect, when a connection succeeds, it still connects to the next portal after 250ms. But when a connection failed, rotonde now immediately tries connecting to the next portal in the queue.
Before this change, it already attempted doing the same, but failed due to the "time of last update" check in r.home.feed.next.
The timeouts are unchanged.
This helps greatly when you're following many portals.
Edit: I'm also smuggling a small fix for the : rune being used in entry headers even when no targets are given.
This allows the portals to connect way faster. In
Portal.connect
, when a connection succeeds, it still connects to the next portal after 250ms. But when a connection failed, rotonde now immediately tries connecting to the next portal in the queue.Before this change, it already attempted doing the same, but failed due to the "time of last update" check in
r.home.feed.next
.The timeouts are unchanged.
This helps greatly when you're following many portals.
Edit: I'm also smuggling a small fix for the
:
rune being used in entry headers even when no targets are given.