stendhal's appreciation for the absurd (tjernobyl) wrote in suggestions,
stendhal's appreciation for the absurd
tjernobyl
suggestions

Duplicate entry checking

Title
Duplicate entry checking

Short, concise description of the idea
A confirmation prompt on post if a journal entry is identical to the previous.

Full description of the idea
On occasion, when posting a new entry, the user may not get feedback confirming that the entry was successfully posted. The natural response for many users is to use their back button and press submit once again. If the problem causing the lack of feedback persists, the user may inadvertendly post an entry many, many times. My proposal is to add code that detects if an entry is substantially similar to the previous. If so, an additional confirmation prompt is generated. If one genuinely intends to make several identical posts, they may confirm and do so. If not, the default action is to ignore the superfluous post request

An ordered list of benefits

  • 1) Less congestion of friendslists when there are problems.
  • 2) More intuitive user experience.
  • 3) If a user genuinely wants to make duplicate posts, it is still possible.
  • An ordered list of problems/issues involved

  • 1) Greater CPU load per post.
  • 2) Additional database hit(s) per post.
  • 3) Cures a symptom rather than the root cause.
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • 1) Assign someone on the coding team to take a look at this.
  • 2) Get internationalization team to generate multilingual versions of the duplicate post confirmation page.
  • Tags: ~ historical
    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 

    • 4 comments