Duplicating the object would mean the discussion is split between objects. The ideal implementation would be the same object present in multiple categories/communities. Is there desire for this in the threadiverse? If the link goes to a controversial news article and it's get posted into pro- and against- community/group the comments will spiral out of control and it won't be a pleasant place. Maybe it could be implemented as a toggle per group/instance within one fedi software. It shouldn't be in Activity Pub protocol.

@renchap@oisaur.com how does RFC9421 differ from Mastodon's existing support for HTTP Signatures? Does this mean you're moving away from cavage-12? That's important to know, and if you're looking for an implementor to handle double-knocking, that is something I can put together for you.. we don't do it at current.

Im running Node 23 on my production install

@iso@lemy.lol what's a "lemmy-like" PM I think this explains why I can't log into the site.

@dansup@mastodon.social no, NodeBB v4 always reports activitypub in protocols, even if disabled. I can update that so it's dependent on the global switch, but it's still possible to have AP enabled but not have any categories federating. I'm just wondering whether FediDB found the forums because content got federated, or whether there was some proactive nodeinfo crawling, that's all. cc @jaz@mastodon.iftas.org

Since we are using https://github.com/Psifi-Solutions/csrf-sync it creates a session whenever a guest loads the forum to set config.csrf_token. Although we used that in 3.7.0 as well so not sure if that's your issue or not. Sessions are also created for guests if you turn on "Allow guests to increase topic view counts", to track which topics they've viewed.

@projectmoon@forum.agnos.is said in Updates to the world page: > > > Also, are there plans to merge the federation synchronization and new remote category following stuff together into one cohesive set of functionality? Yes... the remote category functionality supercedes the category sync functionality in some ways, but there is still a use case for it. Most likely I will need to develop proper support for cross-posting (at least locally), and that would work well with the remote category functionality, so that topics are cross-posted to the synchronized category, instead of moved.

Topic hash is topic: plus the topic id. e.g. the database entry for this one is: topic:13608.