🎯 How It Works
⚠️ IMPORTANT: There is NO hosted encoding client for ZOSCII TrumpetBlower.
You MUST download the client from GitHub and run it locally to ensure your ROM is never uploaded to any server.
Step-by-Step:
- Download the client from GitHub
Visit: https://github.com/PrimalNinja/cyborgzoscii
Download the 'trumpetblower.html' client to your computer - Verify the client is NOT minified
Open the HTML file in a text editor. The code should be readable with proper spacing and comments.
If it looks like compressed gibberish on one line, DO NOT USE IT.
Readable code = trustworthy. Minified code = potential compromise. - Establish Anonymity (Use Tor) 🌐
Your anonymity is your first line of defense.
What Tor Does: Tor routes your connection through multiple relays, making it virtually impossible for the host or any observer to determine your true IP address or geographic location.
Option A (Recommended): Tor Browser
1. Go to the official Tor Project website: https://www.torproject.org/download/
2. Download, install, and launch the Tor Browser.
3. You must use this browser for all subsequent steps involving the server.
Option B (Highest Security): Tails OS
1. Follow the installation guide: https://tails.net/install/
2. Run the local 'trumpetblower.html' file within the Tails environment and Tor Browser. - Run the client locally
Open the HTML file in your browser from your local filesystem
Do NOT use any hosted version - only trust what you've verified yourself - Configure the Server
Enter the ZOSCII TrumpetBlower Server URL you wish to use, See available servers below
Enter a channel number (an integer), something not identifiable to you, it doesn't matter if it is used already or not, it's just easier to find unknown data by a reference in future
Enter a number of desired retention weeks (an integer) - Encode your documents
💡 Recommended: ZIP your files before encoding. This reduces our storage overhead and preserves file metadata like date/time stamps that can serve as evidence of when documents existed.
Use any file as your ROM (photo, document, etc.)
There should be no red lines in the verification character usage
The ROM becomes your encoding key - NEVER upload it anywhere
The client will create an address file (just pointers, no actual data) - Keep your ROM safe
Store your ROM securely - you'll need it to decode later
Losing your ROM = losing your data forever
Your ROM is your key to release the information when you're ready - Submit to Server
Only the address file is uploaded with the channel and retention, the address file contains none of the original data - just pointers
We (and everyone else) can't decode it without your ROM
When you're ready to blow the trumpet, release your ROM publicly - Redundancy
All address files are made available for download, replication and of course for when you wish to make a noise
⚖️ Australian Legal Notice
This service operates under Australian law and is subject to the Assistance and Access Act 2018.
Under this legislation, we may be compelled to:
- Assist with lawful access to communications
- Implement technical capability measures
This is exactly why we recommend downloading and verifying the client yourself. If we were ever compelled to modify our code, you would be able to detect it by comparing against the GitHub source or noticing minification. By running your own verified local copy, you eliminate this risk entirely.
For maximum security: Only use the local client version downloaded from the official GitHub repository.