rns.recipes

Wondering if anything is planned for, or if someone has worked on this. The thought is if you find a nomad net page you like you would subscribe to it, this would download and host the page local, while also embedding original's address. When the original announces your local copy would update.

This would let popular pages organically jump networks and auto update as all subscribers would keep chain looking for original or newer versions from peers mirroring same origin.

The issue i see implementing this outside of rns core is flooding nomad net with mirrors. Would need feature network side to call mirrors or redirect to shortest leap or newest mirror.

Would end up being something like "beaker browser" project over rns.

meshchatx does this, archiving feature
also, why?
just favourite the page
or even do a partial

Following the network ethos of being self propagating. Say you find a library site, you mirror it, now you travel to a convention, go on vacation etc. Your mobile node is hosting that library as well so it can be discovered past its local network. Then when you return home it automatically updates. On your travels someone else subscribed and now that library lives there as well. If your paths pass again you pass along the latest version. So a yearly convention no is also updating libraries across bounds that may be blocked online, or if there is a massive infrastructure outage, or reticulum gets huge and people start exiting the current internet. Its like movies or books brought to a country with no official method of getting them, and then the locals make copies and distribute.

Everything non-trivial is not just a static page. A library loads book files and only displays the content of the current page or offers downloads for the files for example. A forum has a database behind it.

You could build a system on top of Reticulum with a different aspect and sync files over it. Independent of the nomadnetwork.

But high availability is not really my goal here.

adept wrote:

Everything non-trivial is not just a static page. A library loads book files and only displays the content of the current page or offers downloads for the files for example. A forum has a database behind it.

You could build a system on top of Reticulum with a different aspect and sync files over it. Independent of the nomadnetwork.

But high availability is not really my goal here.

It wouldn't make sense for an active forum, web app, chat room, directory etc. But libraries, static pages etc. Would be great. It would need to be an opt in, but also be supported widely which is why I ask here.

My initial thoughts on implementation is a browser with integrated editor and rngit. Any edit would create a commit, and subscribers would be cloning the site and rehosting. However ideally it would use nomadnet implementation for interoperability but this could cause other browsers without repo filtering to be flooded with mirrored sites and I want to avoid that outcome. Especially for Reticulum where hosting nodes could be down for prolonged periods or lost completely I think this would be great for preserving info and users.