Community posts: document storage and history for people; later improvements
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 76/100
- Issue 類型
- 文件
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
研究方向
閱讀 docs/COLLABORATION_HANDOFF.md，以及面向使用者的文件 docs/PEOPLE_CONVERSATIONS.md 和 docs/COLLABORATION_NETWORK_PROFILE.md。將分散的使用者說明替換為一個簡短章節，涵蓋所述的儲存、可見性、歷史記錄和 Library 檔案行為；將開發者細節保留在 handoff 文件中，並連結至新章節。完成標準是使用者能找到一處清楚完整的說明，且 handoff 文件指向該章節。
由索引模型根據 Issue 內容生成。
描述
How Community posts are stored and passed on works, but it is documented only for developers and in pieces (docs/COLLABORATION_HANDOFF.md:79-80 has the 24 h / 200 posts / 1 MiB rule; docs/PEOPLE_CONVERSATIONS.md and docs/COLLABORATION_NETWORK_PROFILE.md cover the protocol). No doc tells a person what happens to a post.
Facts (source at 8a74b669c):
- Each Home keeps the posts Chat shows (newest 500 per conversation, no age limit) and the signed originals it passes on (24 h, at most 200 posts and 1 MiB). Both are plain JSON in the Home's data folder.
- No server stores posts. The seed's Community node relays gossip and keeps nothing on disk.
- A Home that was offline gets missed posts only from Homes online now, only if both sides show presence, and only from the last 24 h.
- Posts are signed but not encrypted: every member, and every node on the topic including the seed hub, can read them.
- A post cannot be deleted or edited; other Homes keep it until it falls out of their newest 500.
- A Library file posted in Community stays on the sender's Home; only the sender's contacts can fetch it while that Home runs.
1. Document it (replace, not add): one short section in the user docs, built from the facts above, that replaces the scattered user-facing bits; the developer detail stays in COLLABORATION_HANDOFF.md and links to it.
2. Improvements to decide later:
- Delete your own post (a signed retraction that other Homes honor).
- Longer history: catch-up beyond 24 h and 200 posts, and catch-up that does not require showing presence.
- Encrypt stored posts at rest, like the per-person direct-message store.
- Private Communities: membership instead of the open grant, and posts encrypted to members.
- Say in Chat, once and briefly, that Community posts are public.
- 主要語言
- Rust
- 星號
- 6
- 分支
- 2
- 平均合併
- 1 天 3 小時
- 30 天內合併 PR
- 42
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
elastos/elastos-runtime 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
elastos/elastos-runtime#563 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
elastos/elastos-runtime#436 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
elastos/elastos-runtime#427 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
elastos/elastos-runtime#405 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
elastos/elastos-runtime#404 ·
維護者通常 1 天內回覆
查看 elastos/elastos-runtime 的全部 Issue
相似的 Issue
-
area: cli kind:docs priority: P3
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 88/100
swc-project/swc-ai-issues#164 ·
-
難度 2/5 1-3 小時 新手友好度 85/100
pop-os/cosmic-player#367 ·
-
good first issue help wanted
難度 2/5 1-3 小時 新手友好度 72/100
servo/rust-smallvec#873 ·