Incoming synchronization between Fediverse publications and Discourse category?

AI-generated summary

The discussion explores the possibility of synchronizing Fediverse publications with a Discourse category. Thomas_Rother initiates the conversation by praising the existing ActivityPub plugin for connecting Discourse categories to the Fediverse and mentions the WP Discourse plugin for WordPress-Discourse integration. He then proposes the idea of incoming synchronization from the Fediverse to a Discourse category, similar to custom incoming email addresses. angus responds by confirming that this functionality already exists, with Discourse and NodeBB having collaborated to develop it through the W3C and other forums. Thomas_Rother expresses gratitude for the clarification.

We currently have a good connection between publications inside of a discourse category and the publication on the Fediverse, thanks to the great work of @angus with the ActivityPub Plugin Moreover, there is a already a good link between publication in the WordPress CMS and Discourse with the WP Discourse plugin from WP Discourse – WordPress plugin | WordPress.org

Still missing (or maybe I did not see this functionality yet?) is a connection between a publication appearing first on the Fediverse and a (possibly internal) Discourse category. This would be similar to the current functionality with custom incoming email addresses based on sub-addressing (RFC 5233 - Sieve Email Filtering: Subaddress Extension):

I heard (but I dont know) that https://nodebb.org/ already has support for “bi-directional” interaction between their forum instance and the Fediverse …

Hey @Thomas_Rother, this already exists. If you enable “Full Topic” publication on an actor then it will accept:

  • Replies to existing topics from any actor.
  • New topics from actors the actor is following.

Yes, NodeBB and Discourse worked closely together to develop this functionality for forums through the W3C and other fora, and helped to create new standards in the process :slight_smile:

Hey Angus, great that this is already implemented and thanks for closing my knowledge gap :grin: