<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Protocols on An Untitled Blog</title>
    <link>/tags/protocols/</link>
    <description>Recent content in Protocols on An Untitled Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 08 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/protocols/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Technical Comparison of Distributed Social Media Protocols v3</title>
      <link>/posts/2026-03-08_microblogging-protocols-v3/</link>
      <pubDate>Sun, 08 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/2026-03-08_microblogging-protocols-v3/</guid>
      <description>
        
          
            &lt;p&gt;&lt;em&gt;Update 3/14/2026: I&amp;rsquo;ve updated the post to reflect that porting Nomadic Identities to Activity Pub is still ongoing. Shoutout to silverpill@mitra.social. Also, less than 24 hours posting this, BlueSky CEO Jay Grabber has stepped down from her roll. A change in leadership may change the state of the platform, which may cause this post to be somewhat inaccurate in the future.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Hello, I&amp;rsquo;m back for round three of my social media protocol comparisons. I wrote v2 because of some mistakes on my part, although it&amp;rsquo;s been two years since writing it, and it&amp;rsquo;s become a bit out of date. It&amp;rsquo;s also a bit long, with a bunch of explainers and clutter right at the start of it, so for this round, I figured I&amp;rsquo;d get things up to date while shortening the text (or at least moving ramblings to footnotes) and move a lot of the explainers to the end.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>This is Fine: an Interim Microblogging Protocols Update</title>
      <link>/posts/2025-12-07_microblog-protocols-update/</link>
      <pubDate>Sun, 07 Dec 2025 00:00:00 +0000</pubDate>
      
      <guid>/posts/2025-12-07_microblog-protocols-update/</guid>
      <description>
        
          
            &lt;p&gt;&lt;em&gt;As is customary on my microblogging posts, let&amp;rsquo;s get us started with an original meme.&lt;/em&gt;
&lt;div&gt;
    &lt;video width=&#34;720&#34; height=&#34;480&#34; controls&gt;
  &lt;source src=&#34;/img/protocol-meme-3.mp4&#34; type=&#34;video/mp4&#34;&gt;
&lt;/video&gt;
&lt;/div&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Also, if you&amp;rsquo;d like to read my previous Microblogging Protocols compared posts, you can read &lt;a href=&#34;/posts/2024-01-30_microblogging-protocols/&#34;&gt;v1 here&lt;/a&gt; and &lt;a href=&#34;/posts/2024-08-11_microbloggingv2/&#34;&gt;v2 here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s been a little over a year since I made my updated microblogging protocols comparison. Since then a few things have happened, and my previous could use some trimming. In the spirit of keeping things shorter (and keeping the comparison v3 post relevant longer), I figured I&amp;rsquo;d split the post into two parts: this one, which includes random updates and things that happened over the last year or so - and a second one, &amp;ldquo;Microblogging Protocols Compared v3&amp;rdquo; which will be a more streamlined protocol comparison. Anyway, as you can probably tell by the meme, the microblogging protocols have been going through a rough patch lately - though it&amp;rsquo;s not all bad news.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>NFTs and Dark Web Shenanagins</title>
      <link>/posts/2025-06-18_standard-server-alternatives/</link>
      <pubDate>Wed, 18 Jun 2025 00:00:00 +0000</pubDate>
      
      <guid>/posts/2025-06-18_standard-server-alternatives/</guid>
      <description>
        
          
            &lt;p&gt;A based design that makes a web that&amp;rsquo;s true&lt;br&gt;
ICANNs and NATs embrace shall be no more&lt;br&gt;
Behind a Pi or in the cloud for you&lt;br&gt;
We use that tool be I2P or Tor&lt;/p&gt;
&lt;p&gt;Come join a world of speech that can flow free&lt;br&gt;
The words by truths of math they shall be bound&lt;br&gt;
A power built right in that&amp;rsquo;s DHT&lt;br&gt;
Identity by key pairs holds its ground&lt;/p&gt;
&lt;p&gt;IPFS a poggers web design&lt;br&gt;
ID by content not by where it is&lt;br&gt;
Defi domain to own your name online&lt;br&gt;
A world that&amp;rsquo;s free of gov and free of biz&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Microblogging Protocols Compared v2</title>
      <link>/posts/2024-08-11_microbloggingv2/</link>
      <pubDate>Sun, 11 Aug 2024 00:00:00 +0000</pubDate>
      
      <guid>/posts/2024-08-11_microbloggingv2/</guid>
      <description>
        
          
            &lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Update: September 20th, 2024:&lt;/strong&gt;
I was incorrect regarding AT&amp;rsquo;s (BlueSky) inability to fully delete things, the protocol DOES support fully deleting posts from the user&amp;rsquo;s repo and I&amp;rsquo;ve updated the post to reflect that. &lt;a href=&#34;https://atproto.com/specs/repository&#34;&gt;Read more&lt;/a&gt;. Big thanks to &lt;a href=&#34;https://snarfed.org/&#34;&gt;Ryan&lt;/a&gt; for providing the info.&lt;/p&gt;
&lt;p&gt;Also, on a less important update (in regards to this post&amp;rsquo;s accuracy) - in keeping tradition with the original post - Bluesky has managed to change rapidly shortly after I finished this. It&amp;rsquo;s good news again, in this case a huge influx of users, many from Brazil after Twitter/X was blocked. Additionally, I also recently saw &lt;a href=&#34;https://frontpage.fyi/&#34;&gt;Frontpage&lt;/a&gt;, an AT based link aggregator. In the post I mention a few times hoping more will be built on AT now that it&amp;rsquo;s opened up, and it appears exactly that is happening.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>I made a client, Nostr surpassed Mastodon, and BlueSky is open?</title>
      <link>/posts/2024-02-24_microblogging-anthology/</link>
      <pubDate>Sat, 24 Feb 2024 00:00:00 +0000</pubDate>
      
      <guid>/posts/2024-02-24_microblogging-anthology/</guid>
      <description>
        
          
            &lt;p&gt;So after two very long posts, one complaining about web browsers and one comparing the three big non-centralized social media protocols, I thought about writing two shorter posts about random things (hats and making sour krout specifically). However, between then and now stuffs happened and I thought I would make an anthology post with three different mini topics I wanted to share.&lt;/p&gt;
&lt;h2 id=&#34;i-made-a-client&#34;&gt;I made a client&lt;/h2&gt;
&lt;p&gt;So yeah, I made a client that can post to Nostr, Activity Pub, and BlueSky (hopefully all of AT once it&amp;rsquo;s fully opened). It&amp;rsquo;s a bit hacky, and written in Python using dependencies that do all the heavy lifting, but it works. It can broadcast the same post to all three, post different posts to different protocols, or skip posting to a protocol altogether. There&amp;rsquo;s a version that uses Keyring to have your OS manage your credentials instead of baking them into a script, and it&amp;rsquo;ll run on just about everything. I&amp;rsquo;m not a programmer by trade, and it&amp;rsquo;s been a very long time since I wrote any code for public consumption, so I&amp;rsquo;m excited to get it working and share it. Apparently I&amp;rsquo;m the second person to do this, as shortly under two weeks before I released mine somebody else made Nootti, so if you like this idea, are on IOS, and want something more polished that is also an option as well.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>ActivityPub/Nostr/AT-BlueSky Compared</title>
      <link>/posts/2024-01-30_microblogging-protocols/</link>
      <pubDate>Tue, 30 Jan 2024 00:00:00 +0000</pubDate>
      
      <guid>/posts/2024-01-30_microblogging-protocols/</guid>
      <description>
        
          
            &lt;p&gt;Note: This post is out of date, &lt;a href=&#34;https://nate.mecca1.net/posts/2024-08-11_microbloggingv2/&#34;&gt;here&amp;rsquo;s a more up to date version&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Update August 5th 2024&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I have some good and bad news regarding this post. First, I made two mistakes. AT crawlers are not in fact crawlers, they are called relays. Also, shared inboxes are actually part of the Activity Pub W3C standard as apposed to hacky additions to the protocol by third party servers. I was wrong about Activity Pub servers sending multiple messages to the same server remote to update it about a single post.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Platform Agnostic Following</title>
      <link>/posts/2023-12-20_followanything/</link>
      <pubDate>Wed, 20 Dec 2023 00:00:00 +0000</pubDate>
      
      <guid>/posts/2023-12-20_followanything/</guid>
      <description>
        
          
            &lt;p&gt;Chances are if you&amp;rsquo;re here it&amp;rsquo;s through an RSS feed (or an RSS feed bridged to something else), so I probably don&amp;rsquo;t need to do too much of an introduction. &lt;a href=&#34;https://www.wpbeginner.com/beginners-guide/what-is-rss-how-to-use-rss-in-wordpress/&#34;&gt;Here&amp;rsquo;s a quick rundown if you&amp;rsquo;re unfamiliar&lt;/a&gt;. However, today I wanted to talk about RSS (as well as three other means of following content), how I&amp;rsquo;ve benefited from it, and a small project I started. Just about every piece of content I follow is through RSS - organized into different categories (news, blogs, videos, audio, etc), and the following benefits really stand out:&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Nostr</title>
      <link>/posts/2023-12-11_nostr/</link>
      <pubDate>Mon, 11 Dec 2023 00:00:00 +0000</pubDate>
      
      <guid>/posts/2023-12-11_nostr/</guid>
      <description>
        
          
            &lt;p&gt;I have recently been re-dipping my toes into Nostr (tried it a while back just to experiment with it but never really stuck around), and so far it&amp;rsquo;s become my preferred microblogging platform. There&amp;rsquo;s a handful of reasons surrounding that, both in the protocol itself and what&amp;rsquo;s being built up around it, and I think it has a lot of promise that merits its very quick growth. Today I thought I would go over why I am a fan of it, and why I think it might be worth checking out if you&amp;rsquo;re interested in a more decentralized web.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>MITM Risks in Signal? Mitigation &#43; Monologue</title>
      <link>/posts/2023-11-19_signal-cons/</link>
      <pubDate>Sun, 19 Nov 2023 00:00:00 +0000</pubDate>
      
      <guid>/posts/2023-11-19_signal-cons/</guid>
      <description>
        
          
            &lt;p&gt;&lt;em&gt;Update 11/25: I was made aware that Signal has some proprietary anti-spam code and added the TLDR.&lt;/em&gt;&lt;/p&gt;
&lt;details&gt;
  &lt;summary&gt;&lt;strong&gt;A More Technical TLDR&lt;/strong&gt;&lt;/summary&gt;
  &lt;p&gt;I never know how much jargon I should include or how much I should explain, and as long as I&amp;rsquo;m writing I&amp;rsquo;m enjoying myself meaning I&amp;rsquo;ve been all over the place. But here&amp;rsquo;s a shortened version for those familiar with encryption.&lt;/p&gt;
&lt;p&gt;A vanilla implementation of the Signal protocol relies on public key infrastructure to perform a handshake between devices. As you may know, a public key server can certify that any device/key belongs to an account if you have nothing more to go on than a phone number. Furthermore, at any point the server may say keys have changed and direct you to start communicating with a device other than the one you expect.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>What is IPFS &#43; basic use</title>
      <link>/posts/2023-08-28_ipfs/</link>
      <pubDate>Mon, 28 Aug 2023 00:00:00 +0000</pubDate>
      
      <guid>/posts/2023-08-28_ipfs/</guid>
      <description>
        
          
            &lt;p&gt;IPFS, an acronym for &amp;ldquo;InterPlanetary File System&amp;rdquo;, is a way to deliver files that takes a different approach to HTTP. As I mentioned in my very first post, I originally considered hosting my entire site/blog on it, and while I decided against it for reasons I mentioned there and reasons I&amp;rsquo;ll get into later here; I am working on something that may involve me sharing files here, which I&amp;rsquo;ll probably use IPFS for. This is of course in addition to me finding it an interesting method of sharing data and worth speaking about.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>