.. meta:: :description: The deeper challenges behind FeedbackFlow --- free speech vs privacy, radical transparency, the Gordian Knot of theodiversity, and why feedback is harder than it looks. :keywords: FeedbackFlow, philosophy, free speech, privacy, transparency, Gordian Knot, theodiversity, feedback ********************************************************************** FeedbackFlow Philosophy: The Hard Problems ********************************************************************** The :doc:`FF System Design ` documents how FeedbackFlow works. This page documents *why it is hard* --- the conceptual, ethical, and structural challenges that any serious feedback system must face. The Gordian Knot of theodiversity ==================================== The problem LLoL is addressing, at its core, is a hairball as complex as the proverbial Gordian Knot, where everything is connected to everything and cutting links can destroy everything. This website is about offering diverse ways of easing access into this hairball of "theodiversity", where everyone is fighting for a different god or idol. By definition, everyone has to find their own individualized way into grasping this core. That means feedback about any single page potentially touches every other page. A suggestion to simplify one explanation may break the connection to another. An improvement for beginners may obscure a point that experts need. Every edit is a tug on a web of interconnected ideas. This is why FeedbackFlow asks contributors to target the most specific page for their topic, and why the "See also on Balospe.com" links on each page matter: they help contributors find the right thread to pull without accidentally unraveling something elsewhere. The three "overs" to avoid ============================ When providing feedback on a system this interconnected, three failure modes are especially common: - **Oversimplifying** --- cutting complexity that is load-bearing. If an explanation seems unnecessarily complicated, it may be because the underlying reality *is* complicated and the current formulation is the least complex version that still holds. - **Overcomplicating** --- adding complexity where simplicity would serve. Not every nuance needs to be on every page. Some refinements belong deeper in the site, not at the surface. - **Overreaching** --- proposing changes whose consequences extend far beyond the page in question. A small editorial fix is easy to integrate; a restructuring of the entire argument requires understanding the whole knot. You can help by reducing all three in your FF. The best feedback is scoped clearly: it says what it sees, where it sees it, and why it matters --- without trying to redesign the whole system in one email. A hard human rights problem ================================ Organizing FeedbackFlows in a gentle kind reasonable way is a hard computational and conceptual problem that touches the core of humanity. This is because it operates in an area with unavoidable tensions between reasonable rights to free speech and reasonable rights to privacy. These questions are complex, and LLoL does not currently have the review capabilities to even define what the best policies might look like. That is a question for ResearchCity, once it has the scale and the diverse expertise to address it properly. In the meantime, a minimalistic approach is in effect: all FF submissions are treated as public domain under the :doc:`Jonah License ` unless the contributor requests otherwise. This is not ideal --- it is the simplest thing that is not obviously wrong. LLoL's radical transparency experiment ========================================== For now LLoL can only resolve this problem at scale by completely waiving forever all rights to his own personal privacy, dignity, etc. to ensure that nobody needs to be afraid of telling the truth as it is about whatever it is that needs to be said about his ResearchCity vision. If prior experience on the web is any indication, this may invite a firestorm of libel as well by all who wish to oppose LLoL's initiative. LLoL trusts that eventually the truth will win and that the self-stabilizing versioning system that he has been developing will help to sort it all out before it is too late. You can help by focussing your FeedbackFlow on the truth of whatever may matter most as best as you can tell. Mathematical theology can prove that Truth is LLoL's worst enemy and he has made peace with that. So, please do not self-censor what matters most in Reality. Only remember that Reality is also gracious. Why this radical approach? It is currently unclear how to resolve this tension between open access and privacy. LLoL intends to explore it by diving in head first. From his own experience in developing complex systems, he concluded that there is no way to develop a gentle kind reasonable solution to this hard problem without first hand experience of worst excesses by someone who is capable of finding a solution. Hence, turning one of his worst fears ("to become a fully transparent citizen") into a baseline, he hopes to find a gentle kind reasonable solution that is worth adapting as a global standard for his Evolvix computer language design effort. To LLoL's knowledge, nobody so far has dared such a radical experiment in full transparency, at least nobody with serious aspirations to a global leadership role. So, people of Earth, if you wish for more transparency in global leadership, here is your opportunity to :doc:`buy in by helping to scale up ResearchCity `. .. ----- FOOTER FORM OOv1r2p1 ----- type open-std ----- START ----- .. |content-vvn| replace:: dv_Auto_MMv1_2026m03d31 .. include:: /_templates/include-file/footer/separator/tidal-gradient.rst .. dropdown:: Notes :class-container: page-footer-form-notes :class-title: page-footer-form-title .. include:: /_templates/include-file/footer/page-footer-stability.rst .. dropdown:: See also on Balospe.com :open: :class-container: page-footer-form-refs-internal :class-title: page-footer-form-title - :doc:`/ff/index` --- how to use FeedbackFlow - :doc:`/ff/system/index` --- technical system design - :doc:`/ff/contact/index` --- preconfigured contact links - :doc:`/legal/index` --- privacy policy and terms of use - :doc:`/buy-in/index` --- fund ResearchCity .. only:: html .. include:: /_templates/include-file/footer/cta/researchcity.rst .. dropdown:: FF FeedbackFlow to improve this page: How you can contribute :class-container: page-footer-form-feedbackflow :class-title: page-footer-form-title .. include:: /_templates/include-file/footer/form-open-std/prelink.rst .. ----- PAGE-SPECIFIC FF (ff-email OOv1r2) ----- START ----- .. raw:: html To: FF+ff-philosophy@balospe.com CC: FF+CompleteFeedbackFlow@balospe.com Subject: FF k2 s2 AIMS for [ff-philosophy] Replace_by_OneLineSummary Body: To make this page [ff-philosophy] more gentle kind reasonable for beginners, producers, andOr experts with a background in xyz: Please consider improving this: .. ----- PAGE-SPECIFIC FF ----- END ----- .. include:: /_templates/include-file/footer/form-open-std/postlink.rst .. ----- FOOTER FORM OOv1r2p1 ----- END -----