Temporary modification of media content metadata

Abstract

Temporary modification of media content metadata is disclosed. An easy-to-use metadata modification system is described for blurring video metadata when sharing videos between different client devices to encourage viewership by recipients. A content item is received at a first client device associated with a first user account. The content item can include metadata associated with the content item and metadata associated with a sender of the content item. The content item can be displayed on the client device with at least some of the metadata blurred from view. In response to an input to the client device, the previously blurred metadata can be provided for display on the client device.

Description

[0001] Case Analysis

[0002] This application is a divisional application of Chinese Invention Patent Application No. 201880022011.6, filed on January 23, 2018. Technical Field

[0003] This disclosure generally relates to the metadata of modified content, and more specifically to the metadata of modified content when content is shared among users. Background Technology

[0004] With the support of numerous websites, video content sharing on websites has evolved into a phenomenon. Thousands of media outlets are released daily, and this number is increasing as devices and opportunities for capturing video become more readily available and widespread. As this phenomenon grows, media can also "spread" and reach millions of viewers within hours.

[0005] Media items, such as videos, contain metadata describing the characteristics of the content item, such as metadata related to the creation of the content item (e.g., the date and / or time of its creation, the creator) or its content (e.g., the title, details of performers featured in the media item, etc.). Sometimes, because videos are widely shared, the metadata shared with the video (e.g., title, creator, etc.) may be unsuitable for new recipients. For example, a title might have a specific meaning to the creator of the media item, but that meaning is lost when the media item is widely shared. One use of the metadata of a media item is to retrieve the media item in response to search queries, and the efficiency of performing searches depends on how accurately the metadata of the media item reflects its content and / or other attributes. Summary of the Invention

[0006] Content sharing interactions, also known as modified sharing interactions, involve creator client devices, sharer client devices, viewer client devices, and a media hosting service. The metadata of the content is modified and shared between devices. The media hosting service provides a platform for devices to host and share content and modify the metadata associated with that content. At various points during a modified sharing interaction, users interacting with client devices can modify the metadata. In one example, a creator client device might upload a video to the media hosting service using metadata associated with the video, such as author and title. A sharer client device shares the video with a viewer client device using an instruction to modify the video's metadata using the media hosting service. If the metadata associated with a media item is incorrect, it can be modified to more accurately reflect the content and / or other attributes of the media item, enabling efficient resource searching and retrieval processes. The media hosting service can monitor the modified metadata during a modified sharing interaction to influence future modified sharing interactions.

[0007] In one embodiment, a first client device associated with a first user account receives a content item for display. The content item includes content item metadata associated with the content item and sender metadata associated with a second user account and also associated with the content item. The content item is displayed on the first client device such that a modified portion of the content item metadata is displayed. In response to receiving input from a user of the first device, an unmodified portion of the content item metadata is displayed. The displayed unmodified portion of the content item metadata was previously displayed as a modified portion of the metadata. (That is, the display of the unmodified portion of the content item metadata had been previously suppressed to facilitate the display of the modified portion. As a result, a portion of the content item metadata is now displayed in a modified form (e.g., the unmodified portion of the content item metadata was previously obscured from view on the first client device).

[0008] In one embodiment, a content item is sent to a first client device in response to a send action initiated by a second user account on a second client device. In yet another embodiment, the sender metadata may include a flag indicating that the metadata of the content item to be displayed should be modified. The flag may be created in response to input from the second user account.

[0009] In one embodiment, the content item is created by a third user account on a third client device (i.e., a client device different from the first client device). The modification portion of the displayed content item metadata may also be based on creator metadata generated by the third user account. Creator metadata may include flags indicating that the metadata of the content item to be displayed should be modified.

[0010] In one embodiment, a computer program product for modifying shared metadata includes a computer-readable storage medium containing computer program code for performing methods including any embodiment or implementation described herein. In one embodiment, the computer-readable medium may be a non-transitory computer-readable medium, but this embodiment is not limited thereto; the computer-readable medium stores instructions for modifying shared interactions. These instructions are executed by a processor, causing the processor to implement any embodiment or implementation described herein.

[0011] In one embodiment, a system includes at least one processor and a computer-readable medium, which may be a non-transitory computer-readable medium, but this embodiment is not limited thereto. The computer-readable medium stores instructions that, when executed by the processor, cause the processor to perform operations including methods according to any embodiment or implementation described herein. In one embodiment, a system includes a media hosting service, a sharer client device, a viewer client device, and a creator client device to share content with modified metadata. The system participates in modified sharing interactions using methods according to any embodiment or implementation described herein. Attached Figure Description

[0012] Figure 1 An example computing environment for shared interaction using modifications made by a modification module is shown according to an example embodiment.

[0013] Figure 2A This is an illustrative example of a user interface for a device participating in a shared interaction in which the metadata associated with a video is modified without obscuring it, according to an example embodiment.

[0014] Figure 2B This is an illustrative example of a user interface for a device participating in a shared interaction in which metadata associated with a video is masked, according to an example embodiment.

[0015] Figure 2C This is an illustrative example of a user interface for a client device according to an example embodiment, in which the client device participates in a shared interaction involving modifications to a front-end interface for accessing a media hosting service, in which video-associated metadata is masked.

[0016] Figure 2D This is an illustrative example of a user interface for a client device according to an example embodiment, in which the client device participates in a shared interaction where video metadata is exposed to access a front-end interface of a media hosting service for modification.

[0017] Figure 3 The process flow that occurs on the sharer's client device during a modified sharing interaction, according to an example embodiment, is illustrated.

[0018] Figure 4 The process flow that occurs on the viewer client device during a modified sharing interaction, according to an example embodiment, is illustrated.

[0019] Figure 5 The process that occurs on the creator client device during a modified sharing interaction, according to an example embodiment, is illustrated.

[0020] Figure 6The process that occurs on a media hosting service during a modified sharing interaction, according to an example embodiment, is illustrated.

[0021] Figure 7 This is an interaction diagram of a shared interaction for modifications between a creator client device, a sharer client device, a viewer client device, and a media hosting service, according to one embodiment.

[0022] Figure 8 This is a high-level block diagram showing an example of a computer used as a video hosting server or client device.

[0023] The accompanying drawings illustrate various embodiments of the invention for illustrative purposes only. Those skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods shown herein can be employed without departing from the principles of the invention as described herein. Detailed Implementation

[0024] Modified sharing interactions in the described environment facilitate the sharing of content with modified metadata by users. Modified sharing interactions can be one or more interactions between client devices and media hosting services that facilitate uploading content to the media hosting service, manipulating and adding metadata associated with the content, searching for content on the media hosting service, sharing content among users, modifying and revealing metadata associated with the content, and collecting usage information about the metadata associated with the content throughout the modified sharing interaction. As mentioned above, this allows for more resource-efficient searching and retrieval by ensuring that metadata correctly reflects the content of the media item. Furthermore, modified sharing interactions can have other applications. For example, a first user might want to share a video item (or other media item) for training or education with a second user, but wants to retain some information about the video after the second user views it. Traditionally, this would require the second user to notify the first user once both users have viewed the video, and then the first user would send the retained information to the second user. Instead, in modified sharing interactions, some or all metadata, such as the video's title and / or author, can be masked from the view on the viewer's client device. The viewing client device may not modify the modified metadata after (or possibly simultaneously with) viewing the video. In this example, the viewer's client device can choose to reveal the previously obscured title and video author. This avoids the need for the first user to send this information in a separate message.

[0025] Figure 1An example computing environment 100 is illustrated for a shared interaction using a modification module, according to some embodiments. For example, a user of client device 110 can share content between client devices 110a-110c without exposing the metadata associated with that content, such as sending media without displaying a title. Devices 110a-110d may include application 112, which provides the ability to share media and metadata associated with the media. The associated metadata can be modified (e.g., masked, removed, or replaced) during the modified shared interaction. Masked metadata is used as an example of modified metadata throughout the document. Application 104 can interact with the front-end interface 132 of video hosting service 130 (i.e., a rendering layer such as a webpage) and other applications within environment 100 to facilitate the sharing of content with modified metadata.

[0026] Each client device 110 is a computer or other electronic device used by one or more users to perform activities including uploading media, participating in shared interactions to modify media, and viewing media content (e.g., video, audio, text, links, documents, etc.) received from the media hosting service 130. For example, client device 110 may be a personal computer running a web browser or dedicated software application that allows users to browse and search media available on the media hosting service 130 website through a front-end interface 132. In other embodiments, client device 110 may be a network-enabled device other than a computer, such as a mobile phone, personal digital assistant (PDA), tablet computer, laptop computer, wearable device, internet TV, or "smart TV."

[0027] Client device 110 includes software applications, such as application 112, which execute on the processor of the respective client device 110 to communicate with each other and with media hosting service 130 (e.g., during modified shared interactions). Applications executing on client device 110 perform various functions for interacting with other applications and modules on the client device and for participating in modified shared interactions between client device 110 and media hosting service 130. Examples of such applications may be web browsers, social networking applications, messaging applications, gaming applications, and media consuming applications. Each application 112 may be linked to a user account on media hosting service 130 associated with client device 102, a client device user, or a group of client device users. In some embodiments, the user account may be accessed via front-end interface 132 of media hosting service 130.

[0028] The setup data store 114 contains metadata and information associated with device users, client devices 110, user accounts, etc. During modified shared interactions, environment 100 can use the metadata and information to facilitate the sharing of modified metadata among devices within environment 100. In one embodiment, the information and metadata can be used to customize modified shared interactions for specific devices, user accounts, device groups, and user account groups (e.g., what metadata is masked, for how long, which users can modify metadata during the modified shared interaction, etc.). Metadata and associated information may include: inter-device security metrics, intra-device security metrics, network security metrics, authentication protocols, user account information and preferences, client device information and preferences, device user information and preferences, records of preferences and changes, and location-based information. For example, the setup data store 114 may contain metadata about the history of modified shared interactions between two devices, and the modification module 140 may modify the metadata based on previous modified shared interactions of the devices.

[0029] User interface 116 includes an input device for data input and an output device for display. The output device can display content provided by the user of client device 110, media hosting service 130, or client device. The input device enables the user to take actions (e.g., input) to interact with application 112 or media hosting service 130 via front-end interface 132. These actions can include typing, speaking, tapping, clicking, swiping, or any other input interaction. For example, a content creator using creator client device 110a can upload content to media hosting service 130. A sharer using sharer client device 110b can use the front-end interface and video search module to search for content and send content to a viewer via network 120 using viewer client device 110c. In some embodiments, interactions between the two client devices 110 and between client device 110 and media hosting service 130 can include information or metadata associated with media or modified sharing interactions.

[0030] User interface 116 (for example, Figures 2A to 2D The user interface is a display that allows the user to interact with the client device 110 during a modified shared interaction. The user interface can process input that can affect the modified shared interaction in various ways, such as: displaying new information on the user interface, triggering a modified shared interaction, displaying media or metadata during a modified shared interaction, manipulating metadata associated with content, or any other interaction, process, or event described within environment 100 during a modified shared interaction.

[0031] Content repository 118 is a storage system in which content files sent to and received from media hosting service 130 are stored.

[0032] Network 120 represents the communication path between client device 110 and media hosting service 130. In one embodiment, network 120 is the Internet, but it can also be any network, including but not limited to LAN, MAN, WAN, mobile, wired or wireless networks, cloud computing networks, private networks or virtual private networks, and any combination thereof. Furthermore, conventional encryption technologies such as Secure Sockets Layer (SSL), Secure HTTP, and / or Virtual Private Network (VPN) can be used to encrypt all or some of the links. In another embodiment, entities may use custom and / or dedicated data communication technologies to replace or supplement those technologies described above.

[0033] Media hosting service 130 provides media (e.g., video) to client device 110 via network 120. Media hosting service 130 includes a media library 144 for storing media and a front-end interface 132 for interacting with client device 110. Media hosting service 130 receives requests from client device 110 for media in media library 144 and provides the media in response. Additionally, media hosting service 130 can receive, store, process, and provide media uploaded by users and other entities on client device 110. Media in media hosting service 130 can be obtained from various sources. For example, media can be obtained from users, such as media submitted by users using upload server 138 via network 120 to upload video from content repository 118 on client device 110 to media library 144 on media hosting service 130.

[0034] Media hosting service 130 includes multiple “modules,” which refer to hardware components and / or computing logic used to provide specified functions. Modules can be implemented using hardware, firmware, and / or software (e.g., a hardware server including computing logic). It should be understood that the mentioned components represent one embodiment of the disclosed methods, and other embodiments may include other components. Furthermore, other embodiments may lack the components described herein and / or distribute the described functionality among components in different ways. Additionally, functionality attributable to multiple components may be incorporated into a single component. When the modules described herein are implemented as software, the modules can be implemented as standalone programs, but may also be implemented in other ways, such as as part of a larger program, as multiple separate programs, or as one or more statically or dynamically linked libraries. In any of these software implementations, the modules are stored on a computer-readable permanent storage device of media hosting service 130, loaded into memory, and executed by one or more processors of the system computer.

[0035] Front-end interface 132 may be a presentation layer of media hosting service 130, allowing users to interact with the back-end data manipulation module of media hosting service 130. Front-end interface 132 receives requests from client devices and communicates with other aspects of media hosting service 130 to process those requests. Front-end interface 132 can be accessed via a web browser or via application 112 installed on the client device. Specifically, for example, front-end interface 132 allows users of client device 110 to interact with media hosting service 130 to participate in modified sharing interactions. Front-end interface 132 may also provide elements of user interface 116 to client device 110, particularly in web-based implementations where the user interface is provided as part of a webpage rather than as part of a dedicated software application. Front-end interface 132 is also configured to collect user interactions with media hosting service 130. For example, front-end interface 132 collects these interactions if a user chooses to modify (e.g., obscure or reveal) metadata associated with shared media. (The front-end interface may also collect other user interactions, such as when a user clicks on a webpage, views a video, makes a purchase, opens a document, fills out a web-based form, etc.) In addition, the interactions between different items presented by the media hosting service 130 are collected by the front-end interface 132 and recorded in the modules, servers and storage units of the media hosting service.

[0036] Media service module 134 receives a request from a client device to view (or play back) a specific media item from media hosting service 130. From the client device's perspective, the device can execute the request by: browsing different categories within media hosting service 130, receiving input from a search results webpage indicating a click on a link to a video, or accessing information and metadata associated with a modified shared interaction (e.g., click interaction history). The request sent by the client device may include an identifier of the content the user wishes to access (this may be automatically included when the user clicks a link to a video). Media service module 134 uses this identifier to search for and locate where the video is stored in media library 144. Media service module 134 provides the media requested from media hosting service 130 to client device 110 for display on user interface 116. In some embodiments, the media service module may use the identifier to provide media with modified metadata.

[0037] The video search module 136 processes any search queries received from the user by the media hosting service 130 via the client device 110. Search queries sent from the client device 110 to the media hosting service 130 include search criteria, such as keywords, which can identify media that the user is interested in viewing. The video search module 130 uses the search criteria to query the metadata of video files stored in the media library 144. Search results from the queries are sent to the client device 110 via the network 120, allowing the search results to be presented to the user through the user interface 116.

[0038] Any content received from a client device via network 124 for publication to media hosting service 130 is transferred via network 120 from the content repository 118 on the client device to the upload server 138 for processing. Content file processing includes assigning an identifier to newly received content. Media processing may also include formatting (e.g., code conversion), compression, metadata tagging, content analysis, and / or other data processing methods. Client device 110 sends information and video files to media hosting service 130. This information may describe the video (e.g., title, description, and tag information). This information may also include an indication of the media type, which, for uploaded media, may be "video". Upload server 138 stores the processed content in media library 144 and stores this information as metadata for the content.

[0039] Modification module 140 can modify (e.g., mask and reveal) the metadata of shared content during shared interactions. Modification module 140 can receive requests from sharer client device 110b to modify the metadata of media stored in media library 144 when shared with viewer client device 110c. When viewer client device 110b accesses media via a front-end interface or when media is provided to a viewer client device with media service module 134, modification module 140 provides the modified metadata associated with the video to the viewer client device. The media hosting service can also receive requests from the viewer client device to modify the metadata associated with the video, and the modification module can provide the modified metadata to the viewer client device.

[0040] Alternatively, instead of retaining the original metadata and providing modified metadata upon request, modification module 140 may provide the viewer client device with video-related metadata that has an indicator that application 112c operating on the viewer client device should mask at least some metadata. The viewer client device may then request the exposure of the video-related metadata, and the application operating on the viewer client device will expose the metadata that was previously marked as masked.

[0041] Modifying metadata associated with media during shared interactions can be accomplished in several different ways: making the text of the metadata illegible (e.g., blurring, blackening, etc.), removing obscured metadata from the view (e.g., not displaying metadata), providing an image to be displayed before the metadata, providing alternative text to be displayed before the metadata, providing alternative metadata to replace the display of obscured metadata, or any other method or combination of methods for modifying metadata information associated with the video. Further modification of the metadata can reverse any of these modification techniques (e.g., revealing obscured metadata or obscuring revealed metadata).

[0042] Throughout the shared interaction event, the client device may request (or determine) to modify (e.g., mask or reveal metadata) the media. This request can be made using a variety of methods, including: clicking an icon on the user interface of client device 110, reading or sending a flag indicating that metadata should be modified, appending new metadata to the video, typing input into client device 110, changing the URL associated with the video location in the media hosting service (e.g., from the URL of a video with unmodified metadata to the URL of a video with modified metadata), modifying or changing the video's identifier (e.g., from the identifier of a video with unmodified metadata to the identifier of a video with modified metadata), or any other similar method in environment 100. In some embodiments, the modification or disclosure of metadata can be automated using a variety of methods, including accessing settings stored in the settings data storage 114 of the client device, accessing information or metadata stored in the user database 142, or interacting with the media usage module 146.

[0043] User database 142 stores information and metadata that can be presented to users or used by other modules in the media hosting service to facilitate functionality during modified shared interactions. User database 142 may include metadata associated with users, user accounts, media, or client devices. Metadata may include geolocation, preferences, device information, device settings, or any other information associated with user interactions within the user or environment 100, especially information that may be useful for modified shared interactions.

[0044] Media library 144 is a storage system in which content files received from and sent to client device 110 are stored. Media library 144 may be a computer-readable permanent storage device (e.g., RAM, hard disk drive, etc.) of media hosting service 130.

[0045] The media usage module 146 collects, stores, and updates metadata associated with the content stored by the media hosting service 130. Content may be accompanied by associated metadata such as: identifier, title, author, tags, description, icon, thumbnail view, comments, view count, and rating. Metadata can be updated based on interactions between users and client devices, between client devices, between client devices and the media hosting service, between client devices and the network, or any other interaction within environment 100. For example, if a user has sent a video to another user, the video usage module 146 may also contain information about previous similar interactions. The video usage module 140 can interact with the modification module 140 to mask metadata during modification interactions to collect masked media usage or to mask media based on usage information metadata.

[0046] For example, a first client device sends video to a second client device. The first client device instructs that the video should have its metadata masked during a modified sharing interaction. The video usage module 146 recognizes that the second client device previously received video from a separate client device in a separate modified sharing interaction. The video usage module can notify either the first or second client device that the video was previously viewed, previously masked, previously shared, etc. In a similar example, the second client device has not yet viewed the video shared during the modified sharing interaction. The second client device views the video with masked metadata, which is revealed after viewing. The video usage module 146 can update and store the metadata associated with the video and the interaction (e.g., incrementing the view count, marking media as viewed, marking media as shared, etc.).

[0047] To simplify and clarify this specification, content received and shared by the media hosting service 130 may be referred to as video, video file, or video item; however, it should be understood that the media hosting service 130 may receive and share content of any media type. This content may be referred to as media, media item, or project. Therefore, the operations described herein for modifying media in a modification-sharing interaction can be applied to any type of media item, not just video; other suitable types of content items include audio files (e.g., music, podcasts, and audiobooks), documents, multimedia presentations, and digital purchases of goods and services. The metadata for each project includes an indication of the project's media type, such as video, audio, document, purchase, or presentation.

[0048] To further simplify and clarify this specification, the following modified sharing interaction will be used: Chris (first client device user 110a) creates a video and uploads it to media hosting service 130. John (second client device user 110b) accesses the video via the media hosting service. John chooses to send the video with masked metadata to Annie (third client device user 110c). Annie accesses the video with masked metadata to view via media hosting service 130 and can choose to display the masked metadata. Throughout the modified sharing interaction, the metadata is updated, and the server can notify Chris, John, and Annie.

[0049] Figure 2A This is an illustrative example user interface displayed on a client device participating in a sharing interaction where the metadata is not obscured. John sends a video to Annie, where the video's metadata reveals important aspects of the media's storyline, such as, "Woman escaped a shark! So close!" Annie can choose not to view the video because the metadata related to the video presented to her during the sharing interaction provides too much background, such as, "I'll watch it later. Sounds like she was lucky to survive the shark." In another example, a friend sends a video to a second friend with the title "Small lizard escapes a swarm of snakes." The second friend can choose not to view the video because the video's title reveals the end of the video. In these traditional types of sharing interactions, the viewing user can choose not to view content that limits the virality and spread of the shared content. As mentioned above, this may be undesirable in some situations, such as when sharing videos for training purposes.

[0050] User interface 202 may include a visual representation of any of the following: a user interacting in a masked shared event; a user interface (UI) element 204 that allows connection to other applications or devices within the environment; or a UI element 206 that allows access to and manipulation of settings in the settings module.

[0051] The user interface includes a region 208 for viewing content associated with a modified shared interaction. Region 208 may include one or more icons for stopping or starting content playback, and indicators of metadata associated with the video (i.e., video length, video quality, subtitles, etc.). Region 208 can also be expanded or reduced via interaction with interface icon 210 or through settings within the settings module. The user interface also includes a region 220 for displaying metadata associated with the video, which can be obscured during a modified shared interaction. The user interface includes a region 214 that displays interactions between participants in a modified shared interaction. This region is configured to display text, video, or any other information or metadata associated with the obscured shared event. The user interface includes one or more icons 212 for interacting with the metadata. These icons, when selected, can indicate mood regarding the metadata, modify (e.g., obscure or reveal) the metadata, send or receive metadata, or any other interaction described therein. The user interface includes a region 216 that allows input from client devices. Access to this region can generate an input interface such as keyboard 218, or can permanently display the keyboard. This area may also include UI elements 222 for inputting other types of data, such as videos, links, images, etc. In some embodiments, the information or metadata displayed within area 214 may also be obscured during modified shared interactions.

[0052] Figure 2B This is an illustrative example of a user interface for a device participating in a modified sharing interaction, where metadata associated with the video is masked. John sends a video to Annie, and the metadata is masked, such as making the video title difficult to read, with an overlay of "John has masked this information. Tap to undo." Annie can send John a message indicating that she is interested in watching the video and can continue watching because she doesn't know the outcome or topic, such as "Oh! This looks interesting. Can't wait to see what happens. I'll watch it now." Annie watches the video, and the metadata can be revealed through several methods described in the process below. She informs John that she has watched the video, is impressed with it, and will share it with her brother, such as "Wow! Very cool. She's lucky to have escaped. I'll send this to my brother." Modified sharing interactions can increase online media viewership and encourage media dissemination.

[0053] Figure 2C This is an illustrative example of a user interface for a client device that participates in a modified shared interaction of the front-end interface for accessing a media hosting service, where video metadata is masked. At least some metadata associated with the video is masked from the viewing user, including the title and related suggested videos.

[0054] The user interface may include a region 222 for displaying content that can be expanded or shrunk, one or more icons for stopping or starting content playback, and indicators of metadata associated with the video (i.e., video length, video quality, subtitles, etc.). The user interface includes a region 220 for displaying metadata associated with the video, which may be obscured during modified sharing interactions. The user interface includes an icon 228 that allows subscription to content from the content creator. The user interface includes a region 226 that displays content and metadata stored within the environment associated with the content shared in the modified sharing interaction. In the example shown, the content in this region has been obscured during the modified sharing interaction. The user interface may include an icon 230 for interacting with additional content and metadata stored within the environment associated with the content shared in the modified sharing interaction.

[0055] Figure 2D This is an illustrative example of a user interface for a client device that participates in a modified shared interaction to access a media hosting service, where metadata associated with the video is exposed. At least some metadata associated with the video, including the title and associated suggested media, has already been exposed to the viewing user. Figure 2C and Figure 2D For example, the video's metadata (e.g., title 232a) and associated metadata (e.g., next video 234a) are in Figure 2C The video is obscured. After the user on the client device selects to expose the obscured metadata (e.g., title 232b), the associated metadata (e.g., the next video 234b) is exposed. The elements of the user interface described above may alternatively be oriented within the interface. The user interface may also include elements not described above, but still allow for modified shared interactions. In some embodiments, elements of the user interface may be displayed within other applications on the client device (e.g., aspects of the user interface displayed in a web browser).

[0056] Figure 3The diagram illustrates a process occurring on a creator client device during a modified sharing interaction 300, according to one embodiment. Creator client device 110a can upload 310 videos from a content repository 118a on the client device to a media hosting service 130 via network 120. Creator client device 110a can interact with a front-end interface 132 and a video upload server 138 to store the video in a media library 144 and create a set of metadata associated with the video. Creator client device 110a can interact with a modification module 140 and send 312 modification settings for the video to the video hosting service, such as: the duration of the modification, whether media can be modified during the modified sharing interaction (e.g., media modification is prohibited / allowed / forced), which types of metadata can be masked (e.g., title, device information, etc.), and which parts of the metadata can be masked (e.g., only a portion of the title, not the entire title), etc.

[0057] For example, Chris has digitally remastered the iconic music video "Never Let You Down - Nick Pastley" and stored it in a content repository 118a on his creator client device 110a. The creator client device receives input via network 120 130 to upload the video to a media hosting service through the user interface 116a of application 112a. Creator device 110a interacts with front-end interface 132 and upload server 138 to add metadata to the video, making it searchable using video search module 138. Chris has no intention of encouraging the spread of his video. Creator client device 110a instructs a modification module 140 not to obscure the metadata associated with the video when it is shared between users by default. When shared by creator client device 110b in a modified sharing interaction, creator client device 110a determines which aspects of the metadata should be obscured when sharing between device users.

[0058] Creator client device 110a can receive 314 updated metadata associated with the video. Creator client device 110a can receive this metadata from the video usage module 146 of media hosting service 130 or directly from applications of other client devices 110 in the operating environment 100. The received metadata may include: notifications that the device has shared / received video, notifications that the device's user has chosen to show / mask shared video and metadata, notifications of automatically shown / masked metadata, etc. The received metadata can be used to modify other aspects of the sharing interaction.

[0059] Figure 4The process occurring on the sharer client device 110b during a modified sharing interaction 300 is illustrated. During the modified sharing interaction 300, the sharer device 110b can access video 410 via media hosting service 130 through network 120 using user interface 116b of application 112b. The sharer device can interact with front-end interface 132 of media hosting service 130 (e.g., via user input) to share video from media library 144 during the modified sharing interaction 300. Media hosting service 130 can provide video to sharer client device 110b for playback on user interface 116b using media service module 134 when accessing the video. In other embodiments, accessing the video only provides the sharer client device 110b with metadata associated with the video.

[0060] For example, John's sharing device can access videos on media hosting service 130 by searching for the term "Nick Pastley" and clicking "Never Let You Down - Nick Pastley," which is the first item provided by user interface 132 of media hosting service 130 on his device 110b. Media hosting service 130 provides the video and its metadata to John's sharing device via the network, and the sharing device can optionally (e.g., via user input) view the video's metadata without playback. In one embodiment, John's sharing device's settings module 114 authenticates his device to media hosting service 130, and media hosting service provides the video to his device 110b, which is configured to be displayed on John's device.

[0061] After accessing the video, the sharer client device 110b can determine 412 (e.g., via user input or information stored in the setup data storage 114b) to mask metadata associated with the video during the modified sharing interaction 300. Determining the metadata of the video to be masked during the modified sharing interaction 300 can add new types of metadata associated with the video (e.g., a notification that metadata has been masked) or additional metadata (e.g., a masked version of media metadata, etc.). During the modified sharing interaction 300, when determining the masked metadata, the sharer client device 110b can select (e.g., via user input) which metadata and / or portions of metadata associated with the video will be masked or revealed. In other embodiments, the sharer client device 110b can change, replace, or insert new metadata (e.g., from user input, modification module 140, setup data storage 114, etc.) to be displayed as masked or revealed during the modified sharing interaction, such as entering a replacement title for the video or a label indicating who masked the metadata. Metadata that is changed, replaced, or inserted during a shared modification interaction can be shared as a notification between devices participating in the shared modification interaction, or displayed on any available area of ​​the user interface 116 of the participating client device 110, where the original data would otherwise be displayed. The sharing device can also determine (e.g., from user input, modification module 140, setting data storage 114, etc.) to provide video playback offset metadata to indicate where video playback will begin. This offset metadata can be provided to avoid displaying embedded titles or spoilers to the viewer client device at the start of video playback. Modification module 140 modifies the appropriate metadata based on this determination.

[0062] For example, after accessing the 310 video "Never Let You Down - Nick Pastley," John's client device can determine the masked video metadata by receiving user input from a user (e.g., John) who selects a UI element labeled "Mask Video Metadata" in the user interface of the sharing client device. In one embodiment, John's sharing device, which determines the masked video metadata, provides John's sharing device with options for which metadata to mask; that is, all or part of "Title," "Artist," "View," "Related Media," etc. John's sharing device selects "Title" and "Artist" to modify by receiving user input indicating the selected options. In another embodiment, John's device automatically selects "Title" and "Artist" as the video metadata to mask based on settings stored in the settings data storage 114 of John's device 110b. John's sharing device selects (e.g., via user input) to insert representative metadata associated with the video to display along with the masked metadata, such as "Check out this funny fat cat video!" John's sharer device also selects (e.g., via user input) to replace the video's artist from "Nick Pastley" to "John's Grandma". In another embodiment, the settings in John's sharer device's settings module automatically insert metadata representing "John has selected to mask the video title and artist. Click Undo".

[0063] After selecting to mask metadata during the modified sharing interaction 300, the sharing client device 110b can share 414 video and masked metadata with different viewer client devices 110c via network 120. Sharing video may include sharing any metadata associated with the video used to identify it, including: an identifier for the video stored in the media library, the video's URL, a short link to the video, the video's title, a clickable icon indicating the video's location in the media library, interactive locations on the user interface, or the like. Sharing video and metadata can occur using several different communication protocols or combinations of communication protocols configured to interact with the network in environment 100; namely, SMS messages, messages from applications on the client device, email messages, or any other communication method available for device-to-device interaction. The video usage module 146 can store and update any metadata associated with the shared video and media masking metadata.

[0064] For example, John's sharing device could send a video "Never Let You Down - Nick Pastley" and metadata associated with that video (e.g., masking metadata, instructions to mask metadata, inserted metadata, etc.). John's sharing device sends the video using an SMS message containing a short link indicating the video's location in the media library 144 of the media hosting service 130. The short link could include metadata associated with a modified sharing interaction, such as a flag indicating that the media hosting service should mask the video's metadata when the short link is clicked.

[0065] After sharing video (or the location of the video in a video hosting service) in the modified sharing interaction 300, the sharing device can receive 416 updated metadata associated with the video or metadata associated with the modified sharing interaction. The sharing device 110b can receive this metadata from the video usage module 146 of the media hosting service 130 or directly from the application 104 operating on another client device 110 in environment 100. The received metadata may include: notifications that the viewer client device 110b has received the video, notifications that the viewer client device 110b has chosen to reveal obscured metadata, or notifications that obscured metadata has been automatically revealed, etc.

[0066] For example, John's sharer device can receive the following notification from the video usage module 146 on his device 110b: Annie's viewer device receives a video with masked metadata, accesses the video for playback using the media hosting service 130, and the masked metadata is automatically revealed.

[0067] Figure 5 The process occurring on viewer client device 110c during modified sharing interaction 300 is illustrated. Viewer client device 110c can receive 510 shared video (or the location of the video in media hosting service 130) and video metadata from sharer client device 110b. The video metadata received from the sharer can be at least partially masked by modification module 140 of media hosting service 130. Receiving video can occur in several ways using any combination of sharing methods and communication protocols within environment 100 as described above. Video usage module 146 can store and update any metadata associated with modified sharing interaction.

[0068] For example, Anne's viewer device can receive an SMS from John containing a short link to an identifier indicating the video's location in the media library 144 of the media hosting service 130. The message and short link may also include information such as metadata associated with the video that will be modified when accessed on the viewer client device 110c (see module 140). Figure 1Masking. For example, when Anne's viewer device selects a link, instead of modifying the metadata stored within the media hosting service, the media hosting service provides masked metadata to her viewer device.

[0069] Viewer client device 110c can access the metadata of video 512 and masking using an identifier provided by the sharing client device. Viewer client device 110c can access the video and metadata via media hosting service 130 through network 120 using the user interface 116c of application 112c running on viewer client device 110c. Viewer client device can input an identifier of the media location in media library 144 using the user interface 132 of media hosting service 130. At least some metadata associated with the video accessed by the viewer client device is displayed on the viewer client, modified by module 140 (see [link]). Figure 1 Masking. In one embodiment, media hosting service 130 may provide video to viewer client device 110b so that it can be automatically played back on user interface 116b using media service module 134 when accessing the video. In other embodiments, accessing the video only provides the viewer client device with the exposed metadata associated with the video, and does not provide metadata related to masking of the video. Access to the video via media hosting service 130 can be determined by settings stored in settings module 114c of the client device or user database 142 of media hosting service 130.

[0070] For example, Anne's viewer device can access a video sent to her by John's sharer device via an SMS message on media hosting service 130 by clicking a short link sent to her viewer device by John's sharer device. Media hosting service 130 provides the video, such as "Never Let You Down - Nick Pastley," so that Anne's viewer device can view it on app 112c on her device 110c. Instead of displaying the original metadata associated with the video on the viewer device, masked metadata (e.g., the masked view count of the video) and metadata modified by John's sharer device (e.g., a title different from the original title of the video) are provided for Anne's viewer device to view, such as "Check out this hilarious fat cat video!" along with the masked video title and artist details. Figure 1 See the description of modification module 140. Anne's device settings module 114c may contain preferences that allow the media hosting service 130 to provide masked metadata to her device.

[0071] After accessing the video, Annie's viewer device can choose to reveal the masked metadata of video 516 (514) or replay video 518. Viewer client device 110c can choose to reveal the masked metadata (514) by interacting with the front-end interface 132 of media hosting service 130 and modification module 140 (e.g., via user input) using the user interface 116c of application 112c. Viewer client device 110c sends a request to reveal the metadata to media hosting service 130 and modification module 140, and media hosting service 130 and modification module 140 reveal the masked metadata. In an alternative embodiment, it is not necessary to request the revealed metadata from the media hosting service, and the reveal occurs locally on application 112c of viewer client device 110c.

[0072] Alternatively, the viewer client device can select to play back the 518 video by interacting with the user interface 116c of the application 112c and the user interface 132 and media service module 134 of the media hosting service 130. The media hosting service 130 uses the media service module 134 to provide the video to the viewer client device 110c for playback on the user interface 116c. The metadata for selecting masking, revealing masking, and playing back the video can be determined by settings stored in the settings data storage 114c of the client device or in the user database 142 of the media hosting service 130.

[0073] For example, before starting playback by clicking the icon presented to her on her device's user interface, Anne selects which metadata to reveal on her client device. The metadata John selects to reveal is then revealed, and the displayed metadata becomes the metadata originally associated with the video; for example, "Check out this funny fat cat video!" becomes "Never Let You Down - Nick Pastley" and no metadata is revealed. In another embodiment, Anne initiates playback by pressing the play icon on the user interface without revealing the hidden metadata, and the video "Never Let You Down - Nick Pastley" begins playing.

[0074] Similar to the previous description, at any point during video playback 518, if the metadata has not yet been exposed, the viewer client device can choose 520 to expose 522 the obscured metadata.

[0075] Video playback can end 524, and if the metadata has not yet been exposed, the viewer client device can choose to expose the masked metadata again 426, similar to what was previously described. In some embodiments, when video playback ends, the masked metadata is automatically exposed using the modification module 140 of the media hosting service 130. See also: Figure 1The description of the modification module 140. Automatically exposed metadata can also be determined by settings stored in the settings data storage 114c of the client device or the user database 142 of the media hosting service 130.

[0076] Subsequently, the video usage module 146 of the media hosting service 130 (automatically or via user input) updates 528 the metadata associated with the interaction (e.g., an indication that a video has been viewed) and the metadata associated with the video (e.g., a view count). In some embodiments, it is possible to... Figure 4 and / or Figure 5 The metadata associated with the interaction or video is updated during any step of the process.

[0077] Figure 6 The process occurring on media hosting service 130 during modified sharing interaction 600 is illustrated. Media hosting service 130 receives 610 video content from creator client device 110a, which interacts with user interface 132 and upload server 138, for uploading to a media library. Media hosting service receives 612 an access request for a video in the media library from sharer client device, which interacts with user interface and video search module. Media hosting service provides 614 the video and associated video metadata to sharer client device using media service module. Media hosting service receives 616 an instruction from sharer client device, which interacts with user interface, to mask metadata using modification module. Media hosting service modifies metadata using modification module. Media hosting service receives 618 a request from viewer client device to access a video in the media library. Access request may include instructions to mask metadata associated with the video on viewer client device (e.g., metadata associated with the video or user input), or media hosting service may store information (e.g., user settings) about the metadata that viewer client device will receive masked during this modified sharing interaction.

[0078] The video hosting service provides the viewer client device with 620 video and video-related metadata, wherein at least some of the metadata is masked by a modification module. In some embodiments, the media hosting service receives from the viewer client device 622 an instruction to expose the masked metadata using modification module 140. The media hosting service can then provide the viewer client device with the requested exposed metadata 624. See also Figure 1The description of the modification module 140 is as follows. At any point during the above process, the media hosting service may use the video usage module 146 to update 628 and / or store metadata associated with the video (or metadata associated with the modified shared interaction) to the creator client device, the sharer client device, or any device associated with the interaction in environment 100. At any point during the above process, the media hosting service may use the video usage module to send 628 metadata associated with the video or metadata associated with the occluded shared event to the creator client device, the sharer client device, or any device associated with the event in environment 100.

[0079] Figure 7 This is an interaction diagram of a modified sharing interaction 300 between a creator client device 110a, a sharer client device 110b, a viewer client device 110c, and a media hosting service 130, according to one embodiment. The creator client device uploads 710 videos 710 from a content repository 118a on client device 110a to the media hosting service 130 via network 120 using the user interface 116a of application 116a. During the upload, the creator can interact with the front-end interface 132 of the media hosting service 130 to access the upload server 138 to upload the video and assign metadata to the video during upload.

[0080] The sharing client device 110b accesses video 712, for example, by searching for videos using the video search module 136 on the media hosting service 130. The sharing client device accesses the front-end interface 132 of the media hosting service 130 via network 120 using the user interface 116b of application 112b. Access to the video can occur by entering (for example, into user interface 116) an identifier that identifies the location of the video stored in the media library 144.

[0081] Media hosting service 130 uses media service module 134 to provide 714 videos and associated metadata to sharer client device 110b. The video and video metadata can be provided to the sharer client device 110b, which interacts with the front-end interface 132 of media hosting service 130, using application 110b and user interface 116b on the sharer client device 110b. In some embodiments, providing the video to the sharer client device 110b configures the video for playback on the user interface 116b of the sharer client device 110b. In other embodiments, providing the video to the sharer client device 110b only provides the video and video metadata to the sharer client device.

[0082] The sharing client device uses the modification module 140 of the media hosting service 130 to mask some or all of the video metadata for further use in the modified sharing interaction 300. The sharing client device uses the user interface 116b of application 112b to access the front-end interface 132 of the media hosting service 130 via network 120 to interact with the metadata associated with the video via the modification module 140.

[0083] The sharing client device 110b and the viewing client device 110c share video 718. Video sharing can be accomplished using any communication protocol within environment 100 via any communication method, which can provide an identifier associated with the location of the video within media hosting service 130 to another client device. The identifier may contain metadata indicating that the video should have its metadata masked during modified sharing interaction 300.

[0084] Viewer client device 110c accesses video 720 on media hosting service 130 using an identifier provided by sharer client device 110b. The video's metadata is masked by modification module 140 of media hosting service 130. Viewer client devices access the video via network 120 using user interface 116b of application 112b and front-end interface 132 of media hosting service 130.

[0085] Media hosting service 130 uses media service module 134 to provide viewer client device 110c with 722 metadata related to the video and video, wherein the metadata is masked by modification module 140. The video and video metadata can be provided to the client device 110c interacting with the front-end interface 132 of media hosting service 130 using application 110c and user interface 116bc on viewer client device 110b. Users can choose to expose the masked metadata when the video is provided. In some embodiments, providing video to viewer device 110c configures video playback on the user interface 116c of viewer client device 110c. Users can choose to expose the masked metadata when the video is played back on viewer device 110c, or the video metadata can be automatically exposed after playback.

[0086] After the viewer client device chooses to expose video metadata, the viewer client device 110c can access the exposed metadata 724 from the media hosting service 130 using the modification module 140. The viewer client device accesses the exposed metadata via the front-end interface 132 of the media hosting service 130 through the network 120 using the user interface 116b of application 112b. In some embodiments, the exposure of metadata on the viewer client device 110c does not require communication with the media hosting service 130 and occurs locally within application 112c.

[0087] The media hosting service 130 uses the modification module 140 to provide 726 of the exposed metadata associated with the video to the viewer client device 110b. The exposed metadata can be provided to the client device 110c that interacts with the user interface 132 of the media hosting service 130 using the application 110c and the user interface 116bc.

[0088] At any point during the modified sharing interaction 300, 728 can be updated and metadata associated with the video can be stored using the video usage module 146 of the media hosting service or any other module that interacts with metadata in environment 100. Furthermore, metadata associated with any of the client devices, user accounts, or users in environment 100 can be updated and stored during the modified sharing interaction 300. In some embodiments, metadata can be updated using application 112c and user interface 116 via client device 110 interacting with user interface 132 and video usage module 146 of media hosting service 130.

[0089] At any point during the modified sharing interaction 300, the server may notify the sharing client device 110b 730 or the creator client device 110c 732 of changes to metadata associated with the video or metadata associated with the modified sharing interaction 300. Notification to the creator and sharing client devices may occur by interacting with the front-end interface 132 and video usage module 146 of the media hosting service 130 using the application 112c and user interface 116c of the viewer client device 110c. In other embodiments, the video usage module 146 automatically notifies the creator client device 110a and sharing client device 110b of changes in metadata.

[0090] In some configurations of client device 110 and media hosting service 130, the media hosting service does not participate in modifying metadata and only shares video content during the modified shared interaction 300. In these configurations, client device 110 participating in the modified shared interaction 300 can receive a video identifier associated with a masked video, which includes masking metadata associated with the modified shared interaction 300, indicating the metadata to be masked on participating device 110. Client device 110 can interpret the identifier, resolving it to a separate video identifier, and use the separate video identifier to access the unmasked video from media hosting service 130. Client device 110 can internally mask the metadata associated with the video indicated by the previously received masking metadata. This in-application modification can be implemented through a modified client device 110d with a modification module 140 within application 112d or through built-in functionality of application 112 on client device 110.

[0091] At any point during the modified shared interaction 300, the interaction between modules, applications, devices, servers, and storage may be constrained by settings and preferences stored in the client device settings module 114, user database 142, and video usage module 146. Settings and preferences may include: playback settings, accessible metadata, user account settings, security and authentication protocols, user preferences, client device settings and configurations, or any other metadata associated with environment 100.

[0092] In the shared interactions where the systems discussed here collect personal information about users or can modify that personal information, users can be given the opportunity to control whether a program or feature collects user information (e.g., information about the user's social networks, social actions or activities, professions, user preferences, or the user's current location), or to control whether and / or how content that may be more relevant to the user is received from the content server. Additionally, some data may be processed in one or more ways before storage or use to remove personally identifiable information. For example, a user's identity may be processed so that personally identifiable information cannot be determined for the user, or the user's geographic location may be augmented when location information (e.g., city, zip code, or state level) is obtained, making it impossible to determine the user's specific location. Therefore, users can control how information about themselves is collected and used by the content server.

[0093] Figure 8 This is a high-level block diagram illustrating an example of a computer 800 used as a video hosting server 130 or a client device 110. At least one processor 802 coupled to a chipset 804 is shown. The chipset 804 includes a memory controller hub 820 and an input / output (I / O) controller hub 822. Memory 806 and a graphics adapter 812 are coupled to the memory controller hub 820, and a display device 818 is coupled to the graphics adapter 812. Storage device 808, keyboard 810, indicating device 814, and network adapter 816 are coupled to the I / O controller hub 822. Other embodiments of the computer 800 have different architectures. For example, in some embodiments, memory 806 is directly coupled to processor 802.

[0094] Storage device 808 is a non-transitory computer-readable storage medium, such as a hard disk drive, optical disc read-only memory (CD-ROM), DVD, or solid-state storage device. Memory 806 stores instructions and data used by processor 802. Pointing device 814 is a mouse, trackball, or other type of pointing device and is used in conjunction with keyboard 810 to input data into computer 800. Adapter 812 displays frames and other information on display device 818. Network adapter 816 couples computer 800 to a network. Some embodiments of computer 800 have... Figure 1 The components shown are different and / or distinct components. The type of computer 800 may vary depending on the embodiment and desired processing power. Computer 800 may include multiple servers that work together to provide the functionality described herein.

[0095] In some embodiments, computer 800 may be a component of a cloud computing network. Computer 800 is adapted to execute computer program modules to provide the functionality described herein. As used herein, the term "module" refers to computer program instructions and other logic for providing a specified function. Thus, modules can be implemented in hardware, firmware, and / or software. In one embodiment, a program module formed by executable computer program instructions is stored on storage device 808, loaded into memory 806, and executed by processor 802.

[0096] The foregoing description has been presented for illustrative purposes; it is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Those skilled in the art will understand from the foregoing disclosure that many modifications and variations are possible.

[0097] This specification contains sections concerning the algorithms and symbolic representations of operations on information. Those skilled in the art of data processing commonly use these algorithmic descriptions and representations to effectively communicate the substance of their work to others skilled in the art. While these operations are described functionally, computationally, or logically, they should be understood as being implemented by computer programs or equivalent circuits or microcode. Furthermore, it has sometimes proven convenient to arrange these operations as modules without loss of generality. The described operations and their associated modules can be embodied in software, firmware, hardware, or any combination thereof.

[0098] Any of the steps, operations, or processes described herein may be performed or implemented, either alone or in combination with other devices, using one or more hardware or software modules. In one embodiment, a software module is implemented using a computer program product comprising a computer-readable medium containing computer program code that can be executed by a computer processor to perform any or all of the described steps, operations, or processes.

[0099] The embodiments may also relate to means for performing the operations described herein. Such means may be specifically constructed for the desired purpose and / or may comprise a general-purpose computing device selectively activated or reconfigured by a computer program stored in a computer. Such a computer program may be stored in a non-transitory tangible computer-readable storage medium or any type of medium suitable for storing electronic instructions, said medium being coupled to a computer system bus. Furthermore, any computing system mentioned in the specification may include a single processor or may be an architecture employing multiple processors to enhance computing power.

[0100] Embodiments may also relate to products generated by the computational processes described herein. Such products may include information generated by the computational processes, wherein the information is stored on a non-transitory tangible computer-readable storage medium, and such products may include any embodiment of a computer program product or other combinations of data described herein.

[0101] Finally, the language used in this specification has been chosen primarily for readability and guidance purposes and was not selected to depict or limit the subject matter of the invention. Therefore, the scope of the invention is intended to be limited not by this detailed description, but by any claims published based on the application herein. Thus, this disclosure is intended to illustrate, and not limit, the scope of the invention as set forth in the appended claims.

Claims

1. A method for modifying shared metadata, comprising: A graphical user interface (GUI) of a first client device associated with a first user account on a media hosting service is used to present content items provided by the media hosting service and metadata associated with the content items, wherein the metadata includes at least one of the content item’s title, identifier, author, tag, or popularity indicator. The first client device receives input from a first user associated with the first user account for modifying metadata of the content item, wherein the modification of the metadata includes at least one of masking, removing, or replacing the metadata; Obtain the identifier of the content item, the identifier of the content item indicating the modification of the metadata of the content; and The identifier of the content item is sent to a second client device associated with a second user account on the media hosting service so that the content item, along with the modified metadata, is presented on the second client device.

2. The method according to claim 1, wherein, The identifier: Indicates the location of the content item stored by the media hosting service; and Includes a flag indicating the original description of the content item to be modified, wherein the flag is set in response to receiving input from the first user associated with the first user account for modifying the metadata of the content item.

3. The method according to claim 1, wherein, Receiving the input from the first user associated with the first user account for modifying the metadata of the content item includes: This causes the identifier of the content item to be modified.

4. The method of claim 1, further comprising at least one of the following: Receive a notification via the media hosting service regarding that the second client device associated with the second user account on the media hosting service has received the identifier of the content item; or The media hosting service receives a notification that it has received a request from the second client device associated with the requested second user account to cancel the modification of the metadata of the content item.

5. The method according to claim 1, wherein, The popularity indicator for the content item includes at least one of the number of views or ratings performed by one or more users associated with a user account on the media hosting service.

6. The method according to claim 1, wherein: The masking includes at least one of the following: hiding or masking the metadata; The removal includes: suppressing the display of the metadata; and The replacement includes providing an image or text in place of the metadata.

7. The method of claim 1, further comprising: The content items are uploaded from the first client device associated with the first user account on the media hosting service to the media hosting service.

8. A system for modifying shared metadata, the system comprising: Memory; and A processor operatively coupled to the memory, the processor being configured to: A graphical user interface (GUI) at a first client device associated with a first user account on a media hosting service is used to present content items provided by the media hosting service and metadata associated with the content items, wherein the metadata includes at least one of the content item’s title, identifier, author, tag, or popularity indicator. The first client device receives input from a first user associated with the first user account for modifying the metadata of the content item, wherein the modification of the metadata includes at least one of masking, removing, or replacing the metadata; Obtain the identifier of the content item, the identifier of the content item indicating the modification of the metadata of the content; and The identifier of the content item is sent to a second client device associated with a second user account on the media hosting service so that the content item, along with the modified metadata, is presented on the second client device.

9. The system according to claim 8, wherein, The identifier: Indicates the location of the content item stored by the media hosting service; and Includes a flag indicating the original description of the content item to be modified, wherein the flag is set in response to receiving input from the first user associated with the first user account for modifying the metadata of the content item.

10. The system according to claim 8, wherein, In order to receive the input from the first user associated with the first user account for modifying the metadata of the content item, the processor is further configured to: This causes the identifier of the content item to be modified.

11. The system of claim 8, wherein the processor is further configured to perform at least one of the following: Receive a notification via the media hosting service regarding that the second client device associated with the second user account on the media hosting service has received the identifier of the content item; or The media hosting service receives a notification that it has received a request from the second client device associated with the requested second user account to cancel the modification of the metadata of the content item.

12. The system according to claim 8, wherein, The popularity indicator for the content item includes at least one of the number of views or ratings performed by one or more users associated with a user account on the media hosting service.

13. The system according to claim 8, wherein: The masking includes at least one of the following: hiding or masking the metadata; The removal includes: suppressing the display of the metadata; and The replacement includes providing an image or text in place of the metadata.

14. The system of claim 8, wherein the processor is further configured to: The content items are uploaded from the first client device associated with the first user account on the media hosting service to the media hosting service.

15. A non-transitory computer-readable medium having instructions recorded thereon, the instructions performing operations when executed by one or more computer processors, the operations including: A graphical user interface (GUI) of a first client device associated with a first user account on a media hosting service is used to present content items provided by the media hosting service and metadata associated with the content items, wherein the metadata includes at least one of the content item’s title, identifier, author, tag, or popularity indicator. The first client device receives input from a first user associated with the first user account for modifying the metadata of the content item, wherein the modification of the metadata includes at least one of masking, removing, or replacing the metadata; Obtain the identifier of the content item, the identifier of the content item indicating the modification of the metadata of the content; and The identifier of the content item is sent to a second client device associated with a second user account on the media hosting service so that the content item, along with the modified metadata, is presented on the second client device.

16. The non-transitory computer-readable medium according to claim 15, wherein, The identifier: Indicates the location of the content item stored by the media hosting service; and Includes a flag indicating the original description of the content item to be modified, wherein the flag is set in response to receiving input from the first user associated with the first user account for modifying the metadata of the content item.

17. The non-transitory computer-readable medium according to claim 15, wherein, Receiving input from the first user associated with the first user account for modifying the metadata of the content item includes: This causes the identifier of the content item to be modified.

18. The non-transitory computer-readable medium of claim 15, further comprising at least one of the following: Receive a notification via the media hosting service regarding that the second client device associated with the second user account on the media hosting service has received the identifier of the content item; or The media hosting service receives a notification that it has received a request from the second client device associated with the requested second user account to cancel the modification of the metadata of the content item.

19. The non-transitory computer-readable medium according to claim 15, wherein, The popularity indicator includes at least one of the number of views or ratings performed by one or more users associated with a user account on the media hosting service.

20. The non-transitory computer-readable medium according to claim 15, wherein: The masking includes at least one of the following: hiding or masking the metadata; The removal includes: suppressing the display of the metadata; and The replacement includes providing an image or text in place of the metadata.

Images