@raphael@mastodon.communick.com hmm interesting, can you share the code that's making the call? Usually if it's working with curl it'll work with Node, so this suggests there's something different with the way the call is made with node. For what it's worth, internally, NodeBB uses the built-in fetch method from Node.js.

Hmm... considering that Piefed cross-posts are entirely separate posts, then if the original is edited, then the modification is not carried over to the cross-posted post, correct? I'm thinking that for NodeBB we could continue to have cross-posts reference the canonical topic. They'd simply be part of a separate audience as well. Whether this is local-only or not, I am not sure yet. Perhaps for federation purposes we'd still report the original category (if there is one) under audience

@young_ullrich #restic - Backup-Tool#forgejo - Software Tool (wie gitlab, github)#minio - S3 Datenspeicher#proxmox - Virtualisierung#Vaultwarden - Passwort Safe#Debian 12 - damit die ganzen Server & VMs auch ordentlich laufenUnd noch ganz viele andere #OSS Tools....

@mariusor@metalhead.club I realized after I replied that I think @reiver@mastodon.social was talking about C2S? Definitely on S2S that's a no-go. There aren't enough guarantees.

@mario@hub.somaton.com since Hubzilla posts (incl. yours) are making it in fine I'm assuming this is only for the "forum" feature?

@mario@hub.somaton.com thanks, I tested that payload and it successfully edited the post, so at least from the payload point of view there is no issue. Perhaps there is a problem with the http signature on update? Is that handled differently than a create?