<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Zack Dunn</title>
    <description>The latest articles on Forem by Zack Dunn (@zcdunn).</description>
    <link>https://forem.com/zcdunn</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F56751%2Fecc5fea2-f1c1-4978-8a90-a5990baf80e8.jpeg</url>
      <title>Forem: Zack Dunn</title>
      <link>https://forem.com/zcdunn</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/zcdunn"/>
    <language>en</language>
    <item>
      <title>Dev.to Interaction Bar</title>
      <dc:creator>Zack Dunn</dc:creator>
      <pubDate>Wed, 19 Sep 2018 14:26:41 +0000</pubDate>
      <link>https://forem.com/zcdunn/devto-interaction-bar-4p04</link>
      <guid>https://forem.com/zcdunn/devto-interaction-bar-4p04</guid>
      <description>&lt;p&gt;I'm not a fan of persistent chrome in apps, especially on mobile. I don't like having screen space taken and chrome distracts me from reading the actual content. While I can and do use extensions on desktop to get rid of the bar, Chrome for Android doesn't support extensions so I'm stuck with the bar. &lt;/p&gt;

&lt;p&gt;My proposal is that Dev.to introduce &lt;a href="https://developer.mozilla.org/en-US/docs/Web/CSS/--*"&gt;CSS variables&lt;/a&gt; to control the position of the interaction bar. CSS variables, or custom properties, are set in a &lt;code&gt;::root&lt;/code&gt; rule and always begin with &lt;code&gt;--&lt;/code&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;::root {
    --interaction-bar-position: fixed;
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Their value can be any valid CSS value. To use the variable, use the &lt;code&gt;var&lt;/code&gt; function.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;.container .article-actions {
    position: var(--interaction-bar-position);
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then override the variable only in specific rules.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;.container .article-actions.relative {
    --interaction-bar-position: relative;
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And that's it. By default, the interaction bar will be fixed at the bottom. A simple checkbox in settings could control the presence of the &lt;code&gt;relative&lt;/code&gt; class on the &lt;code&gt;article-actions&lt;/code&gt; element.&lt;/p&gt;

&lt;p&gt;Here's the complete CSS.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;::root {
    --interaction-bar-position: fixed;
}

.container .article-actions.relative {
    --interaction-bar-position: relative;
}

.container .article-actions {
    position: var(--interaction-bar-position);
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
      <category>meta</category>
      <category>design</category>
      <category>css</category>
    </item>
    <item>
      <title>Implement ActivityPub?</title>
      <dc:creator>Zack Dunn</dc:creator>
      <pubDate>Thu, 19 Jul 2018 15:10:24 +0000</pubDate>
      <link>https://forem.com/zcdunn/implement-activitypub-43c9</link>
      <guid>https://forem.com/zcdunn/implement-activitypub-43c9</guid>
      <description>&lt;p&gt;Hi. I'd like to propose Dev.to implement &lt;a href="https://www.w3.org/TR/activitypub/"&gt;ActivityPub&lt;/a&gt;. ActivityPub is a W3C standard for decentralized social networking. It's currently implemented by a few different projects, including &lt;a href="https://pleroma.social/"&gt;Pleroma&lt;/a&gt;, &lt;a href="https://joinmastodon.org"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://joinpeertube.org"&gt;PeerTube&lt;/a&gt;, &lt;a href="https://github.com/Plume-org/Plume"&gt;Plume&lt;/a&gt;, &lt;a href="https://pixelfed.social/"&gt;PixelFed&lt;/a&gt;, and more are coming every day. GitLab and Ghost both have open issues discussing adding support.&lt;/p&gt;

&lt;p&gt;Adding ActivityPub support would expose dev.to to more than a million new users. Users on the other platforms would be able to follow and interact with dev.to users. Dev.to would gain much larger exposure, while still retaining full control of its own moderation. The lead dev of Mastodon wrote a post that explains the benefits &lt;a href="https://blog.joinmastodon.org/2018/06/why-activitypub-is-the-future/"&gt;here&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thanks for taking the time to read this. If you have any questions, I'd be happy to answer them here or over at my &lt;a href="https://toot.cafe/@zack"&gt;Mastodon account&lt;/a&gt;. &lt;/p&gt;

</description>
      <category>meta</category>
      <category>proposal</category>
    </item>
  </channel>
</rss>
