Expedited SSL

I run an incredibly boring business (SSL certs for Heroku), for which: 1. The majority of my alpha and beta testers came from Twitter. 2. The second highest source of traffic to both my marketing site [1] and the actual add-ons page [2] is from Twitter. 3. All of the testimonials on my site (which have been incredibly helpful in convincing people my service is useful are actually Twitter embeds) 4. There was a Heroku presentation given in Tokyo where my add-on was brought up as an example, which someone in the audience then tweeted about in Japanese. This triggered an alert on my computer (from Tweetdeck) and I was then able to on the fly answer questions people there had about it. To me, with the people I follow, Twitter seems more like a programmers / startups meetup or conference than anything else. 1 - https://www.expeditedssl.com 2 - https://addons.heroku.com/expeditedssl

> Microsoft is terrible at picking good proper nouns for products. I wonder if there's a sort of internal fighting for each team to squat on the "best" names for their product or service. Basically a Dilbertian confusopoly [0] where the goal is to make your project sound like "the obvious choice" regardless of its merits, with "Microsoft" on the front as the only way it stops being impossible to trademark. I imagine other large companies struggle with this as well, although Amazon seems to have taken to the other extreme [1]. [0] https://en.wikipedia.org/wiki/Confusopoly [1] https://www.expeditedssl.com/aws-in-plain-english

May I recommend to set up the SSL expiry notification using this website: https://www.expeditedssl.com/simple-ssl-scanner/scan?target_domain=www… ? That might help to prevent such incidents in the future.

a) This is great. Also, a friend linked me to Expedited SSL yesterday and I link to it in the bottom of this post. b) I think its SHA-1 scanner is mistaken - it flags my site as using SHA-1, but it's SHA-2 in every cert in its chain: https://www.expeditedssl.com/simple-ssl-scanner/scan?target_domain=kon…

Using www puts the customer first. Being able to serve your website from a CDN helps the customer: it means the website is up when they want to visit it, and it usually means it's faster for them. Having static content not get cookies helps the customer: it keeps HTTP traffic down, which means that pages load faster. Separating cookies between different websites helps the customer: it means that when, inevitably, blog.example.com gets broken into, the customer's account info at www.example.com is not compromised. (Of course, this assumes that you're doing least-privilege between your various websites, but you're already doing that because you care about your customer and don't want to send them a letter about how you lost their personal information.) Not using a separate top-level domain for static content helps the customer: they know that www.example.com and static.example.com are from the same company they trust, Example Industries, Inc. If you caused their browser to show that it's loading files from "static.excdn.com" or something, they might worry. The customer isn't personally following the redirect; their browser does, so I'm not sure I understand how the redirect deprioritizes the user. As far as visual clutter goes, get an EV cert, which either supplants or replaces the address bar with something much more useful than a URL: https://www.expeditedssl.com/assets/browser-ssl/extended-validation-mo…

Oddly enough... the same site has it. https://www.expeditedssl.com/azure-in-plain-english

They did Azure: https://www.expeditedssl.com/azure-in-plain-english

It’s not jus the icons. It’s the names too since a lot of them are completely unrelated to the product itself. I actually find myself referring to “Amazon Web Services in Plain English” [0] every once in a while. [0]: https://www.expeditedssl.com/aws-in-plain-english

Speaking of AWS, shouldn't they also hold a poll on naming? I've seen some saner alternatives in the wild: https://www.expeditedssl.com/aws-in-plain-english.

Speaking of which… https://www.expeditedssl.com/aws-in-plain-english

I'm reminded of this site, AWS In Plain English. https://www.expeditedssl.com/aws-in-plain-english

For naming in AWS, this is a must have resource: https://www.expeditedssl.com/aws-in-plain-english

Meanwhile you can use this to get a quick overview of the services offered. Amazon should put this up on their AWS main page. AWS in Plain English https://www.expeditedssl.com/aws-in-plain-english

I quite like this[0] article on what AWS products should have been called. [0] https://www.expeditedssl.com/aws-in-plain-english

michaelbuckbee, please update https://www.expeditedssl.com/aws-in-plain-english

AWS in Plain English: https://www.expeditedssl.com/aws-in-plain-english

We'll need a new entry added to AWS in Plain English: https://www.expeditedssl.com/aws-in-plain-english

What IS it about AWS and the opaque naming of their services?! There is a reason this exists: https://www.expeditedssl.com/aws-in-plain-english

Well, it's a subjective statement as it is my opinion. But for me as a Swede: * The closest retail in Amazon is in GB or Germany, orders takes weeks to reach me which is a mystery since I've ordered stuff from Germany before and they usual deliver within a week. * Closest AWS datacenter is in Ireland, latency is high for nordic countries. * Their documentation is very confusing, you can read all about their web services without understanding one. Leading to sites like this: https://www.expeditedssl.com/aws-in-plain-english But sure, their services works and is probably good for many, but I've never found them any useful at all.

A quick intro to the different AWS services: https://www.expeditedssl.com/aws-in-plain-english

Sure, but AWS don't exactly go out of their way to make themselves comprehensible. The need for an explainer just for their brandnames (https://www.expeditedssl.com/aws-in-plain-english) demonstrates the problem.

https://www.expeditedssl.com/simple-ssl-scanner/scan?target_domain=exp… You only pass 4 out of 5 of our own test :P.