<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cryptography on A cup of coffee</title><link>https://a-cup-of.coffee/tags/cryptography/</link><description>Recent content in Cryptography on A cup of coffee</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2026</copyright><lastBuildDate>Sat, 22 Aug 2026 12:22:17 +0200</lastBuildDate><atom:link href="https://a-cup-of.coffee/tags/cryptography/index.xml" rel="self" type="application/rss+xml"/><item><title>Under Bluesky's hood: the ATProto</title><link>https://a-cup-of.coffee/blog/atproto-pds/</link><pubDate>Sat, 15 Aug 2026 08:00:00 +0200</pubDate><guid>https://a-cup-of.coffee/blog/atproto-pds/</guid><description>It&amp;rsquo;s been a few years now since I migrated from X to Bluesky. Picking Bluesky happened pretty naturally (I&amp;rsquo;d already given Mastodon a shot). But other than reading a few papers about where Bluesky came from and its technical stack, I never took the time to dig into what actually happens &amp;ldquo;behind&amp;rdquo; Bluesky.
Because indeed, when you think of Bluesky, you see the web interface, the timeline, the likes and followers, the &amp;ldquo;skeets&amp;rdquo; (tweets), but behind all that sits a huge building block called ATProto.</description></item></channel></rss>