<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Another Ruh Roh.</title>
	<atom:link href="http://habitablezone.com/2011/04/24/another-ruh-roh/feed/" rel="self" type="application/rss+xml" />
	<link>https://habitablezone.com/2011/04/24/another-ruh-roh/</link>
	<description></description>
	<lastBuildDate>Wed, 29 Apr 2026 20:21:36 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Robert</title>
		<link>https://habitablezone.com/2011/04/24/another-ruh-roh/#comment-61</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Mon, 25 Apr 2011 20:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=114#comment-61</guid>
		<description>Correct about editor privileges to freely mark messages as members of any node. Authors won&#039;t.

Actually, these categories of author and editor are kind of arbitrary, artifacts of WordPress. We can already see how they&#039;re too coarse-grained for this environment. That access-control system project (now #2 in the takeoff queue) is intended to make it very fine-grained. The idea is to be able to specify whether or not a member is allowed to perform particular tasks at each node. The ability to change the checkboxes for your own posts is one discrete privilege, the ability to change it on others&#039; posts is a separate power.

So those titles will be phased out in favor a system more like DamnTikiWiki&#039;s, which shouldn&#039;t be held against it. Assigning privileges to groups and putting users in the groups is a solid standard practice. 

(I just handled a phone call from the client about this very subject. The whole world wants me to get it fixed ASAP. I can tell when the universe is trying to give me a hint.)</description>
		<content:encoded><![CDATA[<p>Correct about editor privileges to freely mark messages as members of any node. Authors won&#8217;t.</p>
<p>Actually, these categories of author and editor are kind of arbitrary, artifacts of WordPress. We can already see how they&#8217;re too coarse-grained for this environment. That access-control system project (now #2 in the takeoff queue) is intended to make it very fine-grained. The idea is to be able to specify whether or not a member is allowed to perform particular tasks at each node. The ability to change the checkboxes for your own posts is one discrete privilege, the ability to change it on others&#8217; posts is a separate power.</p>
<p>So those titles will be phased out in favor a system more like DamnTikiWiki&#8217;s, which shouldn&#8217;t be held against it. Assigning privileges to groups and putting users in the groups is a solid standard practice. </p>
<p>(I just handled a phone call from the client about this very subject. The whole world wants me to get it fixed ASAP. I can tell when the universe is trying to give me a hint.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eri</title>
		<link>https://habitablezone.com/2011/04/24/another-ruh-roh/#comment-30</link>
		<dc:creator>Eri</dc:creator>
		<pubDate>Mon, 25 Apr 2011 13:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=114#comment-30</guid>
		<description>Ah relief!  I&#039;ll play with that today, creating a post and then deleting it.  BTW, will editors be able to move someone else&#039;s posts from one forum to another by check marking topic boxes under edit?  I would assume authors won&#039;t have that capacity.</description>
		<content:encoded><![CDATA[<p>Ah relief!  I&#8217;ll play with that today, creating a post and then deleting it.  BTW, will editors be able to move someone else&#8217;s posts from one forum to another by check marking topic boxes under edit?  I would assume authors won&#8217;t have that capacity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>https://habitablezone.com/2011/04/24/another-ruh-roh/#comment-25</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Mon, 25 Apr 2011 05:54:19 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=114#comment-25</guid>
		<description>Not exactly. First, posts go into a trash bin, and only from the trash can they be permanently deleted. That what you were looking at? Second, the privilege is restricted to Editors, and you&#039;re one, the nearest thing in WordPress equivalent to a moderator. Most people are Authors, with fewer powers, and can&#039;t delete.

Right now WordPress lets everyone in each group have access everywhere in the system. The upcoming access control system will slice-and-dice it a lot more finely, like the old model where privileges are tailored to forums, and moderators have power over their own forums.</description>
		<content:encoded><![CDATA[<p>Not exactly. First, posts go into a trash bin, and only from the trash can they be permanently deleted. That what you were looking at? Second, the privilege is restricted to Editors, and you&#8217;re one, the nearest thing in WordPress equivalent to a moderator. Most people are Authors, with fewer powers, and can&#8217;t delete.</p>
<p>Right now WordPress lets everyone in each group have access everywhere in the system. The upcoming access control system will slice-and-dice it a lot more finely, like the old model where privileges are tailored to forums, and moderators have power over their own forums.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
