A server in the end

[DavidBruant]

Maybe a server would make things convenient.
That would remove the step of creating a Twitter app.
A server would be acceptable only if no reliable server-less solution exists.

The server would only be there for the "sign in with Twitter" part and send the OAuth tokens to the addon.

[DavidBruant]

• Server Phase 1 (server on localhost)
  • Make a localhost server that works ( ADI export script (bug 1014752) mozilla/addons-server#115 )
• Server Phase 2 (shippable on AMO)
  • Buy a server
  • Buy a domain
  • Make the app work via the (hardcoded) server
  • Start server with forever
  • Submit to AMO (BIIIIIM !)
• Server phase 3
  • Addon saves oauth token requirements: newrelic 2.16.0.12 -> 2.20.1.18 mozilla/addons-server#122
  • Server can be modified via panel UI (hidden settings)
  • TLS certificate with letsencrypt
  • Use actual domain name
• Server phase 4
  • Server only does auth & Oauth signature; client does the actual request to Twitter API
    • (see https://stackoverflow.com/questions/4972590/does-twitter-enforce-oauth-timestamp )
  • Dockerize server
  • Use port 443 (https)
  • Make a readme section explaining how to do the server install