.. meta:: :description: FeedbackFlow (FF) is a simple email-based feedback system for Balospe.com. Learn how to contribute ideas, what makes good feedback, and what to expect. :keywords: FeedbackFlow, FF, feedback, email, contribute, Balospe.com :author: Laurence Loewe of Laodicea :og:card:title: FeedbackFlow
How to Contribute Ideas :og:card:description: A simple email-based feedback system. No account needed. No database. No tracking. Just email. Click, write, send. .. title:: FeedbackFlow --- How to contribute ideas to this site ********************************************************************** FeedbackFlow ********************************************************************** What is FeedbackFlow? ====================== You may hold the key to improving a page or a broader aspect of this website for an important audience. How can you open that door? This website tries to pioneer a FeedbackFlow system, abbreviated as FF, that makes it easy to contribute by sending an email. Every page has a preconfigured email link at the bottom. Click it, write your thoughts, and send. That's it. No account needed. No database. No tracking. Just email. The current system is an early MockupModel --- only you can truly bring it alive by providing your feedback and :doc:`enabling appropriately transparent processing with your buy-in `. The FF links at the bottom of pages prefill subject and body with info on what page or topic this is about to help the site maintainers to better sort what you want to comment on in context, so everyone is on the same page to help better focus on the core feedback that matters most. You can adjust any of these before sending. How to use it ============== 1. Look for the **"FF FeedbackFlow to improve this page"** bar at the very bottom of any page on this site. 2. Click the mailto link presented on the most relevant page to open a pre-filled email. 3. Read the section below for what makes good feedback (i.e. feedback that serves gentle kind reasonableness for all). LLoL will only want to adopt feedback that improves the overall gentle kind reasonableness for everybody in the overall outcome. So if you can already tell that something is either not gentle or not kind or not reasonable from someone's point of view that you already know about, then please consider revising such feedback until all three wires of that life-trifecta are fully activated. Then proceed with submission. 4. Replace the placeholder texts in that email with details about your idea, question, or suggestion. Include whatever you think helps explain your case. 5. Send. That gets the process started. You may then get some emails to confirm that you indeed wish such feedback to be considered for making it public if selected. Then it depends on the FF load and the capacity for processing it how long it may take for it to show up. What makes good feedback? =========================== The best feedback is *gentle kind reasonable*: - **Gentle** --- written in a way that invites collaboration, not conflict. - **Kind** --- focused on improving the content for everyone. - **Reasonable** --- grounded in evidence, logic, or lived experience. Consider your audience: are you writing for beginners, producers, or experts? The email template invites you to specify this, which helps LLoL prioritize how to integrate your input. Important notes before you send ================================= .. admonition:: Please read before submitting :class: warning 1. **Public domain by default.** All FeedbackFlow emails are currently treated as public domain submissions under the :doc:`Jonah License `. Please don't include private information, information you don't have the rights to publish, or claims you don't stand by. 2. **Response times.** LLoL is one person working on a shoestring budget. He may not be able to respond to feedback quickly --- or at all --- especially during high-volume periods. Please be patient. 3. **Publish on your own site.** If you have a blog, website, or public platform, publish your response there, especially if you deem it important for your response to reach your preferred audience in time. Your audience already trusts you and your platform already has reach. Then please email LLoL the link via the most relevant FF-link so it can be referenced from the :doc:`FF Archive `. You keep full control of your content and license. This ensures your ideas are not lost if LLoL cannot integrate them in time. Adding a link to an external site is much easier than truly integrating a worthwhile deep critique. 4. **Include links.** If you have published your feedback elsewhere, include the URL in your email so it can be referenced. Other links to relevant sources are also appreciated to cut costs of checking your submission. 5. **No guarantee of publication.** Please note that any submissions whatsoever cannot be guaranteed to be processed, even if most important. They might get lost or overlooked when LLoL gets inundated. Thank you for your patience and long-suffering in getting your points across while LLoL tries to scale up a FeedbackFlow system that can handle what matters most to everybody. 6. **Help scale FF.** The capacity of responding to FF is limited, especially initially. Please consider contributing your $8 to help :doc:`fund ResearchCity ` for scaling up appropriate capabilities for processing and replying to FF. For the full :doc:`privacy policy and terms of use `, see the legal section. The MailForm OOv2r0p0 ======================== Every FF email is pre-filled with the following form. By sending the email with this form intact, the sender gives active consent for their submission to be treated as described. The current version is MailForm=OOv2r0p0: .. code-block:: text To: FF+{PAGE_SLUG}@balospe.com CC: FF+CompleteFeedbackFlow@balospe.com Subject: FF k2 s2 AIMS for [{PAGE_SLUG}] Replace_by_OneLineSummary Body: To make this page [{PAGE_SLUG}] more gentle kind reasonable for beginners, producers, andOr experts with a background in xyz: Please consider improving this: -- By sending this email, I agree that its content may be published under the Jonah License (balospe.com/en/license/joli/) unless I state otherwise above. MailForm=OOv2r0p0 **What the form fields mean:** - **To:** Routes to the page-specific FF inbox via the ``+`` syntax. - **CC:** Collects all FF in one stream for team review. - **Subject:** ``k2 s2`` are default AIMS codes for impact and urgency (see postlink below the form on each page). Replace the summary text. - **Body:** Replace placeholders (audience, background, suggestion) with your actual feedback above the ``--`` line. **What the legal footer means:** - **Public by default.** If you send the email as-is, your submission may be published under the :doc:`Jonah License `. - **Opt out above the line.** If you want your submission to remain private, write "PRIVATE" or equivalent clearly above the ``--`` line. - **You can edit or delete the footer.** It is your email. You are free to modify it. But without the footer, there is no consent on record, and LLoL may need to follow up to clarify before any content can be used. - **MailForm=OOv2r0p0** is the version of this email form. It helps track which terms were in effect when the email was sent. Learn more ============ .. toctree:: :maxdepth: 1 :hidden: contact/index archive/index philosophy/index system/index - :doc:`contact/index` --- preconfigured FeedbackFlow contact links. - :doc:`archive/index` --- public responses and how to contribute yours. - :doc:`philosophy/index` --- the Gordian Knot of theodiversity, radical transparency, and why feedback is harder than it looks. - :doc:`system/index` --- the technical design, rationale, and open questions behind the FF system. .. ----- 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/contact/index` --- preconfigured contact links - :doc:`/ff/philosophy/index` --- why feedback is harder than it looks - :doc:`/ff/system/index` --- design, AIMS classification, scaling roadmap - :doc:`/ff/archive/index` --- public responses archive - :doc:`/faq/index` --- frequently asked questions - :doc:`/buy-in/index` --- support this work .. 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 OOv1r2p1) ----- START ----- .. raw:: html To: FF+ff-guide@balospe.com CC: FF+CompleteFeedbackFlow@balospe.com Subject: FF k2 s2 AIMS for [ff-guide] Replace_by_OneLineSummary Body: To make this page [ff-guide] 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 -----