FeedbackFlow Archive

Coming soon

This archive is not yet active. When it is, selected confirmed public FeedbackFlow contributions will be collected here.

Why publish your response on your own site

The challenges documented on this site — from accidental nuclear winter to the broader crisis of existential threats — deserve public discussion far beyond what one person’s website can host.

If you are a blogger, journalist, researcher, influencer, or anyone with a public platform: publish your response on your own site. Your audience already trusts you. Your platform already has reach. A response on your own site does more for the common good than an email that sits in one person’s inbox.

You are free to respond under whatever license you choose. You do not need to use the Jonah License. You do not need to grant LLoL any rights to your content.

How to connect your public response to this site

After publishing your response, send a short FeedbackFlow email (using the most relevant FF mailto link on this site by navigating to the page you are responding to) containing:

1. The URL of your published response.

2. Which page on Balospe.com your response refers to.

3. A one-line summary of your main point.

That’s it. LLoL can then link to your response from this archive under the Jonah License — referencing your work without republishing it. Your content stays on your site, under your control, under your license.

This approach means:

• You keep full control of your content, presentation, and license.

• Your site gets the traffic from readers who follow the link.

• LLoL avoids liability for third-party content.

• The discussion scales across many platforms rather than bottlenecking through one.

For those without a public platform

If you don’t have your own website, your FeedbackFlow email is still valuable. Confirmed public contributions (those where you reply PUBLICIZE) may be included in this archive directly, once it is activated.

Until then, your feedback is received and will be processed as capacity allows. Please note that no submission — however important — is guaranteed to be read, published, or acted upon. LLoL is one person and may be overwhelmed.

Collapse all Expand all

Notes

Content stability — Content is variant dv_Auto_MMv1_2026m03d31 (see StayVS). Rebuilt 2026-09-17.

See also on Balospe.com

• FeedbackFlow — how to use FeedbackFlow

• FeedbackFlow Contacts — preconfigured contact links

• The Jonah License: JoLi — Jonah License

Epic Fury to Epic Empathy: Fund a ResearchCity for Mathematical Theology

For millennia, Jews, Christians, Muslims, and others have fought wars — and fueled apocalyptic fears — over theological questions that none of them could state precisely enough to resolve. Mathematical theology offers a way out: translate the claims into formal axioms, check them for consistency, and discover where traditions actually agree once ambiguity is removed.

First explorations reveal a striking result: all three Abrahamic scriptures converge on the same pan-en-theistic structure when mapped to formal axioms. If that convergence holds under rigorous scrutiny, it can defuse centuries of eschatological conflict by showing that many disagreements are verbal, not logical.

But this work requires global support to avoid capture by special interests. Refining axioms, engaging scholars across traditions, and running formal consistency checks all require sustained effort — as does real-world testing of what matheology discovers.

If you believe replacing eschatological warfare with mathematical clarity is worth pursuing before it’s too late, please fund this work — every contribution helps evolve a global ResearchCity for finding the narrow path to peace.

FF FeedbackFlow to improve this page: How you can contribute

For the full guide on providing feedback — including how it is handled, licensing, and what to expect — see How to use FeedbackFlow.

Please check if See also on Balospe.com above already addresses your idea. Feedback works best when it targets the most specific page. If none of those pages help, you may have a good case for sending FF here.

To submit your FeedbackFlow:

1. Click anywhere on the email preview below to open a pre-filled email.

2. Replace the placeholder text with your feedback.

3. Send.

To: [email protected] CC: [email protected] Subject: FF k2 s2 AIMS for [ff-archive] Replace_by_OneLineSummary Body: To make this page [ff-archive] more gentle kind reasonable for beginners, producers, andOr experts with a background in xyz: Please consider improving this:

The email subject contains k2 and s2 — default codes for impact and urgency. Most contributors can leave these unchanged. To adjust each as independently as they are:

• Importance of impact: above average k3, average default k2, below average k1.

• Urgency of speedup: above average s3, average default s2, below average s1.

This allows plotting importance over urgency to help triage FF. For more details see FF System Design.