📁 Index of zosciibb

Name Last modified Size Description
Parent Directory--
messages.php2025-08-11 02:424.1K
messages/2025-08-05 10:17-
verifier.html2025-08-11 02:5144K
zosciibb.html2025-08-11 02:5119K

ZOSCII Bulletin Board

ZERO encryption ZERO ciphering 100% secure* communication system

100% disclosure - Complete transparency in operation

What is ZOSCII?

ZOSCII (Zero Overhead Secure Code Information Interchange) is an encoding system loosely based on ASCII, PETSCII and EBCDIC designed for the purpose of speeding up text output on 8-bit computers. ASCII and PETSCII which are common for 8-bit computers require that to output each character, you must first know the start of a table, and then for each character add the offset to find the one required. ZOSCII uses direct addresses treating the entire memory map of the 8-bit computer as the character lookup table. This means that to output text, there is no longer a requirement to add an offset. On a typical Z80 based computer this can give a 40% speed increase in character output. The Z80 is a CPU that was manufactured from July 1976 until June 2024 and is one of the most commonly used 8-bit CPUs in home computers and video game hardware among other uses. In addition to the added performance of character output, using the memory space as the actual character table means that no space within the actual ROM of the computer is required for such ASCII or PETSCII character tables, freeing up the space for better purposes.

A side effect of this approach is the discovery of a revolutionary new secure communication technique that achieves perfect information-theoretic security without any encryption or ciphering algorithms.

Instead of encrypting data, ZOSCII encodes messages as address sequences pointing to locations within a shared ROM (Read-Only Memory) file. Without the ROM, these addresses are completely meaningless. With the correct ROM, messages decode perfectly.

How It Works

🔑 Step 1: ROM Selection

Users select a ROM file (any binary file - image, document, etc.) that becomes their personal encoding key. This ROM is NOT uploaded to the server (unless legally compelled and potentially gagged) but is used only within your web browser.

📝 Step 2: Message Encoding

Messages are converted to sequences of addresses pointing to byte locations within the ROM.

📤 Step 3: Address Storage

Only the address sequences are uploaded and stored on the server - no actual message is ever sent to the server (unless legally compelled and potentially gagged).

🔍 Step 4: Message Decoding

Other users with the same ROM can utilise the addresses to read back the original message.

Security Features

✅ What Makes ZOSCII Secure
  • Information-theoretic security: Security is mathematically provable, not dependent on computational assumptions
  • No encryption algorithms: Nothing to break or compromise with quantum computing
  • Perfect forward secrecy: Each message uses randomly selected addresses from the ROM
  • Server breach protection: Even if servers are compromised, stored data remains meaningless without ROMs

The * in "100% secure*"

ROM Quality Requirements

ZOSCII's security depends on using a high-quality ROM file that contains sufficient character diversity. A ROM consisting of only zeros would provide no security at all.

Check your ROM quality using our verifier tool: verifier.html

Good ROM characteristics:

  • Contains all characters you plan to use in messages
  • Has multiple instances of common characters (letters, spaces, punctuation)
  • Sufficient size (recommended: 16KB or larger)
  • High entropy (random distribution of byte values)

What You See Here

This bulletin board demonstrates complete transparency:

📁 messages/

Browse all stored address files. Each file contains only address sequences - meaningless without the corresponding ROM.

📄 Source Code

View page source to see the complete JavaScript implementation. Zero minification, complete transparency.

Wrong ROM = Orwellian Quotes

When you use the wrong ROM, instead of showing gibberish, the system displays thought-provoking quotes about surveillance and privacy. This serves three purposes:

  • Maintains pagination: Consistent number of items per page
  • Appearance: Is much more attractive than gibberish. Occasionally, due to the way we detect gibberish for performance reasons, it can sometimes get through, but this is only due to our ability to hide meaningless secure information, not the combinatorial security provided. It simply means the ROM used was lucky enough to find printable characters.
  • Provides cover: Makes the system appear to be a discussion forum about privacy topics

Local Client Recommended

🛡️ Maximum Security with Local Client

For users requiring maximum security, we provide a local client that:

  • Processes ROMs entirely on your device
  • Never uploads ROM data to any server
  • Cannot be compromised by server-side attacks
  • Provides configurable server endpoints

Download: https://github.com/PrimalNinja/cyborgzoscii

Technical Documentation

For complete technical details, implementation specifications, and security analysis, refer to the ZOSCII whitepaper available in the GitHub repository.

Key Technical Points from the Whitepaper:

"ZOSCII achieves information-theoretic security by encoding messages as randomized address sequences within shared ROM files. Each character in a message is represented by a randomly selected address pointing to that character's location in the ROM."

"Unlike cryptographic systems that rely on computational complexity to encrypt a message that is still within the actual encrypted file and open to brute force attacks and even identification of the encryption being used in many cases, ZOSCII's security is absolute: without the ROM file, the address file contains no message or recoverable information regardless of available computational resources. This is simply a standard computer address lookup for which no mathematics are required."

Universal Communication Protocol

ZOSCII is designed as a universal communication protocol that bridges different computing eras and character encoding systems:

  • Platform Agnostic: Works on systems from 1980s CP/M to modern cloud platforms
  • Character Set Independent: Supports ASCII, EBCDIC, PETSCII, and custom encodings
  • Cross-Era Communication: Enables secure communication between vintage and modern systems

Server Information

📊 Current Status
  • Logging: None - No IP addresses or metadata collected to our knowledge
  • Data Retention: Automatic cleanup of old messages as we require
  • ROM Storage: None - All ROM processing happens locally in your browser, for absolute security use the local version of the software (see legal mentions above).
🔍 Transparency
  • Open Source: All code publicly viewable
  • Browse Messages: All stored files publicly accessible
  • No Hidden Features: Complete disclosure of capabilities

Getting Started

  1. Choose your security level:
    • Standard: Use this web interface (subject to Australian laws)
    • Maximum: Download local client from GitHub
  2. Prepare a ROM file: Any binary file works - photos, documents, executables
  3. Verify ROM quality: Use verifier.html to check suitability
  4. Start communicating: Share your ROM with intended recipients through secure channels

Limitations and Considerations

⚠️ Important Notes
  • ROM Security: Keep your ROM files secure - they are the keys to your communications. If someone obtains your ROM, they can obtain your data if they realise what your ROM was for. If you lose your ROM, your data is lost forever.
  • Character Coverage: Your ROM must contain all characters you want to use in messages
  • ROM Quality: Use the verifier.html tool to ensure your ROM provides adequate security
  • Server Dependencies: Web version relies on server availability and integrity
  • Legal Compliance: This server operates under Australian jurisdiction