DIGG, INC. Patent applications |
Patent application number | Title | Published |
20130067491 | Content alerts - Detecting one or more preference events is disclosed. A rule defining a set of conditions associated with a set of preference events to be detected is received. An indication that one or more preference events has occurred is received. It is determined whether the set of conditions included in the rule has been met. If the set of conditions has been met, an alert is generated. | 03-14-2013 |
20130067357 | Evaluating content - Recording a user's preference for content is disclosed. An indication of a problem associated with the content is received, in response to only a single action taken by a user interacting with a web page. After receiving the indication, at least a portion of the web page is continued to be displayed. | 03-14-2013 |
20130067348 | RECOMMENDATION ENGINE - Determining an item to present to a first user is disclosed. Preference information is received that comprises the preferences of a plurality of users associated with one or more items. User correlations are determined from the received preference information. For the first user, a set of other users most correlated with the first user is determined. One or more items are presented to the first user based at least in part on the preferences of the other users. | 03-14-2013 |
20130067334 | AUDIENCE PLATFORM - An audience platform is disclosed. In a first example case, a first question is received. A preference event associated with the first question is received. A score is determined for the first question based at least in part on the preference. In a second example case, indications of a first and second potential interviewee are received. Preference events associated with the first and second potential interviewees are received. Scores are determined for the first and second potential interviewees based at least in part on the received preference events. A designated interviewee is selected based on the first and second scores. In a third example case, indications of a first and second potential awardee are received. Preference events associated with the first and second potential awardee are received. Scores are determined for the first and second potential awardees based at least in part on the received preference events. | 03-14-2013 |
20130067312 | Recording and indicating preferences - Recording a first user's preference for a content contribution submitted by a second user is disclosed. In response to only a single action taken by the first user interacting with a web page, an indication is received that a preference event occurred. The preference event is associated with the content contribution. Information associated with the first user's profile is updated. At least of a portion of the web page is continued to be displayed to the user after receiving the preference event. | 03-14-2013 |
20130066884 | EVALUATING AN ITEM BASED ON USER REPUTATION INFORMATION - Evaluating an item based on user reputation information is disclosed. Sharing event data is received. A graph is materialized from the received sharing event data. User reputation scores are determined based at least in part on the graph. A score is assigned to the item based at least in part on the user reputation scores of users associated with the item. | 03-14-2013 |
20130066864 | Detecting associates - Detecting, for a content item, associated preference events is disclosed. For the content item, a plurality of preference events from a plurality of users is received. The received preference events are accumulated. Associated events are detected. The effect of the events is reduced when assigning a status to the item. | 03-14-2013 |
20130066863 | Indicating a content preference - Recording a user's preference for content is disclosed. A first indication that a user has a first preference for the content is received. In response to receiving the first indication, the content is associated with the first preference. A second indication that the user has a second preference for the content is received. In response to receiving the second indication, the content is additionally associated with the second preference. | 03-14-2013 |
20130066858 | Dynamic submission and preference indicator - Indicating preference for a content contribution is disclosed. A request for information associated with the content contribution is received from a first entity. The status of the content contribution is determined. A response is provided to the first entity. Determining the status of the content contribution includes determining whether a submission of the content contribution was previously received. | 03-14-2013 |
20130066852 | Event visualization - Displaying a preference by a first user of a content contribution submitted by a second user is disclosed. A preference event by the first user is detected. A plurality of detected events is stored. In response to a query from a client, at least a portion of the stored detected events is stored. At least a portion of the received events is caused to be rendered graphically. | 03-14-2013 |
20130066841 | Accepting third party content contributions - Accepting a third party news article submission is disclosed. A first submission, including a first URL of a first news article that is different from a second URL of a previously accepted second news article submission, is received. One or more automated checks are performed on at least a portion of the first submission. Whether to accept the first submission is automatically determined based at least in part on the performed checks. | 03-14-2013 |
20130066822 | Promoting content - Promoting a candidate content item included in a plurality of content items is disclosed. A plurality of user reputation scores is received. For the candidate content item in the plurality of candidate content items, a content reputation score is determined based at least in part on a portion of the received user reputation scores. A determination of whether to promote the candidate content item is made based at least in part on the content reputation score. The candidate content item is promoted if it is determined that the candidate content item should be promoted. | 03-14-2013 |
20130066719 | DETERMINING ADVERTISEMENT PREFERENCES - Selecting an advertisement is disclosed. A preference event associated with a first advertisement is received from a first user. A quality score for the first advertisement is determined based at least in part on the received preference event. An advertisement fulfillment request is received. The request is responded to by selecting an advertisement based at least in part on the quality score of the first advertisement. | 03-14-2013 |
20130066710 | INCLUDING CONTENT ITEMS IN ADVERTISEMENTS - Generating an advertisement unit is disclosed. A selection of one or more content items is received. Each of the content items has an associated quality score. A representation of at least one of the content items is included in a generated advertisement. The advertisement also includes, for each included content item, an associated link configured to, when activated by a viewer of the advertisement, direct the viewer to an instance of the respective included content item. | 03-14-2013 |
20130066673 | Adapting thresholds - Promoting a candidate content item included in a plurality of content items is disclosed. A plurality of user reputation scores is received. For the candidate content item in the plurality of candidate content items, a content reputation score is determined based at least in part on a portion of the received user reputation scores. A determination of whether to promote the candidate content item is made based at least in part on the content reputation score and a dynamically adjusted threshold. The candidate content item is promoted if it is determined that the candidate content item should be promoted. | 03-14-2013 |
20110022966 | CONTENT VISUALIZATION - Displaying a preference by a user of a content contribution is disclosed. A preference event by the user is detected. A plurality of detected events is stored. In response to a query from a client, at least a portion of the stored detected events is stored. At least a portion of the received events is displayed in an interface. | 01-27-2011 |