<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>changes &amp;mdash; Write.as Blog</title>
    <link>https://write.as/blog/tag:changes</link>
    <description>What we&#39;re writing.</description>
    <pubDate>Fri, 28 Aug 2026 17:16:12 +0000</pubDate>
    <image>
      <url>https://i.snap.as/esrYxGut.png</url>
      <title>changes &amp;mdash; Write.as Blog</title>
      <link>https://write.as/blog/tag:changes</link>
    </image>
    <item>
      <title>Requiring an Email Address</title>
      <link>https://write.as/blog/requiring-an-email-address?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[We’re making a change today that will affect new writers looking to join Write.as. Due to a couple issues we’ve encountered recently, we’ll now require an email address to create a new Write.as account.&#xA;&#xA;While our high privacy standards remain unchanged, this new requirement will help us reduce abuse and provide a better experience for our writers and customers. Read on for more.&#xA;&#xA;!--more--&#xA;&#xA;Your Privacy&#xA;&#xA;First, we’ve always prided ourselves on the privacy we offer our users — from minimizing data collection to resisting unfounded user data requests from entities both public and private. With this new email requirement, none of that changes.&#xA;&#xA;As you can see in our Privacy Policy, we still maintain our stringent data practices, never sharing your personal information with third parties for marketing or other reasons, and encrypting data like email addresses in transit and at rest.&#xA;&#xA;Though we recommend all Write.as users add an email address to their account, this new requirement only affects people who haven’t signed up yet. Going forward, an email address is no longer optional — everyone will need to supply that and verify that they own it in order to start a Write.as blog.&#xA;&#xA;Why Make This Change&#xA;&#xA;There are two main motivations for this change: a botnet attack we endured last month, and the customer service workload we’ve seen increase over the years.&#xA;&#xA;Over the course of July, we encountered a distributed attack on our service from bots creating Write.as accounts only to test out stolen credit card numbers. Thankfully, with our payment processor Stripe behind the scenes, we were able to prevent and block most fraudulent charges — but many still got through.&#xA;&#xA;We’ve since refunded these fraudulent charges to their rightful owners, blocked the attacks, and put systems in place to prevent this in the future. Going forward, we remain vigilant for attacks like this, and will continue refining the automated protections we have in place.&#xA;&#xA;In the coming weeks, new customers will see additional data requirements around payments — standard billing information you’d supply anywhere on the web — designed to further prevent these fraudulent attempts. This is critically needed, as this activity cost us time and extra revenue losses from both refunds and chargebacks (where we incur a much larger fee).&#xA;&#xA;Customer Service&#xA;&#xA;Otherwise, we’ve seen our customer service workload increase over the years due to accounts without an email address on them. While we’ve always encouraged users not to share this information with us if they don’t want to, we’ve now seen more issues than not from it.&#xA;&#xA;Without an email address on your account, we’re unable to send payment receipts, upcoming renewal reminders, or password-reset emails. And if you ever lose access to your account due to a forgotten password (hey, it happens!), a human on the team has to do an extra level of sleuthing, while maintaining our security standards, just to restore your access to your work.&#xA;&#xA;At this point, we’ve decided it’s more important that writers have their email address on their Write.as account than the minor privacy enhancement they might get from withholding it. While still not required, we strongly suggest that any current Write.as users add an email address to their account today, if they haven’t already.&#xA;&#xA;---&#xA;&#xA;We hope everyone will find this minor change reasonable, and as always, we thank you for continuing to trust us with your writing!&#xA;&#xA;If you have any questions or concerns, we hope you’ll give your feedback on Remark.as (a href=&#34;https://remark.as/p/blog/requiring-an-email-address&#34;Discuss.../a) or by replying in the fediverse @write_as@writing.exchange.&#xA;&#xA;#changes #email]]&gt;</description>
      <content:encoded><![CDATA[<p>We’re making a change today that will affect new writers looking to join Write.as. Due to a couple issues we’ve encountered recently, we’ll now require an email address to create a <strong>new</strong> Write.as account.</p>

<p>While our high privacy standards remain unchanged, this new requirement will help us reduce abuse and provide a better experience for our writers and customers. Read on for more.</p>



<h2 id="your-privacy">Your Privacy</h2>

<p>First, we’ve always prided ourselves on the privacy we offer our users — from minimizing data collection to resisting unfounded user data requests from entities both public and private. With this new email requirement, <strong>none of that changes</strong>.</p>

<p>As you can see in our <a href="https://write.as/privacy">Privacy Policy</a>, we still maintain our stringent data practices, never sharing your personal information with third parties for marketing or other reasons, and encrypting data like email addresses in transit <em>and</em> at rest.</p>

<p>Though we recommend all Write.as users <a href="https://write.as/me/settings">add an email address</a> to their account, this new requirement only affects people who haven’t signed up yet. Going forward, an email address is no longer optional — everyone will need to supply that <em>and</em> verify that they own it in order to start a Write.as blog.</p>

<h2 id="why-make-this-change">Why Make This Change</h2>

<p>There are two main motivations for this change: a botnet attack we endured last month, and the customer service workload we’ve seen increase over the years.</p>

<p>Over the course of July, we encountered a distributed attack on our service from bots creating Write.as accounts only to test out stolen credit card numbers. Thankfully, with our payment processor Stripe behind the scenes, we were able to prevent and block most fraudulent charges — but many still got through.</p>

<p>We’ve since refunded these fraudulent charges to their rightful owners, blocked the attacks, and put systems in place to prevent this in the future. Going forward, we remain vigilant for attacks like this, and will continue refining the automated protections we have in place.</p>

<p>In the coming weeks, <strong>new</strong> customers will see additional data requirements around payments — standard billing information you’d supply anywhere on the web — designed to further prevent these fraudulent attempts. This is critically needed, as this activity cost us time <em>and</em> extra revenue losses from both refunds and chargebacks (where we incur a much larger fee).</p>

<h3 id="customer-service">Customer Service</h3>

<p>Otherwise, we’ve seen our customer service workload increase over the years due to accounts without an email address on them. While we’ve always encouraged users not to share this information with us if they don’t want to, we’ve now seen more issues than not from it.</p>

<p>Without an email address on your account, we’re unable to send payment receipts, upcoming renewal reminders, or password-reset emails. And if you ever lose access to your account due to a forgotten password (<em>hey, it happens!</em>), a human on the team has to do an extra level of sleuthing, while maintaining our security standards, just to restore your access to your work.</p>

<p>At this point, we’ve decided it’s more important that writers have their email address on their Write.as account than the minor privacy enhancement they might get from withholding it. While still not required, we <strong>strongly suggest</strong> that any current Write.as users <a href="https://write.as/me/settings">add an email address to their account</a> today, if they haven’t already.</p>

<hr/>

<p>We hope everyone will find this minor change reasonable, and as always, we thank you for continuing to trust us with your writing!</p>

<p>If you have any questions or concerns, we hope you’ll give your feedback on Remark.as (<a href="https://remark.as/p/blog/requiring-an-email-address">Discuss...</a>) or by replying in the fediverse <a href="/@/write_as@writing.exchange" class="u-url mention">@<span>write_as@writing.exchange</span></a>.</p>

<p><a href="https://write.as/blog/tag:changes" class="hashtag"><span>#</span><span class="p-category">changes</span></a> <a href="https://write.as/blog/tag:email" class="hashtag"><span>#</span><span class="p-category">email</span></a></p>
]]></content:encoded>
      <guid>https://write.as/blog/requiring-an-email-address</guid>
      <pubDate>Fri, 30 Aug 2024 17:45:31 +0000</pubDate>
    </item>
    <item>
      <title>Slightly New Casual Price</title>
      <link>https://write.as/blog/slightly-new-casual-price?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[Almost two years ago, shortly after launching blogs and accounts, we created our Casual subscription. At $10, this is the perfect plan for people who want a little more than what our free tier offers, but don&#39;t need much more. In fact, today it&#39;s just as popular as our Pro plan.&#xA;&#xA;Since then, we&#39;ve added SSL support to the custom domains you can add to your Casual blogs, and Read Write.as has grown to an audience of thousands per month, including readers across Twitter and the fediverse and those who visit Write.as just for the stories.&#xA;&#xA;Because of this, and largely to get rid of the awkward &#34;$0.83 per month&#34; pricing, the price for new Casual subscriptions will go up to $12 per year starting August 1. Existing Casual users, including any who upgrade before August 1, will keep their $10/year rate for as long as their subscription is active.&#xA;&#xA;After this, you likely won&#39;t see any changes to the Casual rate, except perhaps with a new multi-year payment option. If you&#39;d be interested in this, let us know on the forum!&#xA;&#xA;#pricing #casual #changes]]&gt;</description>
      <content:encoded><![CDATA[<p>Almost <a href="https://write.as/blog/latest-updates-end-of-august">two years ago</a>, shortly after launching blogs and accounts, we created our <strong>Casual</strong> subscription. At $10, this is the perfect plan for people who want a little more than what our free tier offers, but don&#39;t need much more. In fact, today it&#39;s just as popular as our Pro plan.</p>

<p>Since then, we&#39;ve added SSL support to the custom domains you can add to your Casual blogs, and <a href="https://read.write.as">Read Write.as</a> has grown to an audience of thousands per month, including readers across <a href="https://twitter.com/readwriteas">Twitter</a> and <a href="https://writing.exchange/@readwriteas">the fediverse</a> and those who visit Write.as just for the stories.</p>

<p>Because of this, and largely to get rid of the awkward “$0.83 per month” pricing, the price for <em>new</em> Casual subscriptions will go up to $12 per year starting <strong>August 1</strong>. Existing Casual users, including any who upgrade before August 1, will keep their $10/year rate for as long as their subscription is active.</p>

<p>After this, you likely won&#39;t see any changes to the Casual rate, except perhaps with a new multi-year payment option. If you&#39;d be interested in this, let us know <a href="https://discuss.write.as/t/slightly-new-casual-price/60">on the forum</a>!</p>

<p><a href="https://write.as/blog/tag:pricing" class="hashtag"><span>#</span><span class="p-category">pricing</span></a> <a href="https://write.as/blog/tag:casual" class="hashtag"><span>#</span><span class="p-category">casual</span></a> <a href="https://write.as/blog/tag:changes" class="hashtag"><span>#</span><span class="p-category">changes</span></a></p>
]]></content:encoded>
      <guid>https://write.as/blog/slightly-new-casual-price</guid>
      <pubDate>Tue, 24 Jul 2018 20:30:30 +0000</pubDate>
    </item>
  </channel>
</rss>