# Federation support for Discourse

**URL:** <https://meta.discourse.org/t/federation-support-for-discourse/90921>\
**Category:** Feature\
**Tags:** completed\
**Created:** [June 28, 2018, 5:32am UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921 "2018-06-28T05:32:10Z")\
**Posts on this page:** 1\
**Showing post:** 100

<div class="post-metadata">

**Author:** ![mcdanlj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcdanlj/32/131829_2.png) [@mcdanlj](https://meta.discourse.org/u/mcdanlj)\
**Post date:** [February 17, 2023, 1:00pm UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/100 "2023-02-17T13:00:35Z")

</div>

> [@angus](#):
>
> I am anticipating we’ll do this in the MVP for the kind of reasons you mention. I’ll discuss it further with the Discourse folks at the right time.

If it’s not significantly more work up front, also federating out post edits as `Update` Activities would be valuable. If it’s one of those things that can be contributed post-MVP, then a design that reasonably accommodates adding that later would be great.

> [@angus](#):
>
> How the delay is set and handled is something we’ll need to address in some fashion in the MVP.

For what it’s worth, I would set the delay low on my instance(s). I would not plan to use it to avoid federating spam posts, because it would reasonably likely be a signal that brings a mod from their fediverse feed into our Discourse to take action. I have `chat_integration_delay_seconds` set to 20 for quick typo edits, and would expect to do something similar here. At the very least, that setting sets a precedent for such a delay. ☺

---

_[View the full topic](https://meta.discourse.org/t/federation-support-for-discourse/90921)._