Security option -- password protected
Short, concise description of the idea
Option to password protect, rather than just user-limit, journal entries.
Full description of the idea
Sometimes I want to share some of my more personal posts with select people who are unlikely to use LiveJournal accounts. However, I do not want to make them entirely public so that _anyone_ can see them.
A solution to this would be to allow the public to enter a password that would unlock some entries even if they do not have an LJ account that's on the access list for them.
My current workaround has been e-mailing the entire entries to them, which is inefficient, and I have to repeat the entire process for every new person I talk to that I want to share them with.
E-mail is also very in-your-face, and I would rather have them come and try to extract the entries, if they feel like it, than have them feel obligated to read through them.
This would be one way to support "banning a particular user" when there is no mechanism for that right now other than ignorance of the journal.
An ordered list of benefits
Nice compromise between public and private for non LJ users.
Partial support for "banning a particular user," by not giving him the password for an otherwise accessible post.
An ordered list of problems/issues involved
Only benefits the users, like me, not the LJ site directly since it may discourage people who would otherwise get an account right away. However, I think it makes the site more attractive...
An organized list, or a few short paragraphs detailing suggestions for implementation
This is very similar to the way photo albums were handled on Photopoint before that went away, if you have any idea what I mean...
At entry creation time, add a textbox for "Entry password" on extended interface for non-public posts.
For people going to the livejournal.com/~ site, add a textbox to add a comma-delimited list of passwords, then click on a button for "Refresh" to see the new list of entries. (As a detail, this textbox should be present regardless of whether there are protected entries on the page, so as not to alert the viewer)
Internally, this involves adding an extra field for each entry object for a password (or a set of passwords, if we get more fancy).
You check the current permissions normally, and then OR them with the set of passwords the viewer has given as you iterate over each entry. Non-matching passwords can be noops.
If you allow sets of passwords, this gives a good degree of freedom in levels of security protection.