Well, yea. By implementing I ment easy front-end part, that is easy to understand for users. Not saying it’s easy to code or something. But do you plan to add this feature in any way thought? It’s kinnda critic for my forum now, because games! To explain this better - we have one staff in Tera guild and other staff in Black Desert guild. And all of them can moderate forum globaly. From my expiriense, people can turn out betrayers. Or just start fighting about something, raging out and try to break things. So I don’t like the idea that our forum holds on trust now, it turns me into paranoic big times.
Thanks for the reply. Picking up on this conversation, if a private category is already in place and a moderator is assigned (by admin / staff) can the moderator invite users to the private category?
We want to support closed conversations for specific groups on Folksy e.g. “Leeds Craft Team” or the “Renegade Seller Team” and there is a desire for these groups to have some autonomy over that conversation within the main forum.
The question of invitations relates to groups rather than categories. Group managers (as opposed to category moderators) have been implemented on the back-end but not exposed in the UI. But you could use that to set up specific users that can invite users into topics that are in restricted categories.
Not so much an early appearance, but in the current beta. Most Discourse sites follow the tests-passed development branch, and thus update fairly frequently as the developers add features. Unlike many pieces of software, Discourse development is constant and ongoing, not just a single large release every 4 months. So, right now this site, and many others are running Discourse 1.6.0.beta2, which has some features planned for Discourse 1.6. When a feature is developed, it is added to the site. Once all the planned features are added, and bugs squashed, then 1.6 is “released” to the stable branch, and those sites that don’t like the frequent updates get the new features. Make sense?
Is this still the plan? @codinghorror removed it from the 1.6 release post on May 16th without a note to the revision explaining why. Was it removed in error? Is it being pushed a version and now scheduled for 1.7 instead? Is it being dropped entirely?
Jeff would need to answer this himself, but I can say that it is not being dropped entirely. Features move between planned releases all the time, based on perceived interest level, need, and development time.