ST0RM.SU // DOCS
OPEN APP

ST0RM.SU Documentation

This guide explains how members use ST0RM.SU safely: account creation, public channels, forum threads, encrypted DMs, moderation, and recovery/troubleshooting steps.

Launch Forum Back To Landing

Quick Start

  1. Open the forum and create a username/password.
  2. Save your generated seed phrase in a secure offline place.
  3. Join public chat channels to read/send encrypted channel messages.
  4. Use forum-only categories to publish threads (announcements/offers).
  5. Start encrypted DM only when you need direct private communication.

Public Channels vs Forum Threads

Public Chat Channels

Realtime, encrypted channel chat. You must have active peers connected to see network messages.

  • Used for live conversation.
  • Messages sync peer-to-peer when peers are online.
  • If no peers: message remains local.

Forum Categories (Thread Mode)

Structured post feed for announcements/jobs/offers. No chat-reply behavior there.

  • Create threads with the `NEW THREAD` button.
  • Forum posts are shown as thread entries.
  • Configured retention cleanup removes old posts (e.g. 7 days).

Encrypted DMs

How It Works

  • Invite a user from `NEW ENCRYPTED DM`.
  • Recipient accepts DM request.
  • Session key is derived with ECDH P-256.
  • Messages are encrypted using AES-256-GCM.

Identity Verify

  • Open DM identity verification modal.
  • Compare peer fingerprint via trusted external channel.
  • Mark as verified before sensitive conversation.

Security Model

Signal/DiscoveryPeerJS Broker
TransportWebRTC DataChannel
Public CipherAES-256-GCM
DM Key ExchangeECDH P-256
DM CipherAES-256-GCM
Password KDFPBKDF2 SHA-256

PANIC WIPE: clears local session/local storage data from browser so this device no longer retains account/session artifacts.

Important: if an attacker controls the live unlocked device, no client-side forum can fully protect active sessions.

Troubleshooting

01

No peers connected: open forum in another browser/device and ensure both are online simultaneously.

02

Peer discovery degraded: broker issue; direct known peer links may still work.

03

Reconnect notices: expected when data channel renegotiates due to transient network drops.

04

Message local only: public channel requires active peer mesh, otherwise only your node stores the message.

Operational Recommendations

  1. Use separate browser profiles for separate identities.
  2. Keep seed phrase offline and never in cloud notes.
  3. Verify DM fingerprints before high-risk conversation.
  4. Keep browser and OS updated to reduce client compromise risk.