haskellweekly · tfausak · Apr 4, 2018 · Mar 8, 2018 · Mar 8, 2018 · Mar 8, 2018
diff --git a/content/issues/10.markdown b/content/issues/10.markdown
@@ -12,7 +12,7 @@
 
     > The pattern Identity element is all about defining the concept of emptiness, and is a good introduction to algebraically modeling programming concepts.
 
--   [The Unreasonable Effectiveness of Reasoning: Eliminating Bottom](http://typed.funops.co/tutorials/2016/05/25/unreasonable-effectiveness-of-reasoning-understanding-bottom.html)
+-   [The Unreasonable Effectiveness of Reasoning: Eliminating Bottom](https://github.com/typedops/funops/blob/f3a2983f655e2d920003ff3b802b3ad8e16f9d32/src/main/tut/2016-05-31-unreasonable-effectiveness-of-reasoning-understanding-bottom.md)
 
     > Any time your code or other dependencies return a bottom value from a function you have violated the contract that allows you to reason mathematically about your code.
 

diff --git a/content/issues/35.markdown b/content/issues/35.markdown
@@ -10,7 +10,7 @@ these are the most-clicked links of 2016.
 4.  [Powerline-hs](https://github.com/rdnetto/powerline-hs/blob/be579f68840c1bb7709d169ea2453a62fafe62d6/README.md)
 5.  [HyperHaskell: the strongly hyped Haskell interpreter](https://mail.haskell.org/pipermail/haskell/2016-October/025010.html)
 6.  [Good way to convert between ad-hoc polymorphic functions and parametric polymorphic ones](http://stackoverflow.com/questions/38326420/good-way-to-convert-between-ad-hoc-polymorphic-functions-and-parametric-polymorp)
-7.  [The unreasonable effectiveness of reasoning: eliminating bottom](http://typed.funops.co/tutorials/2016/05/25/unreasonable-effectiveness-of-reasoning-understanding-bottom.html)
+7.  [The unreasonable effectiveness of reasoning: eliminating bottom](https://github.com/typedops/funops/blob/f3a2983f655e2d920003ff3b802b3ad8e16f9d32/src/main/tut/2016-05-31-unreasonable-effectiveness-of-reasoning-understanding-bottom.md)
 8.  [Modern function programming: part 2](http://degoes.net/articles/modern-fp-part-2)
 9.  [Thoughts on Haskell](http://get-finch.com/2016/09/26/thoughts_on_haskell.html)
 10. [ML modules versus Haskell type classes](http://stackoverflow.com/questions/36927169/ml-modules-vs-haskell-type-classes)

diff --git a/content/issues/73.markdown b/content/issues/73.markdown
@@ -61,7 +61,7 @@ If so, consider [advertising with us](https://haskellweekly.news/advertising.htm
 -   [Checking it's all in place: Placeholders and dependent types](https://mmhaskell.com/blog/2017/9/18/checking-its-all-in-place-placeholders-and-dependent-types)
 -   [Compose Conference 2017](https://www.youtube.com/watch?v=79zzgL75K8Q&list=PLNoHgLVTxtaoolkQo4hLy4ZsA1prUJ51m)
 -   [Functional programming in Haskell: Supercharge your coding](https://www.futurelearn.com/courses/functional-programming-haskell)
--   [Infernal types](https://goc.vivint.com/problems/hm)
+-   [Infernal types](http://goc.vivint.com/problems/hm)
 -   [Making Google tasks better: Part 2](https://haskell.fun/2017/09/17/making-google-tasks-better-part-2/)
 -   [Shake 0.16: Revised rule definitions](https://neilmitchell.blogspot.co.uk/2017/09/shake-016-revised-rule-definitions.html)
 

diff --git a/content/issues/76.markdown b/content/issues/76.markdown
@@ -61,7 +61,7 @@ Tweet us at [@HaskellWeekly](https://twitter.com/haskellweekly) or [open a pull
 -   [`Monoidal` vs `Traversing`](http://oleg.fi/gists/posts/2017-10-05-monoidal-vs-traversing.html)
 -   [Call for contributions: Haskell Communities and Activities Report](https://mail.haskell.org/pipermail/haskell-cafe/2017-October/127970.html)
 -   [Edward Kmett: Monoidal parsing](https://www.youtube.com/watch?v=Txf7swrcLYs)
--   [Growing a date picker in Reflex: Part 1](https://blog.qfpl.io/posts/reflex/widgets/growing-a-date-picker-1/)
+-   [Growing a date picker in Reflex: Part 1](https://blog.qfpl.io/posts/reflex/widget/growing-a-date-picker-1/)
 -   [Higher-order abstract syntax for Cartesian closed categories](http://blog.functorial.com/posts/2017-10-08-HOAS-CCCs.html)
 -   [Making your brain tingle: Explaining monads](http://blogs.intevation.de/wilde/haskell/monads/)
 -   [micro-ci: A tiny CI server built around GitHub and Nix](https://github.com/ocharles/micro-ci)

diff --git a/content/issues/80.markdown b/content/issues/80.markdown
@@ -18,7 +18,7 @@ Tweet us at [@HaskellWeekly](https://twitter.com/haskellweekly) or [open a pull
 
     > Edward Kmett recently posted a puzzling gist seemingly showing that at the type level, the `()` kind has more than one inhabitant. The goal of this post is to explain what's going on.
 
--   [Authorization in Servant: Walkthrough](https://ibnuda.gitlab.io/636452721192300168_authorizationinservant.html)
+-   [Authorization in Servant: Walkthrough](https://ibnuda.gitlab.io/2017-11-03-authorization-in-servant.html)
 
     > This article is about `servant-server` 0.11's `experimental-auth` which is still in experimental stage. Deployment in production is not encouraged. And yes, I know about `servant-auth` but I haven't read it thoroughly, yet.
 

diff --git a/content/issues/91.markdown b/content/issues/91.markdown
@@ -33,7 +33,7 @@ Open an issue or pull request [on GitHub](https://github.com/haskellweekly/haske
 
     > Last week I gave a talk at Off the Beaten Track 2018 about something that Richard Eisenberg, Harley Eades and I have been thinking about recently: namely, how to generate good interactive error explanations for programmers, especially for type errors.
 
--   [`LambdaCase` in the wild](https://storm-country.com/blog/LambdaCase)
+-   [`LambdaCase` in the wild](http://storm-country.com/blog/LambdaCase)
 
     > Of all the many, many Haskell language extensions supported by GHC, `LambdaCase` is one of my favorites. It has essentially no downside, does not conflict with any existing code, and introduces a single, simple, useful new construct to the language.
 

diff --git a/content/issues/92.markdown b/content/issues/92.markdown
@@ -17,7 +17,7 @@ Open an issue or pull request [on GitHub](https://github.com/haskellweekly/haske
 
     > In our previous post, we define a common problem around reproducible build plans. The solution we desired was some form of cryptographic hash based configuration and download system for packages, package metadata, and snapshot definitions.
 
--   [Design patterns in Haskell: The strategy pattern](https://storm-country.com/blog/gof-strategy)
+-   [Design patterns in Haskell: The strategy pattern](http://storm-country.com/blog/gof-strategy)
 
     > This is part one of a series of posts translating the Gang of Four design patterns for object-oriented languages into Haskell. It is intended to be an expansion of Edward Z. Yang's Design Patterns in Haskell, elaborating each pattern into its own post.