Feature proposal: direct/ private messaging

[fisharebest]

Below is a summary of the [[../wiki/Messaging|discussion]]:

• Messaging, which is direct and private.
• Multi-party and threaded (with threads defined by the subject line, possibly auto-generated).
• Asynchronous, or at most "semi-synchronous" – that is, there may be an almost real-time notification of new messages next to the user's name/ sign-out link in the right-hand column, but there won't be heavy use of Ajax.
• Messages will be plain-text, probably without even automatic conversion of URLs to links – to encourage people to move to public Clouds.
• At Rebecca (Galley)'s suggestion, there will be a "Create Cloud" button/ link/ tip on the view-message(s) page – to encourage people to turn their private discussion into a public one. (However, we aren't planning any explicit link between a cloud and a message/thread.)
• We think the option to make a message public would be confusing – better to improve the user/ cloud stream functionality, so people can see new comments (which are messages in a way?) in almost real-time.
• The functionality will (almost certainly) be part of core CloudEngine/ Cloudworks, with feature flags.

---

• Bitbucket: https://bitbucket.org/cloudengine/cloudengine/issue/59
• Originally Reported By: Nick Freear
• Originally Created At: 2010-10-22T18:21:55.954

[fisharebest]

Adding sub-tasks, and related bugs:

• Sub-tasks: <<issue 89>>, <<issue 91>>, <<issue 92>>, <<issue 95>>.
• Related: <<issue 81>>, <<issue 90>>, <<issue 93>>, <<issue 94>>.

---

Original Comment By: Nick Freear

[fisharebest]

Removing version: 1.1.0 (automated comment)

---

Original Comment By: Nick Freear