mirror of
https://github.com/logos-messaging/pm.git
synced 2026-01-02 14:13:09 +00:00
Extend Waku Forum scope
This commit is contained in:
parent
65be43dbf5
commit
5019a96830
@ -2,30 +2,38 @@
|
||||
|
||||
## Functionality
|
||||
|
||||
1. Users identify themselves by signing with their Bitcoin key
|
||||
2. Only users owning Logos ordinal can participate; usage of a centralized API to get current Logos ordinal owners may be needed.
|
||||
3. Any user (authenticated or not) can see the content; basic encryption functionality
|
||||
4. Existing cells can be listed
|
||||
5. Cell can be created with a name, description, icon; icon size will be restricted; created is solo admin
|
||||
6. Post can be created in a cell with a title and body; text only
|
||||
7. Comments can be made on posts and other comments; text only
|
||||
8. Posts can be upvoted
|
||||
9. Users can setup a call sign; bitcoin identity operator unique name - remains - ordinal used as avatar; OP number out-of-scope (not onchain)
|
||||
10. Cell admin can mark posts and comments as moderated
|
||||
11. Cell admin can mark users as moderated
|
||||
1. Users identify themselves by signing with their Bitcoin key.
|
||||
2. Only users owning Logos ordinal or an ENS can create a cell.
|
||||
3. Any user (authenticated or not) can see the content; basic encryption functionality.
|
||||
4. Existing cells can be listed.
|
||||
5. Cell can be created with a name, description, icon; icon size will be restricted; created is solo admin.
|
||||
6. Post can be created in a cell with a title and body; text only.
|
||||
7. Comments can be made on posts and other comments; text only.
|
||||
8. Posts can be upvoted.
|
||||
9. Users can setup a call sign; bitcoin identity operator unique name - remains - ordinal used as avatar; OP number out-of-scope (not onchain).
|
||||
10. Cell admin can mark posts and comments as moderated.
|
||||
11. Cell admin can mark users as moderated.
|
||||
12. Users can identify themselves by signing with their Web3 key.
|
||||
13. Posts, comments and cells have a relevance index, which can be used to order or hide them in the UX.
|
||||
14. The relevance index is lowered for post and comments which are moderated, or from a moderated user.
|
||||
15. The relevance index is increased if the author owns an ENS or Logos ordinal.
|
||||
16. The relevance index is increased if the post or comment is upvoted by an ENS or Logos ordinal owner.
|
||||
17. The relevance index is increased if the post has a comment from an ENS or Logos ordinal owner.
|
||||
|
||||
## Usability
|
||||
|
||||
1. A user can see all topics through all cells
|
||||
2. A user can see the number of active members per cell; deduced from retrievable activity
|
||||
3. Users can bookmark posts and topics; local only
|
||||
4. Users can sort topics per new or top
|
||||
5. The ordinal picture and information are used to identify user, in addition to the custom nickname
|
||||
6. Moderated users, comments, and posts are hidden
|
||||
7. Users do not need to sign every message with their wallet
|
||||
8. Users do not need any software beyond a Bitcoin wallet browser extension
|
||||
9. This includes a prototype UI to dogfood the PoC; Nice UI will be handled by Comms Hubs team
|
||||
10. A library with clear API is produced to enable frontend developers to use it with a nice UI
|
||||
1. A user can see all topics through all cells.
|
||||
2. A user can see the number of active members per cell; deduced from retrievable activity.
|
||||
3. Users can bookmark posts and topics; local only.
|
||||
4. Users can sort topics per new or top.
|
||||
5. The ordinal picture and information are used to identify user, in addition to the custom nickname.
|
||||
6. Moderated users, comments, and posts are hidden.
|
||||
7. Users do not need to sign every message with their wallet.
|
||||
8. Users do not need any software beyond a Bitcoin wallet browser extension.
|
||||
9. This includes a prototype UI to dogfood the PoC; Nice UI will be handled by Comms Hubs team.
|
||||
10. A library with clear API is produced to enable frontend developers to use it with a nice UI.
|
||||
11. ENS holders can choose to use an ENS for display purposes.
|
||||
12. The relevance index is used to push most relevant posts and comments on top.
|
||||
|
||||
## Reliability
|
||||
|
||||
@ -38,4 +46,9 @@ None
|
||||
|
||||
## Supportability
|
||||
|
||||
1. Web app with Bitcoin wallet browser extension
|
||||
1. Web app with Bitcoin wallet browser extension
|
||||
|
||||
## + (Privacy, Anonymity, Deployments)
|
||||
|
||||
1. A centralised API is used to get Bitcoin ordinal information.
|
||||
2. The Forum uses The Waku Network.
|
||||
@ -10,7 +10,7 @@ Harden select Waku Web apps by extracting libraries and writing protocol specifi
|
||||
- Qaku (Q&A over Waku): harden Waku to MVP level, so it can be used for IFT Town Halls, and Logos physical events.
|
||||
- Integrate SDS and write specs.
|
||||
- Logos Operators Forum: Build a web forum PoC over Waku to serve as a basis for a decentralized Logos forum (opchan).
|
||||
- Extend the Forum PoC to new FURPS, to align with Logos Movement needs.
|
||||
- Added: Extend the Forum PoC to new FURPS, to align with Logos Movement needs.
|
||||
|
||||
Explore Codex x Waku integration, in Qaku and one other application.
|
||||
|
||||
@ -61,7 +61,7 @@ TODO
|
||||
|
||||
**Feature**: [Qaku](/FURPS/application/qaku.md)
|
||||
|
||||
**FURPS**:
|
||||
**FURPS**: (see GitHub [issue](https://github.com/waku-org/pm/issues/292))
|
||||
- F1-21
|
||||
- U1-7
|
||||
- R1
|
||||
@ -111,18 +111,24 @@ TODO
|
||||
- ~[ ] Docs: links to README.md or docs.waku.org (TBD)~
|
||||
- [ ] Promote the app
|
||||
|
||||
## Expand Waku Forum MVP
|
||||
|
||||
TODO
|
||||
## Open Forum to Web3 Users and Anons
|
||||
|
||||
**Owner**: App/Chat Dev
|
||||
|
||||
**Feature**: [Waku Forum](/FURPS/application/forum.md)
|
||||
|
||||
**FURPS**:
|
||||
- F1-11
|
||||
- U1-10
|
||||
- R1-2
|
||||
- F2. Only users owning Logos ordinal or an ENS can create a cell.
|
||||
- F12. Users can identify themselves by signing with their Web3 key.
|
||||
- F13. Posts, comments and cells have a relevance index, which can be used to order or hide them in the UX.
|
||||
- F14. The relevance index is lowered for post and comments which are moderated, or from a moderated user.
|
||||
- F15. The relevance index is increased if the author owns an ENS or Logos ordinal.
|
||||
- F16. The relevance index is increased if the post or comment is upvoted by an ENS or Logos ordinal owner.
|
||||
- F17. The relevance index is increased if the post has a comment from an ENS or Logos ordinal owner.
|
||||
|
||||
- U11. ENS holders can choose to use an ENS for display purposes.
|
||||
- U12. The relevance index is used to push most relevant posts and comments on top.
|
||||
|
||||
|
||||
**Checklist**:
|
||||
- [ ] Specs: link to specs and/or API definition
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user