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.

> 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!

> I get that, but right now, if you traverse each "console", you end up with a list of 28 trusted "small web" links. The project grows in value if that list gets bigger over time either by you personally adding nodes or the community adding nodes.

Yes, all of this makes sense.

> I don't really have a way of knowing if you are intending to add more links to your console (thus growing the project) or this is a one and done type of system.

I personally do not plan to add too many page links to my console. However, I will add more console links, which has the effect of expanding my console neighbourhood and thereby increasing the pool of recommendations.

That said, I am not sure why it matters whether I add more links to my console specifically. In my opinion, any single Wander instance should not matter much on its own. What matters more is whether the network as a whole grows, that is, more consoles being set up and more of them linking to each other.

One of my design goals has been to avoid giving any particular console a special status. All consoles are equal participants in the network from a technical perspective. You should be able to pick any console from the network, perhaps one belonging to your favourite blogger, perhaps even your own and explore the neighbourhood from there. Yes, the neighbourhood would look different from each console but that's pretty much the point of this project. As long as the overall graph of consoles is connected, you could in theory reach any community recommendation from any starting point. Even if the graph is not fully connected, I do not see that as a significant issue. It just reflects how connections tend to form in a decentralised system. Please let me know if you think I have missed your point again.

What you are describing sounds a bit like a blogroll, which many of us do indeed maintain. Mine is here, by the way: https://susam.net/roll.html

However, Wander is meant to be a bit like StumbleUpon, but without requiring a centralised service that everyone must go through. One limitation of a blogroll is that it does not provide a consistent way to discover recommendations recursively. For example, I might visit your website A, which recommends website B. I might then visit B, but B may not have any recommendations at all.

Every Wander instance, on the other hand, has a defined list of recommendations. It also links to the /wander pages of its neighbouring sites. If you visit the /wander page of website A, the tool can discover its neighbours (B, C, etc.), then the neighbours of those neighbours and so on. It can fetch recommended links from them and present the links within the same console.

Additionally, the tool provides a way to leave the current console and move to a neighbour's console if the visitor wants to continue browsing from there.

Thank you for taking a look at this project. I'm glad you like the concept. I am not sure I have understood your question accurately, but let me attempt a response anyway. If I get it wrong, please feel free to correct me or ask me again.

There is no need to re-download https://codeberg.org/susam/wander every few weeks. The setup is a one-time activity. From that repository, you copy exactly two files (index.html and wander.js) and place them on your web server, preferably within a /wander/ directory. After that, you only maintain the wander.js file.

You curate your own links and choose which other Wander consoles to link to as neighbours. The contents of wander.js are entirely yours to define. There is no need to diff or compare it with the version in the repository.

In fact, if you do not care about updating or curating links often, you can leave both files untouched indefinitely. The only downside is that some links may eventually succumb to link rot, which could affect the wandering experience. So it may help to review your links occasionally and remove dead ones, but beyond that no ongoing maintenance is required.

Hello HN!

This tool is inspired by Kagi Small Web (recent thread: https://news.ycombinator.com/item?id=47410542). A common concern raised here is that Kagi Small Web currently accepts only blogs, comics and YouTube channels. It does not accept arbitrary small websites. That limitation motivated me to build Wander.

Wander is fully decentralised. Anyone can host it on their own website. It consists of just two files: an `index.html` for the Wander console and a `wander.js` where you link to other Wander consoles. It is a bit like a webring, but more flexible. Each console can link to any number of sites and other consoles.

There is no server-side code, no database, nothing to install. If you have a website, you can set it up by uploading just two files. In fact, you can host it on GitHub Pages or Codeberg Pages too.

If you like the idea, please join the network. I would love to see it grow.

More details about how it works and how to set it up here: https://codeberg.org/susam/wander#readme