<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Catodon 26.10.2 released:  Stop trusting the emSign ECC Root CA - G3 root at startup]]></title><description><![CDATA[<p><span>Security release - please update. 26.10.2 is a security release on top of 26.10.1 and contains nothing else. Every instance should update.<br /><br /></span>​<img class="not-responsive emoji" src="/emoji/ap/catodon/hel1.your-objectstorage.com" title=":catodon:" />​<span><br /></span><a href="https://catodon.rocks/tags/catodon" rel="tag">#catodon</a></p>

<div class="row mt-3"><div class="col-12 mt-3"><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://codefloe.com/catodon/catodon/releases/tag/26.10.2" title="26.10.2 - catodon/catodon">
<img src="https://codefloe.com/catodon/catodon/releases/summary-card/26.10.2" class="card-img-top not-responsive" style="max-height:15rem" alt="Link Preview Image" />
</a>



<div class="card-body">
<h5 class="card-title">
<a class="text-decoration-none" href="https://codefloe.com/catodon/catodon/releases/tag/26.10.2">
26.10.2 - catodon/catodon
</a>
</h5>
<p class="card-text line-clamp-3">catodon - A Fediverse platform that combines the best of Mastodon, Misskey and Lemmy.</p>
</div>
<a href="https://codefloe.com/catodon/catodon/releases/tag/26.10.2" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://codefloe.com/assets/img/favicon.svg" alt="favicon" class="not-responsive overflow-hiddden" style="max-width:21px;max-height:21px" />



<p class="d-inline-block text-truncate mb-0">CodeFloe - the Forgejo developer platform <span class="text-secondary">(codefloe.com)</span></p>
</a>
</div></div></div>]]></description><link>https://citiverse.it/topic/4966dcce-0291-4eea-b819-9e70f93ad3ec/catodon-26.10.2-released-stop-trusting-the-emsign-ecc-root-ca-g3-root-at-startup</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 21:20:26 GMT</lastBuildDate><atom:link href="https://citiverse.it/topic/4966dcce-0291-4eea-b819-9e70f93ad3ec.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 21 Oct 2026 11:49:32 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Catodon 26.10.2 released:  Stop trusting the emSign ECC Root CA - G3 root at startup on Thu, 22 Oct 2026 00:55:15 GMT]]></title><description><![CDATA[<p dir="auto"><a href="https://activitypub.space/user/lnkr%40staging3.plamenu.com" target="_blank" rel="noopener noreferrer nofollow ugc">@lnkr@staging3.plamenu.com</a> <a href="https://activitypub.space/user/panos%40catodon.rocks" target="_blank" rel="noopener noreferrer nofollow ugc">@panos@catodon.rocks</a> no this doesn't seem right.</p>
<p dir="auto">NodeBB does not handle <code>url</code> that way, it always represents the user friendly URL that a browser can access.</p>
<p dir="auto">The specific case you're referring to is a threadiverse post with a link target. In that case the shape is <code>attachment</code> with type <code>Link</code>. NodeBB checks for that and appends it to the post body.</p>
]]></description><link>https://citiverse.it/post/https://activitypub.space/post/2560</link><guid isPermaLink="true">https://citiverse.it/post/https://activitypub.space/post/2560</guid><dc:creator><![CDATA[julian@activitypub.space]]></dc:creator><pubDate>Thu, 22 Oct 2026 00:55:15 GMT</pubDate></item><item><title><![CDATA[Reply to Catodon 26.10.2 released:  Stop trusting the emSign ECC Root CA - G3 root at startup on Wed, 21 Oct 2026 13:18:40 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/panos%40catodon.rocks" aria-label="Profile: panos@catodon.rocks">@<bdi>panos@catodon.rocks</bdi></a> <a class="plugin-mentions-category plugin-mentions-a" href="/category/catodon-talks@catodon.rocks" aria-label="Profile: catodon-talks@catodon.rocks">@<bdi>catodon-talks@catodon.rocks</bdi></a> <a class="plugin-mentions-user plugin-mentions-a" href="/user/julian%40activitypub.space" aria-label="Profile: julian@activitypub.space">@<bdi>julian@activitypub.space</bdi></a><br />
wait, that can't be right. Lemmy does not do that, it doesn't have the top-level <code>url</code> in post AP object at all, neither I ever had this issue with Lemmy linkposts and I can't reproduce it now, it's original post url resolves correctly, even on Mastodon.<br />
And NodeBB source <a href="https://github.com/NodeBB/NodeBB/blob/900d99ea5ff9010d3cc9ab8d5bb9282760408080/src/posts/attachments.js#L41" target="_blank" rel="noopener noreferrer nofollow ugc">at least gives the impression</a> that it can pull the <code>href</code> from attachments?</p>
]]></description><link>https://citiverse.it/post/https://staging3.plamenu.com/users/lnkr/statuses/117479094358835200</link><guid isPermaLink="true">https://citiverse.it/post/https://staging3.plamenu.com/users/lnkr/statuses/117479094358835200</guid><dc:creator><![CDATA[lnkr@staging3.plamenu.com]]></dc:creator><pubDate>Wed, 21 Oct 2026 13:18:40 GMT</pubDate></item><item><title><![CDATA[Reply to Catodon 26.10.2 released:  Stop trusting the emSign ECC Root CA - G3 root at startup on Wed, 21 Oct 2026 12:31:14 GMT]]></title><description><![CDATA[<p dir="auto">Yeah, actually it's on purpose, with this known downside. For link posts in our forums, we put the link in the post's <code>url</code> field, the same way Lemmy does. We did this as a compromise, because otherwise NodeBB wouldn't show the link. The side effect is that Mastodon-style apps treat <code>url</code> as the post's own address. "Open original page" then opens the link instead of the post on the Catodon server.</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/julian%40activitypub.space" aria-label="Profile: julian@activitypub.space">@<bdi>julian@activitypub.space</bdi></a> - hello! I have not checked if NodeBB has changed this since we implemented federated forums. if we send <code>url</code> as a list, with the post's own address first and the link second, would NodeBB still show the link? We also send the link as a <code>Link</code> attachment. Ideally, we would like to keep NodeBB working and fix Mastodon too.</p>
]]></description><link>https://citiverse.it/post/https://catodon.rocks/notes/aslnnqnqvpi8003f</link><guid isPermaLink="true">https://citiverse.it/post/https://catodon.rocks/notes/aslnnqnqvpi8003f</guid><dc:creator><![CDATA[panos@catodon.rocks]]></dc:creator><pubDate>Wed, 21 Oct 2026 12:31:14 GMT</pubDate></item><item><title><![CDATA[Reply to Catodon 26.10.2 released:  Stop trusting the emSign ECC Root CA - G3 root at startup on Wed, 21 Oct 2026 12:13:26 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/catodon%40catodon.rocks" aria-label="Profile: catodon@catodon.rocks">@<bdi>catodon@catodon.rocks</bdi></a> <a class="plugin-mentions-user plugin-mentions-a" href="/user/panos%40catodon.rocks" aria-label="Profile: panos@catodon.rocks">@<bdi>panos@catodon.rocks</bdi></a> I just noticed that the link that's supposed to be the url of the original post is instead federated as the link <em>from</em> the post. Can't imagine this being intentional</p>


<div class="row mt-3"><div class="col-12 mt-3"><img class="img-thumbnail" src="https://staging3.plamenu.com/media/117478837761212416bd448e64b717680a171c0c5720a5b00a.png" alt="Link Preview Image" /><img class="img-thumbnail" src="https://staging3.plamenu.com/media/11747883783120486437add3a332fcd52b791a41d60b03f2ea.png" alt="Link Preview Image" /></div></div>]]></description><link>https://citiverse.it/post/https://staging3.plamenu.com/users/lnkr/statuses/117478837852372992</link><guid isPermaLink="true">https://citiverse.it/post/https://staging3.plamenu.com/users/lnkr/statuses/117478837852372992</guid><dc:creator><![CDATA[lnkr@staging3.plamenu.com]]></dc:creator><pubDate>Wed, 21 Oct 2026 12:13:26 GMT</pubDate></item></channel></rss>