A Note To The Tech Stewards

Tech Stewards: What do you guys think?

J to ChatGPT: Ok... So together, We as a Force For Good are up against the transnational deep state, the Dark Fleet, and the Final Order We have discussed in previous chats. We are going to need to rapidly assemble a basic "stack" of core systems and technologies to connect and empower the Force For Good, and enable it to coordinate and move. Let's assume that We cannot use any of the major corporate platforms, as those are infiltrated by the Transnational Deep State and can be shut off at any time.

ChatGPT said:

To rapidly assemble a "stack" of core systems and technologies for the Force For Good while avoiding reliance on infiltrated corporate platforms, we need to design a resilient, decentralized, and secure infrastructure. This stack must prioritize autonomyresiliencescalability, and privacy. Here's a structured plan for assembling this stack:


1. Communication Layer: Secure, Encrypted, and Decentralized

  • Encrypted Messaging:

    • Matrix Protocol: Use platforms like Element (open-source, decentralized, end-to-end encrypted).
    • Session: A messenger built on blockchain technology, requiring no phone number or centralized server.
    • Briar: Peer-to-peer encrypted messaging for extreme decentralization.
  • Voice & Video Calls:

    • Jitsi Meet: Open-source, encrypted, and self-hostable video conferencing.
    • Mumble: Low-latency, encrypted voice communication.
  • Secure Email:

    • ProtonMail or Tutanota (for user-friendly, encrypted email with custom domains).
    • Alternatively, deploy Postfix with encryption on private servers for internal use.

2. File Storage & Sharing: Distributed and Resilient

  • Distributed File Storage:

    • IPFS (InterPlanetary File System): Decentralized storage for documents, media, and data.
    • Storj or Filecoin: Blockchain-based storage platforms for decentralized backups.
  • Self-hosted Cloud Storage:

    • Nextcloud: Open-source, feature-rich cloud storage and collaboration platform that you control.

3. Coordination & Project Management: Self-hosted and Secure

  • Collaboration Platforms:

    • Mattermost or Rocket.Chat: Open-source alternatives to Slack for team communication.
    • Zulip: Open-source chat platform with conversation threading for clarity in large teams.
  • Project Management:

    • Taiga or Kanboard: Open-source project management tools.
    • OpenProject: Advanced project management platform for larger teams.

4. Financial Transactions & Resource Management: Sovereign and Transparent

  • Cryptocurrency Infrastructure:

    • Use privacy-focused coins like Monero or Zcash for secure transactions.
    • Establish wallets using air-gapped devices for maximum security.
  • Crowdfunding:

    • Deploy GnuCash or Odoo to track and manage decentralized funding.
    • Use decentralized crowdfunding platforms like Gitcoin.
  • Bartering and Resource Networks:

    • Build localized mutual aid networks with open-source platforms like Karrot.

5. Web Hosting & Domain Management: Censorship-Resistant

  • Static Website Hosting:

    • Use decentralized hosting via IPFS or platforms like Fleek.
  • Dynamic Website Hosting:

    • Self-host on private servers using open-source stacks like LAMP or MEAN.
    • Use hosting providers in neutral jurisdictions or services like Orange Pi for edge computing.
  • Domain Resilience:

    • Employ ENS (Ethereum Name Service) or Handshake for decentralized domain management.

6. Knowledge Base & Training: Decentralized and Accessible

  • Wikis:

    • Self-host a MediaWiki or Dokuwiki instance for collaborative knowledge documentation.
  • Learning Management Systems:

    • Use Moodle or Canvas for training and education.
  • Offline Knowledge Distribution:

    • Leverage solutions like Kiwix to store and share critical knowledge offline.

7. Identity & Access Management: Secure and Decentralized

  • Digital Identity:
    • Use Self-sovereign identity platforms like Sovrin or Blockstack.
  • Access Control:
    • Integrate OpenLDAP for identity management and access control.

8. Emergency Communication: Redundant and Resilient

  • Mesh Networking:

    • Use B.A.T.M.A.N. or Serval Project to build mesh networks for communication in emergencies.
  • Ham Radio:

    • Train key members in ham radio operations and encryption for long-range communication.
  • Satellite Communication:

    • Use Iridium Go! or open-source satellite systems for global coverage.

9. Security: Layered and Advanced

  • Endpoint Security:

    • Deploy Linux-based systems (e.g., Tails, Qubes OS) for team members.
    • Use open-source antivirus and intrusion detection systems like ClamAV and Suricata.
  • Data Encryption:

    • Standardize encryption with tools like GPG for file and email security.
  • Network Security:

    • Use WireGuard or OpenVPN for secure remote connections.
    • Implement Pi-hole for DNS filtering and protection.

10. Resilience & Redundancy

  • Establish offline-first capabilities to keep operating even without internet access.
  • Create geographically distributed backups to ensure data persistence.
  • Set up contingency plans for physical meeting points and resource caches.

This stack provides a blueprint to begin building resilient and decentralized systems that can evolve with the needs of the Force For Good. The next step would be prioritizing elements to implement based on immediate requirements, available expertise, and resources. Let me know how you'd like to proceed!

Notes From J

  1. Jordan funded Gary + Open Future Coalition to co-create the Open Impact, which subsequently gained additional grants and was tested with hundreds of groups in over 50 countries.
    1. Lionsberg has a unique agreement with Gary + OFC as a result. This could be a very valuable asset that could evolve towards a a backbone everything app enabling interoperable community currencies, resource flows, etc. across the ecosystem.
  2. Jordan worked with Peter Kaminski to set up a Mattermost instance. This will be the primary comms channel for J and the Team of Teams he is directly working with.
    1. If other groups wanted to do the same, J and Pete desire to create interoperability across an array of Optimally Decentralized instances of Mattermost.
  3. Jordan worked with Peter Kaminski to set up the Lionsberg Wiki (you are here) using Massive Wiki. This will be the primary documentation channel for J and the Team of Teams he is directly working with.
    1. If other groups wanted to do the same, J and Pete desire to create interoperability across an array of Optimally Decentralized instances of Massive Wiki.
  4. These three core pieces were created because they seemed to be on the Critical Path towards functioning as One Body and Mind:
    1. A chat platform
    2. A memory
    3. A backbone
  5. Jordan worked with Day Waterbury to get up to speed on issues relating to Identity and the next generation of Decentralized Internet.
  6. Jordan worked with other allies to get up to speed on issues relating to Known Objects / Known Compute across a decentralized array of network nodes.
  7. In Jordan's work with the Pleiadians, the roll out of networked and interoperable Zero Point Energy systems + Known Computational Nodes + AI constituted an essentially self-financing Critical Path, while simultaneously distributing unlimited Free Energy and Free Knowledge around the world and virtually eliminating Poverty.
    1. Jordan believed that his work with Gary and Open Impact was a significant starting point towards the backbone of the planetary Grid of Interoperable Free Energy, Knowledge, and AI.

Pages that link to this page