Deniz Sarikaya (denizsarikaya) wrote in suggestions,
Deniz Sarikaya

Fold lj user and lj comm into one tag

Fold lj user and lj comm into one tag

Short, concise description of the idea
The lj user tags and lj comm tags are a duplicate of information and lead to confusion in implementation. lj_dev vs. lj_dev and bradfitz vs. bradfitz.

Full description of the idea
Since LJ::ljuser handles users and communities, both, using 'type' 'C' when the user is a community, the abstraction obviously isn't coming from the code base, and when links are made, they'll go to the right user. So, we should stop confusing users. At the very least, if a user is inside a comm tag, it should be switched to a user tag, and vice versa.

An ordered list of benefits

  • User does not have to remember which tag to use, or look up less frequently used tags.
  • Icons will not be misleading (in the cases of lj_dev and bradfitz).
  • Less tags to keep track of on the development end.
  • Reduction in ambiguity. Why use two words when one will suffice?
  • An ordered list of problems/issues involved

  • This involves tags users use on a frequent basis, so if any of the existing tags are removed, users must be notified.
  • Need to go through history and fix user tags pointing at communities and vice versa.
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • Implement code checking on input end which validates lj user and lj comm tags, and replaces style of link in case it's wrong for the LJ::ljuser.
  • Go through databases to fix past entries.
  • Possibly remove misleading lj comm tag, and let everybody use user for everything.
  • Tags: lj-specific markup, § implemented
    • Post a new comment


      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded