<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JWT on NotNil Blog</title><link>https://notnil.org/en/tags/jwt/</link><description>Recent content in JWT on NotNil Blog</description><generator>Hugo</generator><language>en-US</language><copyright>© Matthieu Moreau</copyright><lastBuildDate>Wed, 18 Jan 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://notnil.org/en/tags/jwt/index.xml" rel="self" type="application/rss+xml"/><item><title>It's a JWT and it's pronounced jot</title><link>https://notnil.org/en/posts/9-jot/</link><pubDate>Wed, 18 Jan 2023 00:00:00 +0000</pubDate><guid>https://notnil.org/en/posts/9-jot/</guid><description>&lt;figure&gt;&lt;img src="https://notnil.org/images/posts/jot/wall_feature.jpg" width="800"&gt;&lt;figcaption&gt;&#10;&#9;&#9;&#9;&lt;h4&gt;We&amp;#39;re talking security, so here is a wall&lt;/h4&gt;&#10;&#9;&#9;&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;p&gt;If there is one thing I like about computing, it is the arguments: framework X vs Y, language A vs B, Mac vs Linux vs Win$, Arch Linux vs the world, sysadmin vs the rest of the team.&lt;/p&gt;&#10;&lt;p&gt;The problem with arguments is that they &lt;em&gt;can&lt;/em&gt; generate noise and hide the useful information. That is exactly what I ran into while implementing JWT on an internal project at Coddity, and on one specific case: user session management.&lt;/p&gt;</description></item></channel></rss>