Upgrade http to https

posts/2014-09-15-Rust-1.0.md

@@ -113,7 +113,7 @@ starting point. This is very true. The goal for Rust 1.0 is to be an
 flexible substrate for building efficient libraries -- but libraries
 aren't any good if nobody can find them or they are difficult to install.
 
-Enter [Cargo, the Rust package manager](http://crates.io). Cargo has
+Enter [Cargo, the Rust package manager](https://crates.io). Cargo has
 been undergoing rapid development lately and is already quite
 functional. By the time
 1.0 is released, we plan to also have a central repository up and
@@ -128,8 +128,8 @@ we don't plan on changing that. Once we start having stable releases,
 however, we'll also build up a bit more infrastructure. Our plan is to
 adopt the "channel" system used by many other projects such as
 [Firefox](https://www.mozilla.org/en-US/firefox/channel/),
-[Chrome](http://www.chromium.org/getting-involved/dev-channel), and
-[Ember.js](http://emberjs.com/builds/).
+[Chrome](https://www.chromium.org/getting-involved/dev-channel), and
+[Ember.js](https://emberjs.com/builds/).
 
 The idea is that there are three channels: Nightly, Beta, and
 Stable. The Nightly channel is what you use if you want the latest
@@ -165,7 +165,7 @@ it already has. I can't wait to see what comes out of it.
 [k2]: https://github.com/jvns/puddle
 [k3]: https://github.com/pczarn/rustboot
 [k4]: https://github.com/ryanra/RustOS
-[stability]: http://doc.rust-lang.org/std/stability.html
+[stability]: https://doc.rust-lang.org/std/stability.html
 [dst]: https://github.com/rust-lang/rust/commit/7932b719ec2b65acfa8c3e74aad29346d47ee992
 [cd]: https://github.com/rust-lang/rfcs/blob/master/text/0114-closures.md
 [wc]: https://github.com/rust-lang/rfcs/pull/135

posts/2014-10-30-Stability.md

@@ -6,7 +6,7 @@ description: "The upcoming Rust 1.0 release means a lot, but most fundamentally
 ---
 
 The upcoming Rust 1.0 release means
-[a lot](http://blog.rust-lang.org/2014/09/15/Rust-1.0.html), but most
+[a lot](https://blog.rust-lang.org/2014/09/15/Rust-1.0.html), but most
 fundamentally it is a commitment to stability, alongside our
 long-running commitment to safety.
 
@@ -93,7 +93,7 @@ After extensive discussion, we plan to release globs and macros as
 stable at 1.0. For globs, we believe we can address problems in a
 backwards-compatible way. For macros, we will likely provide an
 alternative way to define macros (with better
-[hygiene](http://en.wikipedia.org/wiki/Hygienic_macro)) at some later
+[hygiene](https://en.wikipedia.org/wiki/Hygienic_macro)) at some later
 date, and will incrementally improve the "macro rules" feature until
 then. The 1.0 release will stabilize all current macro support,
 including import/export.
@@ -131,7 +131,7 @@ standard library, but you can opt into experimental APIs from other
 libraries. The Rust release channels are about making upgrading *Rust
 itself* (the compiler and standard library) painless.
 
-Library authors should follow [semver](http://semver.org/); we will
+Library authors should follow [semver](https://semver.org/); we will
 soon publish an RFC defining how library stability attributes and
 semver interact.
 

posts/2014-11-20-Cargo.md

@@ -9,20 +9,20 @@ Today it is my pleasure to announce that [crates.io](https://crates.io/) is
 online and ready for action. The site is a central location to
 discover/download Rust crates, and Cargo is ready to start publishing to it
 today. For the next few months, we are asking that intrepid early adopters
-[help us](http://doc.crates.io/crates-io.html) get the registry battle-tested.
+[help us](https://doc.crates.io/crates-io.html) get the registry battle-tested.
 
 Until Rust itself is stable early next year, registry dependencies will need to
 be updated often. Production users may want to continue using git dependencies
 until then.
 
 ## What is Cargo?
 
-Cargo is a package manager [for Rust](http://www.rust-lang.org/), [in
+Cargo is a package manager [for Rust](https://www.rust-lang.org/), [in
 Rust](https://github.com/rust-lang/cargo). Managing dependencies is a
 fundamentally difficult problem, but fortunately over the last decade there's
 been a lot of progress in the design of package managers. Designed by Carl
 Lerche and Yehuda Katz, Cargo follows the tradition of successes like
-[Bundler](http://bundler.io/) and [NPM](https://www.npmjs.org/):
+[Bundler](https://bundler.io/) and [NPM](https://www.npmjs.org/):
 
 1. Cargo leverages crates.io to foster a thriving community of crates that can
    easily interoperate with one another and last for years to come.
@@ -42,7 +42,7 @@ its core mechanics.
 
 Cargo makes depending on third-party code as easy as depending on the standard
 library. When using Cargo, each crate will have an associated
-[manifest](http://doc.crates.io/manifest.html) to describe itself and its
+[manifest](https://doc.crates.io/manifest.html) to describe itself and its
 dependencies. Adding a new dependency is now as simple as adding one line to the
 manifest, and this ease has allowed Cargo in just a few short months to enable a
 large and growing network of Rust projects and libraries which were simply
@@ -62,19 +62,19 @@ have largely just downloaded dependencies directly from the source GitHub
 repository, but the primary source will now be shifting to crates.io.
 
 Other programming language communities have been quite successful with this form
-of central repository. For example [rubygems.org](http://rubygems.org/) is your
-one-stop-shop for [Bundler](http://bundler.io/) dependencies and
+of central repository. For example [rubygems.org](https://rubygems.org/) is your
+one-stop-shop for [Bundler](https://bundler.io/) dependencies and
 [npmjs.org](https://www.npmjs.org/) has had over 600 million downloads in just
 this month alone! We intend for crates.io to serve a similar role for Rust as a
 critical piece of infrastructure for [Rust's long-term stability story at
 1.0][stab].
 
-[stab]: http://blog.rust-lang.org/2014/10/30/Stability.html
+[stab]: https://blog.rust-lang.org/2014/10/30/Stability.html
 
 ## Versioning and Reproducible Builds
 
 Over the past few years, the concept of [Semantic
-Versioning](http://semver.org/) has gained traction as a way for library
+Versioning](https://semver.org/) has gained traction as a way for library
 developers to easily and clearly communicate with users when they make breaking
 changes. The core idea of semantic versioning is simple: each new release is
 categorized as a minor or major release, and only major releases can introduce
@@ -93,7 +93,7 @@ then distributed to collaborators of applications to ensure that the crates
 being built remain the same from one build to the next, across times, machines,
 and environments.
 
-[lock]: http://doc.crates.io/guide.html#cargo.toml-vs-cargo.lock
+[lock]: https://doc.crates.io/guide.html#cargo.toml-vs-cargo.lock
 
 ## Building Code
 
@@ -114,7 +114,7 @@ provide some nice standard features as well as some Rust-specific features:
 
 * Cargo generates documentation for all crates in a dependency graph, and it can
   even run [Rust's documentation
-  tests](http://doc.rust-lang.org/rustdoc.html#testing-the-documentation) to
+  tests](https://doc.rust-lang.org/rustdoc.html#testing-the-documentation) to
   ensure examples in documentation stay up to date.
 
 * Cargo can run a [build script][build-scripts] before any crate is compiled to
@@ -125,7 +125,7 @@ provide some nice standard features as well as some Rust-specific features:
   simply specifying a `--target` options and Cargo will manage tasks such as
   compiling plugins and other build dependencies for the right platform.
 
-[build-scripts]: http://doc.crates.io/build-script.html
+[build-scripts]: https://doc.crates.io/build-script.html
 
 ## What else is in store?
 
@@ -135,7 +135,7 @@ stable compiler, which should be [coming soon][road-to-1]! There are also a
 number of extensions to crates.io such as a hosted documentation service or a CI
 build infrastructure hook which could be built out using the crates.io APIs.
 
-[road-to-1]: http://blog.rust-lang.org/2014/09/15/Rust-1.0.html
+[road-to-1]: https://blog.rust-lang.org/2014/09/15/Rust-1.0.html
 
 This is just the beginning for crates.io, and I'm excited to start finding all
 Rust crates from one location. I can't wait to see what the registry looks like

posts/2014-12-12-1.0-Timeline.md

@@ -61,7 +61,7 @@ Six weeks later, we will begin the beta period:
 
 * Release channels take effect: feature gates and `#[unstable]` APIs are
   available on nightly builds, but not on the beta. This change is part of
-  [our commitment to stability](http://blog.rust-lang.org/2014/10/30/Stability.html).
+  [our commitment to stability](https://blog.rust-lang.org/2014/10/30/Stability.html).
 
 Unlike the alpha cycle, where we still expect some minor breakage, the beta
 cycle should *not* involve breakage unless a very significant problem is
@@ -76,7 +76,7 @@ Finally, after one or more beta cycles, we will have produced a release
 candidate that is **ready for the world**:
 
 * We are ready to promise stability --
-  [hassle-free upgrades](http://blog.rust-lang.org/2014/10/30/Stability.html) --
+  [hassle-free upgrades](https://blog.rust-lang.org/2014/10/30/Stability.html) --
   for the duration of the 1.X series.
 
 * The core documentation (The Guide/Guides) is fully in sync with the language and
@@ -86,7 +86,7 @@ We are incredibly excited for Rust to reach this point.
 
 ### What this means for the ecosystem
 
-With the [launch](http://blog.rust-lang.org/2014/11/20/Cargo.html) of Cargo and
+With the [launch](https://blog.rust-lang.org/2014/11/20/Cargo.html) of Cargo and
 [crates.io](https://crates.io/), Rust's ecosystem has already seen significant expansion, but
 it still takes a lot of work to track Rust's nightly releases. Beginning with
 the alpha release, and especially approaching beta1, this will change
@@ -100,6 +100,6 @@ first time.
 
 Let's do this!
 
-[why Rust is reaching 1.0]: http://blog.rust-lang.org/2014/09/15/Rust-1.0.html
-[6-week train model]: http://blog.rust-lang.org/2014/10/30/Stability.html
-[pre-release]: http://semver.org/
+[why Rust is reaching 1.0]: https://blog.rust-lang.org/2014/09/15/Rust-1.0.html
+[6-week train model]: https://blog.rust-lang.org/2014/10/30/Stability.html
+[pre-release]: https://semver.org/

posts/2014-12-12-Core-Team.md

@@ -32,15 +32,15 @@ situation.
 Thanks Yehuda and Steve for all your hard work, and welcome to the core team!
 
 [Rust core team]: https://github.com/rust-lang/rust/wiki/Note-core-team
-[Ember.js]: http://emberjs.com/team/
+[Ember.js]: https://emberjs.com/team/
 [Skylight]: https://www.skylight.io/
-[Tilde]: http://www.tilde.io/
-[Rust guide]: http://doc.rust-lang.org/guide.html
-[Rust for Rubyists]: http://www.rustforrubyists.com/
-[Reddit]: http://www.reddit.com/r/rust
+[Tilde]: https://www.tilde.io/
+[Rust guide]: https://doc.rust-lang.org/guide.html
+[Rust for Rubyists]: https://www.rustforrubyists.com/
+[Reddit]: https://www.reddit.com/r/rust
 [HackerNews]: https://news.ycombinator.com/
 [RFCs repo]: https://github.com/rust-lang/rfcs/
-[Ruby on Rails]: http://rubyonrails.org/
-[jQuery]: http://jquery.com/
-[Bundler]: http://bundler.io/
-[TC39 language committee]: http://www.ecma-international.org/memento/TC39.htm
+[Ruby on Rails]: https://rubyonrails.org/
+[jQuery]: https://jquery.com/
+[Bundler]: https://bundler.io/
+[TC39 language committee]: https://www.ecma-international.org/memento/TC39.htm