<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>@bnjbvr - fediverse</title>
    <subtitle>Technical blog and random musings.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://bouvier.cc/tags/fediverse/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://bouvier.cc"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-06-27T00:00:00+00:00</updated>
    <id>https://bouvier.cc/tags/fediverse/atom.xml</id>
    <entry xml:lang="en">
        <title>Piggybacking on Mastodon, email newsletters edition</title>
        <published>2026-06-27T00:00:00+00:00</published>
        <updated>2026-06-27T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Benjamin Bouvier
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://bouvier.cc/tech/piggybacking-mastodon-emails/"/>
        <id>https://bouvier.cc/tech/piggybacking-mastodon-emails/</id>
        <content type="html" xml:base="https://bouvier.cc/tech/piggybacking-mastodon-emails/">&lt;p&gt;Free email newsletters with Mastodon! It’s now possible to subscribe to email updates for this blog, thanks to a new feature in Mastodon.&lt;&#x2F;p&gt;
&lt;span id=&quot;continue-reading&quot;&gt;&lt;&#x2F;span&gt;
&lt;p&gt;I’ve been a heavy user of Mastodon for a while. Recently, Mastodon has &lt;a rel=&quot;noopener noreferrer external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;blog.joinmastodon.org&#x2F;2026&#x2F;06&#x2F;mastodon-4.6&#x2F;&quot;&gt;released a new version&lt;&#x2F;a&gt; (4.6) that includes a particularly interesting change, in my opinion: the ability to subscribe to email updates for a user’s account, without requiring any Mastodon account, or any other kind of account on the Fediverse, for that matter. If you subscribe with your email address to a user’s account that has enabled this, then you’ll get an email update every time the user posts anything. That’s basically a free newsletter for everyone!&lt;&#x2F;p&gt;
&lt;p&gt;It seems that, by default, this capability is a bit limited in scope, and must be enabled in two steps:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;first, your Mastodon instance administrator must assign you a &lt;em&gt;role&lt;&#x2F;em&gt; which has the permission to enable this feature.&lt;&#x2F;li&gt;
&lt;li&gt;second, as a Mastodon user, you need to go to your settings, and enable the email notification mechanism by default (under the preferences, then “Privacy and Reach”, then “Send posts via email”).&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;That’s awesome! Mastodon (as per the ActivityPub API requirements, as far as I know) already provides RSS feeds for each user, so you can follow a user &lt;em&gt;either&lt;&#x2F;em&gt; using your Fediverse client of choice&lt;sup class=&quot;footnote-reference&quot; id=&quot;fr-3-1&quot;&gt;&lt;a href=&quot;#fn-3&quot;&gt;1&lt;&#x2F;a&gt;&lt;&#x2F;sup&gt;, &lt;em&gt;or&lt;&#x2F;em&gt; an RSS feed, &lt;em&gt;or&lt;&#x2F;em&gt; by email now. No need for extra steps in IFTT or RSS-to-email systems!&lt;&#x2F;p&gt;
&lt;p&gt;I wish it were a bit more universally applicable, and that it would be possible for every user to do that, without the admin having to allow it on a per-user basis. But! I can easily imagine how it would become a moderation nightmare real fast. After all, a post on the Fediverse can be moderated &lt;em&gt;a posteriori&lt;&#x2F;em&gt;, i.e. after it’s been sent to the entire Fediverse; if the admin removed it, this will send a remove notification to all the servers that received it, and if they’re Well-Behaved™&lt;sup class=&quot;footnote-reference&quot; id=&quot;fr-2-1&quot;&gt;&lt;a href=&quot;#fn-2&quot;&gt;2&lt;&#x2F;a&gt;&lt;&#x2F;sup&gt;, they will remove it locally as well. But email doesn’t have that capability! Once an email has been sent, it &lt;em&gt;will&lt;&#x2F;em&gt; be received and it’s not possible to remove it from all the recipients’ inboxes after the fact. So, a user account could expose email subscriptions, then send crap to all its subscribers; this would occur a reputation cost for the sender email address, that would then affect the server reputation for &lt;em&gt;all&lt;&#x2F;em&gt; emails sent by the server… which would be super bad.&lt;&#x2F;p&gt;
&lt;p&gt;I’ve been already using Mastodon as a commenting system for this blog, using &lt;a rel=&quot;noopener noreferrer external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;carlschwan.eu&#x2F;2020&#x2F;12&#x2F;29&#x2F;adding-comments-to-your-static-blog-with-mastodon&#x2F;&quot;&gt;this&lt;&#x2F;a&gt; &lt;a rel=&quot;noopener noreferrer external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;berglyd.net&#x2F;blog&#x2F;2023&#x2F;03&#x2F;mastodon-comments&#x2F;&quot;&gt;technique&lt;&#x2F;a&gt; I’d like to get more in details to later (and the reasoning why I can afford to do this). These days, I’m writing my posts in &lt;a rel=&quot;noopener noreferrer external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;silverbullet.md&#x2F;&quot;&gt;Silverbullet&lt;&#x2F;a&gt;, a free and open-source self-hostable note-taking editor that’s also a fully programmable Lua&lt;sup class=&quot;footnote-reference&quot; id=&quot;fr-1-1&quot;&gt;&lt;a href=&quot;#fn-1&quot;&gt;3&lt;&#x2F;a&gt;&lt;&#x2F;sup&gt; environment. I’ve written small helper code to post a note on the Fediverse, with the post’s summary as well as a link to the post (using the Mastodon API). The code will then embed some metadata in the post’s source, so that the website knows how to fetch the replies to this post later; the replies &lt;em&gt;are&lt;&#x2F;em&gt; the comments.&lt;&#x2F;p&gt;
&lt;p&gt;So I already have a flow where I &lt;em&gt;do&lt;&#x2F;em&gt; post a note to the Fediverse. In addition to the new email notifications I’ve alluded to above, this instantaneously becomes a &lt;em&gt;newsletter&lt;&#x2F;em&gt; for the blog: each email will include the summary as well as the link to the full blog 🥳&lt;&#x2F;p&gt;
&lt;p&gt;If you want to subscribe by email to this blog, you can now do so by going to the blog’s public &lt;a rel=&quot;noopener noreferrer external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;tutut.delire.party&#x2F;@bnjbvr_blog&quot;&gt;profile page here&lt;&#x2F;a&gt;, enter your email address, and get updates whenever a post has been published!&lt;&#x2F;p&gt;
&lt;p&gt;That’s pretty sweet! Email newsletter for free! Yay for the Small Web!&lt;&#x2F;p&gt;
&lt;section class=&quot;footnotes&quot;&gt;
&lt;ol class=&quot;footnotes-list&quot;&gt;
&lt;li id=&quot;fn-3&quot;&gt;
&lt;p&gt;&lt;a rel=&quot;noopener noreferrer external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;phanpy.social&#x2F;&quot;&gt;phanpy&lt;&#x2F;a&gt; is still king for me, especially on mobile! &lt;a href=&quot;#fr-3-1&quot;&gt;↩&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
&lt;&#x2F;li&gt;
&lt;li id=&quot;fn-2&quot;&gt;
&lt;p&gt;aka follow the ActivityPub specification. A bad actor could decide to &lt;em&gt;not&lt;&#x2F;em&gt; keep the post, in one way or another; either not do anything at all and keep it around; or delete it publicly after archiving it somewhere. That’s inherent to any federated&#x2F;decentralized system, as far as I can tell. &lt;a href=&quot;#fr-2-1&quot;&gt;↩&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
&lt;&#x2F;li&gt;
&lt;li id=&quot;fn-1&quot;&gt;
&lt;p&gt;&lt;em&gt;cries in 1-index arrays&lt;&#x2F;em&gt;. &lt;a href=&quot;#fr-1-1&quot;&gt;↩&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
&lt;&#x2F;li&gt;
&lt;&#x2F;ol&gt;
&lt;&#x2F;section&gt;
</content>
    </entry>
</feed>

