{"action":"closed","issue":{"url":"https://api.github.com/repos/SyndroneOnline/SyndroneOnline.com/issues/26","repository_url":"https://api.github.com/repos/SyndroneOnline/SyndroneOnline.com","labels_url":"https://api.github.com/repos/SyndroneOnline/SyndroneOnline.com/issues/26/labels{/name}","comments_url":"https://api.github.com/repos/SyndroneOnline/SyndroneOnline.com/issues/26/comments","events_url":"https://api.github.com/repos/SyndroneOnline/SyndroneOnline.com/issues/26/events","html_url":"https://github.com/SyndroneOnline/SyndroneOnline.com/issues/26","id":178756651,"number":26,"title":"Pros and cons SSL discussion","user":{"login":"emiliobool","id":2165828,"avatar_url":"https://avatars.githubusercontent.com/u/2165828?v=3","gravatar_id":"","url":"https://api.github.com/users/emiliobool","html_url":"https://github.com/emiliobool","followers_url":"https://api.github.com/users/emiliobool/followers","following_url":"https://api.github.com/users/emiliobool/following{/other_user}","gists_url":"https://api.github.com/users/emiliobool/gists{/gist_id}","starred_url":"https://api.github.com/users/emiliobool/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emiliobool/subscriptions","organizations_url":"https://api.github.com/users/emiliobool/orgs","repos_url":"https://api.github.com/users/emiliobool/repos","events_url":"https://api.github.com/users/emiliobool/events{/privacy}","received_events_url":"https://api.github.com/users/emiliobool/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/SyndroneOnline/SyndroneOnline.com/labels/discussion","name":"discussion","color":"c5def5"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-23T00:46:05Z","updated_at":"2016-09-23T00:46:23Z","closed_at":"2016-09-23T00:46:23Z","body":"Pros:\r\n- Using https would fix the cookie bug on mobile when using google's \"data saving\" proxy\r\n- it would show the little green lock icon ![unspecified-1](https://cloud.githubusercontent.com/assets/2165828/18770332/c2c414a8-80e9-11e6-9372-bcd9ab3b4253.png)\r\n- it would increase security on the data transmitted between users and server\r\n\r\nCons:\r\n- Having to pay a CA for the certificate or having to setup and constantly run something like https://letsencrypt.org/\r\n- All assets on the site would need to run under https so the browser doesn't complain\r\n  - this means having to issue separate certificates for each subdomain we use, (as a note: I believe we should not run subdomains for usernames for this and other issues) and this includes cdn services, \r\n- CDN would need to run using SNI, meaning old really old browsers wont be able to establish a connection unless we use a dedicated ip which would be just too much money, and still we need a separate certificate\r\n- also all external images and assets from all posts would need to be https too, which would need to be cached and proxied and locally stored to be able to serve them under https, facebook, this github and others do that, but I don't think we are ready for this\r\n   - this could also imply copyright issues for storing other peoples images, etc\r\n\r\nI believe current reasons are not compelling enough to do the switch as of now, in fact I do not believe we want to take this challenge right now "}}
{"actor":{"display_login":"emiliobool"}}