Twickr is a small tool we’re using @Netlify to get tweets of interest delivered to our Slack.

For us Slack has turned into a sort of command center, where we process support requests, discuss features, share drafts of mails or blog posts, get operational status messages and alerts.

Like most other startups we have a few stored twitter searches we tend to run all the time, to keep up with all that’s going on in our field. Terms like “netlify” and ”static generators”, etc..

So we thought it would be nice if we could just get new notifications in Slack whenever someone tweets with such terms.

Welcome.

A lot of things have happened since our last newsletter.

Netlify

Woohoo!
We’ve launched netlify.com and are now live, both with hosting of static sites and apps (as you knew it from bitballoon.com) & our continuous deployment service.

We want to thank our beta-testers for all their help!

And thanks so much to everyone who has already signed on. We are getting raving feedback, and are really excited to see our work put to such good use as well. It sure seems like we’re on to something :)

Today pretty much every front-end developer is familiar with Amazon’s amazing Simple Storage Service, or S3, and some use it for hosting their front-end projects, so I thought I would take the opportunity to do a proper writeup about the differences between Netlify’s static hosting service and S3.

In short: S3 manages files. Netlify manages sites.

“Does HTTPS really make any sense for a static web site?”

We’ve heard this a couple of times when talking about Netlify’s HTTPS support.

It might seem like a static site is already plenty secure: there’s no moving parts, no risk of SQL injection, no openings for XSS attacks, no cookies to hijack, no personalized data sent over the wire, etc, etc, etc…

So why spend extra and take even the smallest performance hit just to add HTTPS to a static site?

Here’s 5 good reasons you should switch to HTTPS for your static site today: