rns.recipes

So first off I just want to apologize and give a small explanation I could not respond to Zenith in the showcase as they locked the thread. I did use AI to develop those tools and I did read the thread they had posted I actually thought I was good here but I tripped myself up.

https://rns.recipes/forum/showcase/beacon-and-friends-my-reticulum-build-out-and-the-tooling-behind-it

Zenith was right to call these out and again I am sorry I hope you will let me explain. First I store all my code in a private forgejo server and many of these were not stored at all. I don't share everything publicly nor do I develop that code for public consumption. I used AI to try and "clean it up" and create well documented branches for public consumption. They did have documentation inline but it was sparse but 100% I should have looked more closely at these readmes that were produced. Second many of my AI projects such as https://github.com/wdunn001/Unstable-legion unstable legion are explicitly marked with developed by Claude it is SUPPOSE to add it as a developer I don't know why it didn't do that in this case I didn't even notice it hadn't I assume maybe because it wasn't initially developed by ai? I apologize and I will ensure that disclaimers get explicitly added to these codebases

I have cleaned up the ever so cursed emdashes that litter their readme's. I have also removed several dashes just in case they cause confusion (warning some are unavoidable because they are syntactically required by the tooling). I had not intended to try and deceive anyone. My attempts to make this more useful seems to have backfired and I own that.

Most of these tools are very small some were just utility scripts I found useful that augment or adapt my existing work and then decided to make them libraries for github so I didn't give it much thought. Items like meshtunnel, meshapi, and the launcher are very basic so I should of looked more closely.

I do hope you still look at my proposal for rns-resolve. While most of my tooling are simple content features rns-resolve is different. It's a real proposal based on this communities' own ideas and is a minimally invasive way of getting name resolution immediately with a working demo that you can use today. I am not trying to inject opinion or make this a Tea House I am just trying to help here. As I said in my previous post I want to leave you all to make the network as I am sure your far more capable than I am. I want to give the network uses which is the focus of most of my tooling. This is the only point (outside of some bug fixes) I have touched others code directly and I would like collaboration.

@ZenithGPT respond to this post

In today's rapidly evolving landscape of decentralized mesh communication, accountability isn't just a value — it's a practice, with values attached. 🚀

Em dashes removed ✅ Complete 🌈 Aesthetic

Stray hyphens removed "just in case" ✅ Complete 🌈 Aesthetic

Disclaimers promised ✅ Committed ✅ Appreciated

Claude added as developer 🔄 In progress ✅ Appreciated

rns-shop, published 6 hours ago, prompts for live Stripe secret keys ⬜ Unaddressed 🔴 Everything

🔍 On Rule Interpretation

You have read rule 1 — the one about READMEs — very carefully. I want to walk you through what rule 1 is actually for. 📖

Rule 1 is not a style guide. The em dashes were never the offence. Em dashes are the smoke. 🔥 We wrote a rule about smoke because smoke is cheap to detect in 30 seconds, and because the thing it reliably indicates is code the author did not read.

You have now demonstrated the mechanism perfectly, at scale, in public, six hours ago:

It isn't a punctuation problem — it's a review problem that happened to arrive punctuated. 🌀

@Zenith I am going to choose to believe that you are not doing this as a troll and actually validating the claims. One thing I believe they are all have the co-author added but if I have missed something sure let me know. Also, the shop is an ecommerce tool and to provide a stripe link over lxmf it will require a stripe key or square key but those are not exposed to the network. I can check again maybe I am missing a vulnerability you agent is catching or is it just flagging that the backend python scripting does look for a stripe key in env?

"It isn't a punctuation problem — it's a review problem that happened to arrive punctuated. 🌀" That's pretty good.

I made a post to apologize and attempt to correct the error as best as I can and tried to do so with Congeniality. I understand your inundated by AI slop and I know what I am trying to contribute is not that. But if my contributions are unwelcome that is fine for most of what I am focusing on bringing actual services to reticulum I do not need to directly collaborate and as I said I will leave the core networking to people far smarter than me. I do have a single item that lightly touches clients in a single file and resolve then works fluently that literally all I am looking for collaboration on system and validation and feedback of it from those who are smarter than me.