Mark (aradayn) wrote in suggestions,
Mark
aradayn
suggestions

Partially Private Entries

Title
Partially Private Entries

Short, concise description of the idea
Being able to mark sections of an entry such that they will only be visible to you.

Full description of the idea
There have been previous suggestions of making some sections of an entry visible only to friends or only to particular friends groups as well as public, but there are a myriad of problems with those.

This is much simpler - an entry will have one version visible to the people marked under its normal protection level, and one version visible to the writer of the entry.

A new LJ tag that allows you to mark a section within an entry as private.

Example:

This is my entry. Blah blah blah.
<lj-private>These are personal thoughts about what I just said, for my future reference</lj-private>
This is the rest of my entry. Blah blah blah etc.

I also imagine an option in the tag to allow it to mark a section as only visible to you when you're looking at such an entry while logged into your account. For example:

<lj-private display_as_private="true">This is a private section</lj-private>

would possibly display as:

Private: This is a private section


I'm sure a more interesting way of representing this section could be created. The blockquote and italicized "Private:" mark is just an example. I'd prefer not specially formatting private sections by default, but it might be better to make it turned on by default to reduce confusion in people using it.

An ordered list of benefits
  • Gives more flexibility in journaling
  • Reduces redundant entries with multiple protection levels
  • Grants greater creative expression in entry writing
  • Potentially increases people's incentive to journal if they want to share part of an issue but not all the details
  • Makes Livejournal more useful as a private journaling tool
  • It gives people a version of a previously requested feature that's been deemed impossible/impractical
An ordered list of problems/issues involved
  • It will take someone's time.
  • It may or may not be a popular feature when implemented. (But I'd imagine it could be made easily accessible in the rich text editor as LJ-cut is.)
Tags: lj-specific markup, security, § no status
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 36 comments