.txt file or write your full text directly from this site. Only one method can be used at a time.
eport.news has no start page, no file management interface, no rating system, and no search across sub‑URLs — it simply hosts the full texts, within the most minimalistic style possible in use now-, simple a dark screen, with white text that scrolls from right to left; with the function allowing users to manually scroll browser window to desired reading-speed.
reportage.news is the visible, reader‑facing platform where your piece is presented and discovered. eport.news is the quiet storage layer that holds the complete text at a stable address. After evaluation, by me as an editor here at reportage.news & eport.news, an info box appears at reportage.news, beneath the so-called “Latest News”, and as mentioned earlier for recieving views and Heart Rates, but also link to "the non 'center focused'" platform - eport.news - or, as a "passport" for the text.
reportage.news and eport.news act like digital waterways where ideas travel from one shore to another. When a writer publishes a titel, it shows on e-port, but awaits the further evaluation of reportage.news, for a recievement of one of our informational 'article boxes'.:
Comments info:
When a reader posts a comment with notifications turned on, their browser generates a random private string (rnkey), attaches it to their URL (?rnkey=...), and saves it locally in browser storage. The browser then computes an irreversible SHA-256 hash of that key (inbox_id) and sends only the hash to the server along with the comment text. When anyone replies, the server attaches the reply to that public inbox_id. When the original reader returns using their bookmarked link, their browser asks the server if there are any new messages for their computed hash, triggering a notification toast and unlocking options to edit or delete their own comment—all without ever storing an email address, password, or user profile on the server.
We make use of "Tokens" and keep no records of users. Our servers operate in volatile memory: no user profiles, no comment databases, and no permanent logs.
To be truly unseen, you hold your own thread: if you now wipe your browser history, you also erase the only door an answer can knock on.
You only need the bookmark as your emergency key. As long as your browser data remains intact, notifications continue normally. Keeping it bookmarked ensures permanent access: you can clear history, switch devices, or return months later—your bookmark instantly restores your private reply channel.
All operations run in volatile RAM. When you post or request alerts, the server only relays your message to native browser push services. After delivery, the payload and connection are immediately discarded—never written to disk.
Because no user database exists, your activity cannot be leaked, compromised, or linked across visits. Even behind VPN, Tor, or private networks, our servers never bind your actions to an IP identity.
The token lives inside the URL fragment (#). Browsers never send the #fragment to servers during requests. It remains sealed entirely on your device.
You remain fully untracked, but if you clear your browser cache or close private windows, the local connection is lost permanently. Future replies to your thread will no longer reach you.