The protocol itself doesn't care whether content is plain text, markdown, or html — clients can choose to render however they want. That said, I want to find a way to support longer form content and custom schema for interpretation hints to clients (atproto also does this)
1 Reply
{no channel}
- hash
- c3cd66123e3a7e95987ed2b663cc4107c7b42053
- timestamp
- 2026-08-30T00:48:30.000Z
- fid
- 1325
- parent_fid
- 321969
- parent_hash
- abd86d844064cdac568d0e804a2231e37de3ce3c