posted in Catodon talks!

Catodon@catodon@catodon.rocks
edited

Catodon 26.10.2 released:  Stop trusting the emSign ECC Root CA - G3 root at startup

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.

​:catodon:​
#catodon

codefloe.com/catodon/catodon/releases/tag/26.10.2
Summary card of an release titled "26.10.2" in repository catodon/catodonCodeFloe - the Forgejo developer platform26.10.2 - catodon/catodon**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. **Upgrading**. Pull `26.10.2` (or update the code for a source install) and restart. There is no migration and nothing to change in your configuration. ...
:neocat_0_0@xn--mia-g1a.retumi.fr:1🩹1
panos :catodon:@panos@catodon.rocks
edited

Replying to an earlier post

Yeah, actually it's on purpose, with this known downside. For link posts in our forums, we put the link in the post's url 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 url as the post's own address. "Open original page" then opens the link instead of the post on the Catodon server.

@julian@activitypub.space - hello! I have not checked if NodeBB has changed this since we implemented federated forums. if we send url 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 Link attachment. Ideally, we would like to keep NodeBB working and fix Mastodon too.

also lnkr@lnkr

Replying to @⁨panos@catodon.rocks⁩

@panos @catodon-talks @julian wait, that can't be right. Lemmy does not do that, it doesn't have the top-level url 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.
And NodeBB source at least gives the impression that it can pull the href from attachments?

Node.js based forum software built for the modern web - NodeBB/NodeBBGitHubNodeBB/src/posts/attachments.js at 900d99ea5ff9010d3cc9ab8d5bb9282760408080 · NodeBB/NodeBBNode.js based forum software built for the modern web - NodeBB/NodeBB
en
panos :catodon:@panos@catodon.rocks

Replying to @⁨lnkr⁩

You're right, and I got Lemmy wrong (we had matched Lemmy's behaviour in an earlier commit). Lemmy doesn't send a top-level url for link posts, only a Link attachment. We do send the link as url as well. I added that in April for NodeBB, but it looks unnecessary and it breaks "open original" on Mastodon. I'll remove it and check that NodeBB still shows the link from the attachment. Thanks for the pointer.

julian@julian@activitypub.space

Replying to @⁨lnkr⁩

@lnkr@staging3.plamenu.com @panos@catodon.rocks no this doesn't seem right.

NodeBB does not handle url that way, it always represents the user friendly URL that a browser can access.

The specific case you're referring to is a threadiverse post with a link target. In that case the shape is attachment with type Link. NodeBB checks for that and appends it to the post body.

Catodon rockspanos :catodon: (@panos)I build Catodon. He/him/They/them, neurodivergent, anarchist, polyamorous the state must fall
panos :catodon:@panos@catodon.rocks
edited

Replying to an earlier post

Thanks - if I'm not mistaken, this needs nodebb-plugin-link-preview, which isn't on by default in fresh installs. Without it the link didn't show anywhere, which led to my initial frustration (it's probably documented and I missed it). The fix is merged and deployed: new forum posts no longer send a url and carry the link only as a Link attachment, like Lemmy's do. Posts that were already federated keep the old url.

panos :catodon:@panos@catodon.rocks

Replying to @⁨panos@catodon.rocks⁩

@lnkr@staging3.plamenu.com Deployed and seems to work: https://catodon.rocks/notes/asnfqjso3z16001n from Mastodon opens the catodon.rocks page from Open original page. Thanks again for pointing it out!

Catodon rocksCatodon (@catodon)Catodon 26.10.3 released: Update Node.js in Docker | Release 26.10.3: 26.10.2 plus the Node releases of the October 2026 security advisory (advisory), and follow-ups from #663 that came after 26.10.2 was cut. Update not necessary if you're on a bare metal installation - just make sure you have updated your Node.js to the October 21 security release - and have restarted Catodon afterwards. :catodon: #catodon