Chat
Keep the reason for talking close to the conversation.
PostLane chat retains shared context from a circle, plan, or event and keeps Plans and Mutual Consent nearby without treating a message as permission to reveal more.
Conversation that can recover
If a message fails to send, the interface can preserve it and offer retry instead of pretending delivery succeeded. A local sent state describes the sender's action; it is not a delivery receipt or read receipt. Blocking and close-conversation controls provide clear boundaries when a conversation should stop.
Plans remain attached to their details, and a reveal request remains a separate choice with its own state. A plan can be canceled or become stale without rewriting the conversation that led to it.
| State | What it means | Available next step |
|---|---|---|
| Draft or failed | The message has not completed its send action. | Edit, retry, or remove it. |
| Sent locally | The sender completed the send action; this is not proof of delivery or reading. | Continue, make a plan, or close the conversation. |
| Blocked or closed | The conversation boundary prevents continued contact through that path. | Respect the boundary and use Report for a separate conduct concern. |
What chat does not promise at launch
- No read receipts or delivery receipts.
- No pay-to-message or paid inbox priority.
- No voice calls, video calls, or public voice rooms.
- No assumption that continued chat equals consent to reveal a photo or private detail.
Continue with PostLane
PostLane is preparing for launch.