Fixed outdated meta-docs

Contributing.md

@@ -2,57 +2,53 @@
 
 Welcome, and thank you for your interest in contributing to Reticulum!
 
-Apart from writing code, there are many ways in which you can contribute. Before interacting with this community, read these short and simple guidelines.
+Before interacting with this community, read these short and simple guidelines.
+
+If you didn't shit your pants after reading this document, you may well find that we are all really quite cuddly and nice to be around. Mostly.
 
 ## Expected Conduct
 
-First and foremost, there is one simple requirement for taking part in this community: While we primarily interact virtually, your actions matter and have real consequences. Therefore: **Act like a responsible, civilized person** - especially in the face of disputes and heated disagreements. Speak your mind here; discussions are welcome. Just do so in the spirit of being face-to-face with everyone else. Thank you.
+First and foremost, there is one simple requirement for taking part in the development of this technology: While we primarily interact virtually, your actions matter and have real consequences. Therefore: **Act like a responsible, civilized person** - especially in the face of disputes and heated disagreements. Speak your mind here; discussions are welcome. Just do so in the spirit of being face-to-face with everyone else. Thank you.
 
-In order to keep the discussion forums and issue trackers navigable and useful, the following types of posts will be deleted without notice:
+In order to keep the discourse navigable and useful, the following types of posts and inquiries will be deleted and ignored:
 
 - Spam.
-- Questions that have already been adequately answered elsewhere. Use the search function.
-- Low-effort posts or comments that contain no actual information or useful content. This is not a tea-house.
+- Questions that have already been adequately answered elsewhere. Utilize search functions.
+- Low-effort posts or comments that contain no actual information or useful substance. [This is not a tea-house](./This Is Not a Teahouse.md).
 - Post or comments solely containing personal opinions or beliefs without adding anything to the discussion. Facebook and X exists.
 - Content that simply waste the developer's / maintainer's time with completely obvious "ideas", "insights" or "recommendations". Yes, we have *at least* 8 neurons ourselves.
 - Posts that fail to understand that developing a highly complex software project with a very small amount of resources and people takes time. Imagining perfection on our behalf is useless.
 
-If you're new to the community and start out your engagement with any of the above transgressions, you will simply be banned without notice or explanation, and your post will be deleted.
+If you're new to the community and start out your engagement with any of the above transgressions, you will simply be banned permanently without notice or explanation, and any further communication from you will be ignored.
+
+Except for the case of real, well-grounded, clearly documented, human-written security advisories, technical investigations or bug reports, if your inquiry or communication is not attached to a Reticulum Identity, expect it to be ignored.
 
 If you find this "harsh", "unfair" or "unwelcoming", go somewhere else. This is not social club, but a work environment for the people contributing to the project.
 
-## Asking Questions
+## Reporting Bugs
 
-If you want to ask a question, **do not open an issue**. The issue tracker is used by people *working on Reticulum* to track bugs, issues and improvements. Instead, ask away on the [discussions](https://github.com/markqvist/Reticulum/discussions).
-
-Do not post feature requests or general ideas on the issue tracker, or in direct messages to the primary developers. You are much more likely to get a response and start a constructive discussion by posting your ideas in the public channels created for these purposes.
-
-## Reporting Issues
-
-If you have found a bug or issue in this project, please report it using the [issue tracker](https://github.com/markqvist/Reticulum/issues). Be sure to include details on how to reproduce the bug.
-
-Anything submitted to the issue tracker that does not follow these guidelines will be closed and removed without comments or explanation.
+If you have found a bug or issue in this project, please report it to the maintainer over LXMF, or if strictly not possible, over email. Detailed and serious bug reports can also be posted in the various on-network forums and RRC channels that the developers frequent. Due to the realities described in [This Is Not a Teahouse](./This Is Not a Teahouse.md), there is no way to report issues or request features over the internet.
 
 ## Writing Code
 
-If you are interested in contributing code, fixing open issues or adding features, please coordinate the effort with the maintainer or one of the main developers **before** submitting a pull request. Before deciding to contribute, it is also a good idea to ensure your efforts are in alignment with the [Roadmap](./Roadmap.md) and current development focus.
+Patches and code contributions are *generally* only welcomed from developers already known to the community, with a proven track-record of competence, skill, careful and considerate design and responsible conduct. If we do not know you yet, but you have created something that you believe lives up to such standards, we are eager to hear from you.
 
-Pull requests have a high chance of being accepted if they are:
+The current development priorities and work documents are not publicly available on the internet, but shared and coordinated directly between the developers over Reticulum itself, following the principles outlined in [Distributed Development](https://reticulum.network/manual/distributed.html).
 
-- In alignment with the [Roadmap](./Roadmap.md) or solve an open issue or feature request
-- Sufficiently tested to work with all API functions, and pass the standard test suite
-- Functionally and conceptually complete and well-designed
-- Not simply formatting or code style changes
-- Well-documented
+## Machine Assistance & LLMs
 
-Even new ideas and proposals that have not been approved by a maintainer, or fall outside the established roadmap, are *occasionally* accepted - if they possess the remaining of the above qualities. If not, they will be closed and removed without comments or explanation.
+For a highly complex, critical piece of cryptographically based networking infrastructure, we should not need to state the following, but alas, experience has proven otherwise. Therefore:
 
-## Generative AI Policy
+**Including material generated using LLMs or other "AI" programs in Reticulum is, almost without exception, prohibited.**
 
-Contributions written using large language models (LLMs) or other generative 'AI' programs are prohibited. LLMs produce errors so frequently and in a way that is so unlike human error that such issues are incredibly time-consuming to spot and fix. This is not a worthwhile tradeoff for Reticulum.
+Before even *thinking* about using a generative software system to "create" something for Reticulum, read [Brandolini's Reference](https://reticulum.network/manual/brandolinis.html), in full. If you do not have the capacity for that, you have failed the first requirement for contributing: Basic literacy.
 
-This applies to all Reticulum-related projects and documentation, as well as all submitted issues and discussion in official channels, except in cases where language translation and/or speech recogntion technologies are required for communication.
+*If* you are not already a known contributor with a proven record of being able to responsibly handle these tools, a **full** audit trail of all ML-utilizing workflows, including prompts, LLM reasoning traces, tool calls and outputs (that is, the *entire*, unaltered session log) will need to be provided with any proposed contribution. Without that, we will not even *consider* looking at it.
+
+This applies to all Reticulum-related projects and documentation, as well as all submitted issues, reports and discussion, **except** of course in cases where language translation, speech recogntion, or other assistive technologies are required.
 
 ## Contributor License Agreement
 
 By contributing code to this project, you agree that copyright for the code is transferred to the Reticulum maintainers and that the code is irrevocably placed under the [Reticulum License](./LICENSE).
+
+For a more in-depth elaboration on the current CLA position, see [this post](https://rns.recipes/forum/general/brandolinis-reference-or-alternatively-agentsmd?page=1#post-3002).

Roadmap.md

@@ -1,94 +0,0 @@
-# Reticulum Development Roadmap
-This document outlines the currently established development roadmap for Reticulum.
-
-1. [Currently Active Work Areas](#currently-active-work-areas)
-2. [Primary Efforts](#primary-efforts)
-    - [Comprehensibility](#comprehensibility)
-    - [Universality](#universality)
-    - [Functionality](#functionality)
-    - [Usability & Utility](#usability--utility)
-    - [Interfaceability](#interfaceability)
-3. [Auxillary Efforts](#auxillary-efforts)
-4. [Release History](#release-history)
-
-## Currently Active Work Areas
-For each release cycle of Reticulum, improvements and additions from the five [Primary Efforts](#primary-efforts) are selected as active work areas, and can be expected to be included in the upcoming releases within that cycle. While not entirely set in stone for each release cycle, they serve as a pointer of what to expect in the near future.
-
-## Primary Efforts
-The development path for Reticulum is currently laid out in five distinct areas: *Comprehensibility*, *Universality*, *Functionality*, *Usability & Utility* and *Interfaceability*. Conceptualising the development of Reticulum into these areas serves to advance the implementation and work towards the Foundational Goals & Values of Reticulum.
-
-### Comprehensibility
-These efforts are aimed at improving the ease of which Reticulum is understood, and lowering the barrier to entry for people who wish to start building systems on Reticulum.
-
-- Improving [the manual](https://markqvist.github.io/Reticulum/manual/) with tutorials specifically for beginners
-- Updating the documentation to reflect recent changes and improvements
-    - Update descriptions of protocol mechanics
-        - Update announce description
-        - Add in-depth explanation of the IFAC system
-    - Software
-        - Update software descriptions and screenshots
-    - Communications hardware section
-        - Add information about RNode external displays.
-        - Possibly add other relevant types here as well.
-    - Setup *Best Practices For...* / *Installation Examples* section.
-        - Home or office (example)
-        - Vehicles (example)
-        - No-grid/solar/remote sites (example)
-
-### Universality
-These efforts seek to broaden the universality of the Reticulum software and hardware ecosystem by continously diversifying platform support, and by improving the overall availability and ease of deployment of the Reticulum stack.
-
-- Create a standalone RNS Daemon app for Android
-- A lightweight and portable C implementation for microcontrollers, µRNS
-- A portable, high-performance Reticulum implementation in C/C++, see [#21](https://github.com/markqvist/Reticulum/discussions/21)
-- Bindings for other programming languages
-
-### Functionality
-These efforts aim to expand and improve the core functionality and reliability of Reticulum.
-
-- Add interface hot-plug and live up/down control to running instances
-- Add automatic retries to all use cases of the `Request` API
-- Network-wide path balancing
-- Distributed Destination Naming System
-- Globally routable multicast
-- Destination proxying
-- [Metric-based path selection and multiple paths](https://github.com/markqvist/Reticulum/discussions/86)
-
-### Usability & Utility
-These efforts seek to make Reticulum easier to use and operate, and to expand the utility of the stack on deployed systems.
-
-- Easy way to share interface configurations, see [#19](https://github.com/markqvist/Reticulum/discussions/19)
-- Transit traffic display in `rnstatus`
-- `rnsconfig` utility
-
-### Interfaceability
-These efforts aim to expand the types of physical and virtual interfaces that Reticulum can natively use to transport data.
-
-- Plain ESP32 devices (ESP-Now, WiFi, Bluetooth, etc.)
-- More LoRa transceivers
-- AT-compatible modems
-- Filesystem interface
-- Direct SDR Support
-- Optical mediums
-- IR Transceivers
-- AWDL / OWL
-- HF Modems
-- GNU Radio
-- CAN-bus
-- Raw SPI
-- Raw i²c
-- MQTT
-- XBee
-- Tor
-
-## Auxillary Efforts
-The Reticulum ecosystem is enriched by several other software and hardware projects, and the support and improvement of these, in symbiosis with the core Reticulum project helps expand the reach and utility of Reticulum itself.
-
-This section lists, in no particular order, various important efforts that would be beneficial to the goals of Reticulum.
-
-- The [RNode](https://unsigned.io/rnode/) project
-    - [x] Create a WebUSB-based bootstrapping utility, and integrate this directly into the [RNode Bootstrap Console](#), both on-device, and on an Internet-reachable copy. This will make it much easier to create new RNodes for average users.
-
-## Release History
-
-Please see the [Changelog](./Changelog.md) for a complete release history and changelog of Reticulum.

SECURITY.md

@@ -0,0 +1,5 @@
+# Reporting Security Issues
+
+It goes without saying: If you have discovered a security issue in Reticulum or any related project, please report it responsibly to the maintainer over LXMF at `<8dd57a738226809646089335a6b03695>`. If you wish to remain anonymous, please create a disposable identity to send from, and notify us of any such wishes.
+
+If you are not able to use LXMF, you can send an email to the address currently posted on the maintainer's profile on this site.

This Is Not a Teahouse.md

@@ -2,7 +2,7 @@ Recently, and mostly from people who I've never seen before, the opinions about
 
 - The decision to no longer mirror release notes on GitHub.
 - Some people feeling there were too many "barriers to entry" to joining RNS development.
-- The project not really being "open source" because random strangers couldn't just "contribute".
+- The project not really being "[open source](https://reticulum.network/manual/brandolinis.html#open-source-means-open-source)" because random strangers couldn't just "contribute".
 
 Joakim posted some very relevant observations about how Reticulum operates, along with the following quote:
 
@@ -10,7 +10,7 @@ Joakim posted some very relevant observations about how Reticulum operates, alon
 
 That E. F. Schumacher quote perfectly illustrates the ontological schism that makes it so tiresome to deal with stuff like this.
 
-There is, in this day and age, between different people, widely different base conceptual integrations of what "open source" means. For many people, "open source" has become synonymous **not** with skilled people working together in a coordinated and careful way on complex engineering challenges, but a sort of growth- and attention-focused "free-for-all" *behavioral* codex that must be followed above all else; a *social* modus operandi of fake inclusivity where everyone "should have their voice heard", and adherence to that specific process is weighed much higher than the final results.
+There is, in this day and age, between different people, widely different base conceptual integrations of what "open source" means. For many people, "open source" has become synonymous **not** with skilled people working together in a coordinated and careful way on complex engineering challenges, but a sort of growth- and attention-focused "free-for-all" *behavioral* codex that must be followed above all else; a *social* modus operandi of fake inclusivity where everyone "should have their voice heard", and adherence to that specific *process* is weighed much higher than the final results.
 
 I do not subscribe to, and consequently do not operate the Reticulum project under *any* versions of that idea.
 
@@ -28,7 +28,7 @@ I do not subscribe to, and consequently do not operate the Reticulum project und
 
 Can you imagine how much time that wasted? Can you imagine what we could have accomplished with that time instead?
 
-The only thing that this creates is *noise* and confusion. Clogging up the mental and physical workspaces, of people who are actually investing time and effort on the project with stuff like that is objectively just taking time that could have been used on development, and replacing it with *nothing*.
+The only thing that this creates is *noise* and confusion. Clogging up the mental and physical workspaces, of people who are actually investing time and effort on the project, with stuff like that is objectively just taking time that could have been used on development, and replacing it with *nothing*.
 
 I was receiving *actual* bug reports, pull requests, proper technical investigations and patches via methods outside GitHub and "public" internet-based channels *way* before GitHub interaction and similar was closed down. That was were almost *all* of the real contributions were coming from, anyway. Apparently, and not unsurprisingly, the people who has invested the time and effort to understand Reticulum also prefer to collaborate in this way. Since leaving the GitHub madhouse behind, the signal-to-noise ratio has **significantly** increased.
 
@@ -46,7 +46,7 @@ When this pattern repeats, over and over, the only sensible, measured and constr
 
 So, now it's your turn. Go look at the diffs for the last six months. What does it look like I have been doing?
 
-But I will be damned straight with you all, and say that part of that solution is **absolutely** to erect barriers to entry. You can fucking bet your arse on that. I don't want opinionated man-babies running around in my living-room at 3am. I don't want to clean up the floor after a wannabe "dev-ops stars" with LLMs and a peripheral case of influencitis has puked all over the office.
+But I will be damned straight with you all, and say that part of that solution is **absolutely** to erect barriers to entry. You can fucking bet your arse on that. I don't want opinionated man-babies running around in my living-room at 3am. I don't want to clean up the floor after a wannabe "dev-ops star" with LLMs and a peripheral case of influencitis has puked all over the office.
 
 - If you want to join the fun of changing core networking code that thousands of people rely on for communication
    daily, you better know what the fuck you're doing.

docs/source/support.rst

@@ -28,9 +28,6 @@ Donations are gratefully accepted via the following channels:
     Ko-Fi:
     https://ko-fi.com/markqvist
 
-Are certain features in the development roadmap are important to you or your
-organisation? Make them a reality quickly by sponsoring their implementation.
-
 .. raw:: latex
 
     \newpage