# Using private / personal messages as long term chat

**URL:** <https://meta.discourse.org/t/using-private-personal-messages-as-long-term-chat/41356>\
**Category:** Announcements\
**Tags:** new-feature\
**Created:** [21 במרץ,‏ 2016,‏ 9:28am UTC](https://meta.discourse.org/t/using-private-personal-messages-as-long-term-chat/41356 "2016-03-21T09:28:07Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**Post date:** [21 במרץ,‏ 2016,‏ 11:43pm UTC](https://meta.discourse.org/t/using-private-personal-messages-as-long-term-chat/41356/7 "2016-03-21T23:43:25Z")

</div>

OK. 2 points then.

1. You should use a different name than “close” if it is going to function differently than close everywhere else.
2. I’ve brought this up before, but am going to reiterate it here. Staff users (and if not staff users than admins only) should not be constrained by site settings such that they need to edit settings for the whole site to get things done. I last brought this concern up regarding the inability for staff user to move a new user’s post to a new topic because they exceeded their first day topic limit. I feel the same applies here. If site staff has a good reason for opening a specific PM back up to discussion, that’s their perogative. They should not be restricted by the software from doing so, nor should they need to modify site-wide settings to accomplish the task they wish.  
There are obviously limits to this - staff shouldn’t be permitted to break the site, but lowering a PMs performance (or overriding a new user’s rate limits) wouldn’t do that, or come anywhere close.

Just my 2 cents. Take it for what it’s worth.

---

_[View the full topic](https://meta.discourse.org/t/using-private-personal-messages-as-long-term-chat/41356)._
