From 25e8050ed8f9c627493b51f8e9c9a730c71ddcd4 Mon Sep 17 00:00:00 2001 From: elijah Date: Thu, 22 Aug 2013 15:50:27 -0700 Subject: css fixes --- pages/about-us/news/2012/the-big-seven/en.haml | 3 +++ 1 file changed, 3 insertions(+) (limited to 'pages/about-us') diff --git a/pages/about-us/news/2012/the-big-seven/en.haml b/pages/about-us/news/2012/the-big-seven/en.haml index 7d24be0..b8b6fa4 100644 --- a/pages/about-us/news/2012/the-big-seven/en.haml +++ b/pages/about-us/news/2012/the-big-seven/en.haml @@ -1,7 +1,10 @@ - @title = "The big seven hard problems in secure communication" - @author = "Elijah" - @posted_at = "2013-08-22" +- @more = true +- @layout = 'application' - @preview = capture_haml do If you take a survey of interesting initiatives to create more secure communication, a pattern starts to emerge: it seems that any serious attempt to build a system for secure message communication eventually comes up against the following list of seven hard problems. These problems appear to be present regardless of which architectural approach you take (centralized authority, distributed peer-to-peer, or federated servers). + = act_as('hard-problems') \ No newline at end of file -- cgit v1.2.3