Tangent but wow codeberg is not blocked by the Great Firewall?

I love this as a concept. The wander button is great, but it still needs some curating to decide what pages you like, and getting to the actual content. I guess I'd like to know the workflow moving forward? Just re-download the repo every couple weeks, and diff to see what new sites are on the list?

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 ask me again.

There is no need to re-download https://codeberg.org/susam/wander every few weeks. The setup is a one-time step. 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.

I want to like it, but I don't fully understand why one wouldn't just put a bunch of links on a /wander page and maybe randomize the order?

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 these and present them 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.

Because the discovery is transitive. When you wander, it fetches another console's wander.js and picks from their pages, so you're not just exploring one person's list, you're hopping across a graph of curated lists. A static link page can't necessarily do that.

We're inventing stumbleupon from first principles.

That... seems like a good thing!

This is really cool, I think the idea here is fantastic!

Awesome it’s hosted on codeberg too

Earlier from the dev: https://news.ycombinator.com/item?id=47422759

So like StumbleUpon

I don't know how useful this is, but I am getting tired of Google and co ruining the world wide web how it once was. Something has to be done. I have no idea whether this here can be of help or not but the more people think about this, the better. Otherwise the quality will continue to degrade.

Looks cool. Good job!

This will get really fun when influencers get a hold of the idea and start connecting themselves into the Wander community.

Cool idea - it’s like a recommended set of links, but integrated into an interface like stumble upon or Kagi’s small web browser