dappconnect-sdks/apps/website/docs/messaging-and-web3-browser/about-status-messages.md

53 lines
3.6 KiB
Markdown
Raw Normal View History

[website] Add documentation (#403) * setup md/mdx * add test page * setup mdx provider * Add breadcrumbs * links -> routes * add information box * add more remark plugins * text InformationBox * setup contentlayer * add testing docs folder * setup docs static generation * add ssg to blog too * add Shortcut component * add SearchButton * add hook for keyboard shortcuts * update main docs page * update main learn page content * side-bar -> sidebar-menu * rename docs pages * add heading anchors, use new components * add table of contents to docs * move styling to breadcrumbs * cleanup markdown examples * change slugify fn * update getting-started.md * add highlight matches component * update learn pages * rename website InformationBox to Admonition * ?enable user-select * add static helpers to epics * simplify components structure * update insights layout * add link tree utils * add search engine * update docs import * update contenlayer * add docs indexer * support code block highlighting * search index * fix types * remove supporting files * update tree builder * make build work * update docs * update label * update toc * add config.json * update menu * search index import * learn -> help * fix md file * update toc * fix code snippets * add help index route * remove testing files * add original docs * migrate getting started * migrate messaging-and-web3-browser docs * migrate network-nodes-and-statistics docs * handle empty content * add navigation config * wip * migrate status-wallet docs * migrate to new admonitions format * migrate your-profile-and-preferences docs * migrate part of status-communities docs * mv * rm log * index * fix lint * fix warn * fix title * fix docs layout * udpate next.config * use lowercase lang * generate contentlayer types before typechecking * update docs images * update help routes --------- Co-authored-by: Felicio Mununga <felicio@users.noreply.github.com>
2023-06-27 20:30:11 +00:00
---
id: 125
revision: '0'
language: en
title: About Status messages
---
Messaging is a critical Status component. The Status app combines [peer-to-peer messaging][peer-to-peer-messaging] technologies with robust end-to-end encryption across all your devices. Peer-to-peer messaging eliminates the need for centralized servers and intermediaries, providing a censorship-resistant alternative to other popular messaging apps.
We've built the Status app to keep your messages and information out of our reach. Other messaging apps offer end-to-end encryption, but their centralized network design allows interpretation of who is talking to whom and where. See how Status compares to other messaging apps in the table below:
| Privacy feature | Status | Other messaging apps |
| :---------------------------- | :------------------- | :------------------- |
| End-to-end encryption | :material-check-all: | :material-check-all: |
| Network metadata encryption | :material-check-all: | :octicons-x-24: |
| "Who talks to who" encryption | :material-check-all: | :material-check: |
| Censorship resistant | :material-check-all: | :octicons-x-24: |
| Anonymous | :material-check-all: | :material-check: |
| Open source | :material-check-all: | :material-check: |
(:material-check-all: available, :material-check: available on some apps, :octicons-x-24: not available )
## The basics
- Your communications are end-to-end encrypted by default.
- Your messages are not stored on centralized servers.
- Only you and the message recipient can read your messages.
- Status cannot identify you or other participants in the conversation.
:::tip
For answers to general questions about your Status messages, check the [Messages FAQ][messages-faq] topic.
:::
## Understand peer-to-peer messaging
Status provides resilient messaging without relying on centralized servers, data centers, or service providers. The Status app uses [Waku :octicons-tab-external-16:][waku], a peer-to-peer protocol for private, secure, and censorship-resistant communication.
Unlike centralized networks (A), which depend on a central server to relay messages, peer-to-peer networks (B) encrypt and broadcast every message to all participant nodes. A node is a computer or smartphone that relays messages to other nodes or temporarily stores them for disconnected peers. Even when all nodes can access your messages, the content is encrypted so that only you and the intended recipients can read them.
![The peer-to-peer network sends messages to every node and doesn't rely on a central server.](/assets/docs/messaging-and-web3-browser/about-status-messages/125-0-1-dark.png)
## Built-in privacy and security
The Status app secures your messages the entire time they are in transit using end-to-end encryption. This industry standard protection uses strong encryption keys and ensures that only you and the recipients can read your messages. No one else (not even Status) can read your conversations or identify you or other participants.
When you communicate with someone on the Status app, your messages, attachments, sender metadata, group chats, and group metadata are all end-to-end encrypted.
Status incorporates the [Perfect Forward Secrecy :octicons-tab-external-16:][perfect-forward-secrecy] (PFS) encryption mechanism, ensuring that encryption keys change on every message. If your keys are compromised, only the associated message is compromised. All previous messages remain private.
:::info
Status messaging protects your privacy in one-to-one communications, chat groups, public chats, and Communities.
:::