<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Samat Says (Posts about Meta)</title><link>https://blog.samat.org/</link><description></description><atom:link href="https://blog.samat.org/tag/meta.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Fri, 29 Jun 2018 09:25:27 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Going HTTPS</title><link>https://blog.samat.org/2015/12/02/Going-HTTPS/</link><dc:creator>Samat K Jain</dc:creator><description>&lt;div&gt;&lt;p&gt;This &lt;a class="reference external" href="https://blog.samat.org/"&gt;blog&lt;/a&gt;, &lt;a class="reference external" href="https://samat.org/"&gt;my landing page&lt;/a&gt;, &lt;a class="reference external" href="https://wiki.samat.org/"&gt;wiki&lt;/a&gt;, and a few of my other Websites are now being served encrypted over HTTPS (see the lock icon in your address bar?), thanks to &lt;a class="reference external" href="https://letsencrypt.org/"&gt;Let's Encrypt&lt;/a&gt;.
Along with TLS, I've enabled HTTP/2.&lt;/p&gt;
&lt;a class="reference external image-reference" href="https://blog.samat.org/images/2015/12/02/blog.samat.org-SSL-screenshot.png"&gt;&lt;img alt="/images/2015/12/02/blog.samat.org-SSL-screenshot.thumbnail.png" class="align-right" src="https://blog.samat.org/images/2015/12/02/blog.samat.org-SSL-screenshot.thumbnail.png"&gt;&lt;/a&gt;
&lt;p&gt;Hackers won't find anything sensitive on my public Websites, but my private Websites (e.g. my ownCloud and Tiny Tiny RSS instances) have needed more security for a long time.&lt;/p&gt;
&lt;p&gt;Enabling HTTP/2 was very easy, as HTTP/2 support is shipped with the 'http2' module in Apache 2.4.17 and later.
While easy, it wasn't obvious; I've written a &lt;a class="reference external" href="https://blog.samat.org/2015/11/26/Enabling-HTTP2-on-Apache-2.4-on-Debian-Ubuntu/"&gt;tutorial for enabling HTTP/2 on Apache&lt;/a&gt;.
Redirecting non-HTTP connections was trickier than I thought, so I've written a tutorial for &lt;a class="reference external" href="https://blog.samat.org/2015/12/02/Going-HTTPS/"&gt;HTTPS redirects with Apache's mod_rewrite&lt;/a&gt; too.&lt;/p&gt;
&lt;p&gt;I created my TLS certificates as part of &lt;a class="reference external" href="https://community.letsencrypt.org/t/beta-program-announcements/1631"&gt;Let's Encrypt's closed beta&lt;/a&gt;.
I have an unconventional and complex Apache setup (something I'll simplify, one day…)
and because of &lt;a class="reference external" href="https://github.com/letsencrypt/letsencrypt/issues/1531"&gt;bug 1531&lt;/a&gt;, a problem in an upstream library, I can't use the official client the way it was meant to be used (i.e. "install" or "auth" commands).
I don't think I wanted an automated script editing config files on my servers anyway.&lt;/p&gt;
&lt;p&gt;With a lot of fiddling, I've figured out &lt;a class="reference external" href="https://blog.samat.org/2015/12/02/Going-HTTPS/"&gt;how to use the official letsencrypt client reverse proxied through Apache&lt;/a&gt;,
which will let me update certificates regularly without headache.&lt;/p&gt;&lt;/div&gt;</description><category>Apache</category><category>Crypto</category><category>LetsEncrypt.org</category><category>Meta</category><guid>https://blog.samat.org/2015/12/02/Going-HTTPS/</guid><pubDate>Wed, 02 Dec 2015 00:00:00 GMT</pubDate></item><item><title>First post!</title><link>https://blog.samat.org/2014/11/25/first-post/</link><dc:creator>Samat K Jain</dc:creator><description>&lt;div&gt;&lt;p&gt;I'm rebooting this blog. It's a long time coming.&lt;/p&gt;
&lt;p&gt;My first "blog" was back in 2003.
As was fashionable back then, I wrote my own, custom blogging software in PHP.
In 2005, I ditched the custom software and started using Drupal, starting with Drupal 4.5.&lt;/p&gt;
&lt;p&gt;I become fairly skilled with Drupal:
I wrote themes, modules, launched several Websites for myself and clients, ran a Drupal-oriented consulting firm and Web hosting company, and managed scalability at a startup built on Drupal.&lt;/p&gt;
&lt;p&gt;I, very painfully, upgraded those sites and this blog, which started with Drupal 4.5, all the way up to Drupal 7.
It was not easy or fun.&lt;/p&gt;
&lt;p&gt;I had to constantly deal with security upgrades.
Upgrading to new Drupal versions required a witch hunt to find which 3rd party modules were deprecated, which new modules I should use to replace them, and in what ways those modules worked differently.
And then there was all the spam—even with &lt;a class="reference external" href="https://mollom.com/"&gt;Acquia's Mollom&lt;/a&gt; service, too much spam got through, requiring constant moderation.&lt;/p&gt;
&lt;p&gt;The thing that did Drupal in for me was &lt;a class="reference external" href="https://www.drupal.org/SA-CORE-2014-005"&gt;SA-CORE-2014-005&lt;/a&gt;, fixed in Drupal 7.32. After over 10 years of following Drupal security updates, I missed one, by just a few hours—and my site was hacked.
While restoring from my backups, I made a mistake and deleted the most recent one.&lt;/p&gt;
&lt;p&gt;If I wasn't turned off to PHP Web applications before, I'm really, really turned off to them now.
After using Drupal for almost 10 years, I'm switching to something else (at least for my personal stuff).&lt;/p&gt;
&lt;p&gt;Because I didn't want to deal with upgrading or security issues, it meant using something like &lt;a class="reference external" href="https://ghost.org/"&gt;Ghost&lt;/a&gt; or &lt;a class="reference external" href="http://wordpress.org/"&gt;Wordpress&lt;/a&gt; was out.&lt;/p&gt;
&lt;p&gt;The new Samat Says is powered by &lt;a class="reference external" href="http://getnikola.com/"&gt;Nikola&lt;/a&gt;, a static site generator. I looked at &lt;a class="reference external" href="http://jekyllrb.com/"&gt;Jekyll&lt;/a&gt;, &lt;a class="reference external" href="http://blogofile.com/"&gt;Blogofile&lt;/a&gt;, &lt;a class="reference external" href="http://blog.getpelican.com/"&gt;Pelican&lt;/a&gt;, but Nikola seemed the easiest for me to understand, extend, and most importantly has a vibrant, active community.&lt;/p&gt;
&lt;p&gt;For a long time, I cared about owning my comments and not being tied to a 3rd party service.
After dealing with all the spam my old Drupal site received, I now care quite a bit less.
I'd like to move to a self-hosted, or better yet federated, commenting solution in the future but for the time being I'm using &lt;a class="reference external" href="https://www.disquis.com/"&gt;Disqus&lt;/a&gt;.
I haven't figured out how I will migrate old comments yet.&lt;/p&gt;
&lt;p&gt;Worth mentioning: you may have noticed this isn't an actual first post.
I'm slowly migrating content from the &lt;a class="reference external" href="http://oldblog.samat.org/"&gt;old blog&lt;/a&gt; (probably only the popular bits) from my old Drupal installation over to this Nikola-powered one.&lt;/p&gt;&lt;/div&gt;</description><category>Meta</category><guid>https://blog.samat.org/2014/11/25/first-post/</guid><pubDate>Tue, 25 Nov 2014 00:00:00 GMT</pubDate></item><item><title>samat.org upgraded to Drupal 6.5</title><link>https://blog.samat.org/2008/10/08/samatorg-upgraded-drupal-65/</link><dc:creator>Samat K Jain</dc:creator><description>&lt;div&gt;&lt;p&gt;After over 2 years, I've finally upgraded this website from Drupal 4.7 to 6.5. It's something I've been meaning to do for a long while. Hopefully, with the new Drupal version management scheme I've developed for &lt;a href="http://rhombic.net/"&gt;Rhombic Networks&lt;/a&gt; (article coming soon), along with the advancements in update management within Drupal itself, it will be much easier to keep current with updates.&lt;/p&gt;
&lt;p&gt;Like &lt;a href="https://blog.samat.org/weblog/20060511-upgrading-samat-org-to-drupal-4-7.html"&gt;I discussed my last upgrade to Drupal 4.7&lt;/a&gt;, there are several new features I'm excited about:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://openid.net/"&gt;OpenID&lt;/a&gt; support. Instead of having to leave comments anonymously, or waste time creating an account, use your OpenID. If you have your own domain, check out &lt;a href="http://simonwillison.net/2006/Dec/19/openid/"&gt;Simon Willison's article how to turn your blog into an OpenID&lt;/a&gt;. I've noticed with an OpenID, I find myself commenting and participating on sites much more often. Hopefully I can expect the same of others with my website.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://drupal.org/project/mollom"&gt;Drupal's Mollom module&lt;/a&gt;. The old site was getting hit with hundreds of spam comments a day. I gave up trying to filter them all, which meant it took a long time for users' comments to show up on the site. Hopefully, with Mollom, that will change, and I will be able to screen comments again instead of screening spam. I like &lt;a href="http://mollum.com"&gt;Mollom&lt;/a&gt; more than I do &lt;a href="http://akismet.com"&gt;Akismet&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://drupal.org/project/atom"&gt;Drupal's Atom module&lt;/a&gt;. &lt;acronym title="Really Simple Syndication"&gt;RSS&lt;/acronym&gt; sucks. You can now aggregate this blog via an Atom feed.  Like most home pages on the Internet, most surfers find content on this site via search engines, or via their feed reader.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Hopefully, I can get my development mojo going and finish porting my &lt;a href="http://samat.org/drupal-themes/sands"&gt;Drupal Sands and Sands_CSS themes&lt;/a&gt; to Drupal 5.x and 6.x. I'm sorry I took so long!&lt;/p&gt;&lt;/div&gt;</description><category>Meta</category><guid>https://blog.samat.org/2008/10/08/samatorg-upgraded-drupal-65/</guid><pubDate>Wed, 08 Oct 2008 00:00:00 GMT</pubDate></item></channel></rss>