Skip to content

OffCode Tor Chat 0.2

Choose a tag to compare

View all tags
@EmptyCode0x86 EmptyCode0x86 released this 10 Oct 17:52
· 6 commits to main since this release
OffCodeTorChat02
13b9f8b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Info: https://github.com/EmptyCode0x86/OffCode-Tor-Chat-E2EE

https://www.dev-offcode.com/TorChatPage.html

VER: 0.2

  • 10/10/2026

Changes

  1. Create rooms in Server Manager: Use Create room with a name only. That adds an open public room. You own it with the Admin key (paste into Profile Restore on the onion site). Remove selected room still works as before.
  2. Admin key: Server Manager keeps one recovery code for rooms you create there. It is the same kind of code as Profile on the site. Copy it, then Restore in Tor Browser. The i button next to the key explains this. The key is not stored in config.ini. Wiping SQL data does not delete it.
  3. Limit website room creation: Maximum Number of Rooms caps how many public rooms people can create from the onion page. Disable Room Creation blocks all website creates immediately. You can still create rooms from Server Manager.
  4. Save and Windows startup: Save stores ports, Tor, room limits, and Start server on startup. If that box is on, Save also starts Server Manager at Windows logon. ChatServer (and Tor if you saved it on) then start without extra dialogs. Uncheck and Save to turn logon start off.
  5. Faster onion page: Fewer fonts and a smaller download. The chat page should load quicker over Tor. Still no CDN.
  6. Locked 1:1 after reload: Messages from a previous join in a locked two-person room show as a previous-session note. They do not decrypt with the room password. Encryption itself is unchanged.
  7. Leave a room: Leaving or being removed clears the chat on screen (messages, draft, safety number, images). You are not logged out. Recovery codes in the browser stay.
  8. Safety number: Locked 1:1 now shows eight groups of five digits. Both people need this update. Compare the numbers in person or in another app.
  9. Tor flood protection: The Hidden Service can slow down floods (intro DoS and Proof-of-Work) when it is under load. Needs Tor 0.4.8 or newer (this bundle is). Docker uses the same settings.
  10. Admin tools stay off Tor: Server Manager talks to ChatServer on a private local port. Visitors on the .onion cannot see health or room-admin tools.
  11. Harder to fingerprint the host: Time in headers is rounded, and build timestamps are not sent with the page. CSS and fonts still cache so the page stays reasonably fast.
  12. Invite guessing: Invite lookups are limited across the whole server, so spinning new Tor circuits cannot hammer invites as cheaply.
  13. Hidden and closed rooms: A failed join takes a similar amount of time whether the room exists or not, so timing does not give that away.
  14. Official Tor files: Server Manager checks bundled Tor against a known hash. If it does not match, Tor does not start. It does not download a replacement.
  15. Message times: Times are rounded to the minute. Rejected messages all say the same thing, so the error text does not explain why.
  16. Where the chat runs: The UI only opens on localhost or a real Tor v3 .onion address, and only if the browser can do Web Crypto. Otherwise it stays blocked.
  17. Pinned message: The room creator can pin one message. Everyone sees that pin; the server does not learn the text. The pin expires with the message.
  18. Disable Room Creation: Checkbox in Server Manager. When on, nobody can create rooms from the onion site. You can still Create room from Server Manager.
Assets 3
Loading