Program, method, and system

Abstract

To provide a program for, a method of, and a system for allowing a user to smoothly carry out secondary use while reducing the possibility of misunderstanding on the part of users.SOLUTION: A program can set whether or not secondary use by other user of an action received from a user is allowed in response to an operation by the user, and when the user allows the secondary use based on the setting of the user who performed the action, reflects suggestion information suggesting that the action is allowed for secondary use.SELECTED DRAWING: Figure 28

Description

[Technical Field]

[0001] The present invention relates to a program, a method, and a system. [Background technology]

[0002] In fan activities (so-called "oshikatsu") in which fans support a favorite person or thing (so-called "oshi"), such as a celebrity, fan users may post their impressions of the fan activities or derivative works such as fan art related to the favorite person on social media (see, for example, Non-Patent Document 1). The celebrity or other person they support may introduce such posted content from fan users in their own video distribution or on social media.

[0003] Furthermore, when fan user posted content is introduced by the celebrity or other person they support, it leads to more active communication between the fan and the celebrity. Therefore, to enable celebrities and others to smoothly use fan user posted content for distribution, for example, guidelines for derivative works of content related to the celebrity (such as character images) may state that the operator may use derivative works, thereby allowing the content posted by fan users to be used (used). [Prior art documents] [Patent documents]

[0004] [Non-Patent Document 1] "How to support your favorite Vtuber - How to develop your favorite Vtuber", [online], [Retrieved October 24, 2023], Internet<https: / / meeota.com / entry / oshikatu-howto> Summary of the Invention [Problem to be solved by the invention]

[0005] However, if the terms and conditions allow the use of content posted by fan users, there is a risk that users may be confused by the intended use of the content.

[0006] The present invention has been devised in view of the above circumstances, and provides a program, method, and system for facilitating secondary use while minimizing misunderstandings among users. [Means for solving the problem]

[0007] (1) A program according to an aspect of the present invention is a program (e.g., a program stored in the storage unit 120, a program for providing content, etc.) that allows an action (e.g., posting of content such as a thread or a comment) accepted from a user terminal (e.g., user terminal 300) operated by each of a plurality of users to be reflected in the user terminal of each of the plurality of users so that each of the plurality of users can recognize the action, A computer (e.g., a distribution server 100, a user terminal 300) means (for example, the account management unit 133, the input information transmission unit 353, steps S601 to S604 in FIG. 30, etc.) for setting whether or not to permit secondary use of an action accepted from a user (for example, an administrator or a celebrity introducing the user's posted content in a video distribution or quoting the user's posted content) in accordance with an operation from the user (for example, operation of the secondary use permission button 501 on the user setting screen in FIG. 28(A), operation of the secondary use permission button 501 when posting content in FIG. 32, see the modified example (regarding changing secondary use permission information for each content after posting), etc.); When a user who performed an action has permitted secondary use based on the settings of the user (for example, when the secondary use permission information of "Permitted" is associated with the user in the user information database of Figure 29(A) due to the secondary use permission button 501 being in the on state on the user setting screen of Figure 28(A), or when the secondary use permission information of "Permitted" is associated with a thread or comment in the content database of Figure 29(B) or the comment database of Figure 29(C)), the function is as a means (for example, see the content management unit 132, account management unit 133, display control unit 352, step S607 of Figure 30, step S607B of Figure 31, modified example (for extraction of only posts for which secondary use is permitted), etc.) for enabling the reflection of suggestion information suggesting that the action in question is permitted for secondary use (for example, see the content management unit 132, account management unit 133, display control unit 352, step S607 of Figure 30, step S607B of Figure 31, modified example (for extraction of only posts for which secondary use is permitted), etc.).

[0008] With this configuration, whether or not to allow secondary use of an action can be set according to user operation, making it possible to facilitate secondary use while making it less likely for misunderstandings to arise that actions can be used secondary.

[0009] (2) In (1) above, the means for enabling the reflection allows the suggestion information to be reflected only on the user terminals of users who do not satisfy the specific conditions (e.g., special users in Figure 5, administrators, etc.), and not on the user terminals of users who do not satisfy the specific conditions (e.g., steps S606 to S607 in Figure 30, steps S606 to S607B in Figure 31).

[0010] This configuration prevents unintended use or abuse of the data by encouraging secondary use even among users who do not meet certain conditions (for example, users with little need for secondary use).

[0011] (3) In (1) above, the setting means allows the user to set whether or not to permit secondary use when setting information about the user in response to an operation from the user (for example, an operation on the secondary use permission / denial button 501 in Figure 28(A) on a setting screen such as the user's My Page in Figure 8).

[0012] With this configuration, when setting information about a user, the user can choose whether or not to allow secondary use of the action, making it easy for the user to manage the secondary use permission status of the action.

[0013] (4) In the above (3), the computer functioning as a means for managing action information for identifying actions accepted from a user (for example, storing the content management unit 132, content data 122, action information 123, etc.); The managing means manages action information received when the user has permitted secondary use (for example, when the secondary use permission information is associated with "Permitted" in the user information database of FIG. 29(A), or when a post is made with the secondary use permission button 501 on in the posting screen of FIG. 32) as action information for which secondary use is permitted (for example, content posted when the secondary use permission information in the user information database of FIG. 29(A) is "Permitted" in steps S601 to S602 of FIG. 30, is managed in steps S603 to S604 in the content database of FIG. 29(B), comment database of FIG. 29(C), etc., by associating secondary use permission information of "Permitted" for each content), The means for enabling the reflection enables the suggestion information to be reflected (for example, by displaying the secondary use OK icon 701 in Figure 28(B), steps S603 to S607 in Figure 30, etc.) when reflecting an action identified from action information for which secondary use is permitted (for example, when displaying article ID ``a3'' in Figure 29(B) on the user terminal 300).

[0014] According to this configuration, suggestion information can be reflected based on action information, and the processing load when reflecting an action can be reduced.

[0015] (5) In (3) above, the means for enabling the reflection enables the reflection of the suggestion information when reflecting an action received from a user (for example, when displaying article ID “a3” in FIG. 29(B) on the user terminal 300) for actions from users for which the user who originated the action has given permission for secondary use based on the settings of the user who originated the action (for example, secondary use permission information in the user’s current user information database in FIG. 29(A)) (for example, steps S605 to S607B in FIG. 31).

[0016] With this configuration, suggestion information can be reflected based on the user's settings when reflecting an action, making it easier for users to manage the secondary use permission status for their own actions. Also, for the administrator, management is easier because it is only necessary to manage the secondary use permission status for each user.

[0017] (6) In the above (5), the setting means can set whether to permit secondary use when setting information about the user in response to an operation from the user, regardless of whether the action has been reflected (for example, regardless of whether a content screen or the like has been reflected on the user terminal 300 in steps S607B and S608 based on the display request information in step S605 of FIG. 31, or whether it is possible to reflect it), The means for enabling the reflection can update the suggestion information based on the settings of the user who took the action, even when reflecting an action received from the user (for example, even if the content screen displaying the secondary use OK icon 701 in Figure 28(B) is displayed on the user terminal 300, if a reload operation is performed, the display / hide of the secondary use OK icon 701 can be updated in steps S605 to S607B based on the secondary use permission information updated in step S602 in Figure 31, depending on the current secondary use permission status of the user; see the modified examples (Regarding secondary use permission settings for each type of content) and (Regarding changing secondary use permission information for each content after posting)).

[0018] With this configuration, even if the action has been reflected in another user, the suggestion information can be updated in response to an operation from the user, thereby improving user convenience.

[0019] (7) In (1) above, the setting means allows the user to set whether or not to allow secondary use of the action when accepting the action from the user (for example, when posting a thread or comment) in accordance with the user's operation (for example, by displaying the secondary use permission button 501 on the posting screen in Figure 32).

[0020] According to this configuration, the permission status of secondary use can be set when an action is accepted (each time an action is taken), thereby improving user convenience.

[0021] (8) In the above (1), the computer It functions as a means for enabling switching between a first state in which actions received from the user can be reflected regardless of whether secondary use is permitted or not (for example, a state in which both posts for which secondary use is permitted and posts for which secondary use is not permitted are displayed), and a second state in which only actions received from the user for which secondary use is permitted can be reflected (for example, a state in which only posts for which secondary use is permitted are extracted and displayed), depending on a switching operation from the user (for example, see the modified example (regarding the extraction of only posts for which secondary use is permitted)).

[0022] With this configuration, it is possible to reflect only actions for which secondary use is permitted, making it easier for users to identify actions for which secondary use is permitted and improving convenience for users who make secondary use.

[0023] (9) In the above (1), the computer In response to a user's secondary use operation on an action (for example, an operation on a share icon), it functions as a means for obtaining secondary use information to be used for secondary use of the action (for example, link information that can transition to a post that can be embedded in other posts or external content and is to be used for secondary use).

[0024] According to this configuration, by acquiring the secondary use information, it may become easier for a user who has performed a secondary use operation to make secondary use of the action.

[0025] (10) A method according to an aspect of the present invention is a method for controlling a computer (e.g., distribution server 100, user terminal 300) that performs processing to enable actions (e.g., posting of content such as threads or comments) accepted from user terminals (e.g., user terminal 300) operated by each of a plurality of users to be reflected in the user terminals of each of the plurality of users so that each of the plurality of users can recognize the actions, a step (e.g., steps S601 to S604 in FIG. 30) for setting whether or not to permit secondary use of the action received from the user (e.g., an administrator or a celebrity introducing the user's posted content in a video stream or quoting the user's posted content) in accordance with an operation from the user (e.g., operation of the secondary use permission button 501 on the user setting screen in FIG. 28(A), operation of the secondary use permission button 501 when posting content in FIG. 32, see the modified example (regarding changing secondary use permission information for each content after posting), etc.); When the user who performed the action has permitted secondary use based on the settings of the user (for example, when the secondary use permission information of "Permitted" is associated with the user in the user information database of Figure 29(A) due to the secondary use permission button 501 being in the on state on the user setting screen of Figure 28(A), or when the secondary use permission information of "Permitted" is associated with a thread or comment in the content database of Figure 29(B) or the comment database of (C)), the system includes a step (for example, see step S607 of Figure 30, step S607B of Figure 31, and a modified example (for example, see step S607 of Figure 30, step S607B of Figure 31, and a modified example (for example, see step S607 of Figure 30, step S607B of Figure 31, and a modified example (for example, see step S607 of Figure 30, step S607B of Figure 31, and a modified example (For ...

[0026] With this configuration, whether or not to allow secondary use of an action can be set in accordance with a user operation, which makes it less likely that a user will misunderstand that an action can be used secondary, thereby facilitating secondary use.

[0027] (11) A system (e.g., communication system 1) according to an aspect of the present invention is a system including a computer (e.g., distribution server 100, user terminal 300) that performs processing to enable actions (e.g., posting of content such as threads or comments) accepted from user terminals (e.g., user terminals 300) operated by each of a plurality of users to be reflected in the user terminals of each of the plurality of users so that each of the plurality of users can recognize the actions, means (for example, the account management unit 133, the input information transmission unit 353, steps S601 to S604 in FIG. 30, etc.) for setting whether or not to permit secondary use of an action accepted from a user (for example, an administrator or a celebrity introducing the user's posted content in a video distribution or quoting the user's posted content) in accordance with an operation from the user (for example, operation of the secondary use permission button 501 on the user setting screen in FIG. 28(A), operation of the secondary use permission button 501 when posting content in FIG. 32, see the modified example (regarding changing secondary use permission information for each content after posting), etc.); When a user who has performed an action has permitted secondary use based on the settings of the user (for example, when the secondary use permission information of "Permitted" is associated with the user in the user information database of FIG. 29(A) due to the secondary use permission button 501 being in the on state on the user setting screen of FIG. 28(A), or when the secondary use permission information of "Permitted" is associated with a thread or comment in the content database of FIG. 29(B) or the comment database of (C)), the system is provided with means (for example, see the content management unit 132, account management unit 133, display control unit 352, step S607 of FIG. 30, step S607B of FIG. 31, and the modified example (for extracting only posts for which secondary use is permitted)) for enabling the reflection of suggestion information suggesting that the action is permitted for secondary use (for example, information for displaying the secondary use OK icon 701 for each posted content of FIG. 28(B), see the modified example (for extracting only posts for which secondary use is permitted)).

[0028] With this configuration, whether or not to allow secondary use of an action can be set in accordance with a user operation, which makes it less likely that a user will misunderstand that an action can be used secondary, thereby facilitating secondary use. [Brief explanation of the drawings]

[0029] [Figure 1] FIG. 1 illustrates an example of a hardware configuration of a communication system. [Figure 2] FIG. 2 is a diagram illustrating the configuration of a distribution server. [Figure 3] FIG. 2 is a diagram illustrating a configuration of an administrator terminal. [Figure 4] FIG. 2 is a diagram for explaining the configuration of a user terminal in detail. [Figure 5] 1 is an example of a database relating to attributes. [Figure 6] 10 is an example of an attribute selection screen. [Figure 7] 1 is an example of a database related to users. [Figure 8] 10 is an example of a user confirmation screen for information about a user. [Figure 9] FIG. 10 is a flowchart for explaining an attribute selection process. [Figure 10] 10 is an example of a display mode of content information relating to content provided by a distribution server. [Figure 11] 10 is an example of a display mode of content information relating to content provided by a distribution server. [Figure 12] 10 is an example of a display mode relating to content classification for each attribute. [Figure 13] 10 is an example of a display mode of content provided by a distribution server. [Figure 14] 1 is an example of a database relating to content provided by a distribution server. [Figure 15] 10 is an example of a display mode of content information relating to content in response to a switching operation. [Figure 16]FIG. 10 is a flowchart for explaining an attribute extraction process. [Figure 17] 10 is an example of a display aspect of a user posting screen. [Figure 18] FIG. 10 is a diagram illustrating a flowchart of a user posting process. [Figure 19] This is an example of an action that can be taken depending on the user's rating history status. [Figure 20] 10 is an example of a display mode of a user posting screen according to a rating history status. [Figure 21] FIG. 10 is a diagram for explaining a flowchart of a user posting process according to a rating history status. [Figure 22] This is an example of fluctuations in the evaluation history situation due to external evaluation. [Figure 23] FIG. 10 is a diagram for explaining a flowchart of an evaluation history status update process. [Figure 24] 10 is an example of a tap action presentation when a tap action is received from a user. [Figure 25] 10 is an example of a database relating to tap action effects for each content. [Figure 26] FIG. 10 is a diagram illustrating a flowchart of a tap action rendering process. [Figure 27] 10 is an example of a display mode of content information etc. related to externally posted content. [Figure 28] 10A and 10B are examples of a secondary use permission setting screen and a secondary use permission display screen. [Figure 29] 10 is an example of a database relating to secondary use permission related processing. [Figure 30] FIG. 10 is a diagram for explaining a flowchart of secondary use permission related processing. [Figure 31] FIG. 10 is a diagram for explaining another example of a flowchart of the secondary use permission related process. [Figure 32] FIG. 10 is a diagram illustrating an example of a screen for setting permission for secondary use when posting. DETAILED DESCRIPTION OF THE INVENTION

[0030] Hereinafter, an embodiment of a communication system according to the present invention will be described with reference to the drawings. Note that the present invention is not limited to the following examples, but is defined by the claims, and all modifications within the meaning and scope equivalent to the claims are intended to be included in the present invention. In the following description, the same elements in the description of the drawings will be given the same reference numerals, and redundant explanations will not be repeated.

[0031] The communication system according to the present invention can provide users with multiple types of content associated with attributes. The attributes include multiple types of first attributes (e.g., communities) and multiple types of second attributes (e.g., celebrities), and can display content information (e.g., headlines of news posts) related to content associated with the attributes (e.g., news posts related to celebrities). The content information can be displayed by switching between multiple display states, including a first display state (favorite filter off) that displays content information associated with a community, etc. pre-selected by the user so that the user can identify it, and a second display state (favorite filter on) that displays content information associated with both a community, etc. and a celebrity, etc. pre-selected by the user so that the user can identify it, by a user's switching operation on a predetermined icon, etc.

[0032] Furthermore, the multiple types of content provided in the communication system according to the present invention are provided via a fan community, which is a group of users who support a specific target (e.g., a celebrity). Within the community space of the fan community, the actions taken by each user are reflected so that other users can recognize them, thereby promoting interaction between users. Each user who uses the community is associated with an evaluation history status that changes depending on external evaluations, which are evaluations from sources other than the user himself / herself. The actions that a user may take within the community are controlled by external evaluations of the actions taken by the user within the community (e.g., content and comments posted by the user).

[0033] Furthermore, in a fan community of a communication system according to the present invention, posted content (e.g., comments, fan art, etc.) can be associated with information indicating whether the user permits secondary use of the posted content. This makes it easier for operators and celebrities supported by the fan community to obtain information on whether the user who posted the posted content permits secondary use, making it easier for celebrities to feature the posted content in video distribution, etc. As a result, communication between fans and celebrities can be stimulated and the fan community app can be effectively promoted.

[0034] 1 is a diagram illustrating an example of the hardware configuration of a communication system 1. The communication system 1 includes a distribution server 100, an administrator terminal 200, multiple user terminals 300a, 300b, 300c, and an external web service system 400. The multiple user terminals 300a, 300b, 300c, and are terminals owned by multiple users, respectively, and are hereinafter collectively referred to as user terminals 300.

[0035] The distribution server 100, the administrator terminal 200, and the user terminal 300 can each be connected to each other via a network 2, and can transmit and receive information (data) in both directions. The network 2 is, for example, the Internet, and is configured from access networks such as a LAN (Local Area Network), a WAN (Wide Area Network), a mobile communication network (e.g., 5G, wireless network, etc.), a wired telephone network, FTTH (Fiber To The Home), and a CATV (Cable Television) network.

[0036] Furthermore, the distribution server 100, the administrator terminal 200, and the user terminal 300 can be communicatively connected to an external web service system 400 via the network 2. The external web service system 400 is, for example, a sharing service (such as YouTube (registered trademark)) for videos, text, images, etc. posted by users, and provides a Web API (Application Programming Interface) for enabling information (such as text, images, videos, posting dates and times, account names, etc.) to be supplied to other terminals such as the distribution server 100, the administrator terminal 200, and the user terminal 300 in response to access from those terminals. The external web service system 400 is a system operated and managed by a third party other than the administrator and operator of the communication system 1.

[0037] Distribution server 100 is, for example, a computer such as a workstation or personal computer with communication capabilities. Distribution server 100 manages multiple pieces of content that can be provided to users and manages communities to which the content is provided. Distribution server 100 provides the content in response to requests from users via network 2.

[0038] The content provided by the distribution server 100 is managed and configured by type, as described below with reference to FIG. 14. Content informs viewers of specific information and includes information such as video, audio, and text. Examples of content managed by the distribution server 100 include news and announcements from operators (administrators), user posts (including comments), and streaming videos provided by external web services obtained using Web APIs. The content can be provided to users by displaying it on the user terminal 300 via a medium such as a browser or a dedicated smartphone application. The medium through which the content is provided also functions as a fan community for supporting specific targets.

[0039] The distribution server 100 stores information for displaying text, images, etc. corresponding to content that can be provided to users on the user terminal and sound information for outputting sound in the storage unit 120. In addition, the distribution server 100 provides content (services) to users by distributing content data including display information for displaying text, images, etc. of the corresponding content and sound information for outputting sound in response to access from the user terminal 300.

[0040] The administrator terminal 200 is used by an operator of a service provider company, for example. The administrator terminal 200 is a computer having operation input functions and communication functions, such as a personal computer. The administrator creates content (hereinafter also referred to as posted information) managed in the storage unit 120 of the distribution server 100, and creates, modifies, and updates display information related to the display of content, via the administrator terminal 200. For example, images for displaying new content, etc. on the user terminal 300 are generated and created, and images of existing content, etc. are changed and modified. The administrator also sets and updates information managed in the storage unit 120 of the distribution server 100 via the administrator terminal 200. The administrator terminal 200 can also be used to set permissions and restrictions on users' actions on various content.

[0041] In this embodiment, the distribution server 100 and the administrator terminal 200 are each an independent computer (device), but they may be realized by a single computer, or the functions of one of these computers (e.g., distribution server 100) may be realized by multiple computers (e.g., multiple servers).

[0042] The user terminal 300 is used by a user to view, experience, etc. the content. The user terminal 300 may be a computer having an operation input function and a communication function, such as a personal computer, a tablet terminal, or a smartphone.

[0043] In response to an operation on the terminal, the user terminal 300 communicates with the distribution server 100 and receives content data of the content selected by the user. Based on the received content data, the user terminal 300 constructs, in a storage area of ​​the user terminal 300, posted information of the content selected by the user from among the contents managed by the distribution server 100, and displays images and text of the posted information. This allows the user to identify and recognize the content information via the user terminal 300.

[0044] Furthermore, the user terminal 300 accepts action operations on the displayed content and content posting operations by the user himself / herself. The user terminal 300 can transmit information corresponding to the operation on the terminal (for example, information for identifying the action or the posted content) to the distribution server 100, and can reflect the action or the posted content on multiple user terminals via the distribution server 100. Action operations include, for example, tap actions (such as the so-called "like" function) that show a favorable expression of intent, such as liking or empathy for the content, and posting of comments. Hereinafter, user actions, such as content posting operations by the user himself / herself, will be collectively referred to as "actions." Furthermore, user tap actions and favorable comments will also be referred to as "like actions."

[0045] In this embodiment, users include general consumers (also referred to as general users or simply users), talents, celebrities, etc. Talent includes, for example, talents belonging to a service provider company (operating company), entertainers, actors / actresses, comedians, multi-talented people, presenters, news anchors, singers, musicians, models, and other talented people from various genres. Celebrities also include, for example, famous company executives or employees, athletes, e-sports players, famous scholars, cultural figures, cram school instructors, famous students, and other famous people from various genres. Hereinafter, talents or celebrities other than general users will also be referred to as special users.

[0046] Note that a special user may be a general user who views distributed content using a terminal with the same configuration as the user terminal 300, or may be a general user who uses a separate terminal with a different configuration from the user terminal 300. Therefore, the user terminal used by a special user and the user terminal 300 used by a general user may be terminals with the same configuration or may be terminals with different configurations.

[0047] <Distribution server configuration> Next, the configuration of distribution server 100 will be described. As shown in Fig. 2, distribution server 100 includes a communication unit 110 that communicates with other computers, a storage unit 120 that stores various data, and a control unit 130 that controls the entire computer. Communication unit 110, storage unit 120, and control unit 130 are interconnected by a bus line.

[0048] The communication unit 110 is a communication interface that includes a network interface card (NIC) for wired or wireless communication. The communication unit 110 communicates with other computers via the network 2.

[0049] The storage unit 120 is composed of RAM (Random Access Memory), ROM (Read Only Memory), flash memory, HDD (Hard Disk Drive), etc. The storage unit 120 stores programs for executing various control processes (for example, programs for managing and providing content), various data, etc. The various data stored in the storage unit 120 includes posted information provided for each type of content, information related to attributes, user information related to users, etc.

[0050] The control unit 130 is configured by a CPU (Central Processing Unit), etc. The control unit 130 controls the overall operation of the distribution server 100 by executing a program stored in the storage unit 120.

[0051] The following describes the functional configuration of the control unit 130. The control unit 130 functions as at least a data transmission / reception unit 131, a content management unit 132, and an account management unit 133.

[0052] The data transmitter / receiver 131 receives various types of information transmitted from the user terminal 300 and transmits various types of information to the user terminal 300. The data transmitter / receiver 131 refers to various management tables stored in the storage unit 120. The various types of information transmitted and received by the data transmitter / receiver 131 include, for example, information related to content managed in the content management unit 132, various notifications, and the like.

[0053] The content management unit 132 stores and updates information for identifying text, images, etc. corresponding to content posted by the administrator terminal 200 or the user terminal 300 in the storage unit 120 via the communication unit 110. The content management unit 132 stores, for example, information on attributes that can be associated with content to be provided to users as attribute information 121 in the storage unit 120. The content management unit 132 stores and updates information for identifying information such as the category and poster of content posted by the administrator terminal 200 or the user terminal 300, and attributes associated with each piece of content, as content data 122 in the storage unit 120. In addition, the content management unit 132 stores and updates information for identifying the type of action (behavior) performed on content as action information 123, and stores information on the authority to take actions (behaviors) related to content as action authority information 124 in the storage unit 120.

[0054] The account management unit 133 stores and updates user information about users who can use content managed by the distribution server 100 in the storage unit 120, for example, as account information 125. The user information about users includes, for example, an ID for identifying the user, a user name, and permitted action information about actions that the user can take. The user information managed by the account management unit 133 is not limited to general user accounts, but also includes account information for identifying special user accounts and posts made by the administrator terminal 200.

[0055] <Administrator terminal configuration> Next, the configuration of administrator terminal 200 will be described. As shown in Fig. 3, administrator terminal 200 includes a communication unit 210 that communicates with other computers, a storage unit 220 that stores various data, an input unit 230 for inputting operations, etc., an output unit 240 for outputting images, sounds, etc., and a control unit 250 that controls the entire computer. Communication unit 210, storage unit 220, input unit 230, output unit 240, and control unit 250 are interconnected by a bus line.

[0056] The communication unit 210 is a communication interface equipped with a NIC for wired or wireless communication. The communication unit 210 mainly communicates with the distribution server 100 via the network 2. The storage unit 220 is composed of RAM, ROM, etc. The storage unit 220 stores programs for executing various control processes (for example, programs for managing content provided to users by the distribution server 100), various data, etc.

[0057] The input unit 230 includes an input device (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.) for receiving input operations from the administrator. The output unit 240 includes an output device (a display, a speaker, etc.) for presenting information to the administrator.

[0058] The control unit 250 is configured with a CPU, etc. The control unit 250 controls the overall operation of the administrator terminal 200 by executing the programs stored in the storage unit 220.

[0059] The following describes the functional configuration of the control unit 250. The control unit 250 functions as at least a content setting unit 251, an attribute setting unit 252, an action authority setting unit 253, and a user evaluation information updating unit 254.

[0060] The content setting unit 251 stores and updates information about the content managed by the content management unit 132 of the distribution server 100 in response to operations on the administrator terminal 200. This allows, for example, information for identifying the content, categorization of the content, and information set and edited regarding the presentation when the content is provided to be stored and updated in the storage unit 120 of the distribution server 100.

[0061] The attribute setting unit 252 stores and updates attribute information relating to attributes stored as attribute information 121 in the distribution server 100 in response to an operation on the administrator terminal 200. This allows, for example, information relating to attributes to be stored and updated in the storage unit 120 when a new attribute is added or when the organization of attributes is changed.

[0062] The behavior restriction setting unit 253 stores and updates information about the authority to perform actions such as content posting actions and actions showing reactions to content within the provided community space, which are managed as the action information 123 and behavioral authority information 124 of the distribution server 100, in response to operations on the administrator terminal 200. This allows, for example, addition and modification of actions set for each user's rating history status (described later), and the setting of behavior restrictions for each user by the administrator to be stored and updated in the storage unit 120.

[0063] The user evaluation information update unit 254 can perform external evaluations on users that may affect the evaluation history status of each user stored as account information 125 of the distribution server 100, and can also store and update the evaluation history status of each user, in response to operations on the administrator terminal 200. This allows the evaluation history status of each user to fluctuate depending on the evaluation from the administrator, and controls the actions that users can take based on the action authority information 124.

[0064] <User terminal configuration> Next, the configuration of user terminal 300 will be described in detail. As shown in Fig. 4, user terminal 300 includes a communication unit 310 that communicates with other computers including distribution server 100, a storage unit 320 that stores various data, an input unit 330 for inputting operations, etc., an output unit 340 for outputting images, etc., and a control unit 350 that controls the entire computer. Communication unit 310, storage unit 320, input unit 330, output unit 340, and control unit 350 are interconnected by a bus line.

[0065] The communication unit 310 is a communication interface equipped with a NIC for wired or wireless communication. The communication unit 310 communicates with other computers, including the distribution server 100, via the network 2. The storage unit 320 is composed of RAM, ROM, etc. The storage unit 320 stores programs for executing various control processes (for example, programs for viewing content), various data, etc.

[0066] The input unit 330 includes an input device (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, a microphone, etc.) for receiving input operations and voices from the user.

[0067] The output unit 340 includes an output device (display, speaker, etc.) for presenting and outputting information (text, images, audio, etc.) to the user. The control unit 350 is composed of a CPU, etc. The control unit 350 controls the overall operation of the user terminal 300 by executing programs stored in the storage unit 320.

[0068] The following describes the functional configuration of the control unit 350. The control unit 350 functions as an information acquisition unit 351, a display control unit 352, an input information transmission unit 353, and a user management unit 354.

[0069] The information acquisition unit 351 acquires content data and the like from the distribution server 100 via the communication unit 310, and stores information for displaying text and images (posted information) related to the content based on the content data in the storage unit 320. The posted information includes information for displaying, on the user terminal 300, actions taken on the content by other user terminals 300.

[0070] The display control unit 352 displays content information (e.g., headlines of articles about the content) related to the content stored in the storage unit 320 so that the user can identify it, based on the content data acquired by the information acquisition unit 351. For example, by displaying the headline of a news article about a celebrity on the user terminal 300, the user can recognize that the content is news about a celebrity.

[0071] In addition, the display control unit 352 displays UI (User Interface) images (including, for example, menu images that the user can select and operation images that accept operations) in a format that corresponds to the content being distributed based on the program stored in the storage unit 320.

[0072] The input information sending unit 353 sends the voice information and operation input information acquired by the input unit 330 to the distribution server 100. The operation input information includes actions (for example, comments, tap actions, etc.) on various contents in the displayed community space, content posted by the user himself / herself in the community space, and selection operations on various icons displayed on the user terminal 300.

[0073] The user management unit 354 stores and updates user information about users in the storage unit 320. The user information about users includes, for example, an ID for identifying the user, a user name, information about attributes selected in advance by the user, and information about actions that the user can take (permitted or restricted) within the community.

[0074] <About the fan community content provision function> (Overview of the fan community) The following is a more detailed description of a fan community that allows users to view content provided by the distribution server 100 according to this embodiment. The content provided by the distribution server 100 is provided by a dedicated application (program (e.g., a program for a native application)) that runs on a device such as a smartphone or tablet. The dedicated application functions as a so-called fan community used by users who support a common target (e.g., a talent, a character, goods, etc.). The fan community provides content related to the common target (making it viewable by users), thereby facilitating users' fan activities. In addition to allowing users to interact with each other as fans, users can also interact with the target they support. Note that content provision is not limited to a dedicated application, and may also be provided via a web application via a browser. Content may also be provided via a fan community provided via a web application via a browser.

[0075] In this embodiment, the cheering target can be any of a variety of objects such as characters or objects that the user can feel fondness for, be interested in, or be concerned with. Characters include, for example, real people (3D) such as celebrities and famous people, and fictional beings (2D, 2.5D) such as anime characters and mascot characters. Other cheering targets include things such as trains and animals.

[0076] (Specific examples of attributes in fan communities) In the following, in this embodiment, an example will be described in which the user's support target is a talent, and the fan community is the talent's fan community. In this embodiment, the talents are divided into large groups (also referred to as first attributes) consisting of multiple talents. Furthermore, the talents divided into large groups can also be divided into small groups (also referred to as second attributes) consisting of fewer people than the large groups. For example, a small group is a unit group consisting of some of the talents belonging to the large group.

[0077] The unit (attribute) that a user of a fan community supports may not only be a single talent, but may also be multiple talents, a small group (unit), or a large group. For example, supporting (becoming a fan of) a large group is also known as "box pushing." In the fan community of this embodiment, users can set (select) the target of their support in advance by their preferred unit (attribute).

[0078] 5, the talents in the fan community in this embodiment will be described using an example of a talent information database stored as attribute information 121 in this embodiment. In this embodiment, the talents are divided into groups classified as "belonging group 1." Belonging group 1 is a large group, and is classified into, for example, group A, group B, etc.

[0079] Each belonging group 1 is associated with a "talent ID," "talent name," and other information for identifying the talent. Furthermore, each talent is associated with information for identifying the "belonging group 2" to which the talent belongs. Belonging group 2 is a small group made up of fewer people than belonging group 1. For example, it could be a group categorized by the time members joined the group, such as "1st generation members," "2nd generation members," etc., or a group made up of a specific concept (for example, "Gamers," made up of talents who mainly do live game broadcasts).

[0080] It should be noted that some talents may belong to multiple groups. There may also be talents who belong to group 1 but do not belong to any group 2. There may also be group 2s that are made up of talents who belong to different groups 1 (composed across different groups 1, for example, group A and group B).

[0081] For example, a talent with the talent ID "t1" and the talent name "AAA" belongs to group 1 "Group A" and group 2 "A-1st Generation." On the other hand, a talent with the talent ID "t6" and the talent name "FFF" belongs to group 1 "Group A," but belongs to two groups in group 2 "A-3rd Generation" and "A-Gamers."

[0082] <Example of attribute selection processing> (Screen example for attribute selection) Next, with reference to FIGS. 6 to 9, an example of a screen and a processing flow for a user using a fan community to select an attribute (group or talent) to support will be described. The selection (setting) screen for the attribute to support, illustrated in FIG. 6, is displayed on the user terminal 300 when the user starts using the fan community app or when a setting change is requested from My Page or the like. In the fan community of this embodiment, a user can participate in a community (first attribute) corresponding to the group 1 (first attribute) to which the talent belongs, as described with reference to FIG. 5. FIG. 6(A) is an example of a participation community setting screen, and a user can select (set) a community (first attribute) to participate in from multiple types of first attributes. For example, the participation community setting screen of FIG. 6(A) includes a participation community selection area 50. The participation community selection area 50 displays an icon for each community that the user can participate in. The user can select a participation community by selecting the icon of the community they wish to participate in. A check mark or the like is displayed for a community that they have selected to participate in.

[0083] "Community A" corresponds to "Group A" in FIG. 5, and "Community B" corresponds to "Group B" in FIG. 5. In other words, the multiple types of first attributes include Group A, or Community A corresponding to Group A, and Group B, or Community B corresponding to Group B. Note that there may be a community that a user is always expected to participate in regardless of the user's selection, as displayed in FIG. 6(A) as "※Always participating in Community P." For example, "Community P" does not correspond to a group to which a talent belongs, but is a community that makes announcements for the fan community as a whole.

[0084] FIG. 6(B) is an example of a favorite talent setting screen, on which a user can select (set) a favorite talent (second attribute). The favorite talent setting screen in FIG. 6(B) includes, for example, a search box 51, a belonging group selection area 52, and a talent selection area 53. The search box 51 allows a talent to be searched for by entering a keyword. The belonging group selection area 52 displays icons of groups (belonging group 1, corresponding to communities) that can be supported in the fan community app, and by selecting an icon, talents can be displayed, for example, by belonging group 1. Note that the belonging group selection area 52 may allow selection of all groups. Alternatively, icons that can be selected and displayed for each unit may be displayed.

[0085] The talent selection area 53 displays the icon and name of each talent, but as shown in FIG. 6(B), they may be displayed in order by unit, for example. By selecting the icon of each talent, a favorite talent can be selected. A check mark or the like is also displayed on the icon of the selected talent.

[0086] It is also possible to select all of the talents in a group as the favorite talent by operating the icon in the group selection area 52. Alternatively, a "select all" icon may be displayed, allowing all displayed talents to be selected by a selection operation. Also, the favorite talent may be selected not only on a talent-by-talent basis, but also on a unit basis (two groups to which the person belongs), or may be selected as the most favorite (the talent that is most favored among the favorite talents).

[0087] (Example of a user information database for selected attributes) FIG. 7 is an example of a user information database stored as account information 125. In the user information database, each user is associated with a "user ID," "level," "accumulated points," "participating communities," "favorite talent ID," and other information for identifying the user. The "participating communities" and "favorite talent ID" are associated with information for identifying the attributes selected by the user on the setting screen illustrated in FIG. 6. For example, the setting screen illustrated in FIG. 6 is the setting screen for user ID "u1" in FIG. 7. User ID "u1" selects "Community A" as the participating community in FIG. 6(A) and talents "AAA," "BBB," and "EEE" in FIG. 6(B). Therefore, user ID "u1" is associated with the community "Community A" and the favored talent IDs "t1," "t2," and "t5," which correspond to the respective talents. Hereinafter, user IDs are also referred to simply as "users." Note that "level" and "accumulated points" vary depending on the user's behavior within the fan community, as will be described in detail below.

[0088] (Example of a user's My Page) 8 shows an example of a My Page screen for each user in a fan community. For example, when a user selects My Page icon 16, user terminal 300 acquires and displays information about the user stored as account information 125 on user terminal 300. The My Page screen displays, for example, a name area 54, user rating history status 55, favorite talent information 56, participating community settings 57, notification settings 58, and settings and app information 59, and allows editing operations such as changing various settings.

[0089] The My Page screen in FIG. 8 is a screen displayed on the user terminal 300 of user "u1." The name area 54 displays the name "userA" used by user "u1" within the fan community, along with an icon image. The icon image can be, for example, a fan mark of a celebrity. A fan mark is a symbol or the like used by a celebrity to identify themselves, and fans can publicly indicate which celebrity they are fans of by using the same fan mark. For example, the icon image can be edited by tapping the image editing icon displayed in the lower right corner of the icon image, or by selecting and setting it on the initial setting screen.

[0090] The user evaluation history status 55 displays the "level" and "accumulated points" associated with each user in the user information database of Fig. 7 so that the user can check them. The evaluation history status will be described in detail later.

[0091] The favorite talent information 56 displays the talents that the user has selected in advance so that the user can identify (confirm / recognize) them. For example, the icon and name of each talent are displayed so that the user "u1" can confirm the talents "AAA," "BBB," and "EEE" that he or she selected and set on the favorite talent setting screen of Fig. 6(B). Furthermore, the favorite talent can be changed as needed by operating the edit icon displayed on the favorite talent information 56, etc., which displays the screen of Fig. 6(B).

[0092] Furthermore, when a selection operation is performed on the participating community setting 57, the participating community setting screen of FIG. 6(A) is displayed, and the participating community can be changed as appropriate.

[0093] By operating notification settings 58 or settings / app information 59, push notification settings and various other settings for the fan community app can be configured. The My Page in FIG. 8 may be any page that allows the user to check and edit their own information. For example, a list of participating communities may be displayed on the first screen of the My Page (such as the screen displayed when the My Page icon 16 is operated), similar to the preferred talent information 56. Furthermore, the screens for changing participating communities and preferred talent (FIG. 6) may be displayed together by operating a single edit icon.

[0094] (Example of attribute selection process flow) Next, the flow of the attribute selection process will be described with reference to Fig. 9. Fig. 9 is a diagram illustrating a flowchart of the attribute selection process described with reference to Fig. 6. The attribute selection process is repeatedly executed by the account management unit 133 in the distribution server 100 in response to receiving a request (such as operation information) from the user terminal 300.

[0095] In step S101, it is determined whether or not this is the first login. The first login refers to, for example, when the user downloads and launches the fan community app of this embodiment for the first time, or when the user uses the fan community app of this embodiment via a web browser for the first time, and is the timing when the user first sets attributes in the fan community. If it is determined in step S101 that this is the first login, in step S102, information for displaying an attribute selection screen on the display unit of the user terminal 300 is transmitted. The attribute selection screen is, for example, a setting screen for selecting a participating community and a favorite talent, as exemplified in FIG. 6, and may be incorporated into a tutorial or other flow for the first login (such as basic explanations for the first login).

[0096] Next, in step S103, the user terminal 300 determines whether or not a selection and confirmation operation for a participating community and a favorite talent has been performed. For example, the user selects a community they wish to join from among the participating communities displayed in the participating community selection area 50 in FIG. 6(A). Also, in FIG. 6(B), the user selects a favorite talent from among the talents displayed in the talent selection area 53. An icon for performing a confirmation operation, such as a confirmation icon, may be displayed on the attribute selection screen in FIG. 6. It may be determined that a confirmation operation has been performed by receiving information (including information that can identify the selected participating community and favorite talent) transmitted by operating the confirmation icon or an icon such as "Next." If it is not determined in step S103 that a participating community and a favorite talent have been selected and confirmed, step S103 is repeatedly determined until a selection and confirmation operation is performed.

[0097] On the other hand, if it is determined that an attribute has been selected and confirmed by performing a selection operation on a confirmation icon or the like on the user terminal 300, the process proceeds to step S104, where the participating community and the selected favorite talent selected based on the information received from the user terminal 300 are stored as selected attributes. For example, the account management unit 133 associates the selected participating community and the selected favorite talent ID with the user "u1", stores them as account information 125, and ends the process.

[0098] Returning to step S101, if it is not determined in step S101 that this is the first login, it is determined in step S105 whether or not there has been a request to edit the participating community settings or the favorite talent settings. For example, it is determined that an editing request has been made when there is an operation on the edit icon for the favorite talent information 56 on the My Page shown in Fig. 8 or an operation on the participating community settings 57 on the user terminal 300.

[0099] If it is determined in step S105 that an editing request has been made, then in step S106, information is transmitted for displaying an editing screen for the participating community settings or the favorite talent settings on the user terminal 300. This causes, for example, the attribute selection (setting) screen shown in Fig. 6 to be displayed. On the other hand, if it is not determined in step S105 that an editing request for the participating community settings or the favorite talent settings has been made, then the processing ends.

[0100] After the settings editing screen is displayed in step S106, it is determined in step S107 whether a participating community or a favorite talent has been selected. For example, a selection is determined to have been made by receiving information (including information that can identify the selected participating community and favorite talent) transmitted by a selection operation performed on the display of each participating community in Figure 6(A) or the display of each talent in Figure 6(B) on the user terminal 300.

[0101] If it is determined in step S107 that a participating community or a favorite talent has been selected, the selected participating community or the selected favorite talent is updated and stored as a selected attribute in step S109, and the processing ends. For example, in distribution server 100, based on information corresponding to the attribute selection operation received from user terminal 300, the user information database of FIG. 7 stored as account information 125 is updated and stored.

[0102] Returning to step S107, if it is not determined that a participating community or a favorite talent has been selected, it is determined in step S109 whether or not a back selection has been made. For example, a back icon 10 is displayed on the attribute selection screen of FIG. 6, and it is determined whether or not a selection operation has been performed on the back icon 10. If it is determined that a selection operation has been performed on the back icon 10, the process ends. Alternatively, the process may end by moving to another screen by operating the home icon 13 or the like displayed at the bottom of the app. On the other hand, if it is not determined in step S107 that a back selection has been performed, the process returns to step S107.

[0103] As a result, as will be described later, it becomes possible to extract and display information related to attributes pre-selected by the user in the fan community, allowing the user to extract and obtain information related to their favorite group 1 (first attribute) and also information related to each talent (second attribute). Note that although an example in which the attribute selection process is executed by the distribution server 100 has been described, it may also be executed by the user terminal 300.

[0104] <Examples of content provision> (Overview of the content list screen) Next, examples of content provided by the distribution server 100 via a fan community will be described with reference to FIGS. 10 to 14. FIG. 10 shows an example of a home screen in a fan community app (hereinafter simply referred to as the app) according to this embodiment. The home screen is displayed, for example, on the user terminal 300 when logging in to the app (e.g., when the app is launched) or when a home icon 13 displayed at the bottom of the app is selected. The information for identifying content displayed on the home screen in FIG. 10 (headings of content articles) mainly displays information for identifying content posted in a community in which the user participates.

[0105] The channel icon 12 displayed at the top of the app can display a list of channels for each participating community as exemplified in FIG. 12, and may be displayed on any screen of the app, or may be hidden on a predetermined screen (for example, when the contents of the content are displayed as in FIG. 13). Channels are, for example, categorized by topic (theme). The search icon 17 displayed at the top of the app is an icon for searching for content. The search icon 17 may be displayed, for example, when a list of content headings is displayed, such as on the home screen of FIG. 10 or on a screen for each community as will be described later in FIG. 11(A).

[0106] Furthermore, the home icon 13, community icon 14, notification icon 15, and my page icon 16 displayed at the bottom of the app may be displayed on any screen within the app, or may be hidden on a predetermined screen (e.g., when the contents of the content are displayed as in FIG. 13). As described above, the home icon 13 is an icon for displaying the home screen of FIG. 10 when selected, and the community icon 14 is an icon for displaying a screen for each community, such as FIG. 11(A), which will be described later, when selected. The notification icon 15 is an icon for displaying a screen on which various notifications can be checked, such as when there is a post related to a selected attribute (e.g., a talent set by the user as a favorite talent), reply comments to the user's own posts, and mentions of the user. The my page icon 16 is an icon for displaying the my page illustrated in FIG. 8 when selected.

[0107] (Home screen overview) At the top of the home screen in Fig. 10, a favorite filter 20 and a language switching icon 21 are displayed. The favorite filter 20 is a filter icon that can narrow down the list of displayed content headlines so that only headlines of content associated with a favorite talent selected in advance by the user are displayed, and details will be described later with reference to Figs. 15 and 16. The language switching icon 21 is an icon that allows the displayed language to be switched by a selection operation, for example, from Japanese to English.

[0108] The content provided by the distribution server 100 can be categorized into multiple categories, and the home screen can display the content for each category. The content list (heading) screen on the home screen displays content headings 60 (content information) for content (also referred to as articles or threads) for each category, such as features 61, recommended topics 62, popular user posts 63, commemorative broadcasts 64, and merchandise 65. For example, feature 61 displays announcements set by the content setting unit 251, such as notices from the administrator, that are intended to be shared with all users. The content displayed in feature 61 is displayed regardless of which participating community and which recommended talent the user has selected. Selecting a heading or image displayed in feature 61 may transition to a screen showing more detailed information or an external website.

[0109] The categories from Recommended Topic 62 onwards are configured to display content posted within the communities that the user participates in. The "community" referred to in the app in this embodiment refers to communities A to C corresponding to the groups to which the talent belongs, as exemplified in Fig. 6, and community P in which the user is always a participant.

[0110] (About the community channel list screen) The details of the "Community" of the application in this embodiment will be described with reference to Figs. 11 to 14. Fig. 11(A) is an example of a content list (heading) screen of the "Community" (hereinafter also referred to as a community screen or a channel screen). As shown in Fig. 12, each community is classified into channels by topic type. For example, the community screen in Fig. 11(A) is a screen of the "Official Channel" channel of "Community A" (corresponding to Group A illustrated in Fig. 5), and the channel screen displayed in Fig. 11(A) is switched by a channel selection operation on the channel list screen in Fig. 12.

[0111] The channel list screen illustrated in Fig. 12 is displayed by, for example, tapping on channel icon 12 displayed at the top of the app screen (e.g., Fig. 10) or by flicking (e.g., flicking from the left side of the app screen to the right). Note that when the channel list screen in Fig. 12 is displayed, the list screen can be closed by performing the operation performed when it was displayed (such as selecting channel icon 12 or flicking from the right side of the app screen back to the left side).

[0112] The channel list screen in FIG. 12 displays a community bar 81, a favorites confirmation icon 31, a user's post icon 32, a get started icon 33, a notification settings icon 34, and the like. The communities displayed in the community bar 81 include communities in which the user participates (selected by the user). By selecting the open / close icon displayed in the community bar 81, a channel list 82 for each community is displayed. For example, the channel list 82 corresponding to community A displays each channel name. A selection bar 83 displayed next to each channel name indicates which channel is selected.

[0113] For example, FIG. 12 shows a screen displayed on the user terminal 300 of the user "u2" illustrated in FIG. 7. The communities in which the user "u2" participates are "Community A" and "Community B," and therefore the channel screen list in FIG. 12 displays a channel bar 81a for "Community A," a channel bar 81b for "Community B," and a channel bar 81c for "Community P," in which the user "u2" always participates. The selection bar 83 is displayed next to the "Official Channel" for "Community A," indicating that the community screen displayed in FIG. 11(A) is the "Official Channel" for "Community A." For example, a selection operation on a channel name displayed in the channel list 802 moves the selection bar 802b. As a result, the "Official Channel" for "Community A" in FIG. 11(A) is displayed on the app screen.

[0114] When a selection operation is performed on the channel list screen of Fig. 12, the screen may switch to the community screen of Fig. 11(A). Alternatively, as shown in Fig. 12, the channel list screen may be displayed superimposed on another screen, and the screen displayed below the channel list screen may be switched to the screen of the selected channel. By performing an operation to close the channel list screen of Fig. 12, the community screen of Fig. 11(A) may be displayed in full. Also, by selecting a channel on the channel list screen of Fig. 12, when a selection operation is performed on the community icon 14 displayed at the bottom of the app screen, the selected channel will be displayed as the community screen of Fig. 11(A).

[0115] The favorites confirmation icon 31 in FIG. 12 is an icon that, when selected, allows the user to check the content (also called posts) that the user has registered as favorites and that is stored as account information 125 or stored in the storage unit 320. The my posts icon 32 is an icon that, when selected, allows the user to check the content (threads created) that the user has posted in the community and the comments the user has made on the content (threads created). The introduction icon 33 is an icon that, when selected, allows the user to review the tutorial that is displayed upon initial login, or to display information on how to use the app and mental preparations. The notification settings icon 34 is an icon that, when selected, allows the user to display a screen for setting various notifications (e.g., selecting information to be sent by push notification). For example, the same screen as that displayed when the notification settings icon 58 illustrated in the My Page of FIG. 8 is selected may be displayed.

[0116] (About the Community screen) The community screen in Fig. 11(A) displays a recommended filter 20, a language switching icon 21, a sorting icon 22, a posting icon 23, and the like, similar to the home screen exemplified in Fig. 10. The sorting icon 22 is an icon that, when selected, allows the order of the displayed content headings to be sorted in order of newest arrivals or popularity (for example, in order of most likeable actions). The posting icon 23 is an icon that, when selected, allows a user to post content (create a thread) within the community.

[0117] Each piece of content posted within a community is partially displayed as a content heading 70 (content information) on the community screen of Fig. 11(A). For example, content headings 70a, 70b, 70c, etc. are displayed. Each content heading 70 displays a poster 71, a report icon 72, a favorite icon 73, content information 74, etc.

[0118] The icon, name, etc. of the poster of the corresponding content are displayed in contributor 71. For example, if the contributor is an administrator or a special user (described later), the icon, name, etc. of the poster are displayed together with an official mark.

[0119] When the report icon 72 is selected, a screen such as that shown in FIG. 11(B) is displayed (for example, a pop-up display on the current screen). By selecting the text displayed in FIG. 11(B), the user can, for example, report offensive content to the administrator, hide the content on the user terminal 300, or block the content poster in the fan community app (so that the actions such as posts of the blocked user are not displayed on the user's own user terminal 300 thereafter). Note that operations such as hiding and blocking cannot be performed on administrators or special users (or content posted by them), and may be operations that can only be performed on other general users.

[0120] The favorite icon 73 is an icon that, when selected, allows the user to save their favorite posts so that they can be viewed later. For example, when the favorite icon 73 is selected, the user information database of FIG. 7, which is stored as account information 125, is updated and stored with the article ID of the post for which the favorite icon 73 was operated, in association with the user. This allows the user to view their favorite posts when they select the favorite confirmation icon 31 of FIG. 12.

[0121] The content information 74 displays the title of the posted content and part of the description.

[0122] Furthermore, if the posted content is posted together with an image, an image 75 is displayed in the content heading 70, and if there are comments on the content, the comments (for example, the latest comments or some of the most popular comments) are displayed in featured comments 76. Furthermore, the number of comments on the content is displayed in number of comments 77, and the number of tap actions on the content is displayed in number of tap actions 78. The number of tap actions on the content is displayed, for example, as the total number of tap actions from all users on a heart icon 708 displayed together with the number of tap actions 78 in the content heading (60, 70), or on an icon 708 displayed together with the number of tap actions 78 on the content screen in FIG. 13, which will be described later.

[0123] Furthermore, users who use the fan community app include special users, and when a comment or tap action is made by a special user, the comment or tap action from the special user can be displayed as a special action 79 in the content heading 70 along with the icon of the special user. A special user is, for example, a user corresponding to the talent shown in FIG. 5. Therefore, by displaying the special action 79, users can recognize that an action such as a comment or tap action has been made by the talent themselves. This can promote interaction with the target of support in the fan community app, thereby increasing user satisfaction.

[0124] The special actions 79 are displayed with an icon corresponding to each talent, along with an icon indicating that a comment was made by the talent, such as a speech bubble, if the talent has made a comment, and an icon indicating that a tap action was made by the talent, such as a heart. For example, the content heading 70a on the community screen in FIG. 11 displays special actions 79 indicating that actions were made by three talents. The icons of the talents displayed on the left and center are displayed with a speech bubble and a heart, indicating that a comment and a tap action were made. On the other hand, the talent displayed on the right is displayed with only a heart along with the icon, indicating that only a tap action was made without a comment.

[0125] In addition, the special action 79 displayed in the content heading 70 may be displayed within the content heading 60 on the home screen of FIG.

[0126] Fig. 13 is an example of a content screen that is displayed when content heading 70a is selected from among the contents displayed in Fig. 11(A), and is an example of a display screen that displays the content itself (post itself) that is the content of content heading 70a. Note that if similar content is also displayed on the home screen of Fig. 10, the content screen of Fig. 13 is displayed by selecting the corresponding content heading 60 on the home screen.

[0127] 13, a back icon 10b is displayed at the top, and the poster 71, report icon 72, favorite icon 73, number of tap actions 78, category 85, content 74b, related talent 88, and special actions 79 are displayed. If there are comments on the content, the comments are displayed in a list at the bottom. The comment list display includes a comment count 77b that displays the number of comments, each comment 87, and a comment posting field 84 where users can post comments.

[0128] When the back icon 10b is selected, the screen returns to the one the user was displaying immediately before. For example, if the content screen was accessed from the community screen in Fig. 11(A), the screen returns to the community screen in Fig. 11(A), and if the content screen was accessed from the home screen in Fig. 10, the screen returns to the home screen in Fig. 10.

[0129] If a category is associated with the content, the associated category name is displayed in category 85. Posted text information such as the title and description of the content is displayed in content 74b.

[0130] 5 is associated with the content, and displays the icon, name, etc. of the associated talent. Special action 79 is a display to indicate that, when an action has been taken on the content by a special user corresponding to the talent in FIG. 5, the content has been acted upon by that special user.

[0131] Each comment 87 displays a poster 71b that displays the comment poster, a report icon 72b that allows the comment to be reported or hidden as shown in Fig. 11(B), a reply icon 86 that allows a reply to the comment, a reply list 89 that displays a list of replies, etc. Note that the comment posting field 84 may also display an icon of the user himself / herself.

[0132] The display mode of each comment 87 may vary depending on the poster. For example, comment 87a is a comment made by a special user (AAA himself) corresponding to the talent "AAA" illustrated in FIG. 5. For example, the display order of the comments in the list at the bottom of the content screen in FIG. 13 may be changed so that the comment is displayed at the top, and the color may be changed so that it can be distinguished from comments made by other users (the display mode may be different). This can encourage users to interact with the talent in the fan community, improving user satisfaction.

[0133] Next, an example of a database of content in each community stored as content data 122 in distribution server 100 will be described with reference to Fig. 14. For example, Fig. 14 shows a content database for "Community A." The content database stores information such as "channels," "posting authority" for each channel, and "article ID" for each piece of content.

[0134] "Channels" are classified by topic, and the screen of each channel can be selected and displayed by a selection operation on the channel list 82 illustrated in FIG. 12. For example, "Official Channel" is a channel where official announcements from the administrator are posted, and "Group A Chat" is a channel with the theme of chatting about "Group A" of the affiliated group 1 in FIG. 5, which corresponds to "Community A." Furthermore, "Clips" is a channel with the theme of sharing links to clipped videos recommended by users (e.g., videos posted on a video distribution site, which are clipped portions of videos already posted on the video distribution site). "Past Recommendations" is a channel with the theme of recommending videos related to Group A (e.g., videos previously posted by affiliated talent). Note that when "All Channels" is selected on the channel list 82 in FIG. 12, all of the content of the channels in FIG. 14 is displayed together. Note that these channels are merely examples, and temporary special channels may be set up, for example.

[0135] "Posting authority" is information about users who have the authority to post content to each "channel." For example, "Official Channel" and "Past Recommendations" can only be posted from official accounts (e.g., special users such as administrators or celebrities). Posting from official accounts can be made, for example, from the administrator terminal 200 or from a terminal with the same configuration as the user terminal 300, as long as the user ID is identified as an official account. Furthermore, all users can post to "Group A Chat" and "Clips." For example, in the channel list 82 of FIG. 12, channels that can only be posted from official accounts are marked with an official mark, and channels that can be posted to by all users are marked with a speech bubble or the like. This allows users to easily identify whether or not a channel is available for posting.

[0136] An "article ID" is an ID that identifies each piece of content and is assigned to each piece of content. Each "article ID" is associated with a "category," "contributor ID," and "talent ID."

[0137] "Category" is a category that can be associated when content is posted. For example, "Event," "Goods," "Stream / Video," "Fan Art," "Clip," "Music," "Commemorative Stream," etc. can be associated to make it easier to recognize the theme of the content itself. When a "Category" is associated, the category name will be displayed in Category 85 on the content screen example in Figure 13.

[0138] The "contributor ID" is an ID that identifies the contributor of the content.

[0139] The "talent ID" is the talent ID of a related talent associated with the content when the content is posted, among the talent IDs stored in the talent information database of Fig. 5. In this way, in this embodiment, when posting content, the poster can associate a related talent with the content according to the content, and the associated "talent ID" can be stored for each piece of content. In other words, each piece of content data is stored together with the meta information of the talent.

[0140] For example, article ID "a1" is associated with the category "events," the poster is "ou1," and the talent IDs "t1," "t2," "t6," and "t14" are associated with it. Figure 13 above is a display example of article ID "a1," and poster 71 displays the name of "Staff S," who corresponds to user ID "ou1," and an official mark indicating that it is an official account. Category 85 also displays the category "events," which is associated with article ID "a1."

[0141] The related talent 88 displays the icons and names of the talents "AAA," "BBB," "FFF," and "MMM," ​​respectively corresponding to the talent IDs "t1," "t2," "t6," and "t14" associated with the article ID "a1." Since the related talents can be set when posting, the related talents can be displayed in the content, allowing the user to easily identify which talent the post is about. The related talent 88 may also be displayed in the content heading 70 on the community screen shown in FIG. 11(A).

[0142] In this way, related talents can be associated with content. Therefore, if the related talents include a favorite talent selected in advance by the user, the distribution server 100 can notify the user by push notification that a post related to the favorite talent has been made, based on information in the user information database stored as account information 125. For example, when content associated with the favorite talent and a related talent has been posted, or every predetermined time (e.g., every 5 minutes, 15 minutes, etc.), the distribution server 100 sends a push notification to the user that content associated with the favorite talent and a related talent has been posted. When a push notification is made, the user can transition to a content screen (e.g., FIG. 13) for the content associated with the favorite talent by performing an operation in response to the push notification. When content associated with the favorite talent and a related talent has been posted, this occurs when the content heading (60, 70) for the content is displayed on the home screen of FIG. 10 or the community screen of FIG. 11(A).

[0143] It should be noted that the category and related talent can be set at the poster's discretion when posting content, and content can be posted without any association. For example, content may be posted within community A with no related talent, such as article ID "a99," in which case only community A (first attribute) is associated with the content.

[0144] (Example of home screen) Returning to FIG. 10 , the content displayed on the home screen will be described in detail. The home screen of each user terminal 300 displays content stored in a content database corresponding to the "participating community" associated with the user information database shown in FIG. 13 (stored as account information 125) among the content databases shown in FIG. 14 (stored as content data 122). That is, for categories from the recommended topic 62 onward on each user's home screen, only content headings of content posted in the communities in which the user participates are displayed. For example, if the communities pre-selected in FIGS. 6 and 9 are "Community A" and "Community B," the home screen displays content posted in "Community A," "Community B," and "Community P," in which the user is always participating. If there is no community in which the user always participates, the home screen displays content posted in the community pre-selected by the user. However, content posted in "Community C," in which the user is not participating, is not displayed. Furthermore, for categories from the recommended topic 62 onward, the displayed content headings 60 change depending on whether the recommended filter 20 (described later) is turned on or off.

[0145] In any category, the home screen may display only one piece of content, or may display a predetermined number of the most recent content headings 60 (for example, two, five, seven, etc.). Alternatively, a predetermined number of content headings 60 may be displayed in order of popularity. The displayed content headings 60 for each category may be switched by performing a left-right sliding operation on the touch panel of the user terminal 300. For example, by performing an operation (such as a flick operation) to slide a content heading 60 (for example, the most recent dated one) displayed in the commemorative distribution 64 of FIG. 10 to the left, an older content heading 60 may appear on the right side of the screen. Alternatively, for example, only half of the content headings 60 may be displayed on the right side of the screen, or may not appear unless a sliding operation is performed.

[0146] In addition, in the content heading 60 of any category on the home screen, if the content is associated with a talent as shown in Figure 5, an associated talent 88 may be displayed that displays the icon, name, etc. of the associated talent.

[0147] Furthermore, the recommended topic 62 displays a predetermined number of pieces of content posted within the community in which the user participates that are associated with the recommended talent that the user has previously selected as exemplified in Figures 6, 9, etc. For example, the recommended topic 62 of a user who participates in "Community A" and has selected talent "AAA" as their recommended talent will display an extracted piece of content that is associated with the talent ID "t1" corresponding to talent "AAA" from the content stored in the content database of Community A in Figure 14.

[0148] Popular user posts 63 displays a predetermined number of contents that are considered to be popular among contents posted by general users other than the official accounts of the communities in which the user participates. For example, the contents may be sorted in order of the number of like actions (tap actions and / or comments) or the highest engagement rate (for example, contents with a high ratio of like actions to the number of views).

[0149] Furthermore, the content displayed on the home screen may include a category that displays content stored in the content database that is associated with a specific category. For example, commemorative broadcast 64 displays content stored in the content database that is associated with the category "commemorative broadcast," and goods 705 displays content that is associated with the category "goods." There may also be a category that displays only posts from a specific channel of a specific community. For example, there may be a category that displays a predetermined number of the latest content headings 60 posted to a specific channel of "Community P." Furthermore, these categories displayed on the home screen are merely examples, and temporary special categories may also be provided.

[0150] The recommended topic 62 on the home screen is preferentially displayed at the top of the categories that can be displayed on the home screen, excluding the feature 61. This makes it easier for the user to identify information about the recommended talent. However, this is not limiting, and the recommended topic 62 may be preferentially displayed at the top, including the feature 61. Alternatively, there may be other categories that are displayed with priority over the recommended topic 62. The categories can be displayed in the order that the administrator wants users to recognize.

[0151] Furthermore, the content displayed in the content heading 60 of the recommended topic 62 may overlap with the content displayed in the content headings 60 of other categories after the recommended topic 62, or if a content is displayed in the recommended topic 62, it may not be displayed in the content headings 60 of other categories. Note that the recommended topic 62 will not be displayed to users who have not previously selected any talent as their recommended talent.

[0152] (Example of content attribute extraction process related to selected attributes) 15 and 16, a filter function that narrows down the content displayed to those associated with a favorite talent (second attribute) pre-selected by the user will be described. In the fan community app of this embodiment, the content displayed on the user terminal 300 is not only narrowed down to the participating community (first attribute) pre-selected by the user, but also can be further narrowed down to the favorite talent (second attribute) pre-selected by the user when a predetermined condition based on the user's intention is met, since each content data is stored together with the talent's meta information.

[0153] Narrowing down to content associated with a favorite talent is performed by a predetermined switching operation on the user terminal 300. The predetermined switching operation is an operation of selecting a predetermined icon, for example, a selection operation on the favorite talent filter 60 on the home screen of FIG. 10 and the community screen of FIG. 11(A) (note that these may also be referred to as the content list screen and the content screen).

[0154] Figure 15 shows example screens on the content screen of Figure 11(A) when the Oshi Filter 20 is on and off. Figure 15(A) shows an example screen when the Oshi Filter 20 is on and the filtering to the Oshi talent preset by the user is active. Figure 15(B) shows an example screen when the Oshi Filter 20 is off and the filtering to the Oshi talent preset by the user is not active.

[0155] 15 is an example of a screen displayed on the user terminal 300 of the user "u1" in FIG. 7, for example. In FIG. 15(A), the favorite filter 20 is on, so only content associated with the talent selected in advance by the user "u1" as a favorite talent is extracted. That is, in the user information database stored as the account information 125, the talent IDs associated with the user "u1" are the talent ID "t1" of the talent "AAA," the talent ID "t2" of the talent "BBB," and the talent ID "t5" of the talent "EEE." Therefore, only content associated with any of the talent IDs is extracted from the content information database stored as the content data 122. For example, content of the article ID "a1" associated with the talent IDs "t1" and "t2" and content (content headings 60, 70) of the article ID "a7" associated with "t5" in the content information database of the community A in FIG. 14 are displayed.

[0156] On the other hand, article ID "a4," which is not associated with any of the talents selected by user "u1," is not displayed. For example, even if the content is posted within a participating community, content headings (60, 70) of content that is not associated with any related talents are not displayed. In contrast, when the favorite filter 20 is turned off, as shown in FIG. 15(B), content headings 70d of content related to talent "DDD," content heading 70e of content related to talent "FFF," or content heading 70 of content not associated with any talents, which are content that is not associated with the favorite talent selected by user "u1," are displayed.

[0157] (Example of attribute extraction process flow) Next, the flow of the attribute extraction process for extracting content relating to attributes previously selected by the user will be described with reference to Fig. 16. Fig. 16 is a diagram for explaining a flowchart of the attribute extraction process described with reference to Fig. 15. The attribute selection process is repeatedly executed by the content management unit 132 in the distribution server 100 in response to receiving a request from the user terminal 300 (for example, operation information for the recommended filter 20, etc.).

[0158] In step S201, it is determined whether a content display request operation has been made from the user terminal 300. Display request operations include an operation to load display data on the user terminal 300 and a selection operation to turn the favorite filter 20 on or off when a predetermined condition is met. Operations to load display data include, for example, logging in to the app (querying the server when the app is opened), a reload operation (reloading operation), or a selection operation on the home icon 13, community icon 14 on the app screen, or a channel displayed in the channel list 82 in FIG. 12 . The predetermined condition is met, for example, when the user taps to switch the icon of the favorite filter 20 displayed on the user terminal 300.

[0159] If it is determined in step S201 that a display request operation has not been made, the process ends. On the other hand, if it is determined in step S201 that a display request operation has been made from the user terminal 300, it is determined in step S202 whether the Oshi Filter 20 is on. In this embodiment, the default setting for the Oshi Filter 20 is off. Therefore, the Oshi Filter 20 is off when logging in when the app is launched, or on the content screen or home screen of a channel that is displayed for the first time after the app is launched. In this case, since it is not determined in step S202 that the Oshi Filter 20 is on, the process proceeds to step S203.

[0160] In step S203, information about the participating communities selected by the user of the user terminal 300 that sent the display request operation is extracted and transmitted to the user terminal 300, after which the process ends. The selected participating communities include the "belonging communities" for each user that are previously selected by the user and stored as account information 125, as illustrated in FIGS. 6A and 9, and, if there are any communities in which the user is always participating, the communities in which the user is always participating. For example, user "u2" in FIG. 7 is participating in "Community A" and "Community B." Therefore, in step S203, the home screen of the user terminal 300 of user "u2" displays content posted in "Community A," "Community B," and the "Community P" in which the user is always participating, and the community bars 81 for "Community A," "Community B," and "Community P" are displayed on the channel list screen of FIG. 12.

[0161] Returning to step S202, if it is determined that the Oshi Filter is on, the process proceeds to step S204. For example, when a selection operation to turn on the Oshi Filter 20 is performed, it is determined in step S201 that a display request operation has been performed, and it is determined in step S202 that the Oshi Filter is on. Also, after the app is launched, if a reload operation is performed on the community screen or home screen of a channel where the operation to turn on the Oshi Filter 20 has already been performed, or if the content screen of FIG. 13 is displayed with the Oshi Filter 20 on and then the user returns to the community screen or home screen where the Oshi Filter 20 was on, the Oshi Filter 20 on state is stored (stored in the storage unit 120 or the storage unit 320), and it is determined in step S201 that a display request operation has been performed, and it is determined in step S202 that the Oshi Filter is on.

[0162] In step S204, information about the selected favorite talent from the selected participating community is extracted and transmitted to the user terminal 300, and the process ends. For example, for user "u2," only content associated with talent IDs "t2," "t3," "t4," "t7," and "t8" is extracted from content posted in "Community A," "Community B," and "Community P" and displayed on the channel content screen and home screen. On the home screen, for categories from Recommended Topic 62 onward (categories other than Feature 61 and Recommended Topic 62 in FIG. 10), content headings 60 of content associated with the favorite talent previously selected by the user through a selection operation on the Recommended Filter 20 in participating communities are displayed.

[0163] Although an example has been described in which the attribute extraction process is executed by the distribution server 100, it may also be executed by the user terminal 300. For example, information about each user's favorite talent may be stored in the memory unit 320 of the user terminal 300, and information about the content obtained from the distribution server 100 (for example, every 10 items) may be extracted by the user terminal 300.

[0164] Furthermore, even if content is posted by a talent other than the user's favorite talent or the content is centered (main) around a talent other than the user's favorite talent, if the talent associated with the content is associated with a favorite talent previously selected by the user, turning on the favorite filter 20 will display content headings (60, 70) for content related to the talent other than the user's favorite talent on the home screen of FIG. 10 or the community screen of FIG. 11(A). For example, suppose that content posted by talent "AAA" corresponding to content heading 70c in FIG. 11(A) is related to a birthday event for talent "AAA." However, suppose that talent "BBB" is scheduled to participate in the birthday event for "AAA" (also known as a collaboration), and therefore "BBB" is set as a related talent. In this case, in the content database, the talent ID "t2" corresponding to talent "BBB" is associated with the article corresponding to content heading 70c. As a result, even if a user who has not selected talent "AAA" as their favorite talent turns on the favorite filter 20 on their user terminal 300, the content heading 70c related to the birthday event of talent "AAA" will be displayed. As a result, even if the information is likely to be overlooked at first glance because it is not related to the favorite talent, the user will not miss information related to the favorite talent.

[0165] Even if the favorite filter 20 is not on (whether the favorite filter is on or off), the related talent 88 can be displayed on the home screen of Fig. 10, the community screen of Fig. 11(A), or the content screen itself of Fig. 13. Therefore, even without setting favorite talents individually, the user can recognize who in the group is related to the content, which increases interest.

[0166] (Examples of user-submitted associations with categories, talents, etc.) Next, with reference to Figures 17 and 18, a specific example of user posting processing when a user posts content will be described. Figure 17 is an example of a user posting screen. For example, when the content screen of a channel for which "posting authority" is set to "user" in the community content database of Figure 16 is displayed, the posting icon 23 shown in Figure 11(A) is selected to display it. Note that for channels such as official channels where posting authority is limited to official accounts, unauthorized users may be unable to select the posting icon 23 on the content screen. For example, the display mode may be changed, such as by displaying it in gray, or the posting icon 23 itself may not be displayed.

[0167] FIG. 17(A) is a screen that is displayed when the post icon 23 is selected on the content screen of the channel "Group A Chat." FIG. 17(A) displays input fields for the title, main text, etc., an image icon 37, a next icon 38, etc. By selecting the image icon 37, an image saved in the user terminal 300 can be uploaded. By selecting the next icon 38, the screen transitions to that of FIG. 17(B). Note that if the title and main text have not been entered, it is not necessary to proceed to the next step. If an image has been uploaded instead of entering text, it may be possible to proceed to the next step. This is to avoid a proliferation of empty posts.

[0168] On the screen of FIG. 17(B), it is possible to select a category and related talent to associate with the content to be posted. For example, when category bar 39 is selected, a category list 39b opens, as illustrated in FIG. 17(C). The user can select any category from the category list. Note that one category may be selected, or multiple categories may be selectable. When related talent bar 40 in FIG. 17(B) is selected, a list of talents, as shown in FIG. 6(B), is displayed, and any talent (talent to be associated) can be selected. Note that the selection of related talent is not limited to one person, and multiple people can be selected. When a selection operation is performed on icon 41 to post, the content is posted to "Group A Chat."

[0169] Furthermore, in the fan community app of this embodiment, as illustrated in FIG. 11 and other examples, when a special user, such as the talent in FIG. 5, makes a reaction such as a comment or a tap action, a special action 79 is displayed, and the user is notified of this by a push notification (for example, a message sent directly to a mobile device owned by the user and on which the app is installed). Furthermore, the push notification of a reaction such as a comment or a tap action made by a special user talent may be configured to be sent to any user, regardless of user type, even if the special user is not pre-selected by the user as a favorite talent, if the user makes a comment or a tap action on the user's post. Furthermore, even if the user is not pre-selected as a favorite talent, if the special user makes a reaction such as a comment or a tap action in the fan community, a push notification of this may be sent to users of the fan community.

[0170] As described above, in the fan community of this embodiment, when a special user performs a reaction operation such as a tap action, the reaction is displayed on the content screen, and a push notification to that effect may be sent to the user. However, it is also possible that the special user may perform a reaction operation by mistake. Therefore, in this embodiment, an action cancellation time is set after the special user performs a tap action, etc. If the action has not been canceled after the cancellation time has elapsed, the special action 79 is reflected on the user devices of other users, a push notification is sent, and the target action can be canceled in response to a cancellation operation from the special user within the action cancellation time. The action cancellation time can be set, for example, to five minutes after a talent performs a reaction operation such as a tap action. This allows a special user who has a large influence through reactions such as comments and tap actions to accidentally perform a reaction operation before the reaction operation becomes known to other users.

[0171] In addition, a push notification to notify that a special user, such as a celebrity, has performed a tap action or the like may be sent in the form of a voice message from the celebrity who performed the action.

[0172] (User submission processing flow) Next, the flow of the user posting process when a user posts content will be described with reference to Fig. 18. Fig. 18 is a diagram for explaining the flowchart of the user posting process described with reference to Fig. 17. The user posting process is repeatedly executed by the control unit 350 of the user terminal 300.

[0173] In step S301, it is determined whether a posting icon has been selected. For example, it is determined whether a selection operation has been performed on posting icon 23 on a content screen such as FIG. 11(A). If it is determined that posting icon 23 has not been selected, the process ends. On the other hand, if it is determined that posting icon 23 has been selected, it is determined in step S302 whether the channel to which the posting is being attempted is a channel to which user posting is permitted. For example, in the case of the channels "Group A Chat" and "Clips" in FIG. 14, all users are permitted to post, so in step S303, the posting screen in FIG. 17(A) is displayed. This allows, for example, text information to be entered or an image to be attached by operating image icon 37.

[0174] On the other hand, if the content screen when "All Channels" is selected in the channel list 802 of Figure 12, or the content screen for the channel "Official Channel" or "Past Recommendations" is displayed, posting is only permitted to official accounts, so in step S302 it is not determined that the channel is one for which user posting is permitted, and processing is terminated.

[0175] After the posting screen is displayed in step S303, it is determined in step S304 whether or not "Next" has been selected. For example, it is determined whether or not "Next" icon 38 has been selected as an operation to proceed to the next page on the posting screen of FIG. 17(A). If it is determined in step S303 that "Next" has been selected, it is determined in step S305 whether or not character input has been completed. If character input has not been completed, the process returns to step S304.

[0176] On the other hand, if it is not determined in step S304 that "Next" has been selected, it is determined in step S306 whether "Close" has been selected. For example, this may be a selection operation on the close icon 35. If it is determined in step S306 that "Close" has been selected, the process ends. On the other hand, if it is not determined in step S306 that "Close" has been selected, the process returns to step S304.

[0177] If it is determined in step S305 that character input has been completed, a category etc. selection screen is displayed in step S307. For example, this is a screen that allows selection of a category or related talent as shown in FIG.

[0178] After the category selection screen is displayed in step S307, it is determined in step S308 whether or not a category has been selected. If it is determined in step S308 that a category has been selected, the category is associated with the posted information in step S309. For example, if "event" is selected in the category list 39b in FIG. 17(C), the category "event" is associated with the posted information.

[0179] If it is determined in step S308 that no category has been selected, or after a category has been associated in step S309, it is determined in step S310 whether or not a related talent has been selected. If it is determined in step S310 that a related talent has been selected, the related talent is associated with the posted information in step S311. For example, in FIG. 17(B), if the related talent bar 40 is selected to select talent "AAA," talent ID "t1" is associated with the posted information.

[0180] If it is not determined in step S309 that a related talent has been selected, or after the related talent has been associated in step S310, it is determined in step S312 whether a post confirmation operation has been performed. For example, it is determined whether a selection operation has been performed on the posting icon 41 in FIG. 17(B). If it is determined in step S312 that a post confirmation operation has been performed, the posted information (including, for example, input text information, attached image information, selected category, selected related talent, poster ID, etc.) is sent to distribution server 100 for processing in step S313. As a result, for example, if the category "Events" is selected in "Group A Chat" and "DDD" is selected as the related talent, distribution server 100 stores the article ID "a4" as shown in FIG. 14.

[0181] Returning to step S312, if it is determined that the posting confirmation operation has not been performed, it is determined in step S314 whether or not a close selection has been performed. The close selection is, for example, an operation of selecting the close icon 35 on the screen of Fig. 17(B). If it is determined in step S314 that close has been selected, the process ends.

[0182] On the other hand, if it is determined in step S314 that "Close" has not been selected, it is determined in step S315 whether "Back" has been selected. For example, this may be a selection operation on the "Back" icon 36 in FIG. 17(B). If it is determined in step S315 that "Back" has been selected, the process returns to step S303, returning to the display of the text input posting screen in FIG. 17(A). This allows the user to re-edit the text and image information that was input on the posting screen before selecting "Next" in step S304. On the other hand, if it is determined in step S315 that "Back" has not been selected, the category etc. selection screen continues to be displayed in step S307. Note that although an example in which the user posting process is executed on the user terminal 300 has been described, it may also be executed on the distribution server 100, and the display information may be transmitted to the user terminal 300.

[0183] <About behavior control function based on user ratings within fan communities> (Overview of behavior control function) Next, a description will be given of a behavior control function based on user ratings within a fan community in this embodiment. In the fan community in this embodiment, users themselves can post content within the community and share it with other users. While this type of interaction with other users revitalizes the community, if no restrictions are placed on the actions users can take, users who post content that may offend other users may be left unchecked, which could lead to a deterioration in the public order and atmosphere within the community. Therefore, a level that serves as an indicator of trustworthiness, honesty, etc. is set for each user, and the actions that users can take within the community are changed depending on the level. In this embodiment, the user's rating history is updated based on external evaluations other than the user's own evaluation, depending on the user's actions within the community, and the actions that users can take within the community are changed depending on the rating history. As a result, users with high indicators such as trustworthiness and honesty are allowed to take more actions, while users with low indicators are restricted in the actions that they can take. In other words, the rating history changes depending on the actions that are acceptable within the fan community.

[0184] (Summary of user level fluctuations) As shown in the user information database of FIG. 7, each user's "level" is stored in association with the user ID. The "level" changes according to the "accumulated points." The "accumulated points" change according to external evaluation, which will be described later. For example, if a user's level is initially set to 1 and the accumulated points reach 10, the level will change to 2. To increase from level 2 to level 3, more points are required than the number of points required to increase from level 1 to 2. For example, the user will reach level 3 when the accumulated points reach 21. In this way, as the level increases, the number of points required increases, making it more difficult to increase the level. In addition, the "accumulated points" may decrease according to external evaluation. For example, if a user who was at level 2 has accumulated points that fall below 20, the user's level will decrease from 2 to 1.

[0185] Furthermore, each user can check their own "level" and "accumulated points" in the user evaluation history status 55 on their My Page, as shown in FIG. 8. This allows users to be mindful of taking actions that will raise their level. On the other hand, users cannot check the "level" and "accumulated points" of other users. In this way, by not disclosing their own level to other users, users with lower levels in the community can be prevented from feeling inferior, and users with higher levels can be prevented from behaving arrogantly. Note that only one of the "level" and "accumulated points" may be displayed on the My Page.

[0186] (About actions that can be taken by level) Actions that can be taken by user level in this embodiment will be described with reference to Figures 19, 20, and 21. Figure 19 is a table showing examples of actions that are permitted (can be taken) by level, and is divided into levels such as "1 to 49," "50 to 59," "60 to 69," "70 to 79," "80 to 89," "90 to 99," and "100." Actions permitted for each level are stored as action authority information 124 in distribution server 100.

[0187] "Specific actions," which are actions that can be taken or not, are controlled depending on the user's level and include, for example, "no posting link restrictions," "plan creation," "moderator invitation," and "community creation." "No posting link restrictions" means that when a user posts content within a community, there are no restrictions on the URLs that can be posted, and the restrictions are lifted for users with level 60 or higher. Furthermore, content posted by users with no posting link restrictions is also reflected on the user terminals 300 of users with level 59 or lower. In other words, even if content contains a link that is restricted from posting, users with level 59 or lower can view (and access) the link, as long as the content was posted by a user with level 60 or higher.

[0188] "Plan creation" is the right to start a plan (event) within the community, and can be done by users level 80 and above. For example, they can start an event plan such as an offline meetup where people gather in real or virtual space at a specified date and time, or a survey plan. In other words, they can act as a leader. Furthermore, users level 79 and below can participate in plans created by users level 80 and above.

[0189] "Moderator invitation" means that a user can act as an administrator of content posted within a community, and is available to users who are level 90 or higher. For example, this can involve deleting or hiding (also known as restricting) content or comments that have been visually inspected as inappropriate, something that an administrator would normally do. It can also be the authority to take measures such as suspending (for example, for a certain period of time) the accounts of malicious users. Content restricted by users level 90 or higher will no longer be displayed on the user terminals 300 of users level 89 or lower.

[0190] "Community creation" allows users to create new communities that they can participate in, as exemplified in FIG. 6(A) and other examples. This action is permitted only for users with the highest level of trust, level 100. For example, a fan of group A (corresponding to community A) can create a community called "Community A2" to support group A. The created community A2 will be displayed in the participating community selection area 50 on the participating community setting screen in FIG. 6(A). Alternatively, new "channels" may be created. For example, a channel with a new theme can be added to the channel for "Community A." The newly added channel will be displayed in the channel list display 82 in FIG. 12. Communities and channels created by level 100 users can also be joined and selected by users at level 99 or lower.

[0191] Furthermore, in this embodiment, the user's level can not only be raised but also lowered. Therefore, even if a specific action such as the one illustrated in FIG. 19 is permitted as a result of a level increase, it becomes restricted and cannot be performed as the level decreases. For example, a user at level 80 or higher can create a project within a community, but if the user's level decreases to 79, they will no longer be able to create a project. Furthermore, if another user reports a created project or community as inappropriate in the fan community app on the display screen of the created project or community, this is also an external evaluation that may lower the level of the user who created the project or community.

[0192] FIG. 20 shows an example of a posting screen on the user terminal 300 of a user who does not have "no posting link restrictions." In this embodiment, a user with a posting link restriction up to level 59 is only permitted to post links to "video sharing site A" and "SNS-B." In this case, if a URL other than "video sharing site A" or "SNS-B" is entered in the body of a post, a message such as "Currently, only URLs 'video sharing site A' and 'SNS-B' can be posted" is displayed, as shown in FIG. 20. Furthermore, if the next icon 38 is displayed in a different manner depending on whether a post is permitted or not, the next icon 38 may be displayed in a manner that prohibits posting, preventing selection. In this way, while it is relatively easy to automatically detect uploaded images using image recognition to hide inappropriate images (images that may be offensive, such as violent images), it is not easy to determine whether a URL references a malicious website (e.g., a fake site, a fraudulent site, or a page containing offensive content), and the administrator must perform a hide setting, which is time-consuming. Therefore, for content that is difficult to determine whether it is an inappropriate post (in this case, URL links), by allowing only high-level users (users with high levels of trust) to post it, the burden on administrators can be reduced and inappropriate posts can be suppressed, stabilizing public order within the community.

[0193] In addition, "Video Sharing Site A" and "SNS-B," which are open to users who do not have "no posting link restrictions," are websites where streaming videos of celebrities who are the target of support in fan community apps are posted, and relatively safe link destinations have been established.

[0194] The flow of the process for determining whether a user has posted links restricted in the user posting process will be described with reference to Figure 21. Figure 21 is a flowchart for the case where a determination of whether a user has posted links restricted (processing surrounded by a dotted line) is added to the user posting process described with reference to Figure 18, and therefore a description of the same processes as in Figure 18 will be omitted.

[0195] 17(A) is displayed in step S303, it is determined in step S316 whether or not a link other than the predetermined link has been pasted. If it is determined that a link other than the predetermined link has not been pasted, the process proceeds to step S304, where it is determined whether or not Next has been selected.

[0196] On the other hand, if it is determined that a link other than the predetermined link has been pasted, the process proceeds to step S317, where it is determined whether the user is permitted to paste links other than the predetermined link. For example, the user terminal 300 determines whether the level is 80 or higher based on the "level" and "cumulative points" for each user acquired from the distribution server 100 and stored in the storage unit 320.

[0197] If it is determined in step S317 that the user is permitted to paste links other than the predetermined link, the process proceeds to step S304, where it is determined whether or not Next has been selected. On the other hand, if it is not determined in step S317 that the user is permitted to paste links other than the predetermined link, a notice is issued in step S318 that posting is not permitted, and the process returns to step S316. For example, if the user is at level 10, since pasting links other than the predetermined link is not permitted, a notice is issued that links other than the predetermined link cannot be pasted, as illustrated in FIG. 20.

[0198] Returning to FIG. 19, the "report count" is a permission that can influence whether or not a particular piece of content is hidden from all users. In this embodiment, content that has accumulated a predetermined number of users who are level 70 or higher and have been hidden or reported can be hidden from all users. For example, content that has been hidden or reported by five users who are level 70 or higher can be hidden from all users.

[0199] Additionally, content or comments posted by a user who has accumulated a certain number of users with a level of 70 or higher who have been hidden or reported, which are subject to the "report count," can be hidden from all users. For example, content or comments posted by a user who has been hidden or reported by five users with a level of 70 or higher can be hidden from all users.

[0200] Note that the users who are not visible may not include the users who posted the comments or content. This allows the user to know (become aware) that the content or comments posted by the user have been restricted, even though the content or comments posted by the user are reflected on the user's own device, for example, due to the lack of action from other users.

[0201] The "benefits" are associated with different benefits depending on the level. For example, when there is a giveaway, more valuable items for fans, such as rarer items, may be awarded depending on the level. For example, if the benefits are stamps that can be used to post comments or items that can be used at a talent's live performance, the cost of purchasing stamps or items will be higher for benefit D, which is awarded to users at levels 60 to 69, than for benefit E, which is awarded to users at levels 50 to 59. As the level increases, the value of the benefit awarded will also increase.

[0202] (Example of fluctuations in evaluation values) Next, an example of a change in the number of accumulated points (evaluation value) will be described with reference to FIG. 22. FIG. 22 is a table for explaining an example of an external evaluation that changes a user's "accumulated points" and an example of the relationship between the external evaluation and the change number. When a user (including an administrator) takes some action on content (posted article), comments, etc., the account management unit 133 changes or updates the user's accumulated points depending on whether the action is an external evaluation stored as action information 123. If the level changes in response to a change in the accumulated points, the account management unit 133 performs a process of granting or restricting the user the action authority stored as action authority information 124.

[0203] External evaluation is evaluation from other users other than the user himself / herself. For example, if a user posts content or comment and receives "likes" from other users, 5 points are added for each "like" (1 tap action).

[0204] Alternatively, points may be awarded as a result of a high evaluation from the management, such as when the management has a favorable impression that the user is highly trustworthy based on the content posted by the user or the content of the comments, etc. The number of points awarded by the management may be a predetermined number, or may be changed by the management as appropriate.

[0205] Points may also be awarded based on the degree to which the target of support is popularized. In other words, points are awarded based on the degree to which the promotion of content (such as videos or merchandise) related to the target of support contributes to the target of support. Promotional activities include, for example, spreading links to videos of the target celebrity or introducing merchandise of the target celebrity. For example, if a user posts content that includes a video link to a video related to the celebrity or a group to which the celebrity belongs, points may be awarded based on the number of video views from the posted content. Furthermore, if a link to a merchandise page related to the celebrity or a group to which the celebrity belongs is posted, points may be awarded based on the number of clicks on the merchandise page link. A merchandise page may be, for example, an official merchandise page for a celebrity supported by a fan community or a sales page for a product collaboratively planned with another company. A dedicated URL for community posting may be issued for tallying points. Alternatively, points may be awarded to the user who posted the URL when a product is purchased via the dedicated URL for community posting on the merchandise page of the official website.

[0206] On the other hand, points are deducted when a user is reported by another user or when the user is hidden. For example, by operating the screen displayed in FIG. 11(B), it is possible to deduct 5 points for each report. Alternatively, if the administrator is concerned that a user may be deteriorating the atmosphere within the community due to the content posted by the user or the content of the comments, the administrator may give the user a negative evaluation (deduct points). The number of points deducted by the administrator may be a predetermined number, or may be changed by the administrator as appropriate.

[0207] As an example of external evaluation, the text of comments made on content may be evaluated, and if the text contains positive words predetermined by the administrator or the like, points may be increased, and if the text contains negative words predetermined by the administrator or the like, points may be decreased. Text evaluation may also be performed automatically by AI. For example, the proportion of positive and negative words in the content posted by the user or in comments from other users on the content posted by the user may be automatically determined, and points may or may not be awarded depending on which element predominates. Positive and negative words are not determined by the user, but are based on external criteria (for example, criteria set by the administrator (including AI determination)).

[0208] (About the evaluation history status update process) Next, the flow of the user rating history status update process will be described with reference to Fig. 23. Fig. 23 is a diagram illustrating a flowchart of the process of updating the user rating history status that changes depending on the external ratings described with reference to Fig. 22. The rating history status update process is repeatedly executed by the account management unit 133 in the distribution server 100 when some action (for example, an action that is subject to external ratings, such as a tap action, comment, report, or hide) is performed on content, comments, etc. posted by each user in the fan community app. Note that the rating history status refers to the results of ratings given to a user by external factors other than the user himself, including the "level" and "accumulated points" in the user information database of Fig. 7, which are stored as account information.

[0209] In step S401, it is determined whether or not there has been an external evaluation. For example, it is determined whether or not there has been an external evaluation, such as that illustrated in Fig. 22, for content or comments posted by a user. If it is determined that there has not been an external evaluation, the process ends.

[0210] On the other hand, when it is determined that there is an external evaluation, it is determined in step S402 whether the external evaluation is an "increase in the number of points" evaluation. For example, if the external evaluation is a "like from another user" (a tap action from another user) as exemplified in FIG. 22, the number of points increases by 5, and therefore it is determined in step S402 that the external evaluation is an "increase in the number of points" evaluation.

[0211] If it is determined in step S402 that the external evaluation was a "point increase" evaluation, then in step S403 the number of points is added for each user according to the external evaluation, and the evaluation history status is updated and stored. For example, suppose a user is at level 59, and by adding 5 to their accumulated points due to the external evaluation, they reach the number of points required to reach level 60, and their level rises to 60. In this case, in the user information database, the level is updated to 60, and the number of accumulated points is updated to the value after the addition of 5, and stored.

[0212] Next, in step S404, it is determined whether the user has leveled up due to a change in the number of points. If it is determined in step S404 that the user has leveled up due to a change in the number of points, in step S405, the user is permitted to perform specific actions according to the new level, and the user's permitted action information stored as account information 125 is updated and stored. For example, assume that the user has reached level 60 and is no longer restricted in posting links, as illustrated in FIG. 19. In this case, information indicating that the user has no restrictions on posting links is associated and stored in the user information database stored as account information 125. Note that even if the user has leveled up, there may be cases in which no new permitted actions are granted, in which case the permitted action information is not particularly updated and the process ends.

[0213] After the permitted action information is updated and stored in step S405, information is sent to the user in step S406 to notify the user that the specific action is permitted, and the process ends. For example, the user terminal 300 may send a push notification or an in-app notification with a message stating "Your level has been increased, so there are no more restrictions on posting links," or a pop-up message may be displayed the next time you post.

[0214] Returning to step S402, if it is not determined that the external evaluation was "point increase," the process proceeds to step S407, where it is determined whether the external evaluation is "point decrease." For example, if the external evaluation is "report from another user" as illustrated in FIG. 22, the number of points will decrease by 5, and therefore in step S407 it is determined to be a "point decrease."

[0215] If it is determined in step S407 that the external evaluation was a "point reduction" evaluation, then in step S408 the number of points is reduced for each user according to the external evaluation, and the evaluation history status is updated and stored. For example, suppose a user was at level 60, but had their accumulated points reduced by 5 due to the external evaluation, and therefore their accumulated points no longer meet the number of points required for level 60, causing their level to drop to 59. In this case, the user information database updates the level to 59 and stores the accumulated points after the 5 points have been subtracted.

[0216] Next, in step S409, it is determined whether the level has been downgraded due to a change in the number of points. If it is determined in step S409 that the level has been downgraded, in step S410, specific actions that were permitted before the level downgrading are restricted according to the level after the level downgrading, and the permitted action information is updated and stored. For example, suppose that the user's level has reached 59, and posting links are now restricted, as shown in FIG. 19. In this case, information indicating that the user has posted links is associated with the user and stored in the user information database stored as account information 125. Note that there may be cases where no actions are restricted even if the level has been downgraded, in which case the permitted action information is not particularly updated and the process ends.

[0217] After the permitted action information is updated and stored in step S410, information is sent to the user in step S411 to notify the user that a specific action has been restricted, and the process ends. For example, the user terminal 300 may send a push notification or an in-app notification with a message stating "Restrictions have been placed on posting links due to a level downgrade," or a pop-up may be displayed the next time a post is made.

[0218] Returning to step S407, if it is determined that the external evaluation is not a "point reduction" evaluation, the process ends. For example, this occurs when an action that is not defined as affecting the change in the number of points occurs. Note that although an example in which the evaluation history status update process is executed by the distribution server 100 has been described, the process may be executed by the user terminal 300 and then the information may be transmitted to the distribution server 100.

[0219] <About the effects displayed by tap actions> (Example of a display screen for tap action processing) Next, referring to Figs. 24, 25, and 26, a description will be given of a visual effect when a tap action is received from a user on content, a comment, or the like. In this embodiment, the number of tap actions is incremented by an operation (e.g., a click operation or a tap operation from the user terminal 300) on the icon 708 displayed in the content described with reference to Figs. 10, 11, and 13, or the tap action number 78 (78b) displayed in the heading of the content. Furthermore, when the number of tap actions is incremented, a visual effect can be displayed on the user terminal 300. For example, each time an operation is performed on the icon 708, a visual effect is displayed in which a predetermined mark pops out from the icon 708.

[0220] Fig. 24 shows an example of a presentation display (reception presentation) when a tap action is received from a user. Fig. 24(A) shows an example of a screen for each channel of each community as exemplified in Fig. 11(A) and shows an example of an operation performed on icon 708 with tap action count 78 displayed in the top-ranked content heading 70. In this case, since the number of tap operations has reached 50, "50" is displayed in the individual tap action count 48. This allows the user to recognize the number of tap actions they have performed.

[0221] FIG. 24(A) illustrates three consecutive taps (continuous taps). The first tap (48th tap) produces an effect in which a thumbs-up mark 41a pops out from the icon 708, which has a tap action count of 78. The second tap (49th tap) produces an effect in which a thumbs-up mark 41b pops out from the icon 708. The third tap (50th tap) produces an effect in which a fan mark 42 pops out from the icon 708. The fan mark 42 is a fan mark of a related talent associated with the content in which the icon 708 was operated. Thus, if the duration of the effect of the mark that popped out from the previous tap (from the moment it popped out until it disappeared) overlaps with the duration of the effect of the mark that popped out from the next tap, multiple marks are displayed. Thus, the effect of marks popping out one after another due to the continuous tapping produces an effect in which the marks pop out one after another, providing the user with a refreshing feeling for the tap action (operability) and encouraging further tapping actions. The effect of the marks popping out may be such that multiple marks are not displayed at the same time as shown in FIG. 24(A) but only one mark is displayed at a time.

[0222] FIG. 24(B) shows a special effect (special reception effect) that is displayed when a predetermined number of tap actions are performed by the user. For example, when the number of operations on icon 708 reaches 100, an effect is displayed in which various marks rain down across the entire screen. Note that the predetermined number may be the upper limit that the user can perform tap actions on each action target. In other words, once the predetermined number is reached, no effects are generated by operations on icon 708, and no update of the number of individual tap actions 48 is performed. Alternatively, the effect may be performed every time the predetermined number is reached (for example, every 10 times). Also, it is not necessary to set an upper limit.

[0223] Note that the predetermined number of times is not limited to the number of individual tap actions 48, which is the number of individual tap actions a user has performed on the content, but instead, or in addition, each time the number displayed in the number of tap actions 78, which is the total number of tap actions performed by all users in the fan community, reaches a predetermined value (for example, 100 times), a performance may be given to the user who performed the 100th action.

[0224] Next, examples of types of effects executed by accepting a tap action will be described with reference to Fig. 25. Fig. 25 is an example of a content-specific effect data table of effect displays by tap actions stored in storage unit 320 of user terminal 300 based on content data 122 stored in distribution server 100 or content data 122 acquired from distribution server 100. Information related to effect displays is associated with each content (posted article).

[0225] In the content-specific effect data table, an effect type is defined for each article ID. Also, each effect type is associated with a lottery probability used for the effect. The effect type is defined according to whether the number of tap actions is less than a predetermined number or when the predetermined number of times is reached. If the predetermined number of times is 100, the upper limit of the number of tap actions possible, then 1 to 99 is less than the predetermined number of times.

[0226] For effects that are less than the predetermined number of times, default effects are provided, and if a related talent is set for the content, fan mark effects are provided. Default effects include, for example, applause, thumbs up, hearts, and rare marks. Fan marks are associated with the related talents. For example, as shown in FIG. 14, for article ID "a1," talent IDs "t1," "t2," "t6," and "t14" are associated with the related talents. Therefore, fan marks "mark_t1," "mark_t2," "mark_t6," and "mark_t14" are associated with each related talent. The lottery probability for each mark to be used in the effect may be uniformly set, or the appearance probability of fan marks or rare marks may be set to a lower probability. In this way, if a related talent is associated with the content, a fan mark appears when a tap action is performed. This encourages users to perform tap actions and, further, encourages users to select a related talent before posting content. As a result, it becomes easier for other users to obtain information about the favorite talent, and the fan community can be activated through user actions.

[0227] The effects that are displayed when the predetermined number is reached include a luxurious effect and, if a related talent is set for the content, a talent effect. As with the fan marks when the predetermined number is not reached, the talent effects are "special_t1," "special_t2," "special_t6," and "special_t14," which correspond to each of the related talents associated with the article ID "a1." For example, an animation that evokes the talent, such as a fan mark popping out, is displayed.

[0228] Also, when no related talent is set for the content, as exemplified by article ID "a99" in Figure 25, the type of performance is not set to fan mark or talent performance, and if the number is less than the specified number, a default performance is performed, and when the specified number is reached, a luxurious performance is performed.

[0229] For each effect, for example, multiple effect patterns may be defined for the luxurious effect, or there may be one default effect when the number is less than the predetermined number. Also, only one of the fan mark effect when the number is less than the predetermined number or the talent effect when the predetermined number is reached may be defined. For example, even if a related talent is selected for the content, only the luxurious effect may be used when the predetermined number is reached.

[0230] (Example of tap action processing flow) An example of the flow of the tap action rendering process will be described with reference to Fig. 26. Fig. 26 is a diagram illustrating a flowchart of the tap action rendering process described with reference to Fig. 24, Fig. 25, etc. The tap action rendering process is repeatedly executed by the control unit 350 of the user terminal 300 in response to an operation from the user, based on the content information acquired by the distribution server 100.

[0231] In step S501, it is determined whether or not a tap action operation has been performed. For example, a tap operation by the user may be performed on an icon 708 displayed in content or a comment on the home screen of Fig. 10, the community screen of Fig. 11(A), or the content screen of Fig. 13. If it is not determined in step S501 that a tap action operation has been performed, the process ends.

[0232] On the other hand, if it is determined in step S501 that a tap action operation has been performed, it is determined in step S502 whether the total number of tap actions by the user on the content, etc. is less than a predetermined number. For example, assume that the predetermined number is 100, which is the upper limit of the number of tap actions that a user can perform on each action target. In this case, if the total number of tap actions stored in storage unit 320 (or stored as action information 123 in distribution server 100) is 100, it is not determined in step S502 that the total number of tap actions is less than the predetermined number, and the process ends.

[0233] In step S501, for example, if the total number of tap actions is 50, it is determined that the total number of actions is less than a predetermined number, and in step S503, a tap action counter (a counter for determining the total number of tap actions) stored in storage unit 320 is incremented by 1. After the tap action counter is incremented in step S503, it is determined in step S504 whether the total number of tap actions after the increment is a predetermined number. For example, if the total number of tap actions is 50, adding 1 in step S503 makes the total number of tap actions 51, and in step S504 it is determined that the total number is not the predetermined number of 100.

[0234] If it is determined in step S504 that the total number of tap actions is not equal to the predetermined number, it is determined in step S505 whether or not a related celebrity is associated with the content on which the tap action was performed. For example, if the content on which the tap action was performed is article "a1" in Figure 14, it is determined that there is a related celebrity.

[0235] If it is determined in step S505 that there is a related talent, then in step S506, tap actions less than a predetermined number are determined by lottery based on the content-specific effect table of Figure 25. After the effect is determined in step S506, the effect of the determined tap action is executed in step S507, and tap action count update information is sent to distribution server 100, ending the process. For example, if the effect type fan mark "mark_t1" for article ID "a1" in Figure 25 is determined by lottery, the number of tap actions is updated to 78 and the number of individual tap actions is updated to 48, and an effect is executed in which a fan mark corresponding to "mark_t1" pops up.

[0236] Returning to step S505, if it is determined that the content on which the tap action was performed is not associated with a related talent, the process proceeds to step S508, where a tap action less than the predetermined default number is determined by lottery. In step S509, the default tap action determined in step S508 is rendered, and tap action count update information is sent to distribution server 100, and the process ends. For example, in the case of article ID "a99" in FIG. 25, since the content is not associated with a related talent, a default effect is determined by lottery. For example, if a "thumbs up" is determined by lottery, the number of tap actions (78) and the number of individual tap actions (48) are updated, and an effect in which a mark corresponding to the "thumbs up" pops up is executed.

[0237] Returning to step S504, if it is determined that the total number of tap actions has reached the predetermined number, the process proceeds to step S510. For example, this occurs when the number of individual tap actions reaches 100 as a result of the tap action counter being incremented in step S503.

[0238] In step S510, it is determined whether the content on which the tap action was performed has a related celebrity associated with it. For example, if the content on which the tap action was performed is article "a1" in Figure 14, it is determined that there is a related celebrity.

[0239] If it is determined in step S510 that there is a related talent, then in step S511, a tap action effect to be used when the predetermined number is reached is determined by lottery. In step S512, the tap action effect to be used when the predetermined number is reached determined in step S511 is executed, and tap action count update information is sent to distribution server 100, ending the process. For example, if "special_t1" of the talent effect type for article ID "a1" in FIG. 25 is determined by lottery, the number of tap actions (78) and the number of individual tap actions (48) are updated, and the effect corresponding to "special_t1" is executed.

[0240] Returning to step S508, if it is determined that the content on which the tap action operation was performed is not associated with a related talent, in step S513, a tap action effect for when a predetermined number of tap actions is reached is executed, and the tap action count update information is sent to distribution server 100, and the process ends. For example, in the case of article ID "a99" in FIG. 25, since the content is not associated with a related talent, the number of tap actions is updated to 78 and the number of individual tap actions is updated to 48, and an effect corresponding to "luxurious effect" is executed.

[0241] In steps S507, S509, S512, and S513, tap action update information (for example, information specifying that a tap action has been performed) is transmitted to distribution server 100, whereby the total number of tap actions for each content or comment stored as content data 122 is updated and reflected in the number of tap actions 78 (78b) of other users' user terminals 300. In addition, although an example in which the tap action rendering process is executed on user terminal 300 has been described, it may also be executed on distribution server 100 and display information may be transmitted to user terminal 300.

[0242] In the above example, when a related talent is associated with the content, the fan mark corresponding to each related talent or the talent performance is executed by lottery. However, when a favorite talent selected in advance by the user is associated with the related talent, the probability of drawing the lottery (probability of winning) for the fan mark corresponding to the favorite talent may be higher than that of other fan marks.

[0243] <Using APIs provided by external services> Next, with reference to FIG. 27 , an example will be described in which content provided by an external web service system 400 is made available to users by utilizing an API provided by the external web service system 400. The external web service system 400 is, for example, a video distribution site. It is assumed that a talent who is a support target of a fan community in this embodiment is distributing videos on the video distribution site. In this embodiment, it is made possible for users to easily check the distribution schedule of the talent's videos on the video distribution site.

[0244] In this embodiment, by utilizing an API provided by the external web service system 400, information on the video distributor and the person who is co-distributing with the distributor (also called collaboration) is acquired, and information associated with the talent ID of the corresponding talent is generated and can be displayed on the user terminal 300. As the talent ID is associated with the information displayed to the user, it is possible to extract and identify broadcasts of the participating community (first attribute) and favorite talent (second attribute) that the user has selected in advance.

[0245] 27(A) and (B) are examples of distribution schedule screens displayed on the user terminal 300. For example, the distribution schedule screen may be displayed by displaying a distribution schedule icon 18 at the bottom of the application screen and performing a selection operation on the distribution schedule icon 18. Alternatively, the distribution schedule screen may be selectable on the channel list screen exemplified in FIG. 12, or may be displayed in the channel list display 82 for each community.

[0246] Figure 27(C) is an example screen of video content provided by external web service 400, and by performing a specified operation from the screen of Figure 27(A) or Figure 27(B), it is possible to transition to the video content screen.

[0247] The distribution schedule screens of FIGS. 27(A) and 27(B) display a recommended filter 20, a distribution period selection area 91, a group selection area 92, a distribution date and time 93, a content heading 90, a channel account 98, and a featured related talent 94. For example, a user may select a content heading 90 to transition to a distribution page of an external web service shown in FIG. 27(C). The transition destination is the video distribution channel of the account displayed in the channel account 98. The featured related talent 94 displays an icon of the talent appearing in the corresponding distribution. For example, the content heading 90a in FIG. 27(A) indicates that there will be a distribution by the account of the official channel of group A, and the content heading 90b indicates that there will be a distribution by the channel of talent BBB.

[0248] The distribution period selection area 91 displays icons such as "Recent Distribution," which displays a list of content headings 90 (content information) that identify recent past distributions (contents), "Current Distribution," which displays a list of content headings 90 that identify distributions (contents) currently being distributed, and "Upcoming Schedule," which identifies distributions (contents) scheduled for the future. The user can switch the list of displayed content headings 90 by selecting each icon. Fig. 27(A) is an example of a distribution schedule screen when the "Current Distribution" icon is selected, displaying a list of content headings 90 that identify distributions currently being distributed. Fig. 27(B) is an example of a distribution schedule screen when the "Upcoming Schedule" icon is selected, displaying a list of content headings 90 that identify distributions scheduled for the future.

[0249] The group selection area 92 displays icons for selecting the group 1 to which the talent shown in FIG. 5 belongs. Only groups corresponding to communities in which the user participates are displayed in the group selection area 92. For example, FIGS. 27(A) and 27(B) show screens displayed on the user terminal 300 of user "u2" in FIG. 7, and in FIGS. 27(A) and 27(B) icons for "Group A" and "Group B" corresponding to communities A and B in which user "u2" participates are displayed. By operating each icon, content headings 90 for broadcasts related to talents belonging to either group (or both groups may be selectable) are displayed. In FIGS. 27(A) and 27(B), the "Group A" icon is selected, and therefore content headings 90 for identifying broadcasts in which talents belonging to Group A appear are extracted and displayed. The user can identify whether a broadcast features a talent belonging to group A or not because the content heading 90 is associated with the performing talent 94 (talent ID in FIG. 5) by the distribution server 100. Note that, in this example, only groups corresponding to the communities in which the user participates are displayed in the group selection area 92, but this is not limiting and all groups may be displayed regardless of the community in which the user participates.

[0250] Also, as described above with reference to Figure 9, by selecting the favorite filter 20 on the distribution schedule screen, distributions in which the favorite talent selected by the user in advance appear can be extracted and displayed.

[0251] The talents displayed in the appearing related talent 94 in Figures 27(A) and 27(B) are displayed based on information obtained using the video distribution site's API. For example, the distribution screen in Figure 27(C) (including posts during, after, and before distribution) has a description field 95, allowing the broadcast poster to edit the text in the description field 95 as appropriate. By embedding attribute-specific information 96 in the description field 95, the distribution server 100 obtains the attribute-specific information 96 and generates the content heading 90. The attribute-specific information 96 is, for example, a channel account on the video distribution site. Since Figure 27(C) shows a broadcast by a channel account corresponding to the talent "CCC," the distribution server 100 can obtain attribute-specific information 96a, which is the channel account. The appearing related talent 94 may display the talent's name in addition to the talent's icon. The appearing related talent 94 may also be displayed as the associated talent 88 described with reference to Figure 13, etc.

[0252] Additionally, attribute identification information 96b (also referred to as a handle), which is information (identifier) ​​that identifies the channel account corresponding to the talent "AAA," is entered in the description field 95. The handle also serves as a URL that leads to the corresponding channel account. For example, when a joint broadcast is conducted with a talent different from the talent corresponding to the channel account that is broadcasting, a handle that identifies the joint broadcast partner is entered. This input action is also referred to as mentioning another channel by entering text information with an @ sign before the other channel. For example, when a broadcast by the channel of talent "CCC" is a so-called collaborative broadcast with talent "AAA," a handle that identifies the channel account of talent "AAA" is embedded in the description field 95 of the broadcast. By entering a handle, which is attribute identification information 96b, in the description field 95, the server 100 can obtain attribute identification information 96b, which is information about the collaboration partner, in addition to the broadcasting account itself.

[0253] By acquiring the attribute identification information 96, the distribution server 100 generates a content heading 90 that associates the talent ID of the talent corresponding to the channel account (attribute identification information 96a) performing the distribution with the talent ID of the talent corresponding to the co-distribution partner entered in the handle (attribute identification information 96b). For example, assume that the information acquired from the external web service 400 includes attribute identification information 96 corresponding to the talents "CCC" and "AAA." In this case, the content management unit 132 generates and stores information for identifying the content heading 90 associated with the talent IDs "t3" and "t1" of the talents "CCC" and "AAA" in a database that manages the content headings 90 that can be displayed on the distribution schedule screen stored as content data 122, thereby generating the content heading 90. The distribution server 100 also acquires text information (e.g., "Broadcasting with AAA as a Friendly Partner") and thumbnail image information 99 of the title 97 of the distribution screen shown in FIG. 27(C) and displays the text information and thumbnail image in the content heading 90. This makes it possible to identify which talent from the talent information database stored as attribute information 121 illustrated in Figure 5 will be appearing in the broadcast, allowing the user to identify the broadcast associated with attributes previously selected by the user.

[0254] For example, the following description will be given assuming that FIG. 27(B) is the screen of user "u1" in FIG. 7. Note that, assuming FIG. 27(B) is the screen of user "u1," even though user "u1" is not a member of community B, an icon for community B may be displayed in the group selection area 92 as shown in FIG. 27(B), and the distribution schedule screen for group B may be displayed by selection, or only the icons of the participating communities may be displayed (the icon for community B may not be displayed). User "u1" has selected as his or her favorite talents the talents "AAA," "BBB," and "EEE" corresponding to talent IDs "t1," "t2," and "t5," but has not selected talent "CCC" as his or her favorite talent. However, even if a co-distribution with a favorite talent is made through a distribution via the channel account of "CCC," who is not a favorite talent, information about the co-distribution partner may also be obtained using the attribute identification information 96b. Therefore, even if the favorite filter 20 is on, the content heading 90 for identifying the distribution of the talent "CCC" is displayed, and the appearing talent 94 is displayed, so the user will not miss information about the favorite talent.

[0255] Furthermore, even if a user suddenly decides to start a joint broadcast midway through a broadcast and edits the broadcast screen on the external web service 400 to add new attribute identification information 96b (handle) to the summary field 95, the attribute identification information 96b is extracted as needed. Therefore, even if a joint broadcast suddenly begins, the content heading 90 for that broadcast is displayed in the broadcast schedule for the current broadcast in FIG. 27(A). Furthermore, if the content heading 90 is associated with a favorite talent selected by the user in advance, a push notification can be sent, so the user will not miss any sudden broadcasts by their favorite talent.

[0256] 27 is automatically generated using the API of the external web service 400, the present invention is not limited to this and may be manually set from the administrator terminal 200. For example, the content heading 90 may be generated by associating a transition link and a related talent with the content heading 90. Even if an API cannot be used, it is possible to guide the user to a link outside the fan community app related to the talent.

[0257] Furthermore, the content heading 90 generated when the channel account in the external web service is the official channel of the group corresponding to the belonging group 1 in Figure 5 may not be associated with any talent (no associated talent). Even in this case, the content heading 90 is not associated with an individual talent, but is associated with the participating community and group of the group corresponding to the channel account. Therefore, if you participate in the community corresponding to the group, the content heading 90 will be displayed on the distribution schedule screen, and will also be displayed as a content heading 90 extracted for each group by operating the icon for each group in the group selection area 92.

[0258] <Regarding secondary use permission processing> (Outline of the process related to permission for secondary use) 28 to 32, the secondary use permission related processing in this embodiment will be described. In fan activities (so-called "oshi-katsu") in which a fan supports a favorite target (so-called "oshi"), such as a celebrity or other person or thing, there are cases where a fan user posts, for example, their impressions of the fan activities or derivative works such as fan art related to the target on SNS. The celebrity or other target of support may introduce such posted content from the fan user on their own video distribution or SNS.

[0259] Furthermore, having content posted by fan users introduced to celebrities and the like leads to more active communication between fans and celebrities and the like. Therefore, to enable celebrities and the like to smoothly use content posted by fan users for distribution, for example, one method is to include in the terms of use a statement that the posted content is deemed to be consented to by the operator. However, doing so may lead to misunderstandings among users. Therefore, in this embodiment, the user is allowed to optionally permit or prohibit the secondary use (also referred to as citation) of content (user actions) such as threads and comments posted by the user, thereby facilitating the secondary use of user-posted content (including, for example, thread posts made through the posting operations described with reference to FIGS. 17 and 18 , comments on posted content, etc.).

[0260] This makes it easier for the talent you support to feature fan art and supportive comments posted to the fan community in this embodiment in their video distribution, thereby stimulating communication. Also, since real posts from the fan community can be introduced, it also has a promotional effect on the fan community.

[0261] Furthermore, since the permission status of secondary use of content in this embodiment can be set by user operation, for example, when an administrator or a talent plans an individual project, it is possible to save the trouble of stating in the post (content) for each project that the administrator or talent may use the posted comments and images in other media. Individual projects include, for example, various projects that solicit posts (comments, images, video posts, etc.) from users, such as soliciting supportive comments for a talent, Ogiri projects, and survey projects.

[0262] Secondary use is not limited to introductions by talents or operators through video streaming or social media, but also includes, for example, posting user-submitted content on the official website of the site the user supports, or further secondary use (reposting, republishing, reintroducing, etc.) of content that has been used secondary (submitted content that uses a user's post that constitutes secondary use). Any citation or introduction made by operators or talents is also included in secondary use.

[0263] Furthermore, content such as threads and comments (user actions) may include not only text posts, but also posts of images, videos, digital art, etc. Also, posts such as uploads of various files, such as 2D model data, 3D model data, and 3D materials, may be included. Furthermore, posts may be a combination of these (for example, posting an image along with text), or may be only one of the two (for example, posting only an image or only a video).

[0264] (Example of secondary use permission screen) Referring to FIG. 28, an example of a display screen of the user terminal 300 relating to secondary use permission-related processing displayed in the fan community app of this embodiment will be described. FIG. 28(A) is an example of a display screen of the secondary use permission button 501 displayed on a user setting screen such as the My Page screen of FIG. 8. The secondary use permission button 501 is displayed with a message such as "Allow publication in broadcasts and projects by the management and affiliated talents" and a message such as "By turning this button ON, you are authorizing the management and affiliated talents to use your post. You can change it to OFF at any time." By operating the secondary use permission button 501, a user can select whether or not to allow the management, talents, etc. to use the content posted by the user for secondary use in broadcasts, projects, etc. The secondary use permission button 501 illustrated in FIG. 28(A) is an example of a display mode in the ON state. The secondary use permission button 501 can be turned OFF by a user operation such as a tap on the secondary use permission button 501. The default setting can be either on or off, but by leaving it off by default, it will not be turned on unless the user operates it, making it less likely for the user to misunderstand.

[0265] FIG. 28(B) is a diagram illustrating a content display screen when secondary use of posted content is permitted. A secondary use OK icon 701 is displayed for posted content posted by a user who has permitted secondary use by turning on the secondary use permission button 501. FIG. 28(B) is another example of the content screen illustrated in FIG. 13, in which the content poster is a general user, "userA." Furthermore, comments have been made by "userJ" and "userL" on the content posted by "userA" in FIG. 28(B). In FIG. 28(B), "userA" and "userJ" have turned on the secondary use permission button 501, and therefore the secondary use OK icon 701 is displayed next to their usernames. On the other hand, "userL" has turned off the secondary use permission button 501, and therefore the secondary use OK icon 701 is not displayed next to their usernames.

[0266] The secondary use OK icon 701 may be displayed on the screen of the user terminal 300 of all users. However, in this case, there is a risk of unauthorized use or misuse by users who have little need for secondary use. For this reason, it is preferable that the secondary use OK icon 701 be displayed only on the screen of the user terminal 300 of users who meet certain conditions. The specific conditions include the account of a special user such as a celebrity (e.g., “t1,” “t2,” “t3,” etc. in FIG. 5) as exemplified in FIG. 5, or the account of an administrator (e.g., “ou1,” “ou2,” etc. in FIG. 14), and the account corresponds to a user who has been permitted by a user to make secondary use via the secondary use permission / denial button 501. This makes it easy for celebrities, administrators, etc. to recognize content (e.g., threads, posted comments, etc.) that may be used secondary. Furthermore, the secondary use OK icon 701 is not displayed on the screen of the user terminal 300 of users who do not meet the certain conditions, such as celebrities or administrators, thereby preventing accidental secondary use by general users.

[0267] Note that the secondary use OK icon 701 is not limited to being displayed on the content screen of FIG. 13 or FIG. 28(B), but may also be displayed, for example, on the home screen of FIG. 10 or the channel screen of FIG. 11.

[0268] (Example of a database related to secondary use permission processing) An example of a database stored in the storage unit 120 of the distribution server 100 related to the secondary use permission related processing in this embodiment will be described with reference to Fig. 29. Fig. 29(A) is an example of a portion of the user information database stored as the account information 125 described with reference to Fig. 7. In the user information database of Fig. 29(A), secondary use permission information is associated with the user ID of each user. When the secondary use permission button 501 in Fig. 28(A) described above is operated, if the secondary use permission button 501 is in the on state, "permitted" is associated with the secondary use permission information, and if it is in the off state, "not permitted" is associated with the secondary use permission information.

[0269] 29(B) is an example of a content database, which is stored as content data 122 and action information 123 in storage unit 120 of distribution server 100 together with the content database exemplified in FIG. 14. The "article ID" for each piece of content posted to each channel exemplified in FIG. 14 is associated with a "poster ID," "posting date and time," "posting content information," "secondary use permission information," "reaction-related information," and the like. The "posting content information" includes, for example, information such as the title and text of the content displayed in content 74b of the content screen in FIG. 13 or FIG. 28(B), and information identifying the image or video displayed in image 75, etc.

[0270] "Secondary use permission information" is information regarding the permission status of secondary use for each article ID, and is associated based on the secondary use permission information in the user information database of Figure 29(A). Since the secondary use permission information for user ID "u1" is "permitted" in the user information database of Figure 29(A), "permitted" is associated with article ID "a3", which is a post by "u1" in the content database of Figure 29(B). On the other hand, since "u2" is "not permitted" in the user information database of Figure 29(A), "not permitted" is associated with article ID "a10" in Figure 29(B).

[0271] "Reaction-related information" is associated with "tap action information" and "comment information." "Tap action information" is associated with the total number of tap actions on icon 708 for each article ID, the user ID of the user who performed the tap action, the number of taps per user, etc. This total number is displayed on the content screen as tap action 78. "Comment information" is associated with the total number of reply comments for each article ID and the comment ID for each comment, etc. This total number is displayed as comment number 77, etc. The associated comments are comments posted from the comment posting field 84 in Figure 13, etc.

[0272] FIG. 29(C) is an example of a comment database for each comment ID associated with the "comment information" exemplified in FIG. 29(B). This comment database, along with the content databases of FIGS. 14 and 29(B), is stored as content data 122 and action information 123 in the storage unit 120 of the distribution server 100. In the comment database, for each comment ID, the "user ID" of the user who posted the comment, the "posting date and time" of the comment, "comment content," "secondary use permission information," and "reaction-related information" are associated. The "comment content" includes information identifying the text, image, video, and other information posted as a comment. Similar to the "secondary use permission information" in FIG. 29(B), the "secondary use permission information" is associated with either "permitted" or "not permitted" based on the status of the "secondary use permission information" in the user information database of the user who posted the comment. Similar to the "reaction-related information" in FIG. 29(B), the "reaction-related information" in the comment database is associated with information related to tap actions and comments made on each comment.

[0273] FIG. 28(B) is an example of a content screen for article ID "a3" in FIG. 29(B). For example, the poster, user ID "u1" (user1), is a user whose secondary use permission information is "permitted," so a secondary use OK icon 701 is displayed next to the user name. Also, the comment by "userJ" in FIG. 28(B) has comment ID "cm6" associated with article ID "a3," and was posted by user ID "u10" whose secondary use permission information is "permitted," so the secondary use OK icon 701 is displayed next to the user name. On the other hand, the comment by "userL" in FIG. 28(B) has comment ID "cm7" associated with article ID "a3," and was posted by user ID "u12" whose secondary use permission information is "not permitted," so the secondary use OK icon 701 is not displayed next to the user name.

[0274] (Example of the flow of secondary use permission related processing 1) Next, an example of the flow of the secondary use permission-related process 1 will be described with reference to FIG. 30. FIG. 30 is a diagram illustrating a flowchart of the secondary use permission-related process described with reference to FIGS. 28 and 29. The secondary use permission-related process 1 may be repeatedly executed at predetermined time intervals by the distribution server 100, or may be executed when the secondary use permission button 501 is operated on the user terminal 300, when posted information is sent from the user terminal 300, or when a display request for a fan community app screen is made from the user terminal 300. The secondary use permission-related process 1 in FIG. 30 illustrates a case in which "secondary use permission information" is associated with each thread or comment, as illustrated in FIGS. 29(B) and (C). The "secondary use permission information" for each thread or comment is associated with a permission status based on the status of the "secondary use permission information" in the user information database of FIG. 29(A) at the time of posting.

[0275] In step S601, it is determined whether or not secondary use permission information has been received from user terminal 300. If it is determined that secondary use permission information has been received, in step S602, the secondary use permission information of the corresponding user is updated, and the process proceeds to step S603. For example, when secondary use permission button 501 in FIG. 28(A) is turned on or off in user terminal 300, secondary use permission information is transmitted from user terminal 300 to distribution server 100. Based on the received information, account management unit 133 of distribution server 100 updates and stores the secondary use permission information in the user information database in FIG. 29(A) so that it is "permitted" if on-state information has been received, and "not permitted" if off-state information has been received.

[0276] On the other hand, if it is determined in step S601 that secondary use permission information has not been received, then in step S603 it is determined whether posted information has been received. The posted information is information that is transmitted to distribution server 100 when a thread described with reference to Figures 17 and 18 is posted or a comment is posted from comment posting field 84 in Figure 13, etc., at user terminal 300, and is information that identifies the content of the posted thread or comment.

[0277] If it is determined in step S603 that posted information has been received, then in step S604, the post-related information is updated by associating it with the secondary use permission-related information of the corresponding user. The post-related information is content data 122 stored in the storage unit 120 of the distribution server 100, and includes the content database and comment database exemplified in FIG. 14 and FIGS. 29(B) and (C). For example, when a thread is posted from user ID "u1" whose secondary use permission information is set to "permitted" in the user information database of FIG. 29(A), the content management unit 132 updates and stores the content database by associating the secondary use permission information of "permitted" with the article ID "a3" of the content (thread) posted by "u1," as exemplified in FIG. 29(B). On the other hand, when a thread is posted from user ID "u2" whose secondary use permission information is set to "not permitted," the content database is updated and stored by associating the secondary use permission information of "not permitted" with the article ID "a10" of the content (thread) posted by "u2," and proceeding to step S605.

[0278] The same process is performed even when a comment is posted. For example, if a comment is posted from user ID "u10" whose secondary use permission information is "permitted" in the user information database, the secondary use permission information of "permitted" will be associated with comment ID "cm6." On the other hand, if a comment is posted from user ID "u12" whose secondary use permission information is "not permitted" in the user information database, the secondary use permission information of "not permitted" will be associated with comment ID "cm7."

[0279] On the other hand, if it is determined in step S603 that posted information has not been received, then in step S605 it is determined whether display request information has been received. A display request is information transmitted from user terminal 300 to distribution server 100 when, for example, an operation is performed in user terminal 300 to load display data. Examples of such a request include logging in to an app on user terminal 300 (querying the server when the app is opened), a reload operation (reloading operation), or a selection operation of the home icon 13, community icon 14, or a channel displayed in channel list 82 in FIG. 12 on the app screen, or a content heading (60, 70) displayed in FIGS. 10, 11, etc. If it is determined in step S605 that display request information has not been received, then processing ends.

[0280] On the other hand, if it is determined in step S605 that display request information has been received, it is determined in step S606 whether the requesting user is a user who satisfies specific conditions. For example, if the requesting user is a special user account such as a celebrity in FIG. 5, for whom the user has permitted secondary use of the content using the secondary use permission button 501, the requesting user is determined to be a user who satisfies the specific conditions. If it is determined in step S606 that the requesting user is a user who satisfies the specific conditions, in step S607, the post-related information is transmitted to the requesting user terminal 300 together with information (suggestion information) that enables the secondary use permission status of each piece of posted information to be identified, and the process ends. For example, suppose that the distribution server 100 receives display request information for displaying a content screen corresponding to the article ID "a3" in FIG. 29(B) by selecting a content heading from the home screen of FIG. 10 displayed on the celebrity's user terminal 300. In this case, information that identifies the secondary use permission status (permitted or not permitted) of the article ID "a3" and the comments "cm6" and "cm7" as well as post-related information that displays a content screen corresponding to the article ID "a3" are transmitted to the requesting user terminal 300. As a result, on the user terminal 300 of a celebrity or the like, a secondary use OK icon 701 will be displayed for posts by users who have permitted secondary use, as shown in Fig. 28(B) as an example.

[0281] On the other hand, if it is not determined in step S606 that the requesting user is a user who satisfies the specific conditions, the posting-related information, such as the content screen requested for display, is transmitted in step S608, and the process ends. For example, even if a general user who does not satisfy the specific conditions requests the display of the content screen of article ID "a3," the secondary use OK icon 701 is not displayed on the user terminal 300 of the general user. This prevents the general user from being unnecessarily encouraged to make secondary use.

[0282] Furthermore, in secondary use-related processing 1, when the user changes the secondary use permission information by operating the secondary use permission button 501, the secondary use permission information associated with the post made before the change will differ from the secondary use permission information associated with the post made after the change. For example, if user ID "u1" who had set "permission" to "allowed" operates the secondary use permission button 501 to the off state, the secondary use permission information associated with "u1" in the user information database in step S602 is updated to "not permitted," and posts made after that will be associated with secondary use permission information of "not permitted" in step S604. This allows the user to set the secondary use permission status for each post, increasing convenience by allowing permission depending on the content of the post.

[0283] Furthermore, secondary use permission information associated with each piece of content such as a thread or a comment may be set to be non-changeable after the fact. This prevents the content from being used in a secondary manner, for example, if a talent or other person takes a screenshot of the content to introduce it in a later video stream, but secondary use is not permitted when the video is actually streamed.

[0284] (Example of the flow of secondary use permission related process 2) Next, an example of the flow of secondary use permission related processing 2 will be described with reference to FIG. 31. FIG. 31 is a diagram illustrating a flowchart of another processing mode of the secondary use permission related processing described with reference to FIGS. 28 and 29. In the secondary use permission related processing 1 described with reference to FIG. 30, an example was described in which secondary use permission information is associated with each piece of posted information (each thread, each comment) according to the user's secondary use permission information at the time of posting. In contrast, in secondary use permission related processing 2, secondary use permission information is collectively managed in the user information database of FIG. 29(A), and the secondary use OK icon 701 illustrated in FIG. 28(B) and the like is displayed on the user terminal 300 based on the user's current secondary use permission information. In other words, when a user updates the user's secondary use permission information by operating the secondary use permission button 501 illustrated in FIG. 28(A), the display / hide of the secondary use OK icon 701 is updated not only for the updated post but also for threads and comments that the user has already posted. 31, processes that differ from those in Fig. 30 are surrounded by dotted lines, and explanations of processes that are the same as those in Fig. 30 will be omitted. Secondary use permission related process 2 is executed in distribution server 100.

[0285] If it is determined in step S603 that posted information has been received, the content management unit 132 updates the posted related information in step S604B, but unlike step S604 in FIG. 30, the posted related information is not associated with secondary use permission information.

[0286] Furthermore, if it is determined in step S605 that display request information has been received and it is determined in step S606 that the requesting user is a user who satisfies specific conditions, in step S607B, the post-related information is transmitted to the requesting user terminal 300 together with information (suggestion information) that enables the current secondary use permission status of each posting user to be identified, and the processing ends. For example, when display request information for displaying content information of article ID "a3" in FIG. 29(B) is received from the user terminal 300 of a special user such as a celebrity, information for displaying the content image of article ID "a3" is transmitted to the user terminal 300 of the special user together with information that enables the secondary use permission status (permitted or not permitted) to be identified based on the secondary use permission information stored in the current user information database for user ID "u1" who posted article ID "a3" and comment IDs "u10" and "u12" of "cm6" and "cm7". As a result, for example, if the secondary use permission information for user ID "u1" in the user information database of FIG. 29(A) is in the "permitted" state, the secondary use OK icon 701 will be displayed on the special user's user terminal 300, as shown in FIG. 28(B). However, after it is updated to "not permitted" in step S602, the secondary use OK icon 701 will no longer be displayed next to the user name of user ID "u1" based on the information transmitted in step S607B in response to the display request in step S605. This makes it easy for users to collectively manage the secondary use permission status for their own posts. Furthermore, data management in the distribution server 100 is simplified.

[0287] (Setting whether or not to allow secondary use when posting) 28 to 31 may be set for each post when a user posts a thread, comment, or the like. An example of setting secondary use permission at the time of a user's posting will be described below with reference to FIG. 32. FIG. 32(A) is an example of a screen in which the secondary use permission button 501 is displayed on the user posting screen illustrated with reference to FIGS. 17 and 18. FIG. 32(B) is an example of a screen in which the secondary use permission button 501 is displayed in the comment posting field 84 on the content screen illustrated with reference to FIG. 13, etc. For example, the secondary use permission button 501 is displayed together with a message such as "This post is permitted to be featured in broadcasts and projects by management and affiliated talents." The secondary use permission button 501 in FIG. 32(B) shows an example of a display mode in the off state. In this way, the secondary use permission button 501 is displayed on the posting screen, and secondary use permission can be set according to the content of each post by the user. For example, when posting a fan art image, by turning on the secondary use permission button 501 displayed on the posting screen of Fig. 32(A) or (B), secondary use permission information for each piece of posted information is associated with the content database of Fig. 29(B) or (C), etc. Based on this, the secondary use OK icon 701 will be displayed on the user terminal 300 of the celebrity or other person for the fan art posted with the button turned on, making it easier for the celebrity to introduce the fan art in their broadcasts, etc.

[0288] Note that secondary use permission may be set on a user settings screen such as My Page as exemplified in FIG. 28(A), and then it may be possible to set it individually for each post as shown in FIG. 32. For example, even if the default is "permitted" by turning on the secondary use permission button 501 on My Page, it may be possible to turn it off and set it to "not permitted" depending on the post. Alternatively, there may be no secondary use permission setting on the user settings screen, and secondary use permission may be set individually for each posting timing as shown in FIG. 32. In this case, the default may be either on or off; if the default is on, it may be set to off depending on the content of the post, and if the default is off, it may be set to on depending on the content of the post.

[0289] <Examples of specific configurations and effects> (1-1) In the above-described embodiment, as explained with reference to FIGS. 1 to 18, etc., the distribution server 100 included in the communication system 1 can provide users with multiple types of content associated with attributes (e.g., community, group, unit, talent, etc.) based on a stored program or a method of controlling a computer using the program (hereinafter simply referred to as the program). The attributes include communities (first attributes) corresponding to multiple types of groups A, B, etc., such as communities displayed in the participating community list 50 of FIG. 6(A), and multiple types of talents (talent ID, talent name) and units (belonging group 2), etc., stored in the talent information database of FIG. 5 (second attributes). As explained with reference to FIGS. 6, 7, 9, etc., the attributes are stored in the user information database as account information 125 or in the storage unit 320 of the user terminal 300 to enable identification of participating communities and favorite talents selected in advance in response to user operations from among the communities corresponding to multiple types of groups and multiple types of talents.

[0290] Furthermore, as explained with reference to Figures 10, 11, 14 to 16, 27, etc., the distribution server 100 or the user terminal 300 switches between one of a number of display states depending on the operation on the Oshi Filter 20, including a first display state in which content headings (60, 70, 90) are displayed on the display unit of the user terminal 300 when the Oshi Filter 20 is off, as exemplified in Figure 15(B), from among the content associated with the participating community that has been pre-selected and stored by the user (for example, content stored in the content database of community A in Figure 14), so that the user can identify them, and a second display state in which the Oshi Filter 20 is on, such as Figure 15(A), in which content headings (60, 70, 90) related to content associated with both the participating community and the favorite talent that has been pre-selected and stored by the user are extracted and displayed so that the user can identify them. This allows the display to switch between content headings for content posted to a community selected by the user (participation) in advance, regardless of whether the content is associated with a favorite talent, and content headings for content posted to a community selected by the user in advance and associated with a favorite talent. This allows the user to easily identify preferred information. For example, if a user participates in community A and has selected talent "AAA" with talent ID "t1" as their favorite talent, content headings for content associated with the talent ID "t1" from among the content stored in the content database of community A in FIG. 14 are extracted and displayed on the home screen in FIG. 10, the community screen in FIG. 11(A), the distribution schedule screen in FIG. 27, and the like. Note that the favorite filter 20 can be turned on and off regardless of the level of the evaluation history status of each of multiple users stored in the user information database illustrated in FIG. 7.

[0291] (1-2) Furthermore, the on / off operation of the Favorite Filter 20 is a different operation from the series of operations performed when the user preselects a participating community or a favorite talent, and is performed in response to an operation performed by the user on the Favorite Filter 20 icon displayed on the user terminal 300. This allows the user to switch and display content headings related to the preselected community or content associated with both the community and the talent without having to perform an operation to select a participating community or favorite talent again when displaying the home screen of Fig. 10, the community screen of Fig. 11(A), the distribution schedule screen of Fig. 27, etc., thereby improving operability and user convenience.

[0292] (1-3) As illustrated in Figure 15, the favorite filter 20 is always displayed whether the favorite filter 20 is in an on-display state or an off-display state. This simplifies and facilitates switching to a display screen that extracts content associated with the favorite talent.

[0293] (1-4) The multiple types of content available to users include communities corresponding to groups A and B of the belonging group 1 in FIG. 5, as well as community P, which is a different attribute (third attribute) from the talent (or the unit of the belonging group 2, etc.) and is always in a participation state regardless of the user's selection, and content associated with feature 61 in FIG. 10, which is displayed to all users regardless of the community in which the user is participating. Content headings 60 for content posted to community P and content headings 60 for feature 61 are displayed on the home screen in FIG. 10 regardless of the participating community or favorite talent pre-selected by the user, whether the favorite filter 20 is on or off. Furthermore, since community P is displayed on the channel list screen in FIG. 12, if the user selects the community bar 81c for community P, the community screen for community P (FIG. 11(A)) can be displayed. This allows content headings related to attributes different from the attribute pre-selected by the user to be displayed, making it possible, for example, for an administrator to notify users of information that the administrator wants all users to know regardless of the switching state.

[0294] (1-5) The multiple types of content that can be provided to users include content that is not associated with a related talent but is associated only with a participating community (for example, article IDa99 in Figures 14 and 25), and when the display state of the favorite filter 20 is on, the content headings of content that is associated only with a participating community but not with a related talent are not displayed. As a result, when the favorite filter 20 is on, the content headings of content that is not associated with a favorite talent are not displayed, making it easy for users to identify information associated with their favorite communities and talents.

[0295] (1-6) As explained with reference to Figures 5 and 6, the favorite talents that the user can select in advance are multiple talents who belong (are classified) to one of multiple groups A, B, etc. of the group 1 in Figure 5. This makes it possible to identify information that is further narrowed down to information about talents that the user likes from information about the groups into which the talents are classified.

[0296] (1-7) As explained with reference to Figures 5 and 6, the favorite talent that the user can select in advance can be selected for each belonging group 2, which is a smaller unit than belonging group 1. In other words, the selection can be made in units made up of multiple talents. This makes it possible to specify information that is further narrowed down from information about groups that classify talents to information about units made up of multiple characters that the user likes.

[0297] (1-8) As explained with reference to the home screen example of FIG. 10 , the multiple types of content available to the user can be classified into multiple categories, including recommended topics 62, and can be displayed on the user terminal 300 after being classified into multiple categories, as illustrated in FIG. 10 . Furthermore, for recommended topics 62, whether the recommended filter 20 is on or off, content headings 60 related to a predetermined number of pieces of content associated with both the participating community and the recommended talent previously selected and stored by the user are displayed so that the user can identify them. Furthermore, for categories other than recommended topics 62, such as popular user posts 63, commemorative broadcasts 64, and merchandise 65, content headings 60 corresponding to whether the recommended filter 20 is on or off are displayed so that the user can identify them, as explained with reference to FIG. 16 . By displaying the recommended topic 62, some of the content associated with the participating community and recommended talent selected in advance by the user can be displayed without switching the display state, so the user can identify the content associated with their favorite community and talent without the hassle of switching operations.

[0298] (1-9) Furthermore, the content headings 60 for the recommended topic 62 on the home screen shown in Fig. 10 can be displayed with priority, for example, above content headings 60 related to content categorized in other categories, regardless of whether the recommended filter 20 is on or off. This makes it easier for users to identify content associated with their favorite communities and talents.

[0299] (1-10) As explained with reference to Fig. 12, by the user selecting the community bar 81 on the channel list screen of Fig. 12 from among the communities to participate in that the user has previously selected, it becomes possible to display a content screen for each community, as exemplified in Fig. 11(A). This allows the user to further select a preferred community from among the communities to participate in that the user has previously selected, and display the content heading 70 for that selected community, thereby enabling the user to further extract any information as needed, even from among the preferred information, thereby improving convenience.

[0300] (1-11) As described with reference to Figures 24 to 26, the distribution server 100 and the user terminal 300 perform a reception effect such as that shown in Figure 24(A) or 24(B) each time they receive a tap action from a user on a content icon 708. The reception effect displays a fan mark or a talent effect corresponding to a related talent associated with the content (article ID) that received the action from the user, as exemplified in the content-specific effect table of Figure 25. As a result, the reception effect for a tap action includes a talent-related effect, making it possible to encourage the user to take a tap action.

[0301] (1-12) Furthermore, when a predetermined number of tap actions (e.g., 100 taps) are received from the user, a special effect such as a luxurious effect or a talent effect, as shown in Fig. 24(B), is performed. This allows the special effect to be performed when the user performs a predetermined number of tap actions, thereby encouraging the user to take a tap action.

[0302] (1-13) The multiple types of content available to users are associated with related talents, and thus include content associated with a talent ID in the content database of FIG. 14. For content associated with a related talent, the related talent 88, which displays the icon and name of the talent associated with the content, is displayed regardless of whether the recommended filter 20 is on or off. This allows the user to identify the related talent associated with the content regardless of whether the recommended filter 20 is on or off, improving user convenience. It can also provide an opportunity to learn about new talents.

[0303] (1-14) As described with reference to Figures 14, 17, and 18, the multiple types of content that can be provided to users include posted content posted by users. When a user posts information, for example, by selecting the related talent bar 40 in Figure 17, and as a result, in steps S310 and S311 in Figure 18, a talent ID is associated with the posted information, as exemplified in the content database in Figure 14. This allows a talent to be associated with user posts, making it easier for users to share their favorite information.

[0304] (1-15) The multiple types of content include posted content (such as articles with posting authority "User" in FIG. 14) posted by users through the user posting process described with reference to FIGS. 17 and 18. The users include multiple specific users corresponding to each of the talents in FIG. 5. Posted content that has received an action such as a tap action or comment from a specific user is displayed as a content heading (60, 70) on the home screen in FIG. 10 or the community screen in FIG. 11(A), or a special action 79 along with the icon of the special user on the content screen in FIG. 13. This allows users to easily identify posted content that has received an action from a specific user. This improves convenience for users seeking information about talents.

[0305] (1-16) When content associated with a favorite talent previously selected and stored by a user is posted, the distribution server 100 and user terminal 300 send the user a push notification that the content associated with the favorite talent has been posted, based on the user information database of FIG. 7 and the content database of FIG. 14. This makes it easier for the user to identify content information related to the favorite talent. Furthermore, if a specific user takes action on the content posted by the user, the user feels special.

[0306] (1-17) As described with reference to FIG. 27 , the distribution server 100 acquires, via an API provided by the external web service 400, attribute identification information 96a of the channel account that distributes, attribute identification information 96b of the handle included in the summary field 95 of the distribution screen on the external web service 400 shown in FIG. 27(C), title 97, thumbnail image 99, and other information. Since the acquired information includes the attribute identification information 96, a talent ID corresponding to the attribute identification information 96 is identified, and the distribution schedule screen shown in FIG. 27(A) or 27(B) including a content heading 90 generated based on the identified talent ID is displayed on the user terminal 300. For example, if the information acquired from the external web service 400 includes attribute identification information 96 corresponding to talent "AAA," a content heading 90 associated with the talent ID "t1" of talent "AAA" is generated. Information for identifying the content heading 90 is generated and stored by the content management unit 132. Therefore, content headings 90 of broadcasts related to participating communities (groups) pre-selected by the user from among groups corresponding to the channel account are displayed. Furthermore, by further selecting the favorite filter 20, it is possible to narrow down the display to content headings 90 of broadcasts in which the favorite talent appears. This makes it possible to optimize external posts such as broadcasts provided by the external web service 400 to match the user's preferences, making it easier for the user to identify them.

[0307] (2-1) In the above-described embodiment, as described with reference to FIGS. 1 to 4, 7, 8, 19 to 23, etc., the distribution server 100 included in the communication system 1 updates the user's evaluation history status, such as the user's level and accumulated points, in response to external evaluations, such as evaluations from sources other than the user himself / herself, of actions such as content posted by the user and comments, based on a program or a method of controlling a computer using the program (hereinafter simply referred to as the program) that allows actions received from the user terminals 300 operated by each of the plurality of users to be reflected in the user terminals 300 so that each of the plurality of users can recognize the actions. Also, as illustrated in FIG. 19, the distribution server 100 controls actions that can be taken by users whose evaluation history status is at a predetermined level, so that users who are not at the predetermined level cannot take certain actions. For example, even if a user at a predetermined level 80 or above, which is a specific situation, takes a specific action of posting content with an embedded link that is restricted for users at level 59 or below, the content with the embedded link can still be displayed on the user terminals 300 of users at level 59 or below who are not at the specific situation. This allows the actions that users can take to be controlled based on external evaluations, which are evaluations from people other than the user who took the action. Furthermore, specific actions accepted from a user in a specific situation can be reflected in multiple users (even if they are not in the specific situation), making it possible to maintain good public order within the community.

[0308] (2-2) As explained in steps S402 to S406 in Fig. 23, the account management unit 133 allows a user who has increased in level and entered a specific situation to take a specific action according to the level. By allowing a user who has entered a specific situation according to external evaluation to take a specific action, actions that can be taken by users who are not in a specific situation are restricted. Therefore, it is possible to encourage users to take actions that will put them in a specific situation where they can take a specific action, and it is possible to maintain good public order in the community.

[0309] (2-3) As described with reference to FIG. 19 , specific actions that can be taken are defined in stages according to the level. For example, if the user is at level 60 or above, there is no restriction on links to the content that the user posts as a specific action, and if the user is at level 80 or above, the user can create a plan as a specific action. As illustrated in steps S404 to S406 of FIG. 23 , these specific actions allow users who have leveled up from 59 to 60 to remove the link restriction on the content that the user posts, and allow users who have leveled up from 79 to 80 to create plans. Therefore, users who have not yet reached a predetermined level are restricted from taking specific actions. In this way, by gradually allowing specific actions for users who have reached a predetermined level and are in a specific situation, depending on the level, it is possible to encourage users to take actions aimed at a higher level, and it is possible to maintain good public order within the community.

[0310] (2-4) As explained in steps S407 to S411 of Fig. 23, the account management unit 133 restricts a user whose level has dropped and who is no longer in a specific situation from taking a specific action that was permitted according to the level. This restricts a user who is no longer in a specific situation according to external evaluation from taking a specific action, thereby encouraging the user to take an action that can maintain or improve the specific situation, thereby stabilizing public order in the community.

[0311] (2-5) As described with reference to FIG. 19 , the specific actions that can be taken are determined in stages according to the level. For example, if the level is 59 or lower, the specific action of removing the link restriction on posted content is not permitted, and therefore, there is a link restriction on posted content. If the level is 79 or lower, the specific action of creating a plan is not permitted, and therefore, there is a restriction on creating a plan. As illustrated in steps S409 to S411 of FIG. 23 , these specific actions restrict links to the posted content that were previously permitted for a user who has leveled down from 60 to 59. Furthermore, if the level is downgraded from 80 to 79, the user is restricted from creating plans that were previously permitted, and therefore, users who no longer meet the required level are restricted from performing specific actions. In this way, by gradually restricting the specific actions permitted for users who are no longer in a specific situation, it is possible to prevent an extreme reduction in the number of actions that can be taken while encouraging actions that maintain or improve the specific situation, thereby maintaining good public order within the community.

[0312] (2-6) As explained with reference to Fig. 8, the user history status 55, which displays the level and accumulated points as information about the user's evaluation history status, is not made public to other users, but can be viewed by the user himself / herself on the My Page screen. This allows the information related to the evaluation history status that is updated in response to external evaluations to be notified to the user himself / herself, and therefore, the user can be made aware of his / her own situation and encouraged to make efforts to improve the public order of the community.

[0313] (2-7) As explained with reference to Figure 22, external evaluations that can update a user's evaluation history status include points awarded based on a favorable impression from the administrator and negative evaluations. In this way, because the external evaluations include evaluations from the administrator, who is a third party different from the user, personal feelings are less likely to interfere with the external evaluations, and the external evaluations can be fair.

[0314] (2-8) As described with reference to Figure 22 etc., external evaluations that can update a user's evaluation history status include evaluations such as positive actions and reports from other users who are different from the user who took the action among multiple users who use the community app. In this way, because the external evaluations include evaluations from other users who are different from the user who took the action, it is possible to ensure that the public order within the community is in line with the intentions of all users.

[0315] (2-9) As explained with reference to Figure 19 etc., restriction processing such as hiding is performed on the user terminal 300 etc. of each of multiple users for content and comments that are restricted by users who are permitted to take the specific action of "moderator invitation" at level 90 or higher, or users who are permitted to take the specific action of "report count" at level 70 or higher. This restricts user actions by restricting the actions of users whose evaluation history status is in a predetermined status, thereby preventing indiscriminate restriction of user actions.

[0316] (2-10) Furthermore, actions that are subject to regulation by a predetermined number of users who are allowed to take specific actions in the "report count" described with reference to Fig. 19 etc. are restricted from being reflected in the user terminals 300 of multiple users. As a result, when an action subject to regulation is accepted by a predetermined number of users whose evaluation history status is in a predetermined state, it is deemed to be a nuisance action and the reflection of the action is restricted, so that nuisance behavior can be efficiently restricted without hindering free interaction and communication.

[0317] (2-11) As explained with reference to FIG. 19 etc., depending on the level, which is the evaluation history status of each of a plurality of users, for example, if the level is 50 to 59, a bonus E may be awarded, and if the level is 100, a bonus S, which is rarer than the bonuses A to E, may be awarded. With this configuration, bonuses may be awarded depending on the evaluation history status, and users can be encouraged to be conscious of achieving an evaluation history status that will result in the awarding of a bonus.

[0318] (2-12) Multiple users belong to the same fan community, and actions that users can take include, for example, promotional activities such as posting content related to a group they support or a celebrity belonging to the group, such as streaming videos or merchandise. The distribution server 100 changes the external evaluation based on the number of views of the streaming video and the profit contribution from merchandise sales resulting from the promotional activities, and updates the user's evaluation history. This can motivate users to promote the community, thereby revitalizing the community.

[0319] (3-1) In the above-described embodiment, a program is used that enables actions such as the posting of content such as threads and comments, which are received from the user terminals 300 operated by each of a plurality of users, to be reflected on the user terminals 300 of each of the plurality of users so that each of the plurality of users can recognize them. In steps S601 to S604 of FIG. 30, the user can set whether or not to allow the content posted by the user to be used secondary, for example, by an administrator or a talent introducing the user's posted content in a video distribution or quoting it in the posted content, depending on the user's operation of the secondary use permission button 501 on the user settings screen of FIG. 28(A) or the operation of the secondary use permission button 501 when posting content in FIG. 32. Furthermore, when the secondary use permission information of "Allowed" is associated with a user in the user information database of Fig. 29(A) due to secondary use permission button 501 being in the on state on the user settings screen of Fig. 28(A), or when secondary use permission information of "Allowed" is associated with a thread or comment in the content database of Fig. 29(B) or the comment database of Fig. 29(C), information (suggestion information) for displaying secondary use OK icon 701 of Fig. 28(B) suggesting that the posted content can be used for secondary purposes can be reflected in step S607 of Fig. 30 and step S607B of Fig. 31. This allows the setting of whether or not to allow secondary use of posted content to be performed in response to user operation, thereby making it less likely for misunderstandings to arise that posted content can be used for secondary purposes and facilitating secondary use.

[0320] (3-2) In the above-described embodiment, steps S606 to S607 in Fig. 30 and steps S606 to S607B in Fig. 31 make it possible to prevent the secondary use OK icon 701 in Fig. 28(B), which indicates that the posted content can be used for secondary use, from being reflected on the user terminals of users who do not satisfy certain conditions, but to reflect it only on the user terminals 300 of users who satisfy certain conditions, such as special users and administrators in Fig. 5. This prevents the secondary use OK icon 701 from being displayed on the user terminals 300 of general users who do not satisfy certain conditions, encouraging secondary use even among users who do not satisfy the certain conditions (for example, users who have little need for secondary use), and thus preventing use or abuse that is not intended by the administrator or user.

[0321] (3-3) In the above-described embodiment, the user can select whether or not to permit secondary use of posted content by operating secondary use permission button 501 in Fig. 28(A) on a user setting screen such as the user's My Page in Fig. 8. This allows the user to select whether or not to permit secondary use of posted content when setting information about the user, making it easier for the user to manage the secondary use permission status of posted content.

[0322] (3-4) In the above-described embodiment, when the secondary use permission information of "Permitted" is associated with the user in the user information database of Fig. 29(A) in steps S601 to S602 of Fig. 30, or when a post is made with the secondary use permission button 501 on on the posting screen of Fig. 32, posted content that is accepted when the user permits secondary use can be managed in the content database of Fig. 29(B), the comment database of Fig. 29(C), etc. as content information for which secondary use is permitted in steps S603 to S604 of Fig. 30. Furthermore, when content information such as the article ID "a3" in Fig. 29(B) is displayed on the user terminal 300, the secondary use OK icon 701 in Fig. 28(B) can be displayed in steps S603 to S607 of Fig. 30. This allows the secondary use OK icon 701 to be displayed for posts accepted when the user has permitted secondary use, enabling the user to set whether or not secondary use is permitted for each post, thereby reducing the processing burden when reflecting posted content on the distribution server 100, etc., on the user terminal 300.

[0323] (3-5) In the above-described embodiment, steps S605 to S607B in Fig. 31 allow the secondary use OK icon 701 to be displayed on the user terminal 300 when a content screen such as article ID "a3" in Fig. 29(B) posted by a user is displayed based on the user's current secondary use permission information in the user information database in Fig. 29(A). This makes it easier for users to manage the secondary use permission status for their own posted content. Also, management is easier for the administrator (and for the server) because it only needs to manage the secondary use permission status for each user.

[0324] (3-6) Furthermore, based on the display request information in step S605 of FIG. 31, regardless of whether a content screen or the like is reflected or can be reflected in the user terminal 300 in steps S607B and S608, the user can operate the secondary use permission button 501 on the user settings screen in FIG. 28(A), etc. Even if the content screen displaying the secondary use OK icon 701 in FIG. 28(B) is displayed on the user terminal 300, a reload operation or other operation can be performed in steps S605 to S607B to update the content screen to one in which the secondary use OK icon 701 is not displayed, depending on the current user's secondary use permission status, based on the secondary use permission information updated in step S602 of FIG. 31. This makes it possible to update the display status of the secondary use OK icon 701 in response to a user operation, even if the user wishes to change the secondary use permission status of their own posted content after the fact, thereby improving user convenience.

[0325] (3-7) In the above embodiment, by displaying the secondary use permission button 501 on the thread posting screen in Fig. 32(A) or the comment posting screen in Fig. 32(B), a user can set whether or not to permit secondary use of the content to be posted when posting content such as a thread or a comment (each time a user posts). This improves user convenience.

[0326] <Modification> Modifications to the above-described embodiment are listed below.

[0327] (About content information) In the above-described embodiment, content headings (60, 70, 90) in Figures 10, 11, 27, etc. have been exemplified as content information related to content (e.g., news articles, information posted by users, etc.). However, the content information related to content is not limited to this, and may be, for example, explanatory information on the screen of the content itself, as exemplified in Figure 13. For example, it includes various information displayed on the content screen itself in Figure 13, such as poster 71, content 74b, related talent 88, special action 79, and number of tap actions 78.

[0328] (About attribute selection processing) In the above-described embodiment, an example has been described in which a user can select a participating community and a favorite talent in steps S102 to S104 of FIG. 9 upon initial login. When selecting a participating community and a favorite talent upon initial login, both may need to be selected in step S103, or neither may be selected (no attributes selected). Alternatively, a user may select only a participating community or a favorite talent, or may be required to select only one. For example, even if a favorite talent is selected, information about the favorite talent may not be extracted and displayed on the content screen unless the user is participating in a participating community corresponding to the group 1 to which the favorite talent belongs. In other words, even if the favorite talent filter 20 is turned on, content headings of talents belonging to groups corresponding to communities to which the user does not belong are not displayed. Alternatively, a user may not be able to select a participating community unless the user selects one of the participating communities. For example, a user may not be able to proceed to the screen for selecting a favorite talent unless the user selects one of the participating communities.

[0329] In the above-described embodiment, an example has been described in which, when it is determined in step S101 of Fig. 9 that this is the first login, the selection screen for the community to join and the favorite talent shown in Fig. 6 is displayed in step S102. At this time, all of the community to join settings in Fig. 6(A) or the favorite talent settings in Fig. 6(B) may be selected in advance (by default).

[0330] In the above-described embodiment, an example has been described in which, in steps S101 and S102 of Fig. 9, if it is the first login, an attribute selection screen is displayed on the user terminal 300 in step S102, but it may not be displayed on the screen at the time of the first login, and the initial attribute selection may be performed later from My Page, etc. Furthermore, at the time of the first login, the user may be in a state of participating in all communities until later editing is performed by the user on My Page, etc.

[0331] In the above-described embodiment, when the user is not logging in for the first time (NO in step S101 of FIG. 9), the determination in step S107 that a participating community or a favorite talent has been selected after the setting editing screen of FIG. 6 is displayed is based on the timing of a selection operation on an icon or the like. However, this is not limited to this. Alternatively, the user may operate the home icon 13 or the like displayed at the bottom of the app screen to move to another screen, and the attribute selected on the attribute selection screen of FIG. 6 may be deemed to have been selected by transmitting and receiving information regarding the attribute as having been confirmed, and the process proceeds to step S108. Alternatively, instead of or in addition to an operation on the display of each participating community or each talent on the attribute selection screen of FIG. 6, a confirmation icon or the like may be displayed, and the selection may be determined to have been made when the confirmation icon is operated (when information transmitted in response to the operation is received). Furthermore, when the confirmation icon is operated, a special effect may be displayed on the user terminal 300.

[0332] (Regarding the display of special actions on the home screen, community screen, etc.) In the above-described embodiment, as described with reference to FIG. 11(A) and the like, an example has been described in which, for content that has received a comment or tap action from a special user corresponding to a talent, a special action 79 is displayed in the content heading 70 together with the icon of the special user. When the talent who performed the action on the content is a favorite talent previously set by the user, the display mode of the special action 79 displayed in the content heading 70, etc., may be different from that when the talent who performed the action is not the favorite talent, or the content heading 70 itself may be displayed in a different mode from that when the talent who performed the action is not the favorite talent. Alternatively, when the talent who performed the action on the content is a related talent associated with the content, the display mode of the special action 79 displayed in the content heading 70 may be different from that when the talent who performed the action is not the related talent, or the content heading 70 itself may be displayed in a different mode from that when the talent who performed the action is not the related talent. Examples of different modes include modes with different colors, different message content, or the presence or absence of a message.

[0333] (Regarding the display of comments on the content screen) In the above-described embodiment, an example has been described in which, on the content screen described with reference to FIG. 13 and the like, the display mode or display order of each comment 87 can be changed if the comment is from a special user corresponding to a talent. Alternatively, or in addition, if the talent (special user) who made a comment on the content is a favorite talent previously set by the user, the display mode of the comment 87 of the favorite talent may be displayed in a different manner than when the talent who performed the action is not the favorite talent. Alternatively, the comment 87 may be displayed at the top of each comment 87. Alternatively, if the talent who made a comment on the content is a related talent associated with the content, the display mode of the comment 87 of the related talent may be displayed in a different manner than when the talent who performed the action is not the related talent. A different manner may, for example, be a different color, a different message content, or the presence or absence of a message. Alternatively, the comment 87 may be displayed at the top of each comment 87.

[0334] (About the categories displayed on the home screen) In the above-described embodiment, an example has been described in which feature 61 is displayed on the home screen described with reference to FIG. 10 regardless of whether the user has selected any participating community or any favorite talent. However, this is not limiting, and feature 61 may not be displayed. For example, only content posted to participating communities that the user has pre-selected (or communities in which the user is always participating regardless of selection) may be displayed on the home screen. Alternatively, feature 61 may be displayed on a screen different from the home screen on which content headings 60 are displayed for each category.

[0335] In the above-described embodiment, an example has been described in which a recommended topic 62 is displayed on the home screen of Fig. 10 if the user has selected a recommended talent. However, this is not limiting, and the recommended topic 62 may not be displayed even if a recommended talent is selected. For example, content headings 60 associated with the recommended talent may not be extracted in any category unless a selection operation is performed on the recommended filter 20 on the home screen of Fig. 10. Alternatively, the recommended topic 62 may be displayed on a screen different from the home screen on which content headings 60 are displayed for each category.

[0336] (Regarding notification to users) In the above-described embodiment, an example has been described in which a push notification is sent when content associated with a favorite talent selected in advance by a user is posted. In addition, when a special user talent posts a comment on the content, a notification (such as a display on a notification screen or a push notification) may be sent to general users. Alternatively, a notification may be sent only when a comment is sent from the favorite talent. Alternatively, when a comment is sent from a favorite talent selected in advance by a user, the notification mode may be different from when a comment is sent from a talent who is not the favorite talent. The change in notification mode may mean, for example, that in the case of a notification from a favorite talent, the notification icon 15 displayed at the bottom of the app screen is highlighted.

[0337] Furthermore, when a user posts (content or comment) and other users, including special users, take a favorable action such as a comment or tap, the user who posted the content may be notified (displayed on a notification screen, or by push notification, etc.) In this case, for example, notifications are normally sent in bulk once an hour, but when an action is taken by a special user who is a celebrity or a special user who is a favorite celebrity, the notification may be sent in real time.

[0338] In addition, if a user has selected a favorite talent for each unit, the user may be notified by push notification when content associated with one of the talents included in the unit is posted, or when content associated with the unit is posted.

[0339] (About attribute extraction processing) In the above embodiment, when the user turns on the favorite filter 20, content headings (60, 70) associated with the favorite talent previously selected by the user are extracted and displayed. However, if multiple favorite talents are selected, the talents may be further narrowed down individually for each favorite talent. For example, if the user selects talents with talent IDs "t1," "t2," and "t3," the favorite filter 20 may be individually selectable as "t1," "t2," and "t3" when the favorite filter 20 is turned on. Alternatively, if the favorite talents are previously selected by unit, the favorite talents may be individually selectable by unit. Furthermore, by preselecting a more special talent (the most favorite talent) from among the favorite talents, further filtering by the most favorite talent may be possible. In this way, after all favorite talents are extracted using the favorite filter 20, multiple filtering stages, such as first, second, and third, may be possible, such as allowing the user to select more favorite talents individually (further narrowing down the results) by operating a specific icon or the like.

[0340] In addition, if a user has selected a favorite talent on a unit basis in advance, when content is posted in which one of the talents in the unit is associated with a related talent, the favorite filter 20 may be turned on, allowing the user to extract and display the content headings of the content associated with one of the talents in the unit that the user has previously selected.

[0341] It is also possible to associate a talent with a community even if the community is different from the community corresponding to the group to which the talent belongs. For example, talent ID "t1" is a talent belonging to "Group A" of Affiliation Group 1, but talent "t1" may be associated with content posted in "Community B" corresponding to "Group B." Therefore, if a user selects talent ID "t1" and also participates in "Community B," turning on the "Favorite Filter 20" on the home screen or the content screen in "Community B" will extract and display content associated with talent ID "t1." This allows users to obtain information about their favorite talent without missing anything, even if there is a collaboration project between different groups and posts are only made in the community corresponding to one of the groups. It is also possible for content associated with a favorite talent to be displayed on the home screen even if the user does not participate in "Community B."

[0342] (Regarding the specified conditions for attribute extraction processing) In the above embodiment, as described with reference to Figures 15, 16, etc., an example has been described in which the predetermined condition for turning on or off the favorite filter 20 is met when the user taps on the favorite filter 20 icon displayed on the user terminal 300 to turn it on. However, the predetermined condition is not limited to this, and it is sufficient that the favorite filter 20 can be switched on or off according to the user's will, and for example, it may be possible to switch by voice instruction or by vibrating (for example, shaking) the user terminal 300 itself.

[0343] (Regarding the memory state of the Oshi Filter 20 in the attribute extraction process) In the above embodiment, an example has been described in which the on state of the Oshi Filter 20 is stored and maintained after an operation on the Oshi Filter 20 is performed, even when the content screen of FIG. 13 is displayed after the app is launched and the user returns to the content screen or home screen on which the Oshi Filter 20 was on. However, this is not limiting, and the Oshi Filter 20 may always be in either the on or off state when moving to a different screen. For example, after displaying the community screen of FIG. 13 from the community screen of FIG. 11 (or the home screen of FIG. 10) with the Oshi Filter 20 in the on or off state, the Oshi Filter 20 may be in the off or on state when the user returns to the community screen of FIG. 11 (or the home screen of FIG. 10). Alternatively, after turning on the Oshi Filter 20 on the home screen of FIG. 10 (or the community screen of FIG. 11) and displaying the community screen of FIG. 11 (or the home screen of FIG. 10), when you return to the home screen of FIG. 10 (or the community screen of FIG. 11), the Oshi Filter 20 may be in an off or on state.

[0344] (User submission processing) In the above embodiment, an example has been described in which the example user posting screen of FIG. 17 is divided into FIG. 17(A), which is a posting screen for inputting text and uploading images, and FIG. 17(B), which is a screen for selecting categories and related talents. However, this is not limited to this, and FIG. 17(A) and FIG. 17(B) may be displayed on a single screen for input or selection. For example, scrolling may be possible, and transition to a separate screen may not be required. Furthermore, posting may be possible even without inputting text or posting an image. Alternatively, posting may be possible even if there is no title, as long as text is input or an image is uploaded.

[0345] Also, while an example has been described in which the selection of a category and associated talent is optional, both may be required. Alternatively, "no category" or "no associated talent" may be selected, or selection may be possible for each unit in the belonging group 2 in FIG. 5. Furthermore, when selection is made for each unit, the talent IDs of the individual talents belonging to the unit and a unit ID for identifying the unit may be associated with the content. Alternatively, only the unit ID may be associated.

[0346] (Regarding evaluation history status update processing) In the above-described embodiment, an example has been described in which a notification is given in steps S406 and S411 in Fig. 23 that a specific action has been permitted or restricted. However, this is not limiting, and the user may not be notified in steps S406 and S411. Alternatively, a notification may be given if an action is permitted in step S406, but not if the action is restricted in step S411. For example, not notifying the user when a restriction is imposed can avoid upsetting the user.

[0347] (Other examples of evaluation history) In the above-described embodiment, as described with reference to FIG. 19 , an example has been described in which a user's level increases in stages from an initial setting level in accordance with external evaluation, and each time a specific situation (e.g., level 60, level 80, etc.) is reached, specific actions that can be taken are permitted according to the level. However, this is not limited to this. For example, the specific actions shown in FIG. 19 may be permitted for all users in the initial setting, and specific situations may be gradually eliminated as the level decreases, and the specific actions that can be taken may be restricted. Furthermore, the initial setting level is not limited to a lower limit of 1 and an upper limit of 100, but may start from, for example, 80, and the specific actions that can be taken may be gradually permitted or restricted according to changes in the level.

[0348] In the above-described embodiment, an example was described in which fluctuations in a user's level and accumulated points are due to external evaluations from sources other than the user himself / herself. However, in addition to this, the accumulated points may also be increased by a user tapping on another user's post or comment, or by making a comment to another user. This encourages users to be more active within the community, thereby revitalizing the community.

[0349] In the above-described embodiment, an example was described in which, when content or comments posted by a user are hidden or reported, points are reduced, thereby gradually restricting the user's actions. Alternatively, or in addition to the points (variable cumulative points) that affect the user's level, a reflection restriction point may be defined in the evaluation history status as a criterion for restricting the reflection of actions within the community app. For example, a user whose posted content, comments, etc. have been hidden or reported by other users a predetermined number of times (e.g., 20 in either case, or a total of 20), may have their actions restricted (reflection restricted). For example, content, comments, etc. posted by a user subject to reflection restriction may not be displayed to other users for a certain period of time, or the user may be prevented from posting content, comments, etc. for a certain period of time.

[0350] The reflection restriction may be implemented according to the level that changes depending on the number of points as shown in the above-mentioned Figures 22 and 23. For example, a negative level lower than 1 may be set, and the reflection restriction may be implemented for users who reach a negative level. Alternatively, the default level at the start of the community app may be set to 10, and restrictions may be imposed as the level becomes lower than 10.

[0351] (For positive actions from users in a given situation) In the above-described embodiment, an example has been described in which the content of actions, such as special actions that can be taken, varies according to the level described with reference to FIG. 19 . Alternatively, or in addition, other users may be able to recognize that a user has a high level. High-level users tend to take actions that create a positive atmosphere within the community and are considered to be highly trustworthy. Therefore, the display mode of content that has received a favorable action (including a tap action or a favorable comment) from a high-level user (e.g., level 90 or higher) may be changed. Alternatively, the display mode may be changed only when favorable actions are received from multiple highly trustworthy users (e.g., a predetermined number, such as five). For example, the display mode of the content heading 60 on the home screen of FIG. 10 , the content heading 70 in FIG. 11(A), or the number of tap actions 78 may be changed in color, or a mark (e.g., special action 79) indicating that an action has been taken by a highly trustworthy user may be displayed. Alternatively, on the content screen illustrated in FIG. 13 , comments may be displayed in a more prominent manner (e.g., by displaying them at a higher position or by changing their color). Furthermore, when content that has received favorable actions from multiple highly trusted users or when there is a comment, a push notification or a notice may be displayed.

[0352] Furthermore, a user who has posted content or a comment that has received a favorable action from a highly reliable user may be notified of the action from the highly reliable user. For example, a push notification may be sent to the user device of the user, or a notification may be displayed within the app.

[0353] In the above-described embodiment, an example was described in which content or comments that have been restricted, such as those that have been hidden or reported, are hidden from the user terminals 300 of multiple users, or content posted by restricted users is hidden from users, from a predetermined number of users (e.g., five) at level 70 or higher who are the target of the "report count" in FIG. 19 . The restriction process for the restricted content itself and the restriction process for the users who posted the restricted content may use different conditions, such as the number of users in a predetermined situation (e.g., level 70 or higher) who have hidden or reported the content or comments. For example, a restriction process may be performed in which restricted content or comments are hidden from all users from a first number of users (e.g., five) at level 70 or higher who are the target of the "report count," and then a restriction process may be performed in which all content posted by users who have hidden or reported the content is hidden from all users from a second number (e.g., 20) higher than the first number.

[0354] Additionally, content or comments posted by a user who has accumulated a certain number of users with a level of 70 or higher who have been hidden or reported, which are subject to the "report count," can be hidden from all users. For example, content or comments posted by a user who has been hidden or reported by five users with a level of 70 or higher can be hidden from all users.

[0355] Note that the users who are not visible may not include the users who posted the comments or content. This allows the user to know (become aware) that the content or comments posted by the user have been restricted, even though the content or comments posted by the user are reflected on the user's own device, for example, due to the lack of action from other users.

[0356] (Notification of information related to evaluation history status) In the above-described embodiment, an example was described in which each user can check their own "level" and "accumulated points" in the user rating history status 55 on their personal page, as illustrated in FIG. 8 . However, the present invention is not limited to this. Information about the user's rating history status, such as the level and accumulated points, may be viewed only by the administrator on the administrator terminal 200, without being notified to the user or any other users. This allows information related to the rating history status updated in response to external ratings to be notified to any users but to the administrator, thereby preventing excessive inhibitions in user actions and enabling the administrator to grasp information related to the user's rating history status and use it for management purposes. Furthermore, users can more comfortably use the fan community without being overly concerned about their own "level."

[0357] In the above-described embodiment, information related to the evaluation history status described with reference to FIG. 23 and the like may be provided to the user as feedback. For example, the increase or decrease in points or the level up or down updated in response to external evaluations over a predetermined period (e.g., one day or one week) may be fed back to the user as a result of today's (or this week's) actions. Alternatively, or in addition to this, sentiment analysis using, for example, AI may be performed on the content posted by the user over a predetermined period or the text of comments (actions taken by the user), and the percentage of positive words, negative words, or words not classified into either category may be notified to the user (for example, by displaying a pop-up screen or a notice page at a predetermined time). This allows the user to objectively know the tendencies of their own actions and encourages them to take actions that will improve public safety within the community.

[0358] (Regarding external evaluation) In the above-described embodiment, an example was described in which a user's points are reduced when an action, such as content or a comment posted by the user, is hidden or reported. In addition, for example, when hiding, a user may be able to select or input a reason for hiding on a screen such as that shown in FIG. 11(B). A user may hide another user's action due to personal reasons, such as the user being a rival user, and may hide actions that do not pose a risk of negatively impacting the community or worsening public order. Therefore, actions that do not substantially have a negative impact on the community may not affect the user's points, and only actions that do substantially have a negative impact may affect the points. For example, options for hiding may be predefined as having an impact on points and not having an impact on points, and an administrator may check the reasons for hiding and operate to affect the points for actions that are determined to have a negative impact.

[0359] In the above-described embodiment, an example has been described in which a user's points fluctuate depending on external evaluations, such as whether there have been tap actions or comments on content or actions such as comments posted by the user. The number of posts of content posted by this user may be limited. For example, the number of views of a video streamed through content posted by the user and the degree of profit contribution to a support target, such as the number of merchandise purchases, have been given as examples of external evaluations that increase points. However, since there is a risk that content posts will be promiscuous in an attempt to increase points, a limit may be imposed on content posts, such as one per day. Furthermore, for users with higher levels and higher trustworthiness, the upper limit on the number of content posts per day may be increased.

[0360] (Regarding user devices on which the secondary use OK icon 701 is displayed) In the above-described embodiment, in the secondary use-related processing described with reference to FIGS. 28 to 31, an example has been described in which the secondary use OK icon 701 is displayed only on the user terminal 300 of a user who satisfies a specific condition. However, this is not limiting, and the icon may also be displayed on the user terminal 300 of a user who does not satisfy the specific condition. In this way, displaying the secondary use OK icon 701 can serve as a sign that the user is supporting the talent, and it is easier to create a positive atmosphere and a sense of unity in the entire fan community, encouraging active support for the talent. Furthermore, an atmosphere within the community of actively supporting the talent can motivate users to turn on the secondary use OK icon 701, which can lead to further activation of communication between fans and the talent.

[0361] Alternatively, even if a user does not satisfy the specific conditions, the secondary use OK icon 701 may be displayed on the poster's own user terminal 300. This makes it easy to check the secondary use permission status for each of the poster's own posts.

[0362] (Extracting only posts that are permitted for secondary use) In the above embodiment, as illustrated in FIG. 28(B), a secondary use OK icon 701 is displayed on a post for which secondary use is permitted, enabling a user (such as a celebrity) who meets certain conditions to identify posted content for which secondary use is permitted. However, instead of or in addition to the secondary use OK icon 701, a filtering function based on a user's operation on a predetermined icon may be used based on information (suggestive information) that identifies the secondary use permission status received along with the post-related information in step S607 of FIG. 30 or step S607B of FIG. 31. This may switch from a state in which posts for which secondary use is permitted and posts for which secondary use is not permitted to a state in which only posts for which secondary use is permitted are extracted and displayed. This makes it easier to identify posted content for which secondary use is permitted and improves convenience for administrators and celebrities who use the content for secondary use. Furthermore, for example, when streaming videos, even if a fan community app screen is displayed, posts for which secondary use is not permitted may not be captured.

[0363] (Other aspects of the secondary use OK icon 701) In the above embodiment, an example has been described in which the secondary use OK icon 701 is displayed on content for which secondary use has been permitted by the user, as exemplified in Fig. 28 etc. However, the present invention is not limited to this, and a mark (for example, a simple star mark) that at first glance appears unrelated to secondary use (quotation) may be displayed so that a user who knows that the seemingly unrelated mark is a secondary use permission mark can recognize that the content is available for secondary use.

[0364] (About the shared icon for secondary use) In the above embodiment, the secondary use permission related process described in Figures 28 to 32 and the like displays a secondary use OK icon 701 on content posted by a user, thereby facilitating administrators, talents, and the like to secondary use the content in other media, such as streaming videos. Alternatively or additionally, the content may be used not only in other media but also by allowing it to be quoted in other posts within the fan community app, which is the same medium as the posted content. For example, posted content for which secondary use is permitted may be shared by embedding a posting link (secondary use information) that allows transition to the posted content for secondary use in other posted content, such as a share icon for each post. Furthermore, the posted content may be quoted in posts other than the fan community app, which is the same medium as the posted content. The posted content for which secondary use is permitted may be quoted by pasting a URL generated by operating the share icon of the post for which secondary use is permitted in a post on another SNS, etc. Furthermore, the share icon may be displayed or operable only by users who meet certain conditions. This makes it easier for a user who performs a secondary use operation by operating a share icon to make secondary use of the posted content.

[0365] (About changing secondary use permission information for each content after posting) In the above embodiment, an example has been described in which secondary use permission information is associated with each piece of posted information, such as a thread or a comment, based on the secondary use permission information in the user information database at the time of posting, as described with reference to FIG. 30, or the on / off state of the secondary use permission button 501 selected at the time of posting, as described with reference to FIG. 32. Alternatively or additionally, for example, the secondary use permission button 501 may be displayed for each post on a screen listing threads and comments posted by a user, which is displayed by selecting the user's own post icon 32 in FIG. 12, allowing the on / off state of secondary use permission to be switched after the fact. Furthermore, an icon may be displayed for each piece of posted content, allowing the on / off state of secondary use permission to be switched after the fact, only on the user terminal 300 of the user who posted the content. This allows a user to change the information regarding whether or not secondary use is permitted for each piece of posted content after the fact, without deleting the post.

[0366] (Regarding secondary use permission settings for each type of content) The setting of secondary use permission described in the above embodiment with reference to Figures 28 to 32 may not apply to all content posted in a fan community, but may apply to only some of the content. For example, the setting may be possible depending on the type of content, or may be possible for content posted to a specific channel that is likely to be used secondary. Content that is likely to be used secondary may include, for example, a channel for collecting surveys or a channel dedicated to posting users' derivative works.

[0367] Furthermore, a user may be able to set whether or not to permit secondary use depending on the type of content on a user setting screen such as My Page. For example, it may be possible to set whether or not to permit secondary use for each channel, so that secondary use for channel X is permitted and secondary use for channel Y is not permitted.

[0368] (Regarding secondary use permission settings for each secondary user) In the above embodiment, the secondary use permission setting described with reference to Figures 28 to 32 and the like has been described as an example in which the administrator, talent, and the like are uniformly permitted or denied by turning the secondary use permission button 501 on or off. However, the present invention is not limited to this. It is also possible to set whether to permit secondary use for all those who make secondary use, or to permit secondary use individually only for specific special users. For example, secondary use may be permitted for talents designated as talents for whom secondary use is permitted, or talents selected in advance by a user as their favorite talent. In this case, the secondary use permission button 501 may be displayed on a user setting screen such as Figure 28(A) along with options such as for the administrator and talent, for the administrator only, for talents only, and for specific talents only, allowing selection.

[0369] Although the case where the person making secondary use is an administrator or a celebrity has been described, other general users may also be included in the persons making secondary use. In this case, secondary use by other general users may be prohibited, and settings may be individually made to permit secondary use for administrators and celebrities.

[0370] (Regarding indication of secondary use) For posted content that has been used by an administrator or a celebrity, etc., due to the secondary use permission setting described with reference to Figures 28 to 32 in the above embodiment, information suggesting that the content has been used may be reflected in the content. For example, for content that has been used secondary, a predetermined setting (e.g., operating a predetermined icon or setting a used flag) may be performed on the user terminal 300 operated by the celebrity or the administrator terminal 200 of the administrator, so that an icon indicating that the content has been used secondary may be displayed on the content that has been used secondary. This notifies the poster that the content has been used, which may increase the user's motivation in fan activities. Furthermore, the icon indicating the content has been used may be displayed on the user terminal 300 of the poster of the content, but not on the user terminals 300 of other users. This may prevent feelings of superiority or inferiority from arising between a user who posted content that has been used secondary and a user whose content has not been used secondary.

[0371] (Regarding the status of secondary use being permitted) 30 and 31 described in the above embodiment, the secondary use permission information updated to "permitted" by a user operation in steps S501 and S502 may be made identifiable to other users after a certain period of time has passed (for example, five minutes or one day) since the information was updated to "permitted." In other words, even if the secondary use permission button 501 is turned on by a user operation, the secondary use OK icon 701 may not be displayed on the posted content screen exemplified in FIG. 28(B) until a certain period of time has passed. This reduces the possibility that the user will mistakenly set the secondary use permission status to "permitted" and then cause secondary use (quotation) before performing an operation to cancel the change (such as turning off the secondary use permission button 501).

[0372] (Other examples of application of secondary use permission related processing) In the above embodiment, an example has been described in which the secondary use permission-related process described with reference to Figures 28 to 32 is executed on distribution server 100 that provides a fan community app. However, the present invention is not limited to this, and the secondary use permission-related process can be applied to a user-generated content (UGC) platform where users post comments, images, videos, etc. For example, on an image sharing platform, a user who posts may be able to set a message such as "Introduce on other media OK!" or "Free use of image OK!"

[0373] [Software implementation example] The various control blocks of the control unit of a computer such as a server or terminal in the above-described embodiments may be implemented by logic circuits (hardware) formed on an integrated circuit (IC chip) or the like, or by software using a CPU (Central Processing Unit). When implemented by software using a CPU, the computer equipped with the control unit includes a CPU that executes instructions from a program, which is software that implements each function; a ROM (Read Only Memory) or storage device (these are referred to as "recording media") in which the program and various data are recorded so as to be readable by the computer (or CPU); and a RAM (Random Access Memory) in which the program is deployed. The object of the present invention is achieved when the computer (or CPU) reads and executes the program from the recording media. The recording media may be "non-transitory tangible media," such as tapes, disks, cards, semiconductor memories, and programmable logic circuits. The program may also be supplied to the computer via any transmission medium capable of transmitting the program (such as a communication network or broadcast waves). Note that one aspect of the present invention may also be realized in the form of a data signal embedded in a carrier wave, in which the program is embodied by electronic transmission.

[0374] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0375] 1 communication system, 2 network, 100 distribution server, 200 administrator terminal, 300 user terminal, 400 external web service system

Claims

1. a program that allows an action received from a user terminal operated by each of a plurality of users to be reflected in the user terminal of each of the plurality of users so that the action can be recognized by each of the plurality of users; Computer, means for setting whether or not secondary use of an action received from a user is permitted in accordance with an operation from the user; A program that functions as a means for making it possible to reflect suggestion information that suggests that an action can be used for secondary purposes when the user who performed the action has permitted secondary use based on the user's settings.

2. A method for controlling a computer that performs processing to enable actions accepted from user terminals operated by a plurality of users to be reflected in the user terminals of the plurality of users so that the actions can be recognized by each of the plurality of users, a step of setting whether or not secondary use of the action received from the user is permitted in accordance with an operation from the user; and a step of enabling the reflection of suggestion information that suggests that the action is available for secondary use when the user who performed the action has permitted secondary use based on the settings of the user.

3. A system including a computer that performs processing to enable actions received from user terminals operated by a plurality of users to be reflected in the user terminals of the plurality of users so that the actions can be recognized by each of the plurality of users, means for setting whether or not secondary use of an action received from a user is permitted in accordance with an operation from the user; The system is provided with a means for enabling the reflection of suggestion information that suggests that the action can be used for secondary purposes when the user who performed the action has permitted secondary use based on the settings of the user.

Images