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?
Wander – A tiny, decentralised tool to explore the small web
21–30 of 103 posts
Re: Wander – A tiny, decentralised tool to explore the small web
#22Re: Wander – A tiny, decentralised tool to explore the small web
#23Re: Wander – A tiny, decentralised tool to explore the small web
#24Re: Wander – A tiny, decentralised tool to explore the small web
#25Re: Wander – A tiny, decentralised tool to explore the small web
#26Re: Wander – A tiny, decentralised tool to explore the small web
#27Re: Wander – A tiny, decentralised tool to explore the small web
#28So is this web rings all over again?
Re: Wander – A tiny, decentralised tool to explore the small web
#29I 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?
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.
Re: Wander – A tiny, decentralised tool to explore the small web
#30I 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?
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.