this is why slack wanted infinite threading, but they gave up on it. it is not an easy ux to solve. but if we can figure it out, what it gives us that instead of chat happenings, chat becomes locations you can revisit, and grow over time
What the chain says
- Block
- 965 936
- Time
- 2026-09-09T03:07:42Z
- Signer
- 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
- App
- treechat
- Type
- post
- Content type
- text/markdown
- Name in tx
- metamitya
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial