Skip to content

Tadpole / planning

Go to a project
Definite features

Definite features

Last edited by Jessica Hawkwell
Page history

Planned Features

This is not an exhaustive list of what I plan to implement. It will, however, be updated as I think of new thingies.

Account Security

  • 2-factor authentication is a must. Definitely support YubiKey U2F, since that's the hardware I have.
  • Possibly support Authy
  • If I can somehow get the capability to send SMS to phones:
    • 2FA via SMS
    • SMS account recovery
  • Account recovery via third-party email service

Mailing List support

  • Deduplicate messages from known mailing lists
  • Global-reference these messages so subscribers can still get them
  • Known mailing lists can have automagic folders in the web client? Maybe?

Spam Handling

  • SPF record resolution, hosts that shouldn't send mail will have their message silently dropped
  • Exact same message going to multiple users may be flagged automatically

Address Features

  • Address tagging (example [email protected])
    • [email protected] is identical to [email protected]
    • Mail Client: Subject lines are prefixed with the tag inside square braces: [gab] <subject line>
    • Web Client: Subject lines are unmodified, specific highlighting to show user tag
    • Tags could be sorted to their own automagic folders? Maybe?
  • Users can be detectives and see which websites are selling user data

Mail Clients

  • Web-based, located at tadpole.email
  • POP3/SMTP
  • IMAP

Tadpole As A Client

  • Users will be able to use Tadpole as an email client for other email services.
  • TAAC should be able to support every protocol Tadpole supports for its user's mail clients.

Encrypted Mail

  • Tadpole should be able to support encrypted messages. If the user has Tadpole handle decryption, Tadpole will then be able to run its content filters on said messages. Otherwise, skip filters.
  • Tadpole's encrypted message capabilities will enable users to use encrypted messages even if their mail clients don't support it.

Paranoid Users

  • Message headers are always available.
  • Web Client: If headers are hidden, they can become visible with a single click.
  • Service logs for each message could be made available. (Might be Web Client only, tho)

Web Client

  • No need to log access for authenticated users
  • TAAC - all inboxes shown separately

Monetization!

  • All users - 200 messages/week
  • Pro users - 500 messages/week, better control over message filters
  • BYOD (Bring Your Own Domain):
    • 10 addresses free
    • No robot accounts
    • For tech-savvy peeps with personal domains
  • Business:
    • Limited addresses
    • Robot addresses (special box for server software to use, like GitLab)
    • Instead of packages, have flexible billing:
    • Based on number of addresses used
    • Based on number of robot addresses used
    • Extra premium for mailing lists?
  • TAAC could be a premium feature