Roles People Play in Thinking Domains
- developers of (or within) thinking.domains
- The developers have no hierarchical rights at all just as develpers. Their effect as developers to create and trade tools.
- domain administrators – these are usually thought of as the people who own and operate the domain.
- want to find a better word for “administrators” – that has too much baggage in any new aged thinking
- want to find a better word for “administrators” – that has too much baggage in any new aged thinking
- masters (moderators, helpers, teachers, gurus) … maybe “gamemasters”
- authors
- apprentices
- novices
- guests

Discuss the names or the hierarchy ...
Tags
- roles
- thinking.domains
- hierarchy
Comments
Seth says
ok, so maybe we play the game the other way … and have an author earn the option to prevent edit on their thoughts.
2016-02-06 14:16:10 [item 19864#44816]
Here is an example of how such a hierarchy might play into our game. Suppose an author has a relationship to an apprentice in a group common to both. I think it would be reasonable that the author allow, and maybe eve encourage, the apprentice to edit their thoughts. Whereas they would not appreciate a novice in that same group mucking with their thoughts.
Now the relationship between the author and the apprentice is not something that we would expect the system to enforce … but it would need to allow it. That relationship is a person to person thingey and unknown in the plane of representations. But seems to me that the system could disallow a novice from editing an author’s thoughts. For them to have that ability, they would need to earn it.
Now the relationship between the author and the apprentice is not something that we would expect the system to enforce … but it would need to allow it. That relationship is a person to person thingey and unknown in the plane of representations. But seems to me that the system could disallow a novice from editing an author’s thoughts. For them to have that ability, they would need to earn it.
2016-02-06 14:19:49 [item 19864#44817]
I don’t think I want anyone else editing my thoughts or censoring my ideas. Commenting is fine, though. 

2016-02-06 14:23:24 [item 19864#44818]
strange … did you notice that i did that early this morning in Group expands to G+ … should the system have disallowed my edit?
2016-02-06 14:30:18 [item 19864#44819]
Yep – & you kinda messed it up. That’s why I didn’t want to share the pwd. I’m not sure that would be a good idea in open groups, either. Graffiti & filibustering are not much fun to suffer.
ok, so maybe we play the game the other way … and have an author earn the option to prevent edit on their thoughts.
Seth says
i see no problems with starting with “administrators” .
But it is unclear what you mean by it’s “penname” would be “admin”. What does that mean in the light of our solutions to Eliminate clumsiness for starting ?
2016-02-07 04:19:51 [item 19864#44826]
I think it will be fine to call these whatever you want in the domain at large, however in the domain startup screens I am simply calling the Administrator the Administrator with the penname admin.
Otherwise I have to explain everything in the screens and it becomes more difficult and complicated for someone to quickly install a new system. Everyone knows what an administrator is, I don’t have to explain it and people don’t have to remember what that weird account is named for the root user either.
Later, if the domain owner wants to change the administrator name and penname, they can in the normal way.
Otherwise I have to explain everything in the screens and it becomes more difficult and complicated for someone to quickly install a new system. Everyone knows what an administrator is, I don’t have to explain it and people don’t have to remember what that weird account is named for the root user either.
Later, if the domain owner wants to change the administrator name and penname, they can in the normal way.
But it is unclear what you mean by it’s “penname” would be “admin”. What does that mean in the light of our solutions to Eliminate clumsiness for starting ?
Seth says
i think we should discus roles here.
i think we should discus roles here.
Si says
I don’t think the term administrator has baggage. I think it is a well understood term that needs little explanation as most any other term would need. If you want a term with baggage, then it would be something like “CEO”. Root is almost as well known and good, but not quite. Wizard and all those fun terms, while fun, would require much doc to be used whereas admin requires virtually none at all.
I don’t think the term administrator has baggage. I think it is a well understood term that needs little explanation as most any other term would need. If you want a term with baggage, then it would be something like “CEO”. Root is almost as well known and good, but not quite. Wizard and all those fun terms, while fun, would require much doc to be used whereas admin requires virtually none at all.
Si says
thought 19955 pretty much says it all as to how roles, groups, and individual rights can be configured. You can configure a group to grant or remove any rights, on a group wide, or even an individual basis. So using groups as role control structures is entirely feasible. The remaining problem is, who gets to define group rights? Either admin’s only, or it gets rather tricky real quick.
thought 19955 pretty much says it all as to how roles, groups, and individual rights can be configured. You can configure a group to grant or remove any rights, on a group wide, or even an individual basis. So using groups as role control structures is entirely feasible. The remaining problem is, who gets to define group rights? Either admin’s only, or it gets rather tricky real quick.
Si says
p.s. to use groups to control roles you have to be using a panel or live thought in that group itself. Just having auto login privileges in a group, so that it shows as bold in your go to group list, does not give you any rights from that group in some other group.
p.s. to use groups to control roles you have to be using a panel or live thought in that group itself. Just having auto login privileges in a group, so that it shows as bold in your go to group list, does not give you any rights from that group in some other group.
Si says
For reference, here is the code that compiles rights. Anything that applies to user and or group rights happens as a result of this one block of code and the defined quads. It is very efficient because it accumulates and caches the rights for any user id or group id given so you can access it multiple times with only one trip to the sql database per page build.
For reference, here is the code that compiles rights. Anything that applies to user and or group rights happens as a result of this one block of code and the defined quads. It is very efficient because it accumulates and caches the rights for any user id or group id given so you can access it multiple times with only one trip to the sql database per page build.
// // Reads and caches rights for an author and optional group for that author // Returns compiled rights for that author as an array. // $groupRights = array(); $authorRights = array(); $myRights = array( // Default domain rights 'right-domain-tag' => 1, 'right-domain-comment' => 1, 'right-create-group' => 1, 'right-owner-think' => 1, 'right-member-think' => 1, ); function authorRights($uid, $gid = null) { global $authorRights, $groupRights, $myRights; if (!empty($gid)) { if (!@$groupRights[$gid]) { $result = myQuery("SELECT object FROM quads WHERE context IN ({1},'domain') AND subject IN ({2},'all') AND verb = 'rights' ORDER BY subject DESC, context DESC", $gid, $uid); $rights = myTable($result); if (!empty($rights)) { $groupRights[$gid] = 1; foreach ($rights as $v) { $r = json_decode($v['object']); foreach ($r as $rt => $ic) { $myRights[$rt] = $ic; } } } } } else { if (!@$authorRights[$uid]) { $result = myQuery("SELECT object FROM quads WHERE context = 'domain' AND subject = {1} AND verb = 'rights'", $uid); $rights = myTable($result); if (!empty($rights)) { $authorRights[$uid] = 1; foreach ($rights as $v) { $r = json_decode($v['object']); foreach ($r as $rt => $ic) { $myRights[$rt] = $ic; } } } } } return $myRights; }
Mark de LA says
jibberish time ! rolling away to something more useful than decoding it
…. ZZzzz...
p.s. Marks rights calculations are far more advanced. The use of his webcam, keyboard stroke time, choice of words and sentence structure, degree of smile, and skin tone flush, are all used to determine the particular ego identity in operation and select alternative rights blocks accordingly.
kewl! np i do demand a royalty as a test subject, however. 

np … we have a thrown set aside that is right up your alley. 



See Also
- Thought Real Groups with 8 viewings related by tag "thinking.domains".
- Thought thinking.domains logo with 8 viewings related by tag "thinking.domains".
- Thought against hierarchy with 5 viewings related by tag "hierarchy".
- Thought Some Come Here to Sit and Think with 5 viewings related by tag "hierarchy".
- Thought Quads for the minions with 4 viewings related by tag "roles".
- Thought FYI with 3 viewings related by tag "roles".
- Thought tag display and navigation project with 3 viewings related by tag "hierarchy".
- Thought Hyperlinks subvert hierarchy with 2 viewings related by tag "hierarchy".
- Thought about: athink.club with 1 viewings related by tag "thinking.domains".
- Thought How can I sell this on the street? with 1 viewings related by tag "thinking.domains".
- Thought Invitations To The Steering Committee with 0 viewings related by tag "roles".
- Thought a hierarchy of arrows (options) with 0 viewings related by tag "hierarchy".
- Thought hierarchy with 0 viewings related by tag "hierarchy".
- Thought OMG ... a new subdomain with a fresh tag cloud with 0 viewings related by tag "thinking.domains".