# Feature request: cross-posting Twitter status to meta?

**URL:** https://meta.discourse.org/t/feature-request-cross-posting-twitter-status-to-meta/38668
**Category:** Feature
**Created:** [29. Januar 2016 um 01:43 UTC](https://meta.discourse.org/t/feature-request-cross-posting-twitter-status-to-meta/38668 "2016-01-29T01:43:25Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![owenudacity](https://avatars.discourse-cdn.com/v4/letter/o/f07891/32.png) [@owenudacity](https://meta.discourse.org/u/owenudacity)
#### Post date: [29. Januar 2016 um 01:43 UTC](https://meta.discourse.org/t/feature-request-cross-posting-twitter-status-to-meta/38668/1 "2016-01-29T01:43:25Z")

</div>

Greetings,

I posted a support question in the middle of some network issues, and would not have posted if I had known it was a known issue. In this case, the Twitter feed for Discourse had the latest, and I didn’t think to check it until someone pointed it out to me.

For other sites I’ll head to status.x.y when I need to know if there’s an outage. In our case, that points to [meta.discourse.org](http://meta.discourse.org). Unfortunately, in this case, that didn’t give me the status I needed. At the same time, I love that you have a responsive Twitter feed, and don’t want to discourage that.

So, I have a request that status get cross-posted to meta somehow when issues arise - perhaps as something pinned at the top of the support category. You don’t need to be worrying about notifying multiple channels while you’re fighting a problem, but hopefully your API and the Twitter API make it possible to cross-post without driving yourself batty.

Thanks for considering!

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [29. Januar 2016 um 04:12 UTC](https://meta.discourse.org/t/feature-request-cross-posting-twitter-status-to-meta/38668/2 "2016-01-29T04:12:16Z")

</div>

Would not have worked in this case as meta was down as well due to the big DDoS attack.

Short of having a known place to go that is entirely off site, which is Twitter at the moment [https://twitter.com/discourse](https://twitter.com/discourse) – not sure.

We need more IP diversity as well so it is easier to respond to DDoS and we are working on that.