General tips
This section contains general tips for users.
Messages not downloading or refreshing
Find and use Logout to completely clear browser cache and all Haven settings.
Backup your identity, invite links to channels and admin keys for channels you administer. All these will be wiped on Logout.
xx Network stores messages for limited time
xx Network keeps messages for 21 days.
This is a xx Network-wide setting which instructs xx Network gateways to delete stored messages after 21 days. It exists to limit the use of storage capacity.
Currently there's no client-side settings that let one set client-side retention for Haven, but:
- Messages can be deleted by the sender or administrator which propagates to (online) clients in the channel
- If everyone leaves a channel and no invite links or admin keys are preserved, all channel content can be considered lost (probably DM between channel users, too - can be checked experimentally)
Haven client caches messages locally in encrypted browser cache, and re-syncs with xx Network databases when it reconnects:
- Messages that were deleted by admins and users will be deleted in cache upon resync
- Other messages may be retained in Haven's encrypted browser cache beyond 21 days (longer than xx Network databases keep them)
Maximum text message length
It is around 900 bytes after built-in, client-side compression.
Safety and sharing of Internet links in Haven chat
If you don't trust chat participants, you should not click on links shared through Haven.
Among regular browsers, Brave Browser has a convenient feature that lets the user right-click a link and select Open link in private window with Tor
. Here's how that menu looks like:
That doesn't give them the ability to avoid malicious sites, but at least hides their IP address the same way Tor would (or wouldn't).
Users of other browsers could copy links shared in Haven and paste them into a dedicated Tor Browser instance, although that is inconvenient.
Because this feature makes it very easy to eliminate one of top privacy risks in casual Haven use, Brave Browser should be the first choice for Haven - especially if you don't normally use it, as you wouldn't need any add-ons in it either.
Customizing Haven's color scheme (CSS)
Users wishing to make simple changes to Haven's CSS color sheme can find tips and samples here.
Client-side logging and debugging
Generic advice for Web app debugging is to try without add-ons and in Private/Incognito mode. Don't do that with Haven. You should try without Private mode and with privacy features disabled for the site.
Helpful information may include your OS, browser type, browser version and logs from browser's debug tools.
Good places to get help are xx Network Discord (find an invite here, join, and go to #speakeasy
) and xx Network Forum.
Detailed logs may be exported from application settings in the case developers ask for it. Because they may contain private information it's better to not share them in public without checking.
Browser debugging can be done in (Web) Developer Tools (usually in the Console
tab).
Prove wallet or asset ownership in Haven
You may send a cryptographically signed message in Haven. The signature can prove ownership of a wallet or an asset. See this post on how to do that in xx Network wallet.
The channel owner may use that to check if a Haven codename has control over a wallet with specified balance of some token to be unmuted or (out-of-band) invited in order to join a channel.
Workflow example:
- Administrator creates a a public "customer support" channel for "xx coin whales" (condition: wallets with at least $10'000 equivalent in xx coins)
- Interested parties access this channel to DM with Administrator. They submit signed proof of wallet ownership
- Upon ensuring the codename has access to a wallet that meets minimum conditions, the admin shares an invite link for a private "xx whale" channel
There's some opportunity to get around these rules by moving coins around and whatnot, but wallets can be periodically rechecked and it can be automated.