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 over time, 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.
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.
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.
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 over time, 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.