rns.recipes

Hello everyone,

First, I would like to say thank you for such an amazingly well architected mesh solution. I've known about reticulum for years and even used parts of the projects design in other systems I've worked on. But now I'm here. I want to show off a couple of projects and ask for help and advice. I've been thus far disconnected from the community, but I've decided to put it all out there. I've created several projects that are now available on GitHub which maybe are not necessary or duplicate work and if so I apologize.

First off is on I do know steps on another project, and I don't want to be divisive here and my work will be fully FOSS and I'll explain the difference.

My goal has not been to make reticulum usable but to give it use. I think many people far smarter than me have the latter covered.

1. Beacon is a mesh search engine and crawler solution that use a wide variety of factors to rank content. It crawls every page and is accompanied by a small project link removed by moderator which is a schema.org solution for nomadNet simply place the meshdata on the page in comments and beacon will find it. Beacon is heavily service enabled and can do math, give you the weather in the area, give you direction to a location including POI's, you local time, and your local news which it can filter by in the search along with shop listings that utilize the mesh data system. You can fingerprint with Beacon and if you do so you will get the weather, time and a link to your regional news on the home page and searches will be customized to you location (geographical results vastly improve experience) 7d6d19a43af9da25cb5eaeb0d45b90d8:/page/index.mu

2. RNS-WIKI is a small wrapper for kiwix it uses it uses Xapian index to perform a search and applies my Meshdata to the top then uses my solution [html2micron] link removed by moderator solution to convert the page in its page entirely. This is integrated into beacon and you will get relevant ranked wiki results alongside other micron pages on the mesh. af9186e72ae0f7b89c2f8a105da59dbe:/page/index.mu

3. RNS-NEWS (not ready for publishing) This is what it sounds like, and it pulls down feeds from non-profit news sources right now its handling a limited set of news and will localize news for your area. It works great but before I can publish it needs some tweaking and sanitization as well as some evaluation. For now, though its fully hosted on the mesh. You can get your news from beacon especially works well if you share you zip code. or from rns-news directly. fbe7813b26a8858d552b10cd577abdcf:/page/index.mu

4. RNS-WEATHER link removed by moderator This is a fairly simple system that can give you the weather in any location in the US (sorry my international comrades SOON I could use partner I've build a LXMPeers exportable library and its possible we could build a peered network for such things that would be amazing it applies to most of these). This is fairly simple it hits the NWS for a location and provides it to the end user I don't ask for the exact location so its approximate down to the zip code. It is also accompanied by RNS-ALERTS which reads the RNS alerts and will notify you via LXMF message of weather warnings if you choose to register with it.

link removed by moderator

5. RNS-GEO You have heard me talk a lot about location here and this is how I accomplish that location on of the largest costs in my network is my geolocation solution which takes quite a bit to server (I also serve my own offline maps) this is a memory hog but its one of the central systems that makes this all possible. many of these systems I have mentioned yet adopt my OpenAPI equivalent standard for Reticulum and Micron MeshAPI. This is a way of describing an api as well as a way to test it exactly as it would be called. It considers FreeTakTeam's prior art in the field and respects it in its design. It does everything geocoding including PoI and Turn by Turn directions. Again I am sorry to my internation friends I simply do not have the ram and resources to serve the whole world. just to do the us takes a VERY large amount of RAM and unfortunately, I simply don't have enough to serve it all. You can access RNS-GEO at the moment the api is full public (I may have to rate limit if it gets really popular). e8e01ad8de6531f92b250ad1c5cc0cdf:/page/index.mu

6. RNS-TIME I operate my own ntp-server that does operate on the open pool. For off-grid systems some may not be aware just how critical something like this is. While mine it working on some hardening (solar backup for hardcover, full ribidium clock, and clock ensemble) its very solid built on open-timecard https://ntp.quasarke.net/. I created a small tool meshtunnel That bridges my ntp server to a hash on the mesh and a mesh-launcher these can be used for any service and are fully configurable. The meshtunnel converts an identity to a synthetic ip address and can can as a bridge between any service and the mesh. The launcher is also configurable and can bind any host address (essentially a host file without editing a host file) to a mesh hash. doing this you can provide any service over the mesh to a windows or linux machine including ntp services like a do here. As far as I know this is the first true NTP provider over reticulum. But I'm new here. 0d83fb01b73384d063dc61e2dff97af6:/page/index.mu

7. RNS-SHOP An ecommerce store integration it preset your meshdata has a backend browser dashboard and integrates with medusa and squarespace as well as being managable solo. its payment system at the moment can handle invoice, monero, and really anything else via link in LXMF (square, stripe, etc) it integrates with beacon and will list for sale items in the shop section linking straight to the purchasable item. full demo here 7a3b649379c6cc71ac0e7a75b6f38d52:/page/index.mu

AND THAT BRINGS ME TO MY FAVORITE THING ON THIS LIST BY FAR!

8. RNS-EVERQUEST (A slight modified meshtunnel not ready for public consumption) - Everquest was born in the 56k modem days and while my current version is actually prolly not the best version for this (mainly cause the client is huge 7GB). This is a mesh hosted everquest world server. My version has some extended features to further optimize the traffic and my benchmarks right now are theoretical. What I can say is the tunnel works perfectly. I have built a custom launcher for windows and linux (linux uses a proton wrapper). traffic for this system is optimized by a trained zstd compression to further compress those packets as small as possible. When the launcher downloads it asks for a mesh configuration, checks for the game client if it doesn't exist IT DOWNLOADS IT OVER A TORRENT 7GB unfortunately is just to much for reticulum as far as I know (which is why I may move to an older instance of EQ and repack an older game client). Once the client is downloaded it will decompress the ZSTD (goes up to 9GB) it will ask you if it can seed the client for others if your willing. The client is preset up to run over my clear net host but if the launcher is running it will route that traffic over reticulum. link removed by moderator

9. RNS-RESOLVE Ok this is both a demo and a proposal for me this is the big one I hope you consider or have already resolved(heh). RNS-RESOLVE is a human readable name resolver. I've read through quite a bit and I came across this (GITHUB DISCUSSION)[https://github.com/markqvist/Reticulum/discussions/965] regarding dns for reticulum design markqvists rnir design is sensible but loose and I though through my own requirements and considered so many lanes most of them hacky and many not quite feasible. What I landed on was an implementation that is minimal and utilizes existing patterns but I could never avoid client modification but I think I was able to make it entirely ad-hoc for the mesh overall. So here is what I landed on. A node with a has like any other using an extracted version of LXMPeers and LXMRouting (I provided a GAP document to show what I left out and why some are open questions ) importing LXStamp to produce a Name Resolver that ties identities to "pet names" used by the existing resolver and uses the trust on first use pattern. I found the draft-lenders-dns-cbor RFC-1053 proposal I was first looking at replicating clear net dns but then I realized the IETF prolly had treasure here since I imagine it's hard to get anything into this standard due to consistency needs and I found https://datatracker.ietf.org/doc/draft-lenders-dns-cbor/
   You can find it at *3435a207cc2d43cd7ea979e78e89dc16:/page/index.mu *

https://rns.recipes/forum/showcase/rules-and-requirements-for-llmai-assisted-projects

Half of these repos (all LLM generated) aren't even a day old.

render: drop em-dash from the MeshAPI footer (no-em-dash house style)

lol.