-
My goodness, it's not a private conversation in this context. A conversation is private if it's within a close context, the conversation module can be considered generally private thou but not a public timeline. In this case, the conversation module is not involved but the timeline module which is driven by general comments to post.
In any case I could still see the comments whether or not it is served as a new post. This primarily just help populate comments as post, it doesn't change the privacy of comments.
For instance, a much robust framework is used on Twitter for tweets and retweet, so it's all about what is useful for your site and you can simply turn it off if you don't want it Houstonlively
-
Andrew Boon Perhaps you can offer a reasonable explanation of why "A private inbox for asynchronous on-site communication between users " should ever appear on a timeline. There are plenty of ways to put content on a timeline, so why mess with what is supposed to be an intra-site mail system
Comments
-
·
·That does seem to provide a bandaid, but why on earth would you have a setting in the timeline module that affects conversations?
Conversations: "A private inbox for asynchronous on-site communication between users "
Why this would involve a setting in the timeline module , is something I don't understand. What possible reason could there be for placing communication between members on a timeline?