Establish TLS for 'tekuma.io'

[xstephen95x]

• decision as of meeting at 10 Nov 2016: offer both HTTP and HTTPS

-My description from a task that was duplicate of this:
It appears that https://tekuma.io/ is active but has a self-signed certificate. For major browsers, this leads to a big warning page with text like "Your connection is not secure".

[slivingston]

To be clear about motivation, ideally someone should be able to browse artwork on tekuma.io and be very confident that:

• the site visited is in fact Tekuma's website,
• intercepted traffic does not reveal which items were viewed,
• no interference nor injection occurred.

While Tor and similar media can be used to achieve anonymity, authenticity, interference etc. would remain.

[xstephen95x]

reminder: SSL cert for https://tekuma.io ?

decide whether to use www. prefix, or to redirect requests to www.tekuma to tekuma

[slivingston]

thanks for the ping. I will raise discussion about www redirects on Slack, which might make participation in the discussion easier for anyone who is not on GitHub.

[slivingston]

I added a statement about this task at and near https://tekumateam2016.slack.com/archives/general/p1486763747000002

[slivingston]

Kun declared that we should not have the www subdomain as the preferred one. cf. https://tekumateam2016.slack.com/archives/general/p1486763931000005