Change "minimum security level" to "default security level"

Sep 29, 2007 13:21


Title
Change "minimum security level" to "default security level"

Short, concise description of the idea
Change the current setting that controls the minimum security level for new posts to control the default security level for new posts instead.

Full description of the idea

Livejournal currently has a " minimum security level" journal option that ( Read more... )

security, entry creation, default security, § no status

Leave a comment

Comments 13

burr86 October 4 2007, 21:05:46 UTC
This would be a huge change in functionality for people who use clients...

Reply

schnee October 4 2007, 21:28:44 UTC
Ah, didn't think of those. :/

Reply


lied_ohne_worte October 4 2007, 21:35:02 UTC
I wouldn't like that for communities. Say that I decided to keep my comm as members-only, so I set the minimum security level to reflect that. Then didnotreadrules goes to post an entry. They see that the drop-down says "friends-only", think that their important and world-changing post should really be seen by everyone, and change the security level to "public" because they don't even realise that the comm is supposed to be Members-only. As I as the maintainer can't edit the security level once they posted, I need to contact them and ask them to please lock the entry (or else I need to delete it).

Of course, I realise that malicious comm members can now also edit their entries to make them public after they posted them - however, the clueless/un-rule-reading ones most likely won't go that extra step. I like that maintainers have at least a limited ability to counteract the fact that it seems to be a basic rule of human behaviour that people never, ever read the manual.

Reply

lied_ohne_worte October 4 2007, 21:36:25 UTC
Oh yes - if you have a suggestion for un-confuscicating the FAQ, you can always post to lj_userdoc about it.

Reply


cmshaw October 4 2007, 22:19:49 UTC
The problem, as I understand it, is that the update page doesn't know which journal you're posting to -- for example, I have posting access to dozens of communities, only some of which have the security level set to members-only.

One option might be a checkbox to force the selected security setting over the journal's minimum setting.

Reply


ex_uniquewo October 4 2007, 22:20:30 UTC
You make good points but I agree with lied_ohne_worte. I also don't think editing an entry to lower its security level is that hard. Besides, if one has set a minimum security level then posts with lower security levels are rare enough that this is not a problem. Otherwise, setting a minimum security level may not have been the most sensible thing to do. :)

About #1, would it possible to mention on the update page what the minimum security level of the community/journal you're posting to is once you have selected it in the 'Post to' drop down menu?

Reply


justhuman October 5 2007, 02:39:11 UTC
I think that users are aware of the minimum security level that they set for their journal and rely on the fact that it will post at that security level regardless of what the edit.bml page may say. If they find it cumberson then I imagine that they might opt to a lower minimum security and add more security to the posts that need it.

I also agree with lied_ohne_worte that making it a two step process helps protect communities that wish posts to remain locked.

Reply

azurelunatic October 8 2007, 01:44:45 UTC
People may even come to rely on the minimum security level locking posts when posting from clients where specifying the precise security is difficult. If I posted to a locked-down community from my phone, say, and I found it unlocked, I would be wrathful, and my wrath would probably not compare to the wrath of any maintainers watching.

Reply


Leave a comment

Up