blastedheath (blastedheath) wrote in suggestions,

Change to Location field parsing

Change to Location field parsing

Short, concise description of the idea
A post option or journal configuration flag that prevents text entered in a post's 'location' field from being parsed as a Google Maps link.

Full description of the idea
A lot of users slip silly places into the Location field of their posts, or information that LJ's software can't properly translate into a usable Google Maps URI. Rather than add junk hyperlinks to journal entries, a per-user or per-post option to prevent that field from being parsed might be added.

An ordered list of benefits
  • Potentially eliminates junk links from silly entries like 'under the bed' or 'behind you', as well as from incorrectly formatted 'real' locations.

An ordered list of problems/issues involved
  • Yet another option for users to toggle when posting.
  • Not as transparent as the current arrangement.

An organized list, or a few short paragraphs detailing suggestions for implementation
  • Adding a 'Parse for Google Maps?' checkbox next to the Location field, or with the other per-post options would probably work best. The parsing code is already in; this is just a matter of putting it behind an IF...THEN statement.
Tags: currents, entries, location, ~ deferred - needs retagging
  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded