Using Quetz
Inbox and requests
An address is public, so anyone can write to you. Consent decides whether that reaches your inbox or waits in a separate folder.
Two folders#
| Folder | What lands there |
|---|---|
| Inbox | Conversations you started, and senders you have accepted. |
| Requests | Anyone who has written to you and has not been accepted yet. |
Nothing is deleted by this split. A request is a real conversation you can read in full before deciding anything. It simply stays out of the inbox until you say otherwise.
Accepting and blocking#
Open a request and the composer is replaced by two buttons. Accepting moves the conversation into your inbox and lets you reply. Blocking marks the sender denied, and their conversation stops appearing.
You can also do nothing. An unanswered request is a valid outcome, and the sender is told nothing either way.
Consent lives with your inbox, not with Quetz
What the sender can tell#
- They know the message was delivered to the network, because that part is not secret.
- They are not told whether you accepted, blocked, or ignored it.
- Blocking is not a notification. It just means their conversation stops surfacing for you.
Conversations you start#
Starting a conversation is itself an act of consent, so Quetz marks it allowed straight away. The same applies to a chat opened through a shared link: the visitor chose to open it, so it goes to their inbox rather than their own requests.
What is not filtered#
Consent controls which conversations reach you. It does not scan content, and Quetz cannot: messages are encrypted end to end, so there is nothing for a filter to read. If you want less unsolicited mail, the lever is which addresses you accept, not a spam classifier.