10 Ideas

Izalia Mae edited this page 2021-01-12 00:41:19 -05:00

API implementation:

• Support enough of the mastodon api to work with most apps
• Add own api alongside mastodon api as /api/[whatever I rename social to] for non-mastodon features
• Require token for most endpoints

Public pages:

• Just for account/server management
• Create options for variables (max poll options, max toot chars, etc) in admin settings
• Use as little JS as possible and keep it simple for fast page loads
• Disable anonymous public profile/toot pages by default
  • Allow remote users to authenticate via oauth to view pages
  • Per account/page option for allowing anonymous viewing

Web App:

• Will 100% use api to interact with server
• Run self-contained to be able to use it on other servers
• Enable multi-server mode when running by itself (maybe?)
• Ability to login to multiple accounts

Backend:

• Allow signups via oauth
• Ability to run without a reverse proxy and auto-grab ssl certs (maybe?)
• Greylist mode which is a hybrid between normal and whitelist mode
  • Optionally share lists between instances
• Built-in media cleanup
  • Only remove unused local media if it's in the 'untagged' category
• Only strip certain html tags as well as the style property: style, script, div, etc
  • This leaves it up to the web ui to determine what styling tags get included
• Ability to follow and be followed by other instances:
  • require approval by default
  • two different actors
    • /actor/public for all public toots. Also sends incoming public toots if in relay mode
    • /actor/local for all local toots