<story><title>A more privacy-friendly blog</title><url>https://vincent.bernat.im/en/blog/2018-more-privacy-blog</url></story><parent_chain></parent_chain><comment><author>cagrimmett</author><text>Awesome! I dumped Disqus and Google Analytics earlier this year, too. I hadn&amp;#x27;t thought about Google Fonts, so I&amp;#x27;ll dump that soon, too.&lt;p&gt;Since you are using CloudFront, I highly recommend &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;s3stat.com&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;s3stat.com&lt;/a&gt; for analytics. It grabs CloudFront&amp;#x27;s (or S3&amp;#x27;s) server access logs and visualizes them.&lt;p&gt;For search, I like this method Mat Hayward uses for Jekyll: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;mathaywarduk&amp;#x2F;jekyll-search&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;mathaywarduk&amp;#x2F;jekyll-search&lt;/a&gt; 
Dump the site contents out into a JSON file with the titles and links accessible, crawl through the JSON file with javascript whenever someone runs a search, then display the results. I know you use Hyde instead of Jekyll, but you can port over the general idea.</text></comment>
<story><title>A more privacy-friendly blog</title><url>https://vincent.bernat.im/en/blog/2018-more-privacy-blog</url></story><parent_chain></parent_chain><comment><author>theandrewbailey</author><text>&amp;gt; As it is unlikely that more than three people will use the search engine in a year, this seems a good idea to not spend too much time on this non-essential feature.&lt;p&gt;I disagree. When I want to remember something, I blog about it. When I implemented a search feature on my site, it was a godsend, and wondered why I had overlooked it for so long. Finding something I had blogged about years ago wasn&amp;#x27;t a pain anymore, since a box is right there.</text></comment>