Design: Scope
Created by: BrainBlasted
This issue is to work out what exactly the scope of the application should be as a Mastodon client. Using the guidelines laid by the GUADEC video in #8 (closed), I came up with the following Must-haves and Won't-haves:
Must-Haves
- Sending and receiving toots
- Content and Sensitive media warnings
- Timeline viewing
- Custom (pinned) timelines
- Notifications
- Toot conversation view
- Replying
- Direct Messages
- Mute & Block Management
- Multi-account (Working in cli version)
Won't-Haves
- Tracking
- Status text search (for privacy and anti-harassment reasons)
- Encryption (A chat protocol is suggested for private communications)
Community input on this is encouraged.