Glad you like it. Yes, you are right. This is something I realised too initially as a natural consequence of being the only participant in the console network at the beginning. Keeping a list of discovered consoles is exactly what I was thinking too. I built this tool rather quickly as a proof-of-concept while taking a break from another activity, so I couldn't quite find the time to implement this solution. But I might implement it in the next update. Thank you for taking a close look at this project!

> If that's not desirable, it could be avoided by having the client keep a running list of all the consoles it has discovered this session and choosing from that list at random.

Implemented in <https://codeberg.org/susam/wander/commit/f4d95fa>. Thanks again for the discussion!

It would be nice if it wasn’t so framed in. How about a simpler “wander” overlay button that stays fixed (a bit like google recaptcha in the bottom corner) and pops up the console with links?

You can do this via html/css without breaking the functionality.

To add to this fine suggestion, I'd like to highlight that Wander supports customising the appearance of the user interface.

The section https://codeberg.org/susam/wander#customise-your-console describes how someone setting their own /wander URL can customise how their console looks and behaves. I have seen a few consoles already using this feature to change their theme.

So while I will keep my console as it is, because that is how I prefer it, with large buttons occupying the full header width, others who prefer a different layout can do so by adding custom CSS as described in the link above.

Ah I see, I said nothing then :)