<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Dzil on Hashbang.ca</title>
		<link>https://hashbang.ca/tag/dzil</link>
		<description>Recent content in Dzil on Hashbang.ca</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 02 Apr 2012 15:04:00 -0400</lastBuildDate>
		
			<atom:link href="https://hashbang.ca/tag/dzil/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Dist::Zilla::Plugin::Twitter gets an OAuth update</title>
				<link>https://hashbang.ca/post/distzillaplugintwitter-gets-an-oauth-update</link>
				<pubDate>Mon, 02 Apr 2012 15:04:00 -0400</pubDate>
				<guid>https://hashbang.ca/post/distzillaplugintwitter-gets-an-oauth-update/</guid>
				<description>&lt;p&gt;My pluginbundle for &lt;a href=&#34;http://dzil.org&#34;&gt;&lt;code&gt;Dist::Zilla&lt;/code&gt;&lt;/a&gt; includes, among other things, the Twitter plugin so I can brag on Twitter every time I release a module. Mysteriously, it &lt;a href=&#34;https://rt.cpan.org/Public/Bug/Display.html?id=75995&#34;&gt;broke&lt;/a&gt; one day. Looking at the code, I realized that it was sending my username and password to authenticate. I remember being uneasy with that at the time I set it up, but I quickly forgot, and continued along blithely. &lt;a href=&#34;https://en.wikipedia.org/wiki/OAuth&#34;&gt;OAuth&lt;/a&gt; is an authorization standard that allows users to avoid giving their username &amp;amp; password to a potentially-untrusted application. Using OAuth has been requested &lt;a href=&#34;https://rt.cpan.org/Public/Bug/Display.html?id=72918&#34;&gt;since 2011&lt;/a&gt;, and the &lt;code&gt;401 Unauthorized&lt;/code&gt; error I got indicates that now it is mandatory for Twitter.&lt;/p&gt;&#xA;&lt;p&gt;David Golden offered to let me maintain the module, and I&amp;rsquo;m a sucker, so&amp;hellip; :D&lt;/p&gt;</description>
			</item>
			<item>
				<title>Another word on namespaces</title>
				<link>https://hashbang.ca/post/another-word-on-namespaces</link>
				<pubDate>Sat, 02 Apr 2011 19:58:00 -0400</pubDate>
				<guid>https://hashbang.ca/post/another-word-on-namespaces/</guid>
				<description>&lt;p&gt;Kent Frederic&amp;rsquo;s &lt;a href=&#34;http://blog.fox.geek.nz/2011/01/making-minting-profile-as-cpanized-dist.html&#34;&gt;recent post&lt;/a&gt; about &lt;code&gt;Dist::Zilla&lt;/code&gt; minting profiles was a great overview of the subject, but because I try to follow best practices, I was struck by the section &amp;ldquo;A word on namespaces.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;Kent recommends that if you&amp;rsquo;re making an author pluginbundle, you should name it &lt;code&gt;Dist::Zilla::PluginBundle::Author::$CPANID&lt;/code&gt;. This extra bit of namespacing makes life easier for many people in many ways. I was immediately convinced that he was right, and &lt;a href=&#34;https://twitter.com/#!/_doherty/status/29700267352006657&#34;&gt;moved&lt;/a&gt; my author stuff into appropriate author namespaces.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
