lemmy/docs/src/about_goals.md

Goals

• Come up with a name / codename.
• Must have communities.
• Must have threaded comments.
• Must be federated: liking and following communities across instances.
• Be live-updating: have a right pane for new comments, and a main pain for the full threaded view.
  • Use websockets for post / gets to your own instance.

Questions

• How does voting work? Should we go back to the old way of showing up and downvote counts? Or just a score?
• Decide on tech to be used
  • Backend: Actix, Diesel.
  • Frontend: inferno, typescript and bootstrap for now.
• Should it allow bots?
• Should the comments / votes be static, or feel like a chat, like flowchat?.
  • Two pane model - Right pane is live comments, left pane is live tree view.
  • On mobile, allow you to switch between them. Default?

Resources / Potential Libraries

• Diesel to Postgres data types
• helpful diesel examples
• Recursive query for adjacency list for nested comments
• https://github.com/sparksuite/simplemde-markdown-editor
• Markdown-it
• Sticky Sidebar
• RXJS websocket
• Rust JWT
• Hierarchical tree building javascript
• Hot sorting discussion 2
• Classification types.
• RES expando - Possibly make this into a switching react component.
• Temp Icon
• Rust docker build
• Zurb mentions
• TippyJS

Activitypub guides

• https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/
• https://raw.githubusercontent.com/w3c/activitypub/gh-pages/activitypub-tutorial.txt
• https://github.com/tOkeshu/activitypub-example
• https://blog.joinmastodon.org/2018/07/how-to-make-friends-and-verify-requests/
• Use the activitypub crate.
• https://docs.rs/activitypub/0.1.4/activitypub/
• Activitypub vocab.
• Activitypub main
• Federation.md
• Activitypub implementers guide
• Data storage questions
• Activitypub as it has been understood