Browse Prior Art Database

Spoiler Prevention System for Narrative Plots Disclosure Number: IPCOM000247913D
Publication Date: 2016-Oct-11
Document File: 3 page(s) / 23K

Publishing Venue

The Prior Art Database


In order to avoid entertainment spoilers when surfing and searching online, a crowd sourcing system is proposed, composed by a centralized detection system and by a client-side component that collect user’s reports and enforce the rules gathered.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 43% of the total text.

Page 01 of 3

Spoiler Prevention System for Narrative Plots

    Here is disclosed is a crowd sourcing system to help user in safe-surfing and safe-search of any topic without incurring in spoiler contents.

    A spoiler is an element of a summary or description of any piece of fiction that reveals any plot details concerning the turn of events of an episode. Typically, the details of the conclusion of the plot, including the climax and ending, are especially regarded as spoiler material. More generally, it can also be used to refer to any piece of information that a user would not want to know regarding a particular topic in order to avoid this knowledge to "spoil" the enjoyment that he would otherwise have experienced. Thus spoiler blocking becomes of unquestionable relevance. Entertainment spoilers can be found in message boards, social networks, articles, reviews, commercials, and movie trailers. Basic rules of netiquette insist that spoiler could and should be avoided, if not at least they should be preceded by a warning or the spoiler itself has to be masked.

    There is no method to date to protect users from spoiler while surfing the web. Users may incur on a spoiler even on the extract of a web search. Some web browser extensions simply block any content matching the topic we want to avoid, without discriminating if the entry is really malicious and its potential danger (it does not discriminate the gravity of the spoiler).

    The centralized detection system here proposed, instead, is based on rules enforced by users' complaints and reports. The solution proposed aims to discriminate web contents on their level of spoiler danger by using a global repository that collects and analyze each user complaints in terms of distance between words found in the reported malicious piece of text; some word patterns are labeled as keywords and used to anticipate the spoiler warning in other contexts where they appear (this mechanism is similar to the one who detects spam emails or phishing attempts). The user who wants to be protected from spoilers will see the more likely spoiling entries obscured or marked, for example with a big warning, in red for major spoiler and yellow for less details, who tries to persuade the user not to click on it; other entries are shown unmodified. We revert the logic to show the user contents he may like according to his search and interests, trying exactly to prevent him reading about. In addition to the textual content, spoilers can also be based on still pictures, for example specific frames taken from a movie. In this case a picture can be marked as a spoiler and this tagging is reported to the central repository. The crawler analyzes the picture and extracts image recognition features with existing technique used to detect image similarities. Each extracted feature is then marked as spoiler in the central database and becomes part of the rules that are available to the client-side component. The client-side component is thus...