{"action":"created","issue":{"url":"https://api.github.com/repos/google/badssl.com/issues/172","repository_url":"https://api.github.com/repos/google/badssl.com","labels_url":"https://api.github.com/repos/google/badssl.com/issues/172/labels{/name}","comments_url":"https://api.github.com/repos/google/badssl.com/issues/172/comments","events_url":"https://api.github.com/repos/google/badssl.com/issues/172/events","html_url":"https://github.com/google/badssl.com/issues/172","id":162952165,"number":172,"title":"'ssl' is a little archaic. I have badhttps.com, do you want it?","user":{"login":"mikemaccana","id":172594,"avatar_url":"https://avatars.githubusercontent.com/u/172594?v=3","gravatar_id":"","url":"https://api.github.com/users/mikemaccana","html_url":"https://github.com/mikemaccana","followers_url":"https://api.github.com/users/mikemaccana/followers","following_url":"https://api.github.com/users/mikemaccana/following{/other_user}","gists_url":"https://api.github.com/users/mikemaccana/gists{/gist_id}","starred_url":"https://api.github.com/users/mikemaccana/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikemaccana/subscriptions","organizations_url":"https://api.github.com/users/mikemaccana/orgs","repos_url":"https://api.github.com/users/mikemaccana/repos","events_url":"https://api.github.com/users/mikemaccana/events{/privacy}","received_events_url":"https://api.github.com/users/mikemaccana/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/google/badssl.com/labels/wontfix","name":"wontfix","color":"ffffff"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-06-29T15:15:01Z","updated_at":"2016-06-29T20:30:45Z","closed_at":"2016-06-29T20:03:48Z","body":"Hey Lucas,\r\n\r\nLike most of the (non-crap) part of the industry, I've avoided the TLS/SSL discussion (which is mainly by pedantic nerds) entirely by talking about https. https://certsimple.com now uses 'https' almost everywhere, Google Security Blog and Let's Encrypt do too. I suspect https is also more easier to understand as that's what the browser shows.\r\n\r\nWith that in mind, do you want badhttps.com? I registered it before anyone else could, just let me know and I'll transfer it. \r\n\r\nMike / CertSimple"},"comment":{"url":"https://api.github.com/repos/google/badssl.com/issues/comments/229478724","html_url":"https://github.com/google/badssl.com/issues/172#issuecomment-229478724","issue_url":"https://api.github.com/repos/google/badssl.com/issues/172","id":229478724,"user":{"login":"marumari","id":230528,"avatar_url":"https://avatars.githubusercontent.com/u/230528?v=3","gravatar_id":"","url":"https://api.github.com/users/marumari","html_url":"https://github.com/marumari","followers_url":"https://api.github.com/users/marumari/followers","following_url":"https://api.github.com/users/marumari/following{/other_user}","gists_url":"https://api.github.com/users/marumari/gists{/gist_id}","starred_url":"https://api.github.com/users/marumari/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marumari/subscriptions","organizations_url":"https://api.github.com/users/marumari/orgs","repos_url":"https://api.github.com/users/marumari/repos","events_url":"https://api.github.com/users/marumari/events{/privacy}","received_events_url":"https://api.github.com/users/marumari/received_events","type":"User","site_admin":false},"created_at":"2016-06-29T20:30:45Z","updated_at":"2016-06-29T20:30:45Z","body":"Not to mention that getting the certificates reissued would be both\nexpensive and time-consuming.  :)\n\nOn Jun 29, 2016, at 3:02 PM, Lucas Garron <notifications@github.com> wrote:\n\nThanks for holding on to it, but I actually chose badssl.com on purpose:\n\n   - It's shorter and catchier (2 letters shorter, half the syllables).\n   - It doesn't duplicate the scheme in the domain name.\n   https://badhttps.com doesn't look *too* bad, but I think the duplication\n   of https can be unnecessarily confusing. This site is meant for testing\n   UI edge cases, and the domain may show up in all sorts of screenshots. We\n   often write test instructions for people who may not know much about what\n   we're doing; I can easily imagine someone misdescribing/misunderstanding an\n   expected behaviour because the domain contains https.\n   - It subtly disparages the term \"ssl\". badhttps sounds like it's saying\n   HTTPS is bad, as if you named your dog HTTPS and your dog left the front\n   door flap open, and you said \"*Bad HTTPS*, no treats for you tonight.\".\n   ;-)\n\nI usually support using the term HTTPS instead of TLS/SSL when talking\nabout transport security, but I very consciously chose not to do so here. I\nhope that's alright.\n\n—\nYou are receiving this because you are subscribed to this thread.\nReply to this email directly, view it on GitHub\n<https://github.com/google/badssl.com/issues/172#issuecomment-229471296>,\nor mute the thread\n<https://github.com/notifications/unsubscribe/AAOEgF5Frsel2usiVSlih2CY5bLy1D69ks5qQs9OgaJpZM4JBPtn>\n.\n"}}
{"actor":{"display_login":"marumari"}}