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 Art

[0002] In fan activities (so-called oshi activities) to support favorite targets of support such as people like talents or things, for example, fan users may post on SNS etc. feelings about fan activities or secondary creations such as fan art related to the target of support (see, for example, Non-Patent Document 1). In some cases, content posted by such fan users may be introduced by the talent etc. who is the target of support in their own video distribution or on SNS etc.

[0003] Also, the introduction of fan user-posted content by the talent etc. who is the target of support leads to the activation of communication between fans and the target of support. Therefore, in order for talents etc. to be able to smoothly use fan user-posted content for distribution etc., for example, the operator may describe in the secondary creation guidelines for content related to the target of support (such as character images etc.) that the operator may use secondary creations etc., so that fan user-posted content can be used.

Prior Art Documents

Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, if the rules allow the use of fan user-posted content, there is a risk of causing misunderstandings among users due to concerns about the usage purposes.

[0006] The present invention has been conceived in view of such circumstances, and provides a program, method, and system for facilitating secondary use while making it difficult for users to have misunderstandings.

Means for Solving the Problem

[0007] (1) A program according to an aspect of the present invention is a program (for example, a program stored in the storage unit 120, a program for providing content, etc.) that can reflect an action (for example, posting of content such as a thread or a comment) received from user terminals (for example, user terminal 300) operated by each of a plurality of users to the user terminals of each of the plurality of users so that each of the plurality of users can recognize it. A computer (for example, distribution server 100, user terminal 300) is Means (for example, account management unit 133, input information transmission unit 353, steps S601 to S604 in FIG. 30, etc.) for setting whether to permit the secondary use of an action received from a user (for example, an operator or a talent introducing the user's posted content in a video distribution or quoting it within the posted content) according to an operation by the user (for example, an operation of the secondary use permission / denial button 501 on the user setting screen in FIG. 28(A), an operation of the secondary use permission / denial button 501 at the time of posting content in FIG. 32, a modification example (regarding the change of secondary use permission / denial information for each content after posting), etc.). When the user permits secondary use based on the settings of the acting user (for example, in the user settings screen of FIG. 28(A), when the secondary use permission / denial button 501 is in the on state, in the user information database of FIG. 29(A), when "permission" secondary use permission / denial information is associated with the user, in the content database of FIG. 29(B) or the comment database of FIG. 29(C), when "permission" secondary use permission / denial information is associated with the thread or comment, etc.), means (for example, content management unit 132, account management unit 133, display control unit 352, step S607 of FIG. 30, step S607B of FIG. 31, etc. for the extraction of only posts with permitted secondary use in the modification example) is made to function as means for reflecting suggestion information (for example, information for displaying a secondary use OK icon 701 for each posted content in FIG. 28(B), referring to the extraction of only posts with permitted secondary use in the modification example, other aspects of the secondary use OK icon 701, etc.) indicating that the action is secondary useable.

[0008] According to such a configuration, since the setting of whether to permit the secondary use of an action can be performed according to a user operation, it is possible to smoothly perform secondary use while making it difficult to cause a misunderstanding that the action can be secondary used.

[0009] (2) In the above (1), the means for making the reflection possible does not reflect the suggestion information on the user terminals of users who do not satisfy a specific condition and reflects the suggestion information only on the user terminals of users (for example, special users in FIG. 5, operators, etc.) who satisfy the specific condition (for example, steps S606 - S607 of FIG. 30, steps S606 - S607B of FIG. 31).

[0010] According to such a configuration, it is possible to prevent the promotion of secondary use to users who do not satisfy a specific condition (for example, users with low need for secondary use, etc.) and the occurrence of unintended use or abuse.

[0011] (3) In the above (1), when setting information regarding the user in response to an operation from the user, the means for setting can be configured to enable setting whether or not to permit secondary use (for example, an operation on the secondary use permission / denial button 501 in FIG. 28(A) on a setting screen such as the user's my page in FIG. 8).

[0012] According to such a configuration, when setting information regarding the user, since it is possible to select whether or not to permit the action to be secondarily used, it becomes easy for the user to manage the state of permission / denial of secondary use of the action.

[0013] (4) In the above (3), the computer is functioned as means for managing action information for identifying an action received from the user (for example, storing a content management unit 132, content data 122, action information 123, etc.), when the means for managing determines that the user permits secondary use (for example, when "permit" secondary use permission / denial information is associated in the user information database in FIG. 29(A), when a post is made in an on state with the secondary use permission / denial button 501 on the post screen in FIG. 32, etc.), the action information received is managed as action information for which secondary use is permitted (for example, when the secondary use permission / denial information in the user information database in FIG. 29(A) is "permit" due to steps S601 - S602 in FIG. 30, the content posted is, in steps S603 - S604, associated with "permit" secondary use permission / denial information for each content and managed in the content database in FIG. 29(B), the comment database in FIG. 29(C), etc.), when reflecting the action specified from the action information for which secondary use is permitted (for example, when displaying the article ID "a3" in FIG. 29(B) on the user terminal 300), the means for enabling reflection can enable reflection of the suggestion information (for example, displaying the secondary use OK icon 701 in FIG. 28(B), steps S603 - S607 in FIG. 30, etc.).

[0014] According to such a configuration, it is possible to reflect the suggestion information based on the action information, and the processing load when reflecting the action can be reduced.

[0015] (5) In the above (3), the means for making it possible to reflect is, when reflecting the action received from the user (for example, when displaying the article ID "a3" in FIG. 29(B) on the user terminal 300), for the action from the user permitted for secondary use based on the settings of the user who is the source of the action (for example, the information on whether secondary use is permitted in the current user information database of FIG. 29(A) of the user), it is possible to reflect the suggestion information (for example, steps S605 to S607B in FIG. 31).

[0016] According to such a configuration, it is possible to reflect the suggestion information based on the user's settings when reflecting the action, and it becomes easier for the user to manage the permission status of secondary use regarding their own actions. Also, as an operator, since it is only necessary to manage the permission status of secondary use for each user, the management becomes easy.

[0017] (6) In the above (5), the means for setting can set whether to permit secondary use when setting information regarding the user in response to an operation from the user regardless of whether the action has been reflected (for example, based on the display request information in step S605 of FIG. 31, whether the content screen etc. is reflected on the user terminal 300 in steps S607B and S608, or regardless of whether it is in a state where it can be reflected), The means for making the reflection possible can update the suggestion information based on the settings of the user who is the source of the action even when reflecting the action received from the user (for example, even if the content screen on which the reuse OK icon 701 in FIG. 28(B) is displayed is being displayed on the user terminal 300, due to a reload operation or the like, based on the reuse permission / denial information updated in step S602 of FIG. 31, in steps S605 to S607B, the display / non-display of the reuse OK icon 701 can be updated according to the reuse permission / denial state of the current user. (Refer to the modification example (regarding the reuse permission / denial setting for each content type), (regarding the change of the reuse permission / denial information for each content after posting), etc.).

[0018] According to such a configuration, even if an action has been reflected to other users, it is possible to update the suggestion information according to the operation from the user, so that the convenience for the user can be improved.

[0019] (7) In the above (1), the means for setting can set whether to permit the reuse of the action according to the operation from the user when receiving an action from the user (for example, when posting a thread or a comment) (for example, display a reuse permission / denial button 501 on the posting screen in FIG. 32).

[0020] According to such a configuration, when an action is received (every time an action is taken), the permission / denial state of reuse can be set, so that the convenience for the user can be improved.

[0021] (8) In the above (1), the computer is In response to a switching operation from the user (for example, operating a predetermined icon on the user terminal 300), a first state capable of reflecting the action received from the user regardless of whether secondary use is permitted (for example, a state in which both posts permitted for secondary use and posts not permitted are displayed), and a second state capable of reflecting only actions permitted for secondary use among the actions received from the user (for example, a state in which only posts permitted for secondary use are extracted and displayed) are made switchable (for example, refer to (extraction of only posts permitted for secondary use in the modification example)).

[0022] According to such a configuration, since it is possible to reflect only actions permitted for secondary use, it becomes easy for the user to identify actions permitted for secondary use, and the convenience of users who perform secondary use can be improved.

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

[0024] According to such a configuration, by obtaining secondary use information, it may become easy for the user who has performed the secondary use operation to secondarily use the action.

[0025] (10) A method according to an aspect of the present invention is a method for controlling a computer (for example, the distribution server 100, the user terminal 300) that performs processing for making actions (for example, posting of content such as threads and comments) received from user terminals (for example, the user terminal 300) operated by each of a plurality of users reflectable on the user terminals of each of the plurality of users so that each of the plurality of users can recognize them, Steps (such as steps S601 to S604 in FIG. 30) for setting whether to permit the secondary use of an action received from a user (for example, an operator or a talent introducing the user's posted content in a video distribution or quoting it in the posted content, etc.) according to an operation by the user (for example, referring to the operation of the secondary use permission button 501 on the user setting screen in FIG. 28(A), the operation of the secondary use permission button 501 at the time of posting content in FIG. 32, a modification example (regarding the change of secondary use permission information for each content after posting), etc.). Steps (for example, step S607 in FIG. 30, step S607B in FIG. 31, a modification example (regarding the extraction of only posts for which secondary use is permitted), etc.) for enabling the reflection of suggestion information (for example, information for displaying a secondary use OK icon 701 for each posted content in FIG. 28(B), referring to a modification example (regarding the extraction of only posts for which secondary use is permitted), etc.) indicating that the action is available for secondary use when the user permits secondary use based on the settings of the user who performed the action (for example, in the user information database in FIG. 29(A) when the secondary use permission button 501 is in the on state on the user setting screen in FIG. 28(A), and the user is associated with secondary use permission information of "permit", in the content database in FIG. 29(B) or the comment database in FIG. 29(C), when the thread or comment is associated with secondary use permission information of "permit", etc.).

[0026] According to such a configuration, since the setting of whether to permit the secondary use of an action can be performed according to a user operation, it is difficult for a misunderstanding to occur that the action can be secondarily used. As a result, the secondary use can be smoothly performed.

[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 reflect an action (e.g., posting of content such as a thread or a comment) received from a user terminal (e.g., user terminal 300) operated by each of a plurality of users to the user terminals of each of the plurality of users so that each of the plurality of users can recognize it. Means (e.g., account management unit 133, input information transmission unit 353, steps S601 to S604 in FIG. 30, etc.) for setting whether to permit the secondary use of an action received from a user (e.g., an operator or a talent introducing the user's posted content in a video distribution or quoting it in the posted content, etc.) according to an operation by 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 at the time of posting content in FIG. 32, a modification example (regarding the change of secondary use permission information for each content after posting), etc.). When the user who performed the action permits secondary use based on the user's settings (e.g., in the user information database in FIG. 29(A) when the secondary use permission button 501 is in the on state on the user setting screen in FIG. 28(A) and the secondary use permission information of "permit" is associated with the user, in the content database in FIG. 29(B) or the comment database in FIG. 29(C) when the secondary use permission information of "permit" is associated with a thread or a comment, etc.), means (e.g., content management unit 132, account management unit 133, display control unit 352, step S607 in FIG. 30, step S607B in FIG. 31, a modification example (regarding the extraction of only posts for which secondary use is permitted), etc.) for reflecting suggestion information (e.g., information for displaying a secondary use OK icon 701 for each posted content in FIG. 28(B), a modification example (regarding the extraction of only posts for which secondary use is permitted), etc.) indicating that the action is available for secondary use.

[0028] According to such a configuration, since the setting of whether to permit the reuse of an action can be performed according to a user operation, misunderstanding that the action can be reused is less likely to occur. As a result, the reuse can be performed smoothly.

Brief Description of Drawings

[0029]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Mode for Carrying Out the Invention

[0030] Hereinafter, embodiments of the communication system according to the present invention will be described with reference to the drawings. It should be noted 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 reference numerals are given to the same elements in the description of the drawings, and repeated descriptions will not be repeated.

[0031] In the communication system according to the present invention, it is possible to provide a plurality of types of content associated with attributes to a user. The attributes include a plurality of types of first attributes (e.g., communities) and a plurality of types of second attributes (e.g., talents), and content information (e.g., the title of a news post, etc.) regarding the content associated with the attributes (e.g., a news post regarding a talent) can be displayed. The content information can be switched and displayed to any of a plurality of types of display states including a first display state (push filter off) in which the user can identify the content information associated with a community or the like pre-selected by the user by a switching operation from the user for a predetermined icon or the like, and a second display state (push filter on) in which the user can identify the content information associated with any of the communities or the like and talents pre-selected by the user.

[0032] In addition, the plurality of types of content provided in the communication system according to the present invention are provided via a fan community that is a gathering of users who support a specific target (e.g., a talent, etc.). Within the community space of the fan community, communication between users can be achieved by reflecting the actions taken by each user so that other users can recognize them. The users who use the community are associated with an evaluation history status that varies according to an external evaluation that is an evaluation from outside the user himself / herself. When an external evaluation is made on an action taken by a user within the community (e.g., content or comments posted by the user), the actions that the user can take within the community are controlled.

[0033] In addition, in the fan community of the communication system according to the present invention, for posted content (e.g., comments, fan art, etc.) posted by a user operation, it is possible to associate information indicating whether or not the user who posted the posted content permits secondary use of the posted content by the user operation. As a result, for example, it becomes easy for an operator, a talent supported by the fan community, etc. to obtain information on whether or not the user who posted the posted content permits secondary use, and it becomes easier for the talent, etc. to pick up the posted content in video distribution, etc. As a result, activation of communication between fans and talents can be achieved, and it becomes possible to produce an effective promotion effect of the fan community application.

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

[0035] The distribution server 100, the administrator terminal 200, and the user terminal 300 can each be communicatively connected via the network 2 and can transmit and receive information (data) bidirectionally. The network 2 is, for example, the Internet and is composed of an access network 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, an FTTH (Fiber To The Home), a CATV (Cable Television) network, etc.

[0036] In addition, 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 videos, texts, images, etc. by user submissions (e.g., Youtube (registered trademark), etc.), and provides a Web API (Application Programming Interface) that can supply information (e.g., text, image, video, posting date and time, account name, etc.) corresponding to access from other terminals such as the distribution server 100, the administrator terminal 200, and the user terminal 300 to the terminal. The external web service system 400 is a system operated and managed by a third party other than the administrator and operator of this communication system 1.

[0037] The distribution server 100 is a computer such as a workstation or a personal computer having a communication function, for example. The distribution server 100 manages a plurality of contents that can be provided to users and manages the communities where the contents are provided. The distribution server 100 provides the contents in response to requests from users via the network 2.

[0038] The contents provided by the distribution server 100 are managed and set for each type as will be described later with reference to FIG. 14. Contents are those that inform viewers of predetermined information and include the content of information such as videos, voices, texts, etc. The contents managed by the distribution server 100 are, for example, news and announcements articles by operators (administrators), user submissions (including comments), distribution videos provided by external web services obtained by using the Web API, etc. The contents can be provided to users by being displayed on the user terminal 300 via a medium such as a browser or a dedicated application for a smartphone. In addition, the medium through which the contents are provided also functions as a fan community that supports a predetermined support target.

[0039] The distribution server 100 stores in the storage unit 120 information such as text and images corresponding to the content that can be provided to the user, and sound information for outputting sound for displaying such information on the user terminal. Further, the distribution server 100 provides the user with content (service) 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 an access from the user terminal 300.

[0040] The administrator terminal 200 is used by an operator of a service providing company or the like. The administrator terminal 200 is, for example, a computer having an operation input function and a communication function such as a personal computer. The operator creates content (hereinafter also referred to as posting information) managed in the storage unit 120 of the distribution server 100 via the administrator terminal 200, and constructs, modifies, and updates display information regarding the display of the content. For example, an image is generated and constructed for displaying new content or the like on the user terminal 300, and an image of existing content or the like is changed and modified. Further, the operator sets and updates information managed in the storage unit 120 of the distribution server 100 via the administrator terminal 200. Also, in the administrator terminal 200, settings such as permission and restriction regarding actions on various contents of the user can be set.

[0041] In the present 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 function of one of these computers (for example, the distribution server 100) may be realized by a plurality of computers (for example, a plurality of servers).

[0042] The user terminal 300 is used by a user who views and experiences content. The user terminal 300 may be, for example, 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 user terminal 300, the user terminal 300 communicates with the distribution server 100 to receive content data of the content selected by the user. Further, based on the received content data, the user terminal 300 constructs, within the storage area of the user terminal 300, posting information of the content selected by the user among the content managed in the distribution server 100, and displays an image or text of the posting information. Thereby, via the user terminal 300, the user can specify and recognize content information.

[0044] In addition, the user terminal 300 receives an action operation on the displayed content or a content posting operation by the user himself / herself. The user terminal 300 transmits information corresponding to the operation on the terminal (for example, information for specifying an action or posting content) to the distribution server 100, and can reflect the action or posting content to a plurality of user terminals via the distribution server 100. The action operation includes, for example, a tap action (such as the so-called "like" function) indicating a favorable intention such as a favorable feeling or empathy for the content, a comment posting, etc. Hereinafter, actions by the user such as a content posting operation by the user himself / herself are also collectively referred to as an action. Further, it is also referred to as a favorable action including a tap action by the user and a favorable comment.

[0045] The users in the present embodiment include consumers who are general consumers (also referred to as general users or simply users), talents, famous people, etc. Talents include, for example, talents belonging to a service providing company (operating company), entertainers, actors / actresses, comedians, multi-talents, emcees, newscasters, singers, musicians, models, etc., including talented people in various genres. In addition, famous people include, for example, famous company managers or employees, sports players, e-sports players, famous scholars / cultural figures / tutoring teachers, famous students, etc., including famous people in various genres. Hereinafter, talents other than general users or famous people, etc. are also referred to as special users.

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

[0047] <Configuration of the Distribution Server> Next, the configuration of the distribution server 100 will be described. As shown in FIG. 2, the 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. The communication unit 110, the storage unit 120, and the control unit 130 are interconnected by a bus line.

[0048] The communication unit 110 is a communication interface including a NIC (Network Interface Card controller) for performing wired or wireless communication. The communication unit 110 communicates with other computers via the network 2.

[0049] The storage unit 120 is composed of a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an 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 posting information provided for each type of content, information regarding attributes, user information regarding users, etc.

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

[0051] The functional configuration of the control unit 130 will be described below. 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 transmission / reception unit 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 transmission / reception unit 131 refers to various management tables stored in the storage unit 120. The various types of information transmitted and received by the data transmission / reception unit 131 include, for example, information related to the content managed by the content management unit 132 and various notifications.

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

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

[0055] <Configuration of the administrator terminal> Next, the configuration of the administrator terminal 200 will be described. As shown in FIG. 3, the 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 and the like, an output unit 240 for outputting images, sounds, and the like, and a control unit 250 that controls the entire computer. The communication unit 210, the storage unit 220, the input unit 230, the output unit 240, and the control unit 250 are interconnected by a bus line.

[0056] The communication unit 210 is a communication interface including a NIC for performing wired communication 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 a RAM, a ROM, and the like. The storage unit 220 stores programs for executing various control processes (for example, a program for managing the content provided to users by the distribution server 100), various data, and the like.

[0057] The input unit 230 includes an input device for receiving input operations from the administrator (for example, a pointing device such as a touch panel, a touch pad, a mouse, etc., a keyboard, etc.). 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 composed of a CPU or the like. By executing the program stored in the storage unit 220, the control unit 250 controls the overall operation of the administrator terminal 200.

[0059] Hereinafter, the functional configuration of the control unit 250 will be described. 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 update unit 254.

[0060] The content setting unit 251 stores and updates information related to the content managed by the content management unit 132 of the distribution server 100 in response to an operation on the administrator terminal 200. Thereby, for example, information for specifying content, category classification related to the content, and information such as settings and edits related to the production when the content is provided can 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 related to the attributes stored as the attribute information 121 of the distribution server 100 in response to an operation on the administrator terminal 200. Thereby, for example, information related to attributes when a new attribute is added or when there is a change in the composition of the attributes can be stored and updated in the storage unit 120.

[0062] The action restriction setting unit 253 stores and updates information related to the authority to perform actions such as content posting actions and actions indicating reactions to content in the provided community space, which are managed as the action information 123 and the action authority information 124 of the distribution server 100, in response to an operation on the administrator terminal 200. Thereby, for example, addition and change of actions (actions) set for each evaluation history status of a user described later, and setting of individual action restrictions for users by the operator can be stored and updated in the storage unit 120.

[0063] The user evaluation information update unit 254 can perform external evaluations on users that can affect the evaluation history status for each user stored as account information 125 in the distribution server 100 according to operations on the administrator terminal 200, or can store and update the evaluation history status itself for each user. As a result, the evaluation history status for each user is changed by the evaluation from the operator, and the actions (actions) that the user can take based on the action authority information 124 are controlled.

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

[0065] The communication unit 310 is a communication interface including a NIC for performing 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 a RAM, a ROM, and the like. The storage unit 320 stores programs for executing various control processes (for example, a program for browsing content and the like), various data, and the like.

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

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

[0068] Hereinafter, the functional configuration of the control unit 350 will be described. 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 in the storage unit 320 information for displaying text and images (posting information) related to the content based on the content data. The posting information includes information for displaying on the user terminal 300 actions performed on other user terminals 300 with respect to the content.

[0070] The display control unit 352 causes the content information (for example, the title of the content article, etc.) related to the content stored in the storage unit 320 to be displayed so that the user can identify it based on the content data acquired by the information acquisition unit 351. For example, by displaying the title of a news article related to a talent on the user terminal 300, the user can recognize that it is content of news related to the talent.

[0071] Also, the display control unit 352 displays a UI (User Interface) image in a manner corresponding to the distributed content based on the program stored in the storage unit 320 (including, for example, a menu image that the user can select and an operation image that accepts operations).

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

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

[0074] <Regarding the content providing function of the fan community> (Overview of the fan community) Hereinafter, the fan community that enables viewing of the content provided by the distribution server 100 according to this embodiment will be described more specifically. The content provided by the distribution server 100 is provided by a dedicated application (program (for example, a program for a native application, etc.)) that operates on terminals such as smartphones and tablets. The dedicated application functions as a so-called fan community used by users who support a common target (for example, a talent, a character, a good, etc.). In this fan community, in addition to facilitating the fan activities of users by providing content related to the common target (making it viewable by users), not only can fans communicate with each other, but also the user's support target and the user can communicate with each other. Note that the provision of content is not limited to a dedicated application and may also be provided via a browser by a web application. Also, content may be provided via a fan community provided via a browser by a web application.

[0075] In this embodiment, the object of support can be various objects such as characters or items as long as the user can have affection, interest, concern, etc. towards them. Characters include, for example, real people such as talents or famous people (3D), and fictional existences such as anime characters or mascot characters (2D, 2.5D). In addition, the objects of support include items such as railways and animals.

[0076] (Specific examples of attributes in the fan community) Hereinafter, in this embodiment, an example will be described in which the object of support of the user is a talent, and the fan community is the fan community of the talent. In this embodiment, talents are classified into a large group (also referred to as the first attribute) consisting of a plurality of talents. Furthermore, the talents classified into the large group can also be divided into small groups (also referred to as the second attribute) composed of a smaller number of people than the large group. For example, a small group is a unit group consisting of a part of the talents belonging to the large group.

[0077] As the unit (attribute) for which the user who uses the fan community supports, it is possible to support not only one talent but also multiple talents, in units of small groups (units), or in units of large groups. For example, supporting (becoming a fan) in units of large groups is also called so-called box pushing. In the fan community in this embodiment, the user can set (select) the object to be supported by the user in advance for each preferred unit (each attribute).

[0078] Referring to FIG. 5, an example of the talent information database stored as the attribute information 121 in this embodiment will be used to explain the talents in the fan community in this embodiment. In this embodiment, talents are classified into groups classified as "Group 1 Affiliation". Group 1 Affiliation is a large group and is classified into, for example, Group A, Group B, and so on.

[0079] In each affiliated group 1, "talent ID" and "talent name" are associated as information for identifying the affiliated talents. Furthermore, each talent is associated with information for identifying the "affiliated group 2" to which each talent belongs. The affiliated group 2 is a small group composed of fewer people than the affiliated group 1. For example, it is "first-generation members", "second-generation members", etc. classified by the unit of the time of joining the group, or a group composed of a predetermined concept (for example, "Gamers" composed of talents mainly engaged in live game broadcasts).

[0080] Note that for affiliated groups, some talents may belong to multiple affiliated groups. Also, there may be talents who belong to affiliated group 1 but do not belong to any affiliated group 2. In addition, there may be an affiliated group 2 composed of talents belonging to different affiliated groups 1 (constituted across different affiliated groups 1. For example, group A and group B, etc.).

[0081] For example, a talent with talent ID "t1" and talent name "AAA" belongs to affiliated group 1 "group A" and belongs to affiliated group 2 "A - first-generation members". On the other hand, a talent with talent ID "t6" and talent name "FFF" belongs to affiliated group 1 "group A", but belongs to two groups, "A - third-generation members" and "A - Gamers", in affiliated group 2.

[0082] <Specific example of attribute selection process> (Screen example for attribute selection) Next, with reference to FIGS. 6 to 9, an example of a screen and a processing flow in which a user using a fan community selects 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 starting to use the fan community application or by requesting a setting change from the my page or the like. In the fan community in this embodiment, it is possible to participate in a community (first attribute) corresponding to the talent's affiliated group 1 (first attribute) described with reference to FIG. 5. FIG. 6(A) is an example of a participation community setting screen, and the user can select (set) a community (first attribute) to participate in from among a plurality of types of first attributes. For example, the participation community setting screen in FIG. 6(A) includes a participation community selection area 50. In the participation community selection area 50, icons for each community that the user can participate in are displayed. The user can select a participation community by performing a selection operation on the icon of the community that the user wishes to participate in. Also, a check mark or the like is displayed for the community for which the selection of participation has been made.

[0083] "Community A" corresponds to "Group A" in FIG. 5, and "Community B" corresponds to "Group B" in FIG. 5. That is, the plurality of types of first attributes include Group A, or Community A corresponding to Group A, Group B, or Community B corresponding to Group B. Note that, as displayed in FIG. 6(A) as "※ Always participating in Community P.", there may be a community that always participates regardless of the user's selection. For example, "Community P" does not correspond to the talent's affiliated group and is a community that provides notifications for the entire fan community.

[0084] Figure 6(B) shows an example of a favorite talent setting screen, where the user can select (set) their favorite talent (second attribute). The favorite talent setting screen in Figure 6(B) includes, as an example, a search window 51, an affiliated group selection area 52, a talent selection area 53, etc. The search window 51 enables searching for talents by inputting keywords. In the affiliated group selection area 52, icons of groups (affiliated groups 1, corresponding to communities) that can be supported in the fan community app are displayed. By selecting an icon, for example, talents can be displayed for each affiliated group 1. Note that in the affiliated group selection area 52, it may be possible to select all groups. Also, icons that can be selected and displayed for each unit may be displayed.

[0085] In the talent selection area 53, icons and names of each talent are displayed. However, as illustrated in Figure 6(B), they may be displayed, for example, in the order of each unit. By performing a selection operation on the icon, etc. of each talent, the favorite talent can be selected. Also, a check mark or the like is displayed on the icon of the selected talent.

[0086] Note that by operating the icon in the group selection area 52, it may be possible to select all the talents in the group as the favorite talent. Alternatively, an "all select" icon may be displayed, and all the talents displayed by the selection operation may be selectable. Also, not only for each talent, but it may be possible to select the favorite talent in units of units (units of affiliated group 2), and it may be possible to select the most favorite (the most favored talent among the favorite talents).

[0087] (Example of user information database regarding the selected attribute) FIG. 7 is an example of a user information database stored as account information 125. In the user information database, for each user, "user ID", "level", "cumulative points", "participating community", "favorite talent ID", etc. for identifying the user are associated. In the "participating community" and "favorite talent ID", information for identifying the attributes selected by the user on the setting screen illustrated in FIG. 6 is associated. For example, if the setting screen in FIG. 6 is the setting screen for user ID "u1" in FIG. 7, and the user ID "u1" has selected "Community A" as the participating community in FIG. 6(A) and has selected talents "AAA", "BBB", and "EEE" in FIG. 6(B), then for user ID "u1", the affiliated community is "Community A" and the favorite talent IDs are "t1", "t2", and "t5" corresponding to each talent. Hereinafter, the user ID will also be simply referred to as the user. Note that the "level" and "cumulative points" vary depending on the actions of the user within the fan community, but the details will be described later.

[0088] (Example of My Page for Each User) FIG. 8 is an example of a My Page screen for each user in the fan community. For example, due to a selection operation from the user for the My Page icon 16, the user terminal 300 acquires the information of the corresponding user stored as account information 125 and displays it on the user terminal 300. On the My Page screen, as an example, a name area 54, a user evaluation history status 55, favorite talent information 56, participating community settings 57, notification settings 58, settings and app information 59, etc. are displayed, and editing operations such as various setting changes can be performed.

[0089] The my page screen in Fig. 8 is a screen displayed on the user terminal 300 of the user "u1". In the name area 54, the name "userA" used within the fan community of the user "u1" and an icon image are displayed. The icon image can be, for example, the fan mark of a talent. A fan mark is something like a symbol used by a talent to represent themselves, and by fans using the same fan mark, it can publicly indicate which talent's fan they are. For example, it can be edited by tapping on the image editing icon displayed in the lower right corner of the icon image or selected and set on the initial setting screen.

[0090] In the user evaluation history status 55, the "level" and "cumulative points" associated with each user in the user information database in Fig. 7 are displayed so that the user himself / herself can confirm them. Details of the evaluation history status will be described later.

[0091] In the favorite talent information 56, the talents pre-selected by the user are displayed so that the user himself / herself can identify (confirm / recognize) them. For example, the icons and names of each talent are displayed so that the user "u1" can confirm the talents "AAA", "BBB", and "EEE" selected and set on the favorite talent setting screen in Fig. 6(B). Also, the favorite talents can be appropriately changed by operating on the editing icon displayed in the favorite talent information 56, which will display the screen in Fig. 6(B).

[0092] Also, when there is a selection operation for the participating community setting 57, the participating community setting screen in Fig. 6(A) is displayed, and the participating community can be appropriately changed.

[0093] When operations are performed on the notification settings 58 or the settings and app information 59, it is possible to perform push notification settings and various setting operations for the fan community app. Note that the my page in Fig. 8 only needs to be able to display and edit the user's own information. For example, regarding the participating communities, a list of the participating communities may be displayed on the initial screen of the my page (such as the screen displayed when the my page icon 16 is operated), similar to the favorite talent information 56. Also, the change screens for the participating communities and the favorite talents (Fig. 6) may be collectively displayed by operating a single edit icon.

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

[0095] In step S101, it is determined whether it is the first login. The first login is, for example, when the user first downloads and launches the fan community app in this embodiment, or when the user first uses the fan community app in this embodiment via a web browser, etc., which is the timing for performing attribute settings in the fan community for the first time. When it is determined in step S101 that it is the first login, in step S102, information for displaying an attribute selection screen is transmitted to the display unit of the user terminal 300. The attribute selection screen is, for example, the setting screen for selecting the participating communities and the favorite talents exemplified in Fig. 6, and may be incorporated into the flow of the tutorial at the first login (such as the basic explanation at the first login).

[0096] Next, in step S103, it is determined at the user terminal 300 whether an operation of selecting and confirming a participating community and a favorite talent has been performed. For example, among the participating communities displayed in the participating community selection area 50 in FIG. 6(A), the user performs a selection operation on the community he / she wishes to participate in. Also, in FIG. 6(B), among the talents displayed in the talent selection area 53, the user selects a favorite talent. Note that on the attribute selection screen of FIG. 6, an icon for performing a confirmation operation, such as a determination icon, may be displayed. When information (including information capable of specifying the selected participating community and favorite talent) transmitted by operating the determination icon or an icon such as "Next" is received, it may be determined that a confirmation operation has been performed. When it is not determined in step S103 that the selection and confirmation of the participating community and the favorite talent have been made, the determination is repeatedly made in step S103 until a selection and confirmation operation is performed.

[0097] On the other hand, when it is determined that the selection and confirmation of attributes have been made due to a selection operation on the determination icon or the like at the user terminal 300, the process proceeds to step S104, and the selected participating community and the selected favorite talent are stored as the selected attributes based on the information received from the user terminal 300. For example, the account management unit 133 associates the selected participating community and the selected favorite talent ID with the user "u1" and stores them as account information 125 to end the process.

[0098] Return to step S101. When it is not determined in step S101 that it is the first login, it is determined in step S105 whether there is a request to edit the participating community setting or the favorite talent setting. For example, when there is an operation on the edit icon of the favorite talent information 56 or an operation on the participating community setting 57 on the my page illustrated in FIG. 8 at the user terminal 300, it is determined that there is a request to edit.

[0099] In step S105, when it is determined that there is an editing request, in step S106, information for displaying a participating community setting or a setting editing screen for a favorite talent on the user terminal 300 is transmitted. As a result, for example, the attribute selection (setting) screen illustrated in FIG. 6 is displayed. On the other hand, in step S105, when it is not determined that there is an editing request for the participating community setting or the favorite talent setting, the process ends.

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

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

[0102] Return to step S107. When it is determined that the selection of the participating community or the favorite talent has not been made, it is determined whether a selection to return is made in step S109. For example, on the attribute selection screen of FIG. 6, a return icon 10 is displayed, and it is determined whether there is a selection operation for the return icon 10. When it is determined that there is a selection operation for the return 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 application. On the other hand, when it is not determined in step S107 that a selection to return is made, the process returns to step S107.

[0103] As a result, as will be described later, it becomes possible to extract and display information regarding attributes preselected by the user in the fan community. Therefore, the user can extract and acquire information regarding the favorite affiliated group 1 (first attribute) and further information regarding each talent (second attribute). Although an example in which the attribute selection process is executed by the distribution server 100 has been described, it may be executed by the user terminal 300.

[0104] <Example of content provision mode> (Overview of the content list screen) Next, an example of the content provision mode provided by the distribution server 100 via the fan community will be described with reference to FIGS. 10 to 14. FIG. 10 is an example of a home screen in the fan community application (hereinafter also simply referred to as the application) of the present embodiment. The home screen is displayed, for example, on the user terminal 300 when logging in to the application (for example, when the application is started) or when a selection operation is performed on the home icon 13 displayed at the bottom of the application. Information (title of the content article) for specifying the content displayed on the home screen of FIG. 10 mainly displays information for specifying the content posted in the community in which the user participates.

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

[0106] Also, 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 (for example, when the content is displayed as in FIG. 13). As described above, the home icon 13 is an icon for displaying the home screen of FIG. 10 when a selection operation is performed, and the community icon 14 is an icon for displaying a screen for each community such as FIG. 11(A) described later when a selection operation is performed. The notification icon 15 is an icon for displaying a screen where various notifications can be confirmed, such as when there is a post related to the selected attribute (for example, the talent set by the user as the favorite talent), a reply comment to the user's own post, or a mention to the user. The my page icon 16 is an icon for displaying the my page illustrated in FIG. 8 when a selection operation is performed.

[0107] (Overview of the Home Screen) At the upper part of the home screen in FIG. 10, a favorite filter 20, a language switching icon 21, etc. are displayed. The favorite filter 20 is a filter icon that can narrow down the displayed list of content headings so that only the headings of the content associated with the favorite talents preselected by the user are displayed. Details will be described later with reference to FIGS. 15, 16, etc. The language switching icon 21 is an icon that enables switching of the displayed language when a selection operation is performed, such as switching from Japanese to English.

[0108] The content provided by the distribution server 100 can be classified into any of a plurality of types of categories, and on the home screen, the content can be displayed for each classified category. On the content list (heading) screen of the home screen, for example, content headings 60 (content information) of content (also referred to as articles / threads) are displayed for each category such as a feature 61, a favorite topic 62, popular user posts 63, commemorative distribution 64, goods 65, etc. For example, the feature 61 displays notice articles and the like that the content setting unit 251 has set to inform all users, such as notices from the operator. The content displayed in the feature 61 is displayed regardless of which participating community and which favorite talents the user has selected. Also, when a selection operation is performed on the headings, images, etc. displayed in the feature 61, it may be configured to transition to a screen showing detailed information or an external website, etc.

[0109] Regarding the categories after the favorite topic 62, the content posted within the participating communities is displayed. The "community" in the app in this embodiment refers to the communities A to C corresponding to each affiliated group to which the talent belongs, exemplified in FIG. 6, and the community P in which the user is always in a participating state, etc.

[0110] (Regarding the community channel list screen) Referring to FIGS. 11 to 14, the details of the "Community" of the application in this embodiment will be described. FIG. 11(A) is an example of a content list (heading) screen of the "Community" (hereinafter, also referred to as the community screen or the channel screen). Each community is classified into channels for each type of topic as shown in FIG. 12. For example, the community screen in FIG. 11(A) is the screen of the "Official Channel" of the community "Community A" (corresponding to group A exemplified in FIG. 5), and the channel screen displayed in FIG. 11(A) is switched by a selection operation of a channel in the channel list screen in FIG. 12.

[0111] The channel list screen illustrated in FIG. 12 is displayed by, for example, a tap operation on the channel icon 12 displayed at the upper part of the application screen (for example, FIG. 10), or a flick operation (for example, a flick operation from the left side to the right side of the application screen). When the channel list screen in FIG. 12 is being displayed, the list screen can be closed by performing an operation when it is displayed (such as a selection operation on the channel icon 12 or a flick operation to return from the right side to the left side of the application screen).

[0112] On the channel list screen in FIG. 12, a community bar 81, a favorite confirmation icon 31, one's own post icon 32, a start icon 33, a notification setting icon 34, etc. are displayed. The communities displayed on the community bar 81 include the communities that the user has joined (selected by the user). By selecting the open / close icon displayed on the community bar 81, a channel list 82 for each community is displayed. For example, in the channel list 82 corresponding to Community A, each channel name is displayed. The selection bar 83 displayed beside each channel name indicates which channel is selected.

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

[0114] When there is a selection operation on the channel list screen of FIG. 12, it may switch to the community screen of FIG. 11(A). Also, as shown in FIG. 12, the channel list screen can be displayed so as to be superimposed on another screen. When the screen displayed below the channel list screen switches to the screen of the selected channel and an operation to close the channel list screen of FIG. 12 is performed, the community screen of FIG. 11(A) may be displayed in its entirety. Further, when a channel is selected in the channel list screen of FIG. 12, even when a selection operation is performed on the community icon 14 displayed at the bottom of the app screen, the selected channel is displayed as the community screen of FIG. 11(A).

[0115] The favorite confirmation icon 31 in Fig. 12 is an icon that enables the user to confirm the content (also referred to as a post) registered as a favorite in the account information 125 or stored in the storage unit 320 when a selection operation is performed. The self-post icon 32 is an icon that enables the user to confirm the content (thread created) posted by the user himself / herself in the community or comments made by the user himself / herself on the content (thread created) when a selection operation is performed. First, the icon 33 is an icon that enables the user to reconfirm the tutorial displayed at the first login, the usage method of the application, the precautions, etc. when a selection operation is performed. The notification setting icon 34 is an icon that enables a screen for setting various notifications (such as selection of information for which push notifications are sent) to be displayed when a selection operation is performed. For example, the same screen as when the notification setting icon 58 illustrated in the my page of Fig. 8 is selected may be displayed.

[0116] (Regarding the community screen) On the community screen in Fig. 11(A), similar to the home screen illustrated in Fig. 10, a recommended filter 20, a language switching icon 21, a sorting icon 22, a post icon 23, etc. are displayed. The sorting icon 22 is an icon that enables the order of the headings of the displayed content to be sorted in the order of new arrivals, popularity order (for example, in the order of having many like actions), etc. when a selection operation is performed. The post icon 23 is an icon that enables the user to post content (create a thread) in the community when a selection operation is performed.

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

[0118] The contributor 71 is displayed with the icon, name, etc. of the contributor of the corresponding content. For example, when the contributor is an operator or a special user described later, it is displayed together with an official mark or the like.

[0119] When the report icon 72 is selected, a screen as shown in FIG. 11(B) is displayed (for example, popped up on the current screen). By selecting the characters displayed in FIG. 11(B), the user can, for example, report to the operator the content that makes the user feel uncomfortable, an operation to make it non-displayed on the user terminal 300, an operation to block the content contributor itself within the fan community app (so that actions such as posts of the user who has been blocked are not displayed on the user's own user terminal 300 after the operation), and the like. Note that operations such as non-display and block cannot be performed on the operator or special user (content contributed by them), and may be operations that can only be performed on other general users.

[0120] The favorite icon 73 is an icon that enables saving so that the user can check the posts they like later. For example, when the favorite icon 73 is selected, the user information database of FIG. 7 stored as the account information 125 is updated and stored in association with the article ID of the post on which the favorite icon 73 is operated. As a result, the user can check the favorite posts when the favorite confirmation icon 31 in FIG. 12 is selected.

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

[0122] Furthermore, for the content heading 70, if the posted content is posted together with an image, the image 75 is displayed. If there are comments on the content, comments (for example, the latest comments or a part of the most popular comments, etc.) are displayed in the picked-up comment 76. Also, the number of comments on the content is displayed in the comment number 77, and the number of tap actions on the content is displayed in the tap action number 78. The number of tap actions on the content is, for example, the total number of tap actions made by all users on the heart icon 708 displayed together with the tap action number 78 in the content headings (60, 70), or the icon 708 displayed together with the tap action number 78 displayed on the content screen of FIG. 13 described later.

[0123] In addition, the users who use the fan community app include special users. When there are comments or tap actions from special users, it is possible to display that there have been comments or tap actions from special users as a special action 79 together with the icons of special users within the content heading 70. A special user is, for example, a user corresponding to the talent himself / herself exemplified in FIG. 5. Therefore, by displaying the special action 79, the user can recognize that there have been actions such as comments or tap actions from the talent himself / herself. Thereby, in the fan community app, the communication with the object being supported can be promoted, and the user satisfaction can be increased.

[0124] For the special action 79, icons corresponding to each talent are displayed, and when there is a comment by a talent, an icon that can be inferred to have a comment, such as a speech bubble mark, and when there is a tap action by a talent, an icon that can be inferred to have a tap action, such as a heart mark, are displayed. For example, in the content heading 70a on the community screen of FIG. 11, a special action 79 indicating that there have been actions from three talents is displayed. Since speech bubble marks and heart marks are displayed on the icons of the talents shown on the left and in the center, it is shown that there have been comments and tap actions. On the other hand, for the talent shown on the right, only a heart mark is displayed along with the icon, indicating that only a tap action has been taken without a comment.

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

[0126] FIG. 13 is an example of a content screen displayed when the content heading 70a is selected from the contents displayed in FIG. 11(A), and is an example of a display screen of the content itself (the post itself) which is the content of the content heading 70a. Note that even on the home screen of FIG. 10, when the same content is displayed, the content screen of FIG. 13 is displayed by a selection operation on the corresponding content heading 60 on the home screen.

[0127] On the content screen of FIG. 13, a return icon 10b is displayed at the top, and the poster 71, a report icon 72, a favorite icon 73, the number of tap actions 78, the category 85, the content 74b, related talents 88, and the special action 79, etc. are displayed. Also, when there is a comment on the content, the comments are listed and displayed at the bottom. For the list display of comments, a comment number 77b indicating the number of comments, comments 87 which are each comment, a comment posting field 84 for the user to post a comment, etc. are displayed.

[0128] When there is a selection operation on the return icon 10b, return to the screen that the user was displaying until immediately before. For example, if the user has transitioned to the content screen from the community screen in FIG. 11(A), return to the community screen in FIG. 11(A), and if the user has transitioned from the home screen in FIG. 10, return to the home screen in FIG. 10.

[0129] Category 85 is displayed with the associated category name when a category is associated with the content. In content 74b, the posted text information such as the title and description of the content is displayed.

[0130] Related talent 88 is displayed when a talent in FIG. 5 is associated with the content, and icons and names of the associated talents are displayed. Special action 79 is a display for indicating that the content has an action from a special user corresponding to the talent in FIG. 5 when there is an action from the special user with respect to the content.

[0131] Each comment 87 displays a poster 71b who displays the comment poster, a report icon 72b that enables reporting, hiding, etc. of the comment as shown in FIG. 11(B), a reply icon 86 that enables replying to the comment, a reply list 89 that displays a list of replies, etc. Note that the user's own icon may be displayed in the comment posting field 84.

[0132] Each comment 87 may have its display mode changed by the poster. For example, comment 87a is a comment by a special user (AAA himself) corresponding to the talent "AAA" illustrated in FIG. 5. For example, the display order of the comment list at the bottom of the content screen in FIG. 13 may be set to be displayed at the top, or the color may be changed so as to be distinguishable from comments by other users (the display mode may be made different). This can promote communication between users and talents in the fan community and improve user satisfaction.

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

[0134] "Channels" are classifications by topic, and the screens of each channel can be selected and displayed by a selection operation on the channel list 82 illustrated in FIG. 12. For example, the "official channel" is a channel where official announcements from the operator are posted, and the "Group A chat" is a channel themed on chats about "Group A" in the affiliated group 1 in FIG. 5 corresponding to "Community A". Also, "Highlights" is a channel themed on sharing links to recommended highlight videos of users (for example, videos that have been posted on a video distribution site and a part of which has been clipped from the video already posted on the video distribution site). "Past recommendations" is a channel themed on recommending, for example, videos related to Group A (such as past posted videos of affiliated talents). When a selection operation is performed on "All channels" in the channel list 82 in FIG. 12, all the channel content in FIG. 14 will be displayed together. Also, these channels are just examples, and for example, a temporary special channel may be provided.

[0135] "Submission Permission" is information regarding users who have the permission to submit content in each "channel". For example, for the "Official Channel" and "Past Recommendations", submissions can only be made from official accounts (such as special users like operators or talents). Submissions from official accounts can be made using a user ID that can be identified as an official account, even if they are submissions from an administrator terminal 200 or a terminal with the same configuration as a user terminal 300. Also, for "Group A Chitchat" and "Clip", all users can submit. For example, in the channel list 82 in Fig. 12, official marks are displayed for channels where submissions can only be made from official accounts, and speech bubble marks or the like are displayed for channels where all users can submit. This allows users to easily identify whether a channel allows submissions or not.

[0136] "Article ID" is an ID that identifies each piece of content and is assigned to each piece of content. Also, for each "Article ID", a "Category", "Submitter ID", and "Talent ID" are associated.

[0137] "Category" is a category that can be associated when content is submitted. For example, it can be associated to easily recognize what kind of theme the content itself is, such as "Event", "Goods", "Distribution / Video", "Fan Art", "Clip", "Music", "Special Distribution", etc. When a "Category" is associated, the category name will be displayed in the category 85 in the example of the content screen in Fig. 13.

[0138] "Submitter ID" is an ID that identifies the submitter of the content.

[0139] The "talent ID" is the talent ID of the related talent associated at the time of content posting among the talent IDs stored in the talent information database of FIG. 5. Thus, in this embodiment, when posting content, the poster can associate related talents according to the content of the content, and can store the "talent ID" associated for each content. That is, each content data is stored together with the meta information of the talent.

[0140] For example, for article ID "a1", category "event" is associated, the poster is "ou1", and talent IDs "t1", "t2", "t6", "t14" are associated. The aforementioned FIG. 13 is a display example of article ID "a1", and for poster 71, the name "Staff S" corresponding to user ID "ou1" and the official mark indicating that it is an official account are displayed. Also, in category 85, the category "event" associated with article ID "a1" is displayed.

[0141] For related talent 88, the icons and names of talents "AAA", "BBB", "FFF", "MMM" corresponding to the talent IDs "t1", "t2", "t6", "t14" associated with article ID "a1" are respectively displayed. Thus, since related talents can be set at the time of posting, related talents can be displayed for the content, and users can easily identify which talent the post is about. Note that related talent 88 may also be displayed in content heading 70 of the community screen illustrated in FIG. 11(A).

[0142] In this way, related talents can be associated with the content. Therefore, if the related talents include the user's pre-selected favorite talent, the distribution server 100 can notify the user of the posting related to the favorite talent by push notification based on the information in the user information database stored as the account information 125. For example, when there is a posting of content in which the favorite talent is associated with the related talent, or at every elapse of a predetermined time (e.g., every 5 minutes, every 15 minutes, etc.), the user is pushed a notification that there is a posting of content in which the favorite talent is associated with the related talent. When a push notification is received, by performing an operation on the push notification from the user, it is possible to transition to the content screen (e.g., Figure 13, etc.) of the content associated with the favorite talent. When there is a posting of content in which the favorite talent is associated with the related talent means when the content title (60, 70) of the content is displayed on the home screen of Figure 10 or the community screen of Figure 11(A).

[0143] Note that the category and the related talent can be arbitrarily set by the poster at the time of content posting, and the content can be posted without association. For example, a content without a related talent associated like the article ID "a99" may be posted within community A, and in this case, only community A (the first attribute) is associated with the content.

[0144] (Specific example of the home screen) Returning to FIG. 10, the details of the content displayed on the home screen will be described. On the home screen for each user terminal 300, among the content databases illustrated in FIG. 14 stored as content data 122, the content stored in the content database corresponding to the "participated communities" associated in the user information database illustrated in FIG. 13 stored as account information 125 is displayed. That is, for the categories after the recommended topic 62 on the home screen for each user, only the content headings of the content posted within the communities the user has participated in are displayed. For example, if the communities preselected in FIGS. 6, 9, etc. are "Community A" and "Community B", the content posted in "Community A", "Community B", and "Community P" which is always in the participation state is collectively displayed on the home screen. Note that if there is no community that is always in the participation state, the content posted within the communities preselected by the user is displayed on the home screen. On the other hand, the content posted in the "Community C" that the user has not participated in is not displayed. Also, for the categories after the recommended topic 62, the content headings 60 displayed change according to the on / off operation of the recommended filter 20 described later.

[0145] In any category, the content that can be displayed on the home screen may be one, or the content headings 60 of the latest predetermined number (for example, 2, 5, 7, etc.) of contents may be displayed. Alternatively, the content headings 60 of a predetermined number of contents in the order of popularity may be displayed. Also, the content headings 60 for each category may be switched so that the displayed headings are changed by performing a left or right slide operation or the like on the touch panel or the like of the user terminal 300. For example, by performing an operation (such as a flick operation) of sliding the content heading 60 (for example, the latest date) displayed in the commemorative distribution 64 of FIG. 10 to the left, the content heading 60 with an older date may appear from the right side of the screen. Also, for example, it may be displayed only halfway on the right side of the screen and may not appear unless a slide operation is performed.

[0146] Note that in the content headings 60 of any category on the home screen, when a talent in FIG. 5 is associated with the content, a related talent 88 that displays the icon, name, etc. of the associated talent may be displayed.

[0147] Also, in the favorite topic 62, a predetermined number of contents associated with the favorite talent preselected by the user, such as those illustrated in FIGS. 6 and 9, among the contents posted within the community in which the user participates, are displayed. For example, in the favorite topic 62 of a user who participates in "Community A" and has selected the talent "AAA" as the favorite talent, among the contents stored in the content database of Community A in FIG. 14, the contents associated with the talent ID "t1" corresponding to the talent "AAA" are extracted and displayed.

[0148] Among the popular user submissions 63, a predetermined number of contents that are considered popular among the contents submitted by general users other than the official accounts of the communities in which the users participate are displayed. For example, they may be in the order of the most number of favorable actions (tap actions and / or comments), or in the order of high engagement rate (such as contents with a high ratio of favorable actions to the number of views).

[0149] In addition, among the contents displayed on the home screen, there may be a category in which the contents associated with a specific category among the contents stored in the content database are displayed. For example, in the commemorative distribution 64, the contents associated with the category "commemorative distribution" among the contents stored in the content database are displayed, and in the goods 705, the contents associated with the category "goods" are displayed. Note that there may be a category in which only the submissions of a specific channel of a predetermined community are displayed. For example, there may be a category in which the latest predetermined number of content headings 60 submitted to a specific channel of "Community P" are displayed. Also, these categories displayed on the home screen are just examples, and a temporary special category may be provided.

[0150] Note that the favorite topic 62 on the home screen is preferentially displayed at the top among the categories that can be displayed on the home screen, excluding the feature 61. This makes it easier for the user to identify the information of the favorite talent. However, it is not limited to this, and the favorite topic 62 may be preferentially displayed at the top including the feature 61. Alternatively, there may be other categories that are preferentially displayed over the favorite topic 62. The operator can display them in the order of the categories that the operator wants the user to recognize.

[0151] Also, the content displayed in the content heading 60 of the favorite topic 62 may overlap with the content displayed in the content headings 60 of other categories after the favorite topic 62, or it may be such that if it is displayed in the favorite topic 62, it is not displayed in the content headings 60 of other categories. Note that the favorite topic 62 is not displayed for a user who has not selected any talent as a favorite talent in advance.

[0152] (Specific example of content attribute extraction process for selected attributes) Next, referring to FIGS. 15 and 16, a filter function for narrowing down the display of content associated with the favorite talent (second attribute) preselected by the user will be described. In the fan community application in this embodiment, the content displayed on the user terminal 300, in addition to narrowing down to the community (first attribute) that the user has preselected to participate in, since each content data is stored together with the meta information of the talent, further narrowing down to the favorite talent (second attribute) preselected by the user can be performed when a predetermined condition based on the user's intention is satisfied.

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

[0154] FIG. 15 is an example of a screen when the favorite filter 20 is in the on state and the off state on the content screen of FIG. 11(A). FIG. 15(A) is an example of a screen when the favorite filter 20 is on and the narrowing down to the favorite talent preset by the user is effective. FIG. 15(B) is an example of a screen when the favorite filter 20 is off and the narrowing down to the favorite talent preset by the user is not effective.

[0155] FIG. 15 is assumed to be an example of a screen displayed on the user terminal 300 of the user "u1" in FIG. 7, for example. In FIG. 15(A), since the favorite filter 20 is on, only the content associated with the talents previously selected by the user "u1" as favorite talents is extracted. That is, in the user information database stored as the account information 125, since 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", only the content associated with any of the talent IDs is extracted from the content information database stored as the content data 122. For example, the content of the article ID "a1" associated with the talent IDs "t1" and "t2" in the content information database of community A in FIG. 14, and the content (content headings 60, 70) of the article ID "a7" associated with "t5" are displayed.

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

[0157] (Example of the flow of attribute extraction process) Next, with reference to FIG. 16, the flow of the attribute extraction process for extracting content related to attributes preselected by the user will be described. FIG. 16 is a diagram for explaining the 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 to the push filter 20, etc.).

[0158] In step S201, it is determined whether there has been a content display request operation from the user terminal 300. The display request operation includes an operation to cause the user terminal 300 to load display data and a selection operation to turn the push filter 20 on or off when a predetermined condition is satisfied. The operation to cause the user terminal 300 to load display data includes, for example, logging in to the application (inquiring to the server at the timing of opening the application), a reload operation (reloading operation), or a selection operation to a home icon 13 of the application screen, a community icon 14, a channel displayed in the channel list 82 of FIG. 12, etc. The satisfaction of the predetermined condition is, for example, that the user switches the icon of the push filter 20 displayed on the user terminal 300 by a tap operation.

[0159] If it is determined in step S201 that there has been no display request operation, the process ends. On the other hand, when it is determined in step S201 that there has been a display request operation from the user terminal 300, it is determined in step S202 whether the push filter is on. In this embodiment, the default setting of the push filter 20 is off. Therefore, at the timing of logging in when the application is started, etc., or on the content screen or home screen of the channel that is first displayed after the application is started, the push filter 20 is off. In this case, since it is not determined in step S202 that the push filter 20 is on, the process proceeds to step S203.

[0160] In step S203, information regarding the participating community selected by the user of the user terminal 300 that is the source of the display request operation is extracted, transmitted to the user terminal 300, and the process ends. The selected participating community refers to the "belonging community" for each user that is stored as account information 125 by being pre-selected by the user illustrated in FIGS. 6(A) and 9, and when there is a community that is always in a participating state, the community that is always in a participating state is included. For example, for the user "u2" in FIG. 7, the user participates in "Community A" and "Community B". Therefore, in step S203, on the home screen of the user terminal 300 of the user "u2", the content posted within "Community A", "Community B", and the always participating "Community P" is displayed, and on the channel list screen in FIG. 12, the community bars 81 of "Community A", "Community B", and "Community P" are displayed.

[0161] Return to step S202, and when it is determined that the recommended filter is on, proceed to step S204. For example, when a selection operation to turn on the recommended filter 20 is performed, it is determined that there is a display request operation in step S201, and it is determined that the recommended filter is on in step S202. Also, when a reload operation is performed on the community screen or the home screen of a channel for which an operation to turn on the recommended filter 20 has already been performed after the application is started, or when returning to the community screen or the home screen where the recommended filter 20 is on after displaying the content screen in FIG. 13 while the recommended filter 20 is on, the state where the recommended filter 20 is on is stored (stored in the storage unit 120 or the storage unit 320), it is determined that there is a display request operation in step S201, and it is determined that the recommended filter is on in step S202.

[0162] In step S204, among the selected participating communities, information regarding the selected favorite talent is extracted and transmitted to the user terminal 300 to end the process. For example, if the user is "u2", only the content associated with the talent IDs "t2", "t3", "t4", "t7", "t8" among the content posted in "Community A", "Community B", and "Community P" is extracted and will be displayed on the content screen of the channel or the home screen. On the home screen, for categories after the favorite topic 62 (the feature 61 in FIG. 10 and categories other than the favorite topic 62), the content headings 60 of the content associated with the favorite talent pre-selected by the user through participating in the community and the selection operation on the favorite filter 20 will be displayed.

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

[0164] In addition, even for content posted by a talent different from the favorite talent or content with a talent different from the favorite talent as the main subject (main character), if the favorite talent pre-selected by the user is associated with the talent associated with the content, by turning on the favorite filter 20, content headings (60, 70) related to a talent different from the favorite talent will be displayed on the home screen of FIG. 10 or the community screen of FIG. 11(A). For example, assume that the content posted by the talent "AAA" corresponding to the content heading 70c in FIG. 11(A) is content related to the event of the birthday of the talent "AAA". However, assume that the talent "BBB" is scheduled to participate (also referred to as a collaboration) in the birthday event of "AAA", so "BBB" is set as the related talent. Then, in the content database, the talent ID "t2" corresponding to the talent "BBB" will be associated with the article corresponding to the content heading 70c. As a result, even when the favorite filter 20 is turned on in the user terminal 300 of a user who has not selected the talent "AAA" as the favorite talent, the content heading 70c related to the birthday event of the talent "AAA" will be displayed. As a result, even if it is information that might be overlooked as not being related to the favorite talent at first glance, the user will not miss information related to the favorite talent.

[0165] Note that even if the favorite filter 20 is not in the on state (regardless of 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 the favorite talent individually, the user can recognize who in the group is related to the content, and the interest will be improved.

[0166] (Specific examples of association of categories, talents, etc. by user posts) Next, with reference to FIGS. 17 and 18, a specific example of user posting processing when content is posted from a user will be described. FIG. 17 shows an example of a user posting screen. For example, when a content screen of a channel in which the "posting permission" is set to "user" in the community content database of FIG. 16 is displayed, it is displayed by selecting the posting icon 23 illustrated in FIG. 11(A). Note that for channels where the posting permission of an official channel or the like allows only official accounts to post, a user without permission may not be able to select the posting icon 23 on the content screen. For example, the display mode may be changed, such as being displayed in gray, or the posting icon 23 itself may not be displayed.

[0167] FIG. 17(A) is a screen displayed when the posting icon 23 is selected on the content screen of the channel "Group A Chat". FIG. 17(A) displays a title, an input field for the main text, an image icon 37, a next icon 38, and the like. When the image icon 37 is selected, an image stored in the user terminal 300 can be uploaded. When the next icon 38 is selected, the screen transitions to the screen of FIG. 17(B). Note that it may not be necessary to proceed to the next step if the title and the main text have not been input. Instead of inputting the main text, if an image has been uploaded, it may be possible to proceed to the next step. This is to avoid a situation where empty posts are scattered.

[0168] On the screen of Fig. 17(B), it is possible to select a category associated with the content to be posted and related talents. For example, when the category bar 39 is selected, as illustrated in Fig. 17(C), the category list 39b opens. The user can select any category from the category list. Note that only one category may be selectable, or multiple categories may be selectable. When the 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 (the talent to be associated) can be selected. Note that the selection of related talents is not limited to one person, and multiple people can be selected. If a selection operation is performed on the posting icon 41, the content is posted to "Group A Chat".

[0169] Also, in the fan community app in this embodiment, as illustrated in Fig. 11 etc., when a talent who is a special user as shown in Fig. 5 performs a reaction such as a comment or a tap action, a special action 79 is displayed, and the user is notified by a push notification to that effect (for example, a message that can be directly sent to the mobile terminal owned by the user and installed with the app). Also, the push notification due to a reaction such as a comment or a tap action by a talent who is a special user may be set to be notified regardless of the user type if there are comments or tap actions on the user's own post, even if the special user is not pre-selected by the user as a favorite talent. Also, even if the user has not pre-set a favorite talent, if the special user performs a reaction such as a comment or a tap action in the fan community, it can be set so that the fact is push-notified to the 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, it may be displayed on a content screen or the like, and the user may be push-notified to that effect. On the other hand, it is also assumed that the special user may accidentally perform a reaction operation. Therefore, in this embodiment, an action cancellation time is provided after the special user performs a tap action or the like, and when the action has not been cancelled after the cancellation time has elapsed, the reflection of the special action 79 on the user terminals of other users, push notifications, etc. are made, and within the action cancellation time, the target action can be cancelled in response to a cancellation operation from the special user. As the action cancellation time, for example, 5 minutes or the like can be set after the talent performs a reaction operation such as a tap action. This enables cancellation before other users are aware that the special user who has a great influence due to a reaction such as a comment or a tap action has accidentally performed a reaction operation.

[0171] Also, the push notification for notifying that a special user such as a talent has performed a tap action or the like may be made by the voice message of the talent who performed the action.

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

[0173] In step S301, it is determined whether the posting icon has been selected. For example, it is determined whether a selection operation has been performed on the posting icon 23 on the content screen such as in Fig. 11(A). When it is determined that the posting icon 23 has not been selected, the process ends. On the other hand, when it is determined that the posting icon 23 has been selected, in step S302, it is determined whether the channel to be posted to is a channel where user posting is permitted. For example, if it is the channel "Group A Chat" or "Clip" in Fig. 14, since posting is permitted for all users, in step S303, the posting screen in Fig. 17(A) is displayed. Thereby, for example, character information can be input or an image can be attached by operating on the image icon 37.

[0174] On the other hand, when the content screen when "All Channels" is selected in the channel list 802 in Fig. 12 or the content screens of the channels "Official Channel" and "Past Recommendations" are being displayed, since posting is permitted only for official accounts, it is not determined in step S302 that it is a user posting permitted channel, and the process ends.

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

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

[0177] When it is determined in step S305 that character input has been completed, in step S307, a category selection screen or the like is displayed. For example, it is a screen on which categories and related talents in FIG. 17(B) can be selected.

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

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

[0180] When it is not determined in step S309 that a related talent has been selected, or after the related talent is associated in step S310, it is determined in step S312 whether a post confirmation operation has been performed. For example, it is determined whether there is a selection operation for the post icon 41 in FIG. 17(B). When it is determined in step S312 that a post confirmation operation has been performed, in step S313, the post information (for example, information specifying the input character information, attached image information, selected category, selected related talent, ID of the poster, etc.) is transmitted to the distribution server 100 for processing. Thereby, for example, in "Group A Chat", when the category "event" is selected and the related talent "DDD" is selected, in the distribution server 100, it is stored like the article ID "a4" illustrated in FIG. 14.

[0181] Return to step S312. When it is determined that there has been no post confirmation operation, it is determined whether the selection to close has been made in step S314. The selection to close is, for example, a selection operation on the close icon 35 in the screen of FIG. 17(B). When it is determined in step S314 that the close option has been selected, the process ends.

[0182] On the other hand, when it is determined in step S314 that the selection to close has not been made, it is determined whether the selection to go back has been made in step S315. For example, it is a selection operation on the back icon 36 in FIG. 17(B). When it is determined in step S315 that the go back option has been selected, return to step S303 and return to the display of the character input post screen in FIG. 17(A). Thereby, the information of the characters and images input on the post screen before the selection of the next step in step S304 can be re-edited. On the other hand, when it is determined in step S315 that the go back option has not been selected, continue to display the category selection screen in step S307. Although an example in which the user post process is executed on the user terminal 300 has been described, it may be executed on the distribution server 100 and the display information may be transmitted to the user terminal 300.

[0183] <Action control function based on user evaluation within the fan community> (Overview of the action control function) Next, the behavior control function based on the evaluation of users within the fan community of this embodiment will be described. In the fan community of this embodiment, users themselves can also post content within the community and share it with other users. In this way, while the community is activated by promoting communication with other users, if there are no restrictions on the actions that users can take, users who post content that may make other users feel uncomfortable may run wild, which may deteriorate the public order and atmosphere within the community. Therefore, a level serving as an index such as a credit level and an honesty level is determined for each user, and the actions that can be taken within the community are changed according to the level. In this embodiment, according to the actions taken by a user within the community, an evaluation from an external source different from the user himself / herself is made, so that the evaluation history status of the user is updated, and according to the evaluation history status, the actions that can be taken within the community are changed. As a result, the actions that users with high indexes such as credit levels and honesty levels can take increase, and restrictions are imposed on the actions that users with low indexes can take. That is, by taking actions that are acceptable within the fan community, the evaluation history status fluctuates.

[0184] (Overview of the change in the user's level) The "level" of each user is stored in association with the user ID as exemplified in the user information database of FIG. 7. The "level" fluctuates according to the "cumulative points". The "cumulative points" fluctuate according to the external evaluation described later. For example, if the initial setting has the user level at 1 and the cumulative points reach 10, the level becomes 2. To rise from level 2 to level 3, a larger number of points than the number of points required to rise from level 1 to 2 are needed. For example, when the cumulative points reach 21, the level becomes 3. In this way, as the level rises, the number of points required increases, and it becomes more difficult to raise the level. Also, since the "cumulative points" may decrease according to the external evaluation, for example, when the cumulative points of a user at level 2 drop below 20, the level drops from 2 to 1.

[0185] In addition, each user can check their own "level" and "accumulated points" in the user evaluation history status 55 on the my page exemplified in FIG. 8. As a result, the user can try to take actions that will increase their level. On the other hand, the "level" and "accumulated points" of other users cannot be checked. In this way, by not disclosing one's own level to other users, it is possible to prevent users with a low level in the community from feeling ashamed and users with a high level from acting arrogantly. Note that either the "level" or the "accumulated points" may be displayed on the my page.

[0186] (Actions that can be taken according to level) With reference to FIGS. 19, 20, and 21, actions that can be taken by the user in this embodiment according to level will be described. FIG. 19 is a table showing examples of action contents permitted (possible) according to level. For example, it is divided into levels "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 range are stored as action authority information 124 in the distribution server 100 and the like.

[0187] "Specific actions", which are actions whose execution is controlled according to level, include, for example, "no restriction on posting links", "creation of a project plan", "invitation of a moderator", "creation of a community", etc. "No restriction on posting links" means that when a user posts content in the community, there is no restriction on the URLs that can be posted, and the restriction is lifted for users with a level of 60 or higher. In addition, the content posted by a user without the restriction on posting links is also reflected on the user terminal 300 of users with a level of 59 or lower. That is, for users with a level of 59 or lower, even if the content contains links whose posting is restricted, if the content is posted by a user with a level of 60 or higher, the user with a level of 59 or lower can view (including the operation of accessing the link) the content including the link.

[0188] "Community planning creation" refers to the right to launch a plan (event) within a community, which can be created by users with a level of 80 or above. For example, it is possible to launch event plans such as so-called offline meetings where people gather in a real or virtual space at a predetermined date and time, or questionnaire plans. That is, it becomes possible to take actions as a leader. Also, even users with a level of 79 or below can participate in plans created by users with a level of 80 or above.

[0189] "Moderator invitation" means being able to serve as an administrator of the content posted within the community, which becomes possible for users with a level of 90 or above. For example, it is to delete inappropriate posts and comments visually, or to set them to non-display (also referred to as regulation), which is usually done by an operator. Also, it may be the right to take measures to suspend the accounts of malicious users, etc. (for example, for a certain period). Content regulated by users with a level of 90 or above will not be displayed even on the user terminals 300 of users with a level of 89 or below.

[0190] "Community creation" means being able to newly create a community that users can participate in, as exemplified in Fig. 6(A), etc., and is an action content permitted only for users with the highest credit level of 100. For example, as a community that supports Group A created by fans of Group A (corresponding to Community A), it is possible to create "Community A2", etc. The created Community A2 will be displayed in the community selection area 50 on the participation community setting screen in Fig. 6(A). Alternatively, it may be possible to create a new "channel". For example, a new theme channel can be added to the channels of "Community A". The newly added channel will be displayed in the channel list display 82 in Fig. 12. Communities and channels created by users with a level of 100 can also be participated in and selected by users with a level of 99 or below.

[0191] Also, in this embodiment, the user's level can not only increase but also decrease. Therefore, for the specific actions illustrated in FIG. 19, even if they are specific actions permitted due to an increase in level, they can be restricted and become unavailable due to a decrease in level. For example, users with a level of 80 or above can create plans within the community, but if the level drops to 79, they can no longer create plans. Also, if a created plan or community is considered inappropriate in the fan community app and reports from other users are made on the display screen of the created plan or community, etc., this can be an external evaluation that may cause the level of the user who created the plan or community to decrease.

[0192] FIG. 20 is an example of a posting screen on the user terminal 300 of a user who does not have "no posting link restriction". In this embodiment, it is assumed that for a user with a posting link restriction up to level 59, only the links to "Video Sharing Site A" and "SNS-B" are permitted for the URLs that can be posted. In this case, if a URL other than "Video Sharing Site A" and "SNS-B" is entered in the text to be posted, a message such as "Currently, only the URLs of 'Video Sharing Site A' and 'SNS-B' can be posted" is displayed as exemplified in FIG. 20. Also, when the Next icon 38 is to be displayed in different modes depending on whether it can be posted or not, it may be displayed in a mode where the Next icon 38 cannot be posted so that a selection operation cannot be performed. In this way, for an uploaded image or the like, it is relatively easy to hide an inappropriate image (an image that may give an unpleasant feeling such as violence) by automatic determination using image recognition. On the other hand, for a URL, even if the destination is a malicious website (for example, a fake site, a fraud site, or a page where unpleasant content is posted), it is not easy to make a determination, and it is necessary for the operator to perform a hiding setting or the like, which is time-consuming. Therefore, for content (here, a URL link) for which it is difficult to determine whether it is an inappropriate post, by allowing only users with a high level (users with a high reliability) to post, the burden on the operator can be reduced, and at the same time, the security within the community can be stabilized by suppressing inappropriate posts.

[0193] Note that "Video Sharing Site A" and "SNS-B", etc., which can be posted even by a user who does not have "no posting link restriction", are, for example, websites where distribution videos of talents to be supported are posted in a fan community application, and relatively safe link destinations are defined.

[0194] Referring to FIG. 21, the flow of the determination process for post link restrictions in the user post process will be described. Since FIG. 21 is a flowchart of the user post process described with reference to FIG. 18 when the determination (the process enclosed by the dotted line) of whether the user has post link restrictions is added, the description of the same process as in FIG. 18 will be omitted.

[0195] When the post screen in FIG. 17(A) is displayed in step S303, in step S316, it is determined whether a link other than the predetermined link is pasted. If it is not determined that a link other than the predetermined link is pasted, the process proceeds to step S304, and it is determined whether Next is selected.

[0196] On the other hand, if it is determined that a link other than the predetermined link is pasted, the process proceeds to step S317, and it is determined whether the user is a user who is permitted to paste a link 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] In step S317, when it is determined that the user is a user who is permitted to paste a link other than the predetermined link, the process proceeds to step S304, and it is determined whether Next is selected. On the other hand, in step S317, when it is not determined that the user is a user who is permitted to paste a link other than the predetermined link, in step S318, it is notified that the post is not permitted, and the process returns to step S316. For example, for a user with a level of 10, since pasting a link other than the predetermined link is not permitted, as illustrated in FIG. 20, it is notified that a link other than the predetermined link cannot be pasted.

[0198] Returning to FIG. 19, the "Report Count" is a privilege that can affect whether or not to make specific content invisible to all users. In this embodiment, content that has been hidden or reported by users with a level of 70 or higher, or content for which the number of reports has reached a predetermined number, can be made invisible to all users. For example, content that has been hidden or reported by five or more users with a level of 70 or higher can be made invisible to all users.

[0199] In addition, content and comments posted by users for whom the number of times hidden or reported by users with a level of 70 or higher has reached a predetermined number, which are subject to the "Report Count", can be made invisible to all users. For example, content and comments posted by a user who has been hidden or reported by five or more users with a level of 70 or higher can be made invisible to all users.

[0200] Note that the user to be made invisible may not include the user himself / herself who posted the comment or content. As a result, although the content and comments posted by the user himself / herself are reflected on the user's own terminal, for example, it is possible to be aware (make the user aware) that the content has become a regulated target due to no action from other users.

[0201] For the "Benefits", different benefits are associated according to the level. For example, when there is a present plan or the like, items that are more beneficial to fans, such as items with a higher rarity, can be given according to the level. For example, when the benefit is a stamp that can be used for posting comments or an item that can be used at a talent's live show, etc., the benefit D given to users with a level of 60 - 69 has a higher price when purchasing a stamp or an item than the benefit E given to users with a level of 50 - 59, and as the level increases, the equivalent amount of the benefit given increases.

[0202] (Regarding examples of fluctuations in evaluation values) Next, referring to FIG. 22, an example of the variation in the cumulative point count (evaluation value) will be described. FIG. 22 is a table for explaining an example of external evaluation that varies the "cumulative points" of a user and an example of the relationship between the external evaluation and the number of variations. When there is any action from a user (including the operator) with respect to content (posted articles), comments, etc., the account management unit 133 varies and updates the cumulative points of the user according to whether it is an external evaluation stored as action information 123. If the level varies in response to the variation in the cumulative points, the account management unit 133 performs a process of permitting or restricting the action authority stored as action authority information 124 for the user.

[0203] External evaluation is evaluation from other users other than the user himself / herself. For example, when there is a "like from another user" for the content or comment posted by a user, for each "like" (1 tap action), the cumulative points increase by 5.

[0204] Alternatively, there may be points given due to a high evaluation from the operation, such as when the operator has a good impression of a user with high reliability as seen from the content of the content or comment posted by the user. The points given from the operation may be a predetermined number of points, or may be changed appropriately by the operation of the operator.

[0205] Points may also be awarded according to the evangelism level of the supported target. That is, points are awarded according to the degree of benefit contribution to the supported target by the act of promoting the content (such as videos and goods) related to the supported target. For example, the promotional acts include the act of spreading the link of the distribution video of the talent who is the supported target, the act of introducing the goods of the talent who is the supported target, etc. For example, when a video link of a distribution video related to a talent or a group to which the talent belongs is posted on the content posted by the user, points are awarded according to the number of video views from the posted content. In addition, when a link to a goods page related to a talent or a group to which the talent belongs is posted, points can also be awarded according to the number of clicks on the goods page link. The goods page is, for example, the official goods page of the talent who is the support target of the fan community, the sales page of the collaborative planning products with other companies, etc., and a dedicated URL for community submission may be issued for aggregation. Alternatively, when a product is purchased via the dedicated URL for community submission of the goods page on the official website, points may be awarded to the user who posted the URL.

[0206] On the other hand, points will be reduced if there are reports or non-displays from other users. For example, each time there is one report, 5 points can be deducted by operating on the screen shown in FIG. 11(B). Alternatively, when there is a concern that a user may deteriorate the atmosphere in the community as seen by the operator due to the content of the content or comments posted by the user, etc., the user may be negatively evaluated (points are deducted) by the operation. The points deducted by the operation may be a predetermined number of points, or may be changed by the operation of the operator as appropriate.

[0207] Also, as an example of external evaluation, the text of comments made on content is judged. If it contains positive words predetermined by an operator or the like, points may be increased, and if it contains negative words predetermined by an operator or the like, points may be decreased. Also, the text judgment may be performed by automatic judgment using AI. For example, for the content itself posted by the user himself / herself or comments from other users made on the content posted by the user, after automatically judging the ratio of positive words or negative words, points may be given or not given depending on which element is more numerous. Positive words and negative words are not determined by the user, but are based on criteria due to external factors (for example, criteria on the operation side (including AI judgment)).

[0208] (Regarding the flow of evaluation history status update process) Next, with reference to FIG. 23, the flow of the user's evaluation history status update process will be described. FIG. 23 is a diagram for explaining a flowchart of a process for updating the user's evaluation history status that varies according to the external evaluation described with reference to FIG. 22. The evaluation history status update process is repeatedly executed by the account management unit 133 in the distribution server 100 when there is some action (for example, an action that is the target of external evaluation such as a tap action, a comment, a report, or non-display) on the content, comments, etc. posted by each user in the fan community app. Note that the evaluation history status indicates the result of the user being evaluated by external factors other than the user himself / herself, including "level" and "cumulative points" in the user information database of FIG. 7 stored as account information.

[0209] In step S401, it is determined whether there is an external evaluation. For example, it is determined whether there is an external evaluation exemplified in FIG. 22 for the content, comments, etc. posted by the user. When it is determined that there is no external evaluation, the process ends.

[0210] On the other hand, when it is determined that there has been an external evaluation, in step S402, it is determined whether the external evaluation is a "point increase" evaluation. For example, if the external evaluation is "likes from other users" (tap actions from other users) illustrated in FIG. 22, since the number of points increases by 5, in step S402, it is determined that it is a "point increase" evaluation.

[0211] In step S402, when it is determined that the external evaluation is a "point increase" evaluation, 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, assume a user at level 59 reaches level 60 because 5 points are added to the cumulative points due to an external evaluation. At this time, in the user information database, the level is updated to 60, and the cumulative number of points is stored as the value after the 5 - point addition.

[0212] Next, in step S404, it is determined whether the level has been upgraded due to the change in the number of points. In step S404, when it is determined that the level has been upgraded due to the change in the number of points, in step S405, specific actions corresponding to the level after the upgrade are permitted to the user, and the user's permitted action information stored as account information 125 is updated and stored. For example, assume that when the level reaches 60, as illustrated in FIG. 19, the restriction on posting links is removed. Then, for example, in the user information database stored as account information 125, information indicating that there is no restriction on posting links for the user is associated and stored. Note that there may be cases where there are no newly permitted actions even if the level has been upgraded, and in such cases, the permitted action information is not updated particularly and the process ends.

[0213] In step S405, after the permission action information is updated and stored, in step S406, information for notifying the user that a specific action has been permitted is transmitted to end the process. For example, a push notification of a message such as "The restriction on posting links has been lifted due to level up" is sent to the user terminal 300, a notification within the application is provided, or a pop-up is displayed at the next posting time, etc.

[0214] Return to step S402. When it is not determined that the external evaluation is "increase in the number of points", proceed to step S407 to determine whether the external evaluation is an "evaluation of decrease in the number of points". For example, if the external evaluation is "report from other users" illustrated in FIG. 22, since the number of points decreases by 5, in step S407, it is determined that the evaluation is "evaluation of decrease in the number of points".

[0215] In step S407, when it is determined that the external evaluation is an "evaluation of decrease in the number of points", in step S408, the number of points is decreased for each user according to the external evaluation, and the evaluation history status is updated and stored. For example, assume a user at level 60, but the cumulative points are decreased by 5 due to the external evaluation, and as a result, the cumulative points no longer meet the number of points required for level 60, and the level drops to level 59. At this time, in the user information database, the level is updated to 59, and the cumulative points are updated and stored to the value after subtracting 5.

[0216] Next, in step S409, it is determined whether or not the level has been downgraded due to the change in the number of points. When it is determined in step S409 that the level has been downgraded, in step S410, according to the level after the downgrade, the specific actions that were permitted before the level downgrade are restricted, and the permitted action information is updated and stored. For example, suppose that when the level reaches 59, as illustrated in FIG. 19, restrictions are imposed on the posting link. Then, for example, in the user information database stored as account information 125, information indicating that there are restrictions on the posting link for the user is stored in an associated manner. Note that there may be cases where there are no actions to be restricted even if the level is downgraded. In such cases, the process ends without particularly updating the permitted action information.

[0217] After the permitted action information is updated and stored in step S410, in step S411, information for notifying the user that the specific action has been restricted is transmitted, and the process ends. For example, on the user terminal 300, a push notification of a message such as "Due to the level downgrade, restrictions have been imposed on the posting link", a notification within the application, or a pop-up display at the time of the next posting is made.

[0218] Returning to step S407, when it is not determined that the external evaluation is the "point decrease" evaluation, the process ends. For example, this is the case when there is an action that is not defined as affecting the change in the number of points. Although an example in which the evaluation history status update process is executed by the distribution server 100 has been described, it may be the case that after being executed by the user terminal 300, information is transmitted to the distribution server 100.

[0219] <Regarding the production display by the tap action> (Example of the display screen of the tap action production process) Next, with reference to FIGS. 24, 25, and 26, the effect display when a tap action is received from a user for content, comments, etc. will be described. In this embodiment, when an operation (such as a click operation or a tap operation from the user terminal 300) is performed on the icon 708 displayed in the content described with reference to FIGS. 10, 11, and 13 or the number of tap actions 78(78b) displayed in the heading of the content, the number of tap actions is incremented. Further, when the number of tap actions is incremented, an effect display can be performed on the user terminal 300. For example, each time an operation is performed on the icon 708, an effect is produced in which a predetermined mark pops out from the icon 708.

[0220] FIG. 24 is an example of an effect display (reception effect) when a tap action from a user is received. FIG. 24(A) is an example of a screen for each channel for each community exemplified in FIG. 11(A), etc., and is an example when an operation is performed on the icon 708 of the number of tap actions 78 displayed in the content heading 70 displayed at the top. In this case, since the number of tap operations has reached 50, "50" is displayed in the individual tap action number 48. Therefore, the user can recognize the number of times they have performed a tap action.

[0221] In Fig. 24(A), an example is shown where three consecutive taps (rapid taps) are made. In the first tap (the 48th tap), an effect is produced such that the thumbs-up mark 41a pops out from the icon 708 with a tap action count of 78. Next, in the second tap (the 49th tap), an effect is produced such that the thumbs-up mark 41b pops out from the icon 708. Also, in the third tap (the 50th tap), an effect is produced such that the fan mark 42 pops out from the icon 708. The fan mark 42 is the fan mark of related talents associated with the content on which the icon 708 is operated. In this way, when the display times (from popping out to disappearing) of the marks that popped out in the previous tap and the marks that pop out in the next tap overlap due to consecutive taps, a state where multiple marks are displayed occurs. In this way, since an effect is produced where marks pop out successively by consecutive taps, the user can obtain a sense of comfort (operability) in the tap action and can be prompted to perform further tap actions. Note that the effect where the marks pop out may be such that, as illustrated in Fig. 24(A), multiple marks are not displayed simultaneously, and the marks to be displayed may be one by one.

[0222] Fig. 24(B) shows a special effect (special reception effect) that is displayed when the number of tap actions from the user reaches a predetermined number. For example, when the operation on the icon 708 reaches 100, an effect is produced where various marks pour down over the entire screen. Note that the predetermined number may be the upper limit value at which the user can perform a tap action on each action target. That is, when the predetermined number is reached, no effect or update of the individual tap action count 48 is performed by the operation on the icon 708. Alternatively, it may be something that is performed every time a predetermined number of times is reached (for example, every 10 times). Also, it is not necessary to set an upper limit value.

[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 performed by the user on the content. Instead of this, or in addition to this, each time the number displayed as the number of tap actions 78, which is the number of tap actions of all users in the fan community, reaches a predetermined value (for example, 100 times), an effect may be performed on the user who performed the 100th action.

[0224] Next, with reference to FIG. 25, an example of the type of effect executed by receiving a tap action will be described. FIG. 25 is an example of a content-specific effect data table for effect display by tap action stored in the storage unit 320 of the user terminal 300 based on the content data 122 stored in the distribution server 100 or the content data 122 acquired from the distribution server 100. Information regarding the effect display is associated with each content (posted article).

[0225] In the content-specific effect data table, an effect type is determined for each article ID. In addition, a lottery probability used for the effect is associated with each effect type. The effect type is determined according to whether the number of times a tap action has been performed is less than the predetermined number of times or has reached the predetermined number of times. Assuming that the predetermined number of times is the upper limit value 100 at which a tap action is possible, 1 to 99 are less than the predetermined number of times.

[0226] For performances less than the specified number of times, the default performance and, if a related talent is set for the content, the fan mark performance are defined. For the default performance, marks such as applause, thumbs up, heart, and rare mark are defined, for example. For the fan mark, a mark corresponding to the related talent is associated. For example, for article ID "a1", as illustrated in FIG. 14, the related talents are associated with talent IDs "t1", "t2", "t6", "t14". Therefore, "mark_t1", "mark_t2", "mark_t6", "mark_t14", which are fan marks corresponding to each of the related talents, are associated. Regarding the lottery probability for each mark to be used in the performance, the same probability may be uniformly defined, or the appearance probability may be set to be low for the fan mark or the rare mark. In this way, when a related talent is associated with the content, the fan mark appears by performing a tap action. This can encourage the user to perform a tap action, and further encourage the user to select a related talent before posting the content when posting the content. As a result, it can be made easier for other users to obtain information about the favorite talent, and the fan community can be activated by user behavior.

[0227] For the performance when the specified number is reached, a luxurious performance and, if a related talent is set for the content, a talent performance are defined. The talent performance is, similar to the fan mark when the number is less than the specified number, "special_t1", "special_t2", "special_t6", "special_t14", which are performances corresponding to each of the related talents associated with article ID "a1", are defined. For example, an animation display that reminds of the talent, such as the fan mark popping out, is shown.

[0228] Also, when no related talent is set for the content, as exemplified by the article ID "a99" in FIG. 25, no fan mark or talent performance is defined for the production type. When the number is less than a predetermined number, a default production is performed, and when the predetermined number is reached, a luxurious production is performed.

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

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

[0231] In step S501, it is determined whether there is a tap action operation. For example, in the home screen of FIG. 10, the community screen of FIG. 11(A), and the content screen of FIG. 13, it is a tap operation by the user on the icon 708 displayed on the content or comment. When it is not determined in step S501 that there is a tap action operation, the process ends.

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

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

[0234] When it is not determined in step S504 that the total number of tap actions is equal to the predetermined number, in step S505, it is determined whether related talents are associated with the content on which the tap action operation was performed. For example, assume that the content on which the tap action operation was performed is the article "a1" in FIG. 14. Then, it is determined that there are related talents.

[0235] In step S505, when it is determined that there is relevant talent, in step S506, based on the content-specific production table in FIG. 25, less than a predetermined number of tap actions are randomly selected and determined. After the production is determined in step S506, in step S507, the production of the tap action determined in step S507 is executed, and the tap action number update information is transmitted to the distribution server 100 to end the process. For example, when the production type fan mark "mark_t1" of the 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 production in which the fan mark corresponding to "mark_t1" pops out is executed.

[0236] Return to step S505. When it is determined that no relevant talent is associated with the content where the tap action operation occurred, proceed to step S508, and randomly select and determine less than a predetermined number of default tap actions. In step S509, the production of the default tap action determined in step S508 is executed, and the tap action number update information is transmitted to the distribution server 100 to end the process. For example, for the article ID "a99" in FIG. 25, since it is content with no associated relevant talent, a production lottery is conducted from the defaults. For example, if "Summary" is determined by lottery, the number of tap actions 78 and the number of individual tap actions 48 are updated, and the production in which the mark corresponding to "Summary" pops out is executed.

[0237] Return to step S504. When it is determined that the total number of tap actions is the predetermined number, proceed to step S510. For example, this is when the number of individual tap actions reaches 100 due to the tap action counter being incremented in step S503.

[0238] In step S510, it is determined whether or not related talents are associated with the content for which the tap action operation has been performed. For example, if the content for which the tap action operation has been performed is the article "a1" in FIG. 14, it is determined that there are related talents.

[0239] In step S510, when it is determined that there are related talents, in step S511, a tap action effect for when a predetermined number is reached is selected and determined by lottery. In step S512, the tap action effect for when the predetermined number is reached determined in step S511 is executed, and tap action number update information is transmitted to the distribution server 100 to end the process. For example, when "special_t1" of the production type talent production of the 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 production corresponding to "special_t1" is executed.

[0240] Return to step S508. When it is determined that no related talents are associated with the content for which the tap action operation has been performed, in step S513, the tap action effect for when the predetermined number is reached is executed, and tap action number update information is transmitted to the distribution server 100 to end the process. For example, for the article ID "a99" in FIG. 25, since it is content with no associated related talents, the number of tap actions 78 and the number of individual tap actions 48 are updated, and the production corresponding to the "luxury production" is executed.

[0241] In steps S507, S509, S512, and S513, tap action update information (for example, information identifying that a tap action has been executed) is transmitted to the distribution server 100, thereby updating the aggregation of the number of tap actions for each piece of content or comment stored as content data 122, which is reflected in the number of tap actions 78 (78b) of the user terminal 300 of other users. Although an example in which the tap action rendering process is executed on the user terminal 300 has been described, it may be executed on the distribution server 100 and display information may be transmitted to the user terminal 300.

[0242] In addition, when related talents are associated with the content, an example in which a fan mark corresponding to each associated talent or talent rendering is executed by lottery has been described. However, when a user's favorite talent pre-selected by the user is associated with the related talent, the lottery probability (winning probability) of the fan mark corresponding to the favorite talent may be increased compared to other fan marks.

[0243] <Use of APIs provided by external services> Next, with reference to FIG. 27, an example will be described in which content provided by the external web service system 400 is made available to the user by using 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 the talent who is the support target of the fan community in this embodiment is distributing videos on the video distribution site. In this embodiment, the user can easily check the distribution schedule for the talent to distribute videos on the video distribution site.

[0244] In this embodiment, by using the API provided by the external web service system 400, information on the video distributor and the co-distribution (also referred to as collaboration) partner with the distributor is obtained, and information associated with the talent ID of the corresponding talent is generated and can be displayed on the user terminal 300. By associating the talent ID with the information to be displayed to the user, it is possible to extract the distributions of the communities (first attribute) and favorite talents (second attribute) pre-selected by the user so that the user can be identified.

[0245] FIGS. 27(A) and (B) are examples of a distribution schedule screen displayed on the user terminal 300. For example, the distribution schedule icon 18 may be displayed at the lower part of the app screen and may be displayed due to a selection operation on the distribution schedule icon 18. Alternatively, it may be possible to select it on the channel list screen illustrated in FIG. 12, or it may be displayed in the channel list display 82 for each community.

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

[0247] On the distribution schedule screens of FIGS. 27(A) and 27(B), the favorite filter 20, distribution period selection area 91, group selection area 92, distribution date and time 93, content heading 90, channel account 98, talent related to the performance 94, etc. are displayed. For example, by performing a selection operation on the content heading 90, the user transitions to the distribution page on the external web service in FIG. 27(C). The destination of the transition is the video distribution channel of the account displayed in the channel account 98. In the talent related to the performance 94, icons of the talents appearing in the corresponding distribution are displayed. For example, in the content heading 90a of FIG. 27(A), it is displayed that there is a distribution by the account of the official channel of Group A, and in the content heading 90b, it is displayed that there is a distribution by the channel of Talent BBB.

[0248] In the distribution period selection area 91, for example, there are displayed icons of "Recent Distribution" for displaying a list of content headings 90 (content information) that identify the most recent past distributions (contents), "Currently Distributing" for displaying a list of content headings 90 that identify the currently distributed distributions (contents), and "Future Schedule" for identifying future scheduled distributions (contents). By a selection operation from the user on each icon, the list of content headings 90 to be displayed can be switched. FIG. 27(A) is an example of the distribution schedule screen when the "Currently Distributing" icon is selected, and a list of content headings 90 for identifying the currently distributed distributions is displayed. FIG. 27(B) is an example of the distribution schedule screen when the "Future Schedule" icon is selected, and a list of content headings 90 for identifying the future scheduled distributions is displayed.

[0249] In the group selection area 92, icons for selecting the affiliated group 1 to which the talents exemplified in FIG. 5 belong are displayed. The groups displayed in the group selection area 92 are only the groups corresponding to the communities in which the user participates. For example, FIGS. 27(A) and 27(B) are the screens displayed on the user terminal 300 of the user "u2" in FIG. 7. In FIGS. 27(A) and 27(B), the icons of "Group A" and "Group B" corresponding to community A and community B in which the user "u2" participates are displayed. By operating on each icon, the content heading 90 of the distribution related to the talents belonging to any (or both may be selectable) group is displayed. In FIGS. 27(A) and 27(B), since the icon of "Group A" is selected, the content heading 90 for specifying the distribution in which the talents belonging to Group A appear is extracted and displayed. Whether it is a distribution in which the talents belonging to Group A appear or not can be specified by the user because the appearance-related talent 94 (talent ID in FIG. 5) is associated in the distribution server 100 with the content heading 90. Although an example is shown in which the groups displayed in the group selection area 92 are only the groups corresponding to the communities in which the user participates, it is not limited to this, and all groups may be displayed regardless of the communities in which the user participates.

[0250] Also, as described above with reference to FIG. 9, in the distribution schedule screen as well, by performing a selection operation on the favorite filter 20, it is possible to extract and display the distributions in which the favorite talents pre-selected by the user appear.

[0251] The talents displayed in the appearance-related talent 94 in FIGS. 27(A) and 27(B) are displayed based on information obtained by using the API of the video distribution site. For example, in the distribution screen in FIG. 27(C) (including live, post-distribution, and pre-distribution posts), a summary column 95 is provided, and the poster of the distribution can appropriately edit the text in the summary column 95. By embedding the attribute identification information 96 in the summary column 95, the distribution server 100 acquires the attribute identification information 96 and generates the content heading 90. The attribute identification information 96 is, for example, a channel account on the video distribution site. Since FIG. 27(C) is a distribution by the channel account corresponding to the talent "CCC", the distribution server 100 can acquire the attribute identification information 96a which is a channel account. In addition to the icon of the talent, the name of the talent may also be displayed in the appearance-related talent 94. Also, the appearance-related talent 94 may be displayed as the related talent 88 described with reference to FIG. 13 and the like.

[0252] Also, in the summary column 95, the attribute identification information 96b (also referred to as a handle), which is information (identifier) for identifying the channel account corresponding to the talent "AAA", is input. The handle is also a URL that leads to the corresponding channel account. For example, when a co-distribution is made with a talent different from the talent corresponding to the channel account that performs the distribution, the handle for identifying the co-distribution partner is input. This input action is also said to mention another channel by adding an @ mark before the other channel and inputting character information. For example, when the distribution by the channel of the talent "CCC" is a so-called collaboration distribution with the talent "AAA", the handle for identifying the channel account of the talent "AAA" is embedded in the summary column 95 of the distribution. By the handle, which is the attribute identification information 96b, being input in the summary column 95, the server 100 can acquire the attribute identification information 96b, which is the information of the collaboration partner, in addition to the account itself that performs the distribution.

[0253] As described above, by acquiring the attribute identification information 96, the distribution server 100 generates a content heading 90 in which the talent ID of the talent corresponding to the channel account (attribute identification information 96a) for distribution and the talent ID of the talent corresponding to the co-distribution partner entered in the handle (attribute identification information 96b) are associated. For example, assume that the information acquired from the external web service 400 includes the attribute identification information 96 corresponding to the talents "CCC" and "AAA". In this case, in the database that manages the content heading 90 that can be displayed on the distribution schedule screen stored as the content data 122, the information for specifying the content heading 90 in which the talent IDs "t3" and "t1" of the talents "CCC" and "AAA" are associated is generated and stored by the content management unit 132, thereby generating the content heading 90. Further, the distribution server 100 acquires the text information (e.g., "Co-distribution with AAA") of the title 97 of the distribution screen in FIG. 27(C) and the thumbnail image information 99, and causes the text information and the thumbnail image to be displayed in the content heading 90. Thereby, since it is possible to specify which of the talents in the talent information database stored as the attribute information 121 illustrated in FIG. 5 is for the distribution, it is possible to cause the user to specify the distribution associated with the attribute preselected by the user.

[0254] For example, in the following, FIG. 27(B) will be described as being the screen of user "u1" in FIG. 7. Note that when FIG. 27(B) is the screen of user "u1", user "u1" has not participated in community B. However, as shown in FIG. 27(B), the icon of community B may be displayed in the group selection area 92, and the distribution schedule screen of group B may be displayed by selection. Alternatively, only the icons of the communities the user has joined may be displayed (the icon of community B is not displayed). The talents selected by user "u1" as their favorite talents are talents "AAA", "BBB", and "EEE" corresponding to talent IDs "t1", "t2", and "t5", but talent "CCC" is not selected as a favorite talent. However, even if there is a co-distribution with the channel account of "CCC", which is not a favorite talent, the information of the co-distribution partner can also be obtained by the attribute identification information 96b. Therefore, even when the favorite filter 20 is on, the content heading 90 for identifying the distribution of talent "CCC" is displayed, and the performing talent 94 is displayed, so that the user will not overlook the information of their favorite talents.

[0255] Also, for example, if a co-distribution suddenly occurs during the distribution, and there is an edit in which new attribute identification information 96b (handle) is added to the summary column 95 of the distribution screen in the external web service 400, it will be extracted at any time. Therefore, even if a co-distribution suddenly starts, the content heading 90 of the distribution will be displayed in the currently distributed distribution schedule in FIG. 27(A). Also, if the favorite talent pre-selected by the user is associated with the content heading 90, a push notification can be sent, so that the user will not overlook the sudden distribution of their favorite talent.

[0256] Note that although the content heading 90 displayed in the distribution schedule of FIG. 27 has been described as an example automatically generated using the API of the external web service 400, it is not limited to this. For example, it may be manually set from the administrator terminal 200. For example, the content heading 90 may be generated by associating a link to the destination and related talents. Even when the API cannot be used, it is possible to guide the user to a link destination outside the fan community app related to the talent.

[0257] Also, the content heading 90 generated when the channel account in the external web service is the official channel of the group corresponding to the affiliated group 1 in FIG. 5 may not have any associated talents (no associated related talents). Even in this case, although no individual talent is associated with the content heading 90, the participating communities and groups of the group corresponding to the channel account are associated. Therefore, if you participate in the community corresponding to the group, the content heading 90 will be displayed on the distribution schedule screen, and it will be displayed as the content heading 90 extracted for each group by operating the icon for each group in the group selection area 92.

[0258] <Regarding the reuse permission-related process> (Outline of the reuse permission-related process) With reference to FIGS. 28 to 32, the reuse permission-related process in this embodiment will be described. In fan activities (so-called oshi activities) that support favorite support targets (so-called oshi), such as people like talents or things, for example, fan users may post on SNS, etc., feelings about fan activities or secondary creations such as fan art related to the support target. There are cases where such posted content from fan users is introduced by the talent or the like who is the support target in their own video distribution, SNS, etc.

[0259] In addition, introducing the posted content of fan users to talents and the like leads to the activation of communication between fans and talents. Therefore, in order to enable talents and the like to smoothly use the posted content of fan users for distribution and the like, for example, there is a method of stating in the terms of use that the operator is deemed to have obtained permission to use the posted content. However, if this is done, there is a risk of causing misunderstandings among users. Therefore, in this embodiment, regarding the secondary use (also referred to as citation) of content such as threads and comments posted by users (actions by users), it is possible to allow or disallow it at the discretion of the user, so as to facilitate the smooth secondary use of the posted content of the user (for example, including the posting of threads by the posting operation described with reference to FIGS. 17 and 18, and comments on the posted content).

[0260] As a result, for example, fan art and support comments of users posted in the fan community in this embodiment are more likely to be picked up by the supported talents in video distribution and the like, and communication is activated. In addition, since real posts in the fan community can be introduced, a promotion effect of the fan community will also be produced.

[0261] In addition, since the permission status of secondary use of the content in this embodiment can be set by user operations, for example, when operators or talents conduct individual projects, the trouble of describing in the post (within the content) each time the project is carried out that comments and images posted may be used by the operator or talent in other media can be saved. Individual projects include various projects that solicit posts from users (such as soliciting support comments for talents, pun contests, and questionnaire projects), including posts (such as comments, images, and video posts) from users.

[0262] Note that secondary use is not limited to cases where talents, operators, etc. introduce [content] on video distribution, SNS, etc. For example, in the official website of the user's support target, posting the user's posted content, or further secondary use (reposting, republishing, reintroducing, etc.) of the content that has been secondarily used (posted content in which the posts of the users corresponding to secondary use are used). All kinds of quotations and introductions made by operators, talents, etc. are also included in secondary use.

[0263] In addition, content such as threads and comments (actions by users) may be posts of images, videos, digital art, etc. in addition to text posts of characters. Further, it may include posts such as uploads of various files such as 2D model data, 3D model data, and 3D materials. Further, it may be a post of each combination (for example, posting an image together with text), or a post of only one of them (for example, posting only an image, posting only a video).

[0264] (Example of secondary use permission / denial screen) With reference to FIG. 28, an example of the display screen of the user terminal 300 regarding the secondary use approval-related process displayed in the fan community app of this embodiment will be described. FIG. 28(A) is an example of the display screen of the secondary use approval button 501 displayed on the user setting screen such as the my page in FIG. 8. The secondary use approval button 501 is displayed together with a message such as "Permit distribution and publication in operations and projects of affiliated talents" and a message such as "※ By turning on this button, it is considered that the operator and affiliated talents have approved the use of your posts. Note that you can change it to OFF at any time." By operating the secondary use approval button 501 by the user, it is possible to select whether to permit the content posted by the user to be secondarily used in distribution, planning, etc. by the operator, talent, etc. The secondary use approval button 501 illustrated in FIG. 28(A) is an example of the display mode in the on state, and by performing a user operation such as a tap operation on the secondary use approval button 501, it can be set to the off state. Note that the default setting may be either the on or off state, but by setting it to the off state by default, the on state will not occur without user operation, so it is less likely to cause misunderstanding to the user.

[0265] FIG. 28(B) is a diagram for explaining a content display screen when secondary use of posted content is permitted. When the secondary use permission / denial button 501 is in the on state, a secondary use OK icon 701 is displayed for posted content submitted by a user who permits secondary use. FIG. 28(B) is another example of the content screen illustrated in FIG. 13, and the content poster is the general user "userA". Also, comments have been made on the content posted by "userA" in FIG. 28(B) from "userJ" and "userL". In FIG. 28(B), since "userA" and "userJ" are users who have set the secondary use permission / denial button 501 to the on state, a secondary use OK icon 701 is displayed beside their user names. On the other hand, since "userL" has set the secondary use permission / denial button 501 to the off state, a secondary use OK icon 701 is not displayed beside their user name.

[0266] Also, the secondary use OK icon 701 may be displayed on the screens of the user terminals 300 of all users. However, in this case, there is a risk that the operation side does not intend for use or abuse by users with low need for secondary use. Therefore, it is preferable that the secondary use OK icon 701 is only displayed on the screens of the user terminals 300 of users who meet specific conditions. The specific conditions are accounts of special users such as talents exemplified in FIG. 5 (for example, "t1", "t2", "t3" in FIG. 5), or accounts of operators (for example, "ou1", "ou2" exemplified in FIG. 14), etc., that is, users corresponding to those who have been permitted secondary use by the secondary use permission / denial button 501. Thereby, it becomes easier for talents, operators, etc. to recognize content (threads, comment postings, etc.) that may be used for secondary use. Also, since the secondary use OK icon 701 is not displayed on the screens of the user terminals 300 of users who are not talents or operators and do not meet the specific conditions, it is possible to prevent accidental secondary use by general users.

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

[0268] (Example of Database Related to Reuse Permission / Prohibition Processing) Referring to FIG. 29, an example of the database stored in the storage unit 120 of the distribution server 100 related to the reuse permission / prohibition processing in this embodiment will be described. FIG. 29(A) is an example of a part 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), reuse permission / prohibition information is associated with each user ID. The reuse permission / prohibition information is associated with "permission" if the reuse permission / prohibition button 501 in FIG. 28(A) described above is operated and the reuse permission / prohibition button 501 is in the on state, while it is associated with "prohibition" if it is in the off state.

[0269] FIG. 29(B) is an example of the content database, and together with the content database exemplified in FIG. 14, for example, content data 122 and action information 123 are stored in the storage unit 120 of the distribution server 100. For each "article ID" of the content posted on each channel exemplified in FIG. 14, "poster ID", "posting date and time", "posting content information", "reuse permission / prohibition information", "reaction related information", etc. are associated. The "posting content information" includes, for example, information such as the title and text of the content displayed on the content 74b of the content screens of FIGS. 13 and 28(B), and information specifying images and videos displayed on the 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 Fig. 29(A). Since the user ID "u1" has "permission" for secondary use in the user information database of Fig. 29(A), the article ID "a3", which is a post by "u1" in the content database of Fig. 29(B), is associated with "permission". On the other hand, since "u2" is "not permitted" in the user information database of Fig. 29(A), the article ID "a10" in Fig. 29(B) is associated with "not permitted".

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

[0272] FIG. 29(C) is an example of a comment database for each comment ID associated with the "comment information" illustrated in FIG. 29(B). Along with the content databases of FIGS. 14 and 29(B), content data 122 and action information 123 are stored 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 made the comment, the "posting date and time" of the comment, the "comment content", the "secondary use permission information", and the "reaction-related information" are associated. The "comment content" includes information for identifying information such as the text posted as a comment, images, videos, etc. The "secondary use permission information" is associated with "permission" or "dispermission" based on the state of the "secondary use permission information" in the user information database of the user who posted the comment, similar to the "secondary use permission information" in FIG. 29(B). The "reaction-related information" in the comment database is associated with tap actions and information related to comments made for each comment, similar to the "reaction-related information" in FIG. 29(B).

[0273] FIG. 28(B) is an example in which the content screen of the article ID "a3" in FIG. 29(B) is displayed. For example, the user ID "u1" (user1) who is the poster 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 a comment ID "cm6" associated with the article ID "a3" and is a comment posted by the user ID "u10" whose secondary use permission information is "permitted", so a 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 a comment ID "cm7" associated with the article ID "a3" and is a comment posted by the user ID "u12" whose secondary use permission information is "disallowed", 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 process 1) Next, with reference to FIG. 30, an example of the flow of the secondary use permission / denial related process 1 will be described. FIG. 30 is a diagram for explaining the flowchart of the secondary use permission / denial related process described with reference to FIGS. 28 and 29. The secondary use permission / denial related process 1 may be repeatedly executed at predetermined time intervals in the distribution server 100, or may be executed when an operation is performed on the secondary use permission / denial button 501 on the user terminal 300, when posting information is transmitted from the user terminal 300, when a display request for the screen of the fan community application is made from the user terminal 300, etc. The secondary use permission / denial related process 1 in FIG. 30 explains the case where "secondary use permission / denial information" is associated with each thread and comment, as exemplified in FIGS. 29(B) and (C). The "secondary use permission / denial information" for each thread and comment is associated with the permission / denial state based on the state of the "secondary use permission / denial information" in the user information database of FIG. 29(A) of the user at the time of posting.

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

[0276] On the other hand, when it is not determined in step S601 that the secondary use permission information has been received, in step S603, it is determined whether post information has been received. The post information is information transmitted to the distribution server 100 when a thread is posted with reference to FIGS. 17 and 18 or a comment is posted from the comment posting column 84 in FIG. 13 on the user terminal 300, and is information specifying the content of the posted thread or the content of the comment.

[0277] When it is determined in step S603 that post information has been received, in step S604, the post-related information is updated by associating 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 the comment database illustrated in FIGS. 14 and 29(B) and (C). For example, when a thread is posted from the user ID "u1" whose secondary use permission information is set to "permitted" in the user information database in FIG. 29(A), as illustrated in FIG. 29(B), the content database is updated and stored by associating the secondary use permission information of "permitted" with the article ID "a3" of the content (thread) posted by "u1". On the other hand, when a thread is posted from the 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 the process proceeds to step S605.

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

[0279] On the other hand, in step S603, when it is determined that the posting information has not been received, in step S605, it is determined whether display request information has been received. The display request is information transmitted from the user terminal 300 to the distribution server 100, such as by an operation of causing the user terminal 300 to read display data. For example, when logging in to the application on the user terminal 300 (inquiry to the server at the timing of opening the application), a reload operation (reloading operation), or a selection operation for the home icon 13, community icon 14 of the application screen, a channel displayed in the channel list 82 of FIG. 12, or the like, or a content heading (60, 70) displayed in FIGS. 10, 11, etc. is selected. When it is determined in step S605 that the display request information has not been received, the process ends.

[0280] On the other hand, when it is determined in step S605 that display request information has been received, in step S606, it is determined whether the requesting user is a user who satisfies specific conditions. For example, if the requesting user is an account of a special user such as the talent in FIG. 5 who has permitted the secondary use of the content by the secondary use permission / denial button 501, it is determined that the user satisfies the specific conditions. When it is determined in step S606 that the requesting party is a user who satisfies the specific conditions, in step S607, together with information (suggestive information) that enables the determination of the secondary use permission / denial status for each piece of posting information, the posting-related information is transmitted to the user terminal 300 of the requesting user, and the process ends. For example, it is assumed that the distribution server 100 has received display request information for displaying the content screen corresponding to the article ID "a3" in FIG. 29(B) by selecting the content heading from the home screen in FIG. 10 displayed on the user terminal 300 of the talent. In that case, together with information that enables the determination of the secondary use permission / denial status (permission or denial) of the article ID "a3" and the comments "cm6" and "cm7", the posting-related information for displaying the content screen corresponding to the article ID "a3" is transmitted to the user terminal 300 of the requesting user. As a result, as illustrated in FIG. 28(B), on the user terminal 300 of a user such as a talent, the secondary use OK icon 701 is displayed for the postings of users who have permitted secondary use.

[0281] On the other hand, in step S606, when it is not determined that the requesting user is a user who satisfies the specific conditions, in step S608, the posting-related information such as the content screen for which the display request was made is transmitted, and the process ends. For example, even if there is a request to display the content screen of the article ID "a3" from a general user who does not satisfy the specific conditions, the secondary use OK icon 701 is not displayed on the user terminal 300 of the general user. Therefore, it is possible to prevent unnecessarily prompting the general user or the like to perform secondary use.

[0282] Also, in the secondary use related process 1, when the user operates the secondary use permission / denial button 501 and the secondary use permission / denial information is changed, the secondary use permission / denial information associated with the post made before the change will be different from the secondary use permission / denial information associated with the post made after the change. For example, when the user ID "u1" which had given "permission" operates the secondary use permission / denial button 501 to turn it off, after the secondary use permission / denial information associated with "u1" in the user information database in step S602 is updated to "denial", the post made afterwards will have the secondary use permission / denial information of "denial" associated with it in step S604. As a result, the user can set the secondary use permission / denial status for each post, and since permission can be given according to the content of the post, convenience is increased.

[0283] Also, the secondary use permission / denial information associated with each content such as a thread or a comment may not be changeable afterwards. Thereby, for example, in the case where, for instance, a celebrity takes a screenshot for later introduction in a video distribution, and the content that was permitted for secondary use at the time of taking the screenshot becomes not permitted for secondary use by the time of actually doing the video distribution, it is possible to prevent the content that has become not permitted from being used for secondary use.

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

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

[0286] Also, when it is determined in step S605 that display request information has been received, and it is determined in step S606 that the requesting user satisfies the specific conditions, in step S607B, the posting-related information is transmitted to the requesting user terminal 300 together with information (suggestive information) that enables identification of the current secondary use permission status for each user of the posting source, and the process ends. For example, when receiving display request information for displaying the content information of article ID "a3" in Fig. 29(B) from the user terminal 300 of a special user such as a talent, the user ID "u1" who is the poster of article ID "a3", the user information database of "u10" for comment ID "cm6", and the secondary use permission status (permission or non-permission) based on the secondary use permission information stored in the current user information database of "u12" for "cm7", together with information for displaying the content image of article ID "a3", are transmitted to the user terminal 300 of the special user. As a result, for example, if the secondary use permission information in the user information database of Fig. 29(A) for user ID "u1" is in the "permitted" state, on the user terminal 300 of the special user, a secondary use OK icon 701 is displayed as shown in Fig. 28(B). However, after being updated to "not permitted" in step S602, based on the information transmitted in step S607B according to the display request in step S605, the secondary use OK icon 701 is not displayed next to the user name of user ID "u1". This makes it easy for the user to collectively manage the permission status of secondary use regarding their own posts. Also, data management in the distribution server 100 is simplified.

[0287] (Setting of Permission for Secondary Use at the Time of Posting) Also, the setting of permission for secondary use described with reference to FIGS. 28 to 31 may be set for each post at the timing when the user posts a thread, a comment, or the like. Hereinafter, an example in which the permission for secondary use can be set at the timing of the user's post will be described with reference to FIG. 32. FIG. 32(A) is an example of a screen when the secondary use permission button 501 is displayed on the user post screen exemplified with reference to FIGS. 17 and 18. Also, FIG. 32(B) is an example of a screen when the secondary use permission button 501 is displayed in the comment posting field 84 on the content screen exemplified with reference to FIG. 13 or the like. For example, the secondary use permission button 501 is displayed together with a message such as "Permit the operation and the affiliated talent to distribute or publish this post in a plan". Note that the secondary use permission button 501 in FIG. 32(B) shows an example of the display mode in the off state. In this way, by displaying the secondary use permission button 501 on the post screen, it is possible to set the permission for secondary use according to the post content every time the user posts. For example, when posting an image of fan art, by turning on the secondary use permission button 501 displayed on the post screen of FIG. 32(A) or (B), the secondary use permission information for each post information is associated with the content database in FIGS. 29(B) and (C). Based on this, on the user terminal 300 such as a talent, the secondary use OK icon 701 is displayed for the post of the fan art posted in the on state, so that it becomes easier to get the talent to introduce the fan art in the distribution or the like.

[0288] In addition, on the basis of the setting of whether or not secondary use is permitted on the user setting screen such as the my page illustrated in FIG. 28(A), it may be possible to make individual settings for each post in FIG. 32. For example, even if the default is permitted because the secondary use permission button 501 is in the on state and “permitted” on the my page, it may be possible to turn it off and set it to “not permitted” according to the post. Alternatively, there may be no setting of whether or not secondary use is permitted on the user setting screen, and the setting of whether or not secondary use is permitted may be individually set for each post timing in FIG. 32. In this case, the default may be either in the on state or the off state. If the default is in the on state, it can be set to the off state according to the post content, and if the default is in the off state, it can be set to the on state according to the post content.

[0289] <Examples of specific configurations and effects> (1-1) In the above-described embodiment, as described with reference to FIGS. 1 to 18 and the like, the distribution server 100 included in the communication system 1 can provide a user with a plurality of types of content associated with attributes (for example, communities, groups, units, talents, etc.) based on the stored program and the method of controlling a computer by the program (hereinafter simply referred to as a program). The attributes include a community (first attribute) corresponding to a plurality of types of groups A such as the communities displayed in the participating community list 50 in FIG. 6(A), groups B, etc., and a plurality of types of talents (talent ID, talent name), units (affiliated group 2), etc. (second attribute) stored in the talent information database in FIG. 5. Further, as described with reference to FIGS. 6, 7, 9, etc., in order to identify the participating communities and favorite talents preselected according to the operation from the user among the communities corresponding to a plurality of types of groups and a plurality of types of talents, etc., it is stored as account information 125 in the user information database, or stored in the storage unit 320 of the user terminal 300.

[0290] Furthermore, as described with reference to FIGS. 10, 11, 14 to 16, 27, etc., the distribution server 100 or the user terminal 300, in response to an operation on the recommendation filter 20, displays, on the display unit of the user terminal 300, content headings (60, 70, 90) of content (e.g., content stored in the content database of community A in FIG. 14) associated with the participating communities preselected and stored by the user, such as those illustrated in FIG. 15(B), in a first display state where the user can identify them, and extracts and displays content headings (60, 70, 90) regarding content associated with both the participating communities and the recommended talents preselected and stored by the user in a second display state as shown in FIG. 15(A) where the recommendation filter 20 is on, so that the user can identify them. By doing so, it is possible to switch between and display content headings that are displayed regardless of whether a recommended talent is associated with the content posted in the (participating) community preselected by the user, and content headings regarding content posted in the (participating) community preselected by the user and associated with a recommended talent. As a result, the user can easily identify preferred information. For example, for a user who has joined community A and selected the talent "AAA" with talent ID "t1" as the recommended talent, among the content stored in the content database of community A in FIG. 14, the content headings of the content associated with talent ID "t1" 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, etc. Note that the recommendation filter 20 can be turned on and off regardless of the level of the evaluation history status of each of the multiple users stored in the user information database illustrated in FIG. 7.

[0291] (1-2) Also, the on / off operation of the favorite filter 20 is an operation different from a series of operations when the user pre-selects a participating community or favorite talent, and is established in response to an operation on the icon of the favorite filter 20 displayed on the user terminal 300 from the user. As a result, when displaying the home screen in FIG. 10, the community screen in FIG. 11(A), the distribution schedule screen in FIG. 27, etc., there is no need for the user to perform an operation of re-selecting a participating community or favorite talent, or an operation of transitioning to a screen for selection. Instead, it is possible to switch and display so that the content heading related to the pre-selected community, or the content related to the community and the talent associated with both, is displayed. Therefore, the operability and user convenience can be improved.

[0292] (1-3) As illustrated in FIG. 15 etc., the favorite filter 20 is always displayed regardless of whether it is in the on-display state or the off-display state. As a result, the switching to the display screen that extracts the content associated with the favorite talent can be simplified and facilitated.

[0293] (1-4) Among the multiple types of content that can be provided to the user, there are communities corresponding to Group A, Group B, etc. of the affiliated group 1 in FIG. 5, and Community P that is always in a participating state regardless of the user's selection, which has an attribute (third attribute) different from that of a talent (or a unit of the affiliated group 2, etc.), and content associated with Feature 61 in FIG. 10 that is displayed to all users regardless of the community the user is participating in. The content heading 60 of the content posted in Community P and the content heading 60 of Feature 61 are displayed on the home screen of FIG. 10 regardless of whether the push filter 20 is on or off, regardless of the participating community or the favorite talent preselected by the user. In addition, since Community P is displayed on the channel list screen of FIG. 12, if the user selects the community bar 81c of Community P, the community screen of Community P (FIG. 11(A)) can be displayed. Thereby, by enabling the display of content headings related to attributes different from the attributes preselected by the user, it becomes possible to notify the user of information that, for example, the operator wants to notify all users regardless of the switching state.

[0294] (1-5) Among the multiple types of content that can be provided to the user, there is content (for example, article ID a99 in FIGS. 14 and 25) in which no related talent is associated and only the participating community is associated. When the push filter 20 is in the on display state, the content headings of the content in which only the participating community is associated and no related talent is associated are not displayed. Thereby, when the push filter 20 is in the on state, since the content headings of the content with no related talent are not displayed, it becomes easy for the user to identify information associated with the preferred community and the talent.

[0295] (1-6) As described with reference to FIGS. 5 and 6, etc., the favorite talents that can be pre-selected by the user are a plurality of talents belonging to (classified into) any of a plurality of groups A, B, etc. in group 1 of the belonging group in FIG. 5. Thereby, it becomes possible to specify information further narrowed down to the information of the talents preferred by the user from the information regarding the groups for classifying the talents.

[0296] (1-7) Also, as described with reference to FIGS. 5 and 6, etc., the favorite talents that can be pre-selected by the user can be selected for each belonging group 2, which is a unit smaller than belonging group 1. That is, it can be selected in unit units composed of a plurality of talents. Thereby, it becomes possible to specify information further narrowed down to the information of a unit composed of a plurality of characters preferred by the user from the information regarding the groups for classifying the talents.

[0297] (1-8) As described with reference to the home screen example in FIG. 10, the plurality of types of content that can be provided to the user can be classified into any of a plurality of types of categories including the recommended topic 62, and as illustrated in FIG. 10, it can be classified for each of the plurality of types of categories and displayed on the user terminal 300. Further, in the recommended topic 62, regardless of whether the recommendation filter 20 is on or off, the content headings 60 for a predetermined number of contents among the contents associated with any of the participating communities and recommended talents pre-selected and stored by the user are displayed so that the user can identify them. Also, in categories such as popular user posts 63, commemorative distributions 64, and goods 65 other than the recommended topic 62, as described with reference to FIG. 16, the content headings 60 corresponding to whether the recommendation filter 20 is on or off are displayed so that the user can identify them. By displaying the recommended topic 62, a part of the contents associated with the participating communities and recommended talents pre-selected by the user can be displayed without performing a switching operation of the display state. Therefore, the user can identify the contents associated with the preferred communities and talents without the trouble of the switching operation.

[0298] (1-9) Also, the content headings 60 of the recommended topic 62 on the home screen illustrated in FIG. 10 can be preferentially displayed, such as being displayed above the content headings 60 for the contents classified into other categories, regardless of whether the recommendation filter 20 is on or off. Thereby, it becomes easy for the user to identify the contents associated with the preferred communities and talents.

[0299] (1-10) As described with reference to FIG. 12, among the communities preselected by the user, by the user selecting the community bar 81 on the channel list screen of FIG. 12, the content screen for each community illustrated in FIG. 11(A) can be displayed. As a result, since the user can select a more preferred community from among the communities preselected by the user and display the content heading 70 for each selected community, the user can further extract arbitrary information as needed even from the information the user likes, improving convenience.

[0300] (1-11) As described with reference to FIGS. 24 to 26, each time the distribution server 100 and the user terminal 300 receive a tap action from the user on the content icon 708, a reception effect such as that shown in FIG. 24(A) or FIG. 24(B) is performed. As illustrated in the content-specific effect table of FIG. 25 for the reception effect, a fan mark or a talent effect display corresponding to the related talent associated with the content (article ID) that has received an action from the user is performed. As a result, since the reception effect by the tap action includes an effect related to the talent, it is possible to prompt the user to take a tap action.

[0301] (1-12) Further, when the reception effect of the tap action has received a predetermined number of tap actions from the user (for example, 100 times), a special effect such as a luxurious effect or a talent effect as illustrated in FIG. 24(B) is performed. As a result, since a special effect is performed when the tap action is performed a predetermined number of times, it is possible to prompt the user to take a tap action.

[0302] (1-13) Among the multiple types of content that can be provided to the user, there is content associated with a talent ID in the content database of FIG. 14 because related talents are associated with it. Regarding the content associated with related talents, regardless of whether the push filter 20 is on or off, the related talent 88 that displays the icon and name of the talent associated with the content is displayed. As a result, the user can identify the related talents associated with the content regardless of whether the push filter 20 is on or off, improving the convenience for the user. In addition, it can provide an opportunity to learn about new talents and the like.

[0303] (1-14) As described with reference to FIGS. 14, 17, and 18, the multiple types of content that can be provided to the user include posted content posted by the user. When a selection operation is performed on the related talent bar 40 in FIG. 17 at the time of posting from the user, if a related talent is associated with the posting information in steps S310 and S311 of FIG. 18, the content generated by the posting information is associated with a talent ID as illustrated in the content database of FIG. 14. As a result, talents can also be associated with user posts, facilitating the sharing of favorite information among users.

[0304] (1-15) The plurality of types of content includes the posted content (such as the article with the posting permission of "user" in FIG. 14) posted by the user through the user posting process described with reference to FIGS. 17 and 18. The users include a plurality of specific users corresponding to each of the talents in FIG. 5. For the posted content with actions such as tap actions or comments from the specific users, the content headings (60, 70) on the home screen in FIG. 10, or the community screen in FIG. 11(A), or the special action 79 is displayed together with the icon of the special user on the content screen in FIG. 13. Thereby, the user can easily identify that the content is the posted content on which the specific user has taken an action. Therefore, the convenience is improved for the users who seek information about the talents.

[0305] (1-16) When the content associated with the favorite talent pre-selected and stored by the user is posted based on the user information database in FIG. 7 and the content database in FIG. 14, the distribution server 100 and the user terminal 300 send a push notification to the user indicating that the content associated with the favorite talent has been posted. Thereby, it becomes easier for the user to identify the content information regarding the favorite talent. Also, if there is an action from a specific user for the posted content made by the user, the user can obtain a special feeling.

[0306] (1-17) As described with reference to FIG. 27, the distribution server 100 uses an API provided by the external web service 400 to obtain the attribute identification information 96a of the channel account to be distributed, the attribute identification information 96b of the handle included in the summary column 95 of the distribution screen in the external web service 400 in FIG. 27(C), the title 97, the information of the thumbnail image 99, etc. Since the obtained information includes the attribute identification information 96, the talent ID corresponding to the attribute identification information 96 is specified, and the distribution schedule screens in FIGS. 27(A) and 27(B) including the content heading 90 generated based on the specified talent ID are displayed on the user terminal 300. For example, if the information obtained from the external web service 400 includes the attribute identification information 96 corresponding to the talent "AAA", a content heading 90 associated with the talent ID "t1" of the talent "AAA" is generated. The information for specifying the content heading 90 is generated and stored by the content management unit 132. Therefore, among the groups corresponding to the channel accounts, the content headings 90 of the distributions related to the communities (groups) pre-selected by the user are displayed. Further, by a selection operation on the favorite filter 20, it becomes possible to narrow down and display the content headings 90 of the distributions in which the favorite talents appear. Thereby, for external submissions such as distributions provided by the external web service 400, it can be optimized according to the user's preference information and made easier for the user to identify.

[0307] (2-1) In the above-described embodiment, as described with reference to FIGS. 1 to 4, FIGS. 7 and 8, FIGS. 19 to 23, etc., the distribution server 100 included in the communication system 1 reflects the actions received from the user terminals 300 operated by each of the plurality of users stored therein to the user terminals 300 of each of the plurality of users so that each of the plurality of users can recognize them. Based on a program or a method of controlling a computer by the program (hereinafter simply referred to as a program), in response to an external evaluation, which is an evaluation from outside the user himself / herself such as the content and comments posted by the user as exemplified in FIG. 22, the evaluation history status such as the level and cumulative points of the user himself / herself is updated. Further, as exemplified in FIG. 19, the actions that a user whose evaluation history status is at a predetermined level can take are controlled so that users who are not at the predetermined level cannot take them. Further, for example, even if a user who is at a predetermined level 80 or higher, which is a specific situation, performs a specific action of posting content in which a link restricted for users at level 59 or lower is embedded, the content in which the link is embedded can also be displayed on the user terminal 300 of a user at level 59 or lower who is not in the specific situation. Thereby, the actions that a user can take are controlled in response to an external evaluation, which is an evaluation from outside the user who has taken the action. Moreover, since the specific actions received from a user in a specific situation can be reflected to a plurality of users (even when users not in the specific situation are included), it is possible to maintain good public order within the community.

[0308] (2-2) As described in steps S402 to S406 of FIG. 23, etc., the account management unit 133 allows a user whose level has increased and who has become in a specific situation to be able to take a specific action according to the level. Thereby, by allowing a user who has become in a specific situation in response to an external evaluation to be able to take a specific action, the actions that a user who is not in the specific situation can take are restricted, so that it is possible to encourage taking actions that lead to a specific situation in which a specific action can be taken, and the public order within the community can be maintained in a good state.

[0309] (2-3) As described with reference to FIG. 19, specific actions that can be taken are defined step by step according to the level. For example, if the level is 60 or higher, there is no restriction on the link to the content to be posted as a specific action, and if the level is 80 or higher, a project can be created as a specific action. These specific actions, as exemplified in steps S404 to S406 of FIG. 23, allow, for a user whose level has increased from 59 to 60, the restriction on the link to the content to be posted to be removed, and allow, for a user whose level has increased from 79 to 80 by increasing the level, the creation of a plan. Therefore, a user who has not reached a predetermined level is restricted from performing a specific action. By allowing, step by step according to the level, specific actions that are allowed for a user who has reached a predetermined level and is in a specific situation, it is possible to encourage actions aiming at a higher level, and the security within the community can be maintained in a good state.

[0310] (2-4) As described in steps S407 to S411 of FIG. 23 and the like, the account management unit 133 restricts a user whose level has decreased and is no longer in a specific situation from being able to take a specific action that was permitted according to the level. As a result, since a user who is no longer in a specific situation according to an external evaluation is restricted from being able to take a specific action, it is possible to encourage taking actions that can maintain and improve the specific situation, and the security within the community can be stabilized.

[0311] (2-5) As described with reference to FIG. 19, specific actions that can be taken according to the level are defined step by step. For example, if the level is 59 or lower, since it is not allowed to lift the restriction on the link for the content to be posted, which is a specific action, there is a restriction on the link for the content to be posted. If the level is 79 or lower, since it is not allowed to create a project, which is a specific action, there is a restriction on creating a project. These specific actions, as exemplified in steps S409 to S411 of FIG. 23, by lowering the level, restrict the link for the content to be posted that was allowed for a user whose level has changed from 60 to 59. Also, by lowering the level, for a user whose level has changed from 80 to 79, in order to restrict the creation of a project that was allowed, a user who is no longer at a predetermined level is restricted from performing a specific action. Thereby, by gradually restricting the specific actions allowed for a user who is no longer in a specific situation, it is possible to prevent the actions that can be extremely taken from decreasing, and at the same time, it is possible to encourage actions that can maintain and improve the specific situation, and the public order within the community can be maintained in a good state.

[0312] (2-6) As described with reference to FIG. 8, the user history status 55 in which the level and cumulative points, which are information regarding the evaluation history status of the user, are displayed is not publicly disclosed to other users, while the user himself / herself can confirm it on the my page screen. Thereby, since the information related to the evaluation history status updated according to the external evaluation can be notified to the user himself / herself, it is possible to encourage the user to make efforts to improve the public order of the community while grasping his / her own situation.

[0313] (2-7) As described with reference to FIG. 22 and the like, the external evaluation that can update the evaluation history status of the user includes point assignment due to a favorable impression from the operator and negative evaluations. Thus, since the external evaluation includes the evaluation from the operator who is a third party different from the user, it is difficult for personal feelings to intervene in the external evaluation, and the external evaluation can be fair.

[0314] (2-8) As described with reference to FIG. 22 and the like, external evaluation that can update the user's evaluation history status includes evaluations such as a favor action or a report from other users different from the user who took the action among a plurality of users who use the community app. In this way, since the external evaluation includes evaluations from other users different from the user who took the action, the public order within the community can be made to conform to the intention of all users.

[0315] (2-9) As described with reference to FIG. 19 and the like, for content and comments subject to restrictions such as non-display and reporting, restriction processing such as non-display is performed on each user terminal 300 of a plurality of users from users who are allowed a specific action of "moderator invitation" with a level of 90 or more or users who are allowed a specific action of "report count" with a level of 70 or more. Thereby, since the restriction processing for the user's action is performed on the action subject to restriction by the user whose evaluation history status is a predetermined status, it is possible to suppress the situation where the restriction processing for the user's action is performed arbitrarily.

[0316] (2-10) Also, the reflection of the action subject to restriction from a predetermined number of users who are allowed the specific action of "report count" described with reference to FIG. 19 and the like is restricted on each user terminal 300 of a plurality of users. Thereby, since the action received as the action subject to restriction by a predetermined number of users whose evaluation history status is a predetermined status is regarded as a nuisance action and the reflection of the action is restricted, it is possible to efficiently restrict nuisance behaviors and the like without hindering free communication and communication.

[0317] (2-11) As described with reference to FIG. 19 etc., according to the level which is the evaluation history status of each of a plurality of users, for example, if it is level 50 to 59, privilege E is granted, and if it is level 100, a privilege S which is rarer than privileges A to E can be granted. According to such a configuration, since a privilege can be granted according to the evaluation history status, it is possible to prompt the user to be aware so as to be in an evaluation history status where a privilege is granted.

[0318] (2-12) A plurality of users belong to the same fan community, and actions that a user can take include, for example, a publicity act of posting about a group to be supported or distribution videos and goods which are contents related to the talents belonging to the group. The distribution server 100 has its external evaluation fluctuate according to the number of views of the distribution video due to the publicity act and the degree of contribution to profits such as goods sales, and the evaluation history status of the user is updated. As a result, it can serve as a motivation for the user to perform a publicity act, and the community becomes activated.

[0319] (3-1) In the above-described embodiment, a program that can reflect on each of the user terminals 300 of the plurality of users so that each of the plurality of users can recognize content such as threads and comments, which are actions received from the user terminals 300 operated by each of the plurality of users, such as posting content, allows, in steps S601 to S604 in FIG. 30, whether content posted by a user can be reused, for example, by an operator or a talent introducing the user's posted content via video distribution or quoting it within the posted content. This can be set according to the operation of the reuse permission button 501 on the user setting screen in FIG. 28(A) by the user or the operation of the reuse permission button 501 at the time of content posting in FIG. 32. Also, in the user information database in FIG. 29(A) when the reuse permission button 501 is in the on state on the user setting screen in FIG. 28(A), when the reuse permission information of "permission" is associated with the user, or in the content database in FIG. 29(B) or the comment database in FIG. 29(C), when the reuse permission information of "permission" is associated with a thread or a comment, information (suggestion information) for displaying the reuse OK icon 701 in FIG. 28(B) indicating that the posted content can be reused can be reflected by step S607 in FIG. 30 and step S607B in FIG. 31. As a result, since the setting of whether to allow the posted content to be reused can be performed according to the user operation, it is difficult to cause a misunderstanding that the posted content can be reused, and the reuse can be made smooth.

[0320] (3-2) In the above-described embodiment, icons such as the reuse OK icon 701 in FIG. 28(B) indicating that the posted content is reusable are not reflected on the user terminals of users who do not meet the specific conditions, but can be reflected only on the user terminal 300 of users who meet the specific conditions, such as special users in FIG. 5 and operators. This can prevent the reuse OK icon 701 from being displayed on the user terminal 300 of general users who do not meet the specific conditions, which may prompt reuse for users who do not meet the specific conditions (for example, users with low need for reuse), and prevent unintended use or abuse by the operator or users.

[0321] (3-3) In the above-described embodiment, the user can select whether to permit the reuse of the posted content by operating the reuse permission / denial button 501 in FIG. 28(A) on the user setting screen such as the user's my page in FIG. 8. This enables the user to select whether to permit the reuse of the posted content when setting information about the user, thus facilitating the user's management of the reuse permission / denial status of the posted content.

[0322] (3-4) In the above-described embodiment, when the secondary use permission / non-permission information of "permission" is associated with the user in the user information database of FIG. 29(A) according to steps S601 to S602 of FIG. 30, or when a post is made with the secondary use permission / non-permission button 501 in the on state on the post screen of FIG. 32, etc., when the user permits secondary use, the post content received can be managed as content information with secondary use permitted in the content database of FIG. 29(B), the comment database of FIG. 29(C), etc. in steps S603 to S604 of FIG. 30. Also, when displaying content information such as the article ID "a3" in FIG. 29(B) on the user terminal 300, the secondary use OK icon 701 in FIG. 28(B) can be displayed according to steps S603 to S607 of FIG. 30. As a result, since the secondary use OK icon 701 is displayed for posts received when the user permits secondary use, the user can set the permission / non-permission of secondary use according to each post, and the processing burden when reflecting the post content in the distribution server 100, etc. on the user terminal 300 is reduced.

[0323] (3-5) In the above-described embodiment, when displaying the content screen such as the article ID "a3" in FIG. 29(B) posted by the user on the user terminal 300 according to steps S605 to S607B of FIG. 31, the secondary use OK icon 701 can be displayed based on the secondary use permission / non-permission information in the current user information database of FIG. 29(A) of the user. As a result, it becomes easier for the user to manage the permission / non-permission state of secondary use regarding their own post content. Also, for the operator (and also for the server), since the permission / non-permission state of secondary use only needs to be managed for each user, the management becomes easy.

[0324] (3-6) Also, based on the display request information in step S605 of FIG. 31, regardless of whether the content screen or the like is reflected on the user terminal 300 in steps S607B and S608, or whether it is in a state where it can be reflected, the user can operate the secondary use permission / denial button 501 on the user setting screen such as in FIG. 28(A). Even if the content screen with the secondary use OK icon 701 shown in FIG. 28(B) is displayed on the user terminal 300, due to a reload operation or the like, based on the secondary use permission / denial information updated in step S602 of FIG. 31, in steps S605 to S607B, according to the current user's secondary use permission / denial state, the content screen without the secondary use OK icon 701 can be updated. Thereby, even if the screen of the content posted on another user's user terminal 300 is displayed, the display state of the secondary use OK icon 701 can be updated according to the operation from the user. Thereby, it becomes possible to change the permission / denial state of secondary use even when the user wants to change the permission / denial state of their own posted content afterwards, and the convenience of the user can be improved.

[0325] (3-7) In the above embodiment, by displaying the secondary use permission / denial button 501 on the thread posting screen in FIG. 32(A) and the comment posting screen in FIG. 32(B), when the user posts content such as a thread or a comment (every time a post is made), the permission / denial state of secondary use of the posted content can be set. Thereby, the convenience of the user can be improved.

[0326] <Modification Example> Modification examples and the like for the above-described embodiment are listed below.

[0327] (Regarding content information) In the above-described embodiments, content headings (60, 70, 90) such as those in FIGS. 10, 11, and 27 were exemplified as content information regarding content (e.g., news articles, posting information from users, etc.). However, it is not limited to this, and the content information regarding the content may be, for example, explanatory information on the screen of the content itself exemplified in FIG. 13. For example, it includes various information displayed on the content screen itself in FIG. 13, such as the poster 71, the content 74b, the related talent 88, the special action 79, and the number of tap actions 78.

[0328] (Regarding attribute selection processing) In the above-described embodiments, an example in which the selection of participating communities and favorite talents can be made in steps S102 to S104 of FIG. 9 at the time of first login was described. At the time of first login, it is not necessary to select both the participating communities and the favorite talents in step S103, and an operation of not selecting either (the selected attributes are zero) may also be possible. Also, only one of the participating communities or the favorite talents may be selected, and it may be necessary to select one of them. For example, even if a favorite talent is selected, if the user has not joined the participating community corresponding to the group to which the favorite talent belongs, information regarding the favorite talent may not be extracted and displayed on the content screen. That is, even if the favorite filter 20 is turned on, the content headings of talents belonging to a group corresponding to a community that the user has not joined are not displayed. Alternatively, it may be that the selection of a favorite talent cannot be made unless a participating community is selected. For example, if none of the participating communities are selected, it may not be possible to proceed to the screen for selecting a favorite talent.

[0329] In the above-described embodiment, in step S101 of FIG. 9, when it is determined that it is the first login, an example in which the selection screen of the participating communities and favorite talents illustrated in FIG. 6 is displayed in step S102 has been described. At this time, for the participating community setting in FIG. 6(A) or the favorite talent setting in FIG. 6(B), all selections may be made in advance (by default).

[0330] In the above-described embodiment, in steps S101, S102, etc. of FIG. 9, an example in which if it is the first login, the attribute selection screen is displayed on the user terminal 300 in step S102 has been described. However, it may not be displayed on the screen at the time of the first login, and the selection of the first attributes may be made later from the my page or the like. Also, until the user edits it later on the my page or the like, at the time of the first login, the user may be in a state of participating in all communities.

[0331] In the above-described embodiment, in the case where it is not the first login (NO in step S101 of FIG. 9), after the setting edit screen of FIG. 6 is displayed, the determination that the participating community or favorite talent is selected in step S107 has been described with an example where it is the timing when a selection operation is performed on an icon or the like. However, it is not limited to this. By operating the home icon 13 or the like displayed at the bottom of the app screen to move to another screen, it is regarded as if the attributes selected on the attribute selection screen of FIG. 6 are determined, and information is transmitted and received and then selected, and the process may proceed to step S108. Alternatively, on the attribute selection screen of FIG. 6, when there is an operation on the display of each participating community or the display of each talent, instead of or in addition to that, a determination icon or the like may be displayed, and it may be determined that the selection is made when there is an operation on the determination icon (when the information transmitted in response to the operation is received). Also, when there is an operation on the determination icon, a special effect may be performed on the user terminal 300.

[0332] (Regarding the display mode 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, for the content with comments or tap actions from special users corresponding to talents, an example in which the special action 79 is displayed together with the icons of special users within the content heading 70 has been described. When the talent who performed the action on the content is the favorite talent preset by the user, the display mode of the special action 79 displayed within the content heading 70 or the like may be displayed in a mode different from the case where the talent who performed the action is not the favorite talent, or the content heading 70 itself may be displayed in a mode different from the case where the talent who performed the action is not the favorite talent. Alternatively, when the talent who performed the action on the content is the relevant talent himself / herself associated with the content, the display mode of the special action 79 displayed within the content heading 70 may be displayed in a mode different from the case where the talent who performed the action is not the relevant talent himself / herself, or the content heading 70 itself may be displayed in a mode different from the case where the talent who performed the action is not the relevant talent himself / herself. The different modes are, for example, modes with different colors, modes with different message contents, modes with different presence or absence of messages, and the like.

[0333] (Regarding the display mode of comments on the content screen) In the above-described embodiment, in the content screen described with reference to FIG. 13 and the like, when each comment 87 is a comment from a special user corresponding to a talent, an example in which a change in the display mode or a change in the display order can be made was described. Instead of or in addition to this, when the talent (special user) who commented on the content is the favorite talent preset by the user, the display mode of the comment 87 of the favorite talent may be displayed in a mode different from the case where the talent who performed the action is not the favorite talent. Or, it may be displayed at the top of each comment 87. Or, when the talent who commented on the content is the person of the related talent associated with the content, the display mode of the comment 87 of the person of the related talent may be displayed in a mode different from the case where the talent who performed the action is not the person of the related talent. The different modes are, for example, modes with different colors, modes with different message contents, modes with different presence or absence of messages, etc. Or, it may be displayed at the top of each comment 87.

[0334] (Regarding the categories displayed on the home screen) In the above-described embodiment, an example of being displayed in the feature 61 that is displayed on the home screen described with reference to FIG. 10 regardless of whether the user has selected any participating communities and any favorite talents was described. However, it is not limited to this, and the feature 61 may not be displayed. For example, only the content posted to the participating communities preselected by the user (including communities that are always in a participating state regardless of the selection) may be displayed on the home screen. Or, the feature 61 may be displayed on a different screen from the home screen where the content headings 60 are displayed for each category.

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

[0336] (Notification to the user) In the above-described embodiments, an example has been described in which a push notification is sent when there is a post of content associated with a favorite talent pre-selected by the user. In addition to this, when there is a comment from the talent himself / herself, who is a special user, to the content, a notification (display on the notification screen or push notification, etc.) may be sent to the general user. Alternatively, the notification may be sent only when there is a comment from the favorite talent himself / herself. Alternatively, when there is a comment from the talent himself / herself who is the favorite talent pre-set by the user, the notification mode may be different from when there is a comment from a talent who is not the favorite talent. The change in the notification mode means that, for example, if it is a notification from the favorite talent, the notification icon 15 displayed at the bottom of the app screen may be emphasized.

[0337] Also, when there is a favorable action such as a comment or a tap action from another user including a special user on a post (content or comment) made by the user, a notification (display on the notification screen or push notification, etc.) may be sent to the user who made the post. At this time, for example, normally, the notifications are sent together once an hour, but when there is an action from a special user who is a talent or from a special user who is a favorite talent, the notifications may be sent in real time.

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

[0339] (Regarding attribute extraction processing) In the above embodiment, when the favorite filter 20 is turned on, an example in which content headings (60, 70) associated with the favorite talents preselected by the user are extracted and displayed has been described. However, when multiple people are selected as favorite talents, it may be possible to further narrow down the talents individually for each favorite talent. For example, if talents with talent IDs "t1", "t2", and "t3" are selected, when turning on the favorite filter 20, it may be possible to select them individually with "t1", "t2", and "t3". Alternatively, when the favorite talents are preselected in units, it may be possible to select them individually in units. Furthermore, by preselecting a more special talent (the most favorite talent) from the favorite talents in advance, it may be possible to create a further filter with the most favorite talent. In this way, after extracting all the favorite talents with the favorite filter 20, it may be possible to perform filtering in multiple stages such as the first, second, third, etc., where individual selection (further narrowing down) can be performed by operating a predetermined icon or the like.

[0340] Also, when the favorite talents are preselected in units, if content associated with any of the talents included in the unit is posted, by turning on the favorite filter 20, it may be possible to extract and display the content headings of the content associated with any of the talents of the unit preselected by the user.

[0341] Even between communities that are different from the community corresponding to the affiliated group to which the talent belongs, it may be possible to associate any talent. For example, the talent ID "t1" belongs to the "Group A" of the affiliated group 1, but it may be associated with the content posted within the "Community B" corresponding to the "Group B". Therefore, for a user who has selected the talent ID "t1" and also participated in the "Community B", if they perform an operation to turn on the favorite filter 20 on the home screen or the content screen within the "Community B", the content associated with the talent ID "t1" will be extracted and displayed. As a result, even if there is a collaboration plan between different groups and the posting has only been made within the community corresponding to one of the groups, the user can obtain the information of the favorite talent without missing it. Note that even if the user has not participated in the "Community B", the content associated with the favorite talent may be displayed on the home screen.

[0342] (Regarding the predetermined conditions in the attribute extraction process) In the above embodiment, as an example of the predetermined conditions for turning on or off the favorite filter 20, which was described with reference to FIGS. 15 and 16, etc., an example was described where when the user taps the icon of the favorite filter 20 displayed on the user terminal 300, the predetermined conditions are satisfied when it is turned on. However, it is not limited to this. The predetermined conditions may be any conditions as long as the on / off of the favorite filter 20 can be switched according to the user's intention. For example, it may be possible to switch by voice instruction or by vibrating the user terminal 300 itself (such as shaking).

[0343] (Regarding the storage state of the favorite filter 20 in the attribute extraction process) In the above embodiment, regarding the on memory state of the push filter 20 after the operation on the push filter 20, after the content screen in FIG. 13 is displayed after the application is launched, even when returning to the content screen or the home screen where the push filter 20 was on, an example where the on state of the push filter 20 is memorized and maintained has been described. However, not limited to this, when moving to a different screen, the push filter 20 may always be in either the on or off state. For example, after displaying the community screen in FIG. 13 from the community screen (or the home screen in FIG. 10) where the push filter 20 is in the on or off state, when returning to the community screen (or the home screen in FIG. 10) in FIG. 11, the push filter 20 may be off or on. Alternatively, when the push filter 20 is turned on on the home screen in FIG. 10 (or the community screen in FIG. 11), and after displaying the community screen (or the home screen in FIG. 10) in FIG. 11, when returning to the home screen (or the community screen in FIG. 11) in FIG. 10, the push filter 20 may be in the off or on state.

[0344] (Regarding user post processing) In the above embodiment, in the example of the user post screen in FIG. 17, an example where the post screen for character input and image upload in FIG. 17(A) and the screen for selecting categories and related talents in FIG. 17(B) are separated has been described. However, not limited to this, FIG. 17(A) and FIG. 17(B) may be displayed on one screen for input or selection or the like. For example, scrolling or the like may be possible, and it may not be necessary to transition to another screen. Also, it may be possible to post even without character input or image upload. Alternatively, even if there is no title, it may be possible to post if character input or an image has been uploaded.

[0345] Also, although examples where the selection of categories and related talents is optional have been described, either or both of them may be made mandatory. Alternatively, it may be possible to select "no category" or "no related talent", and it may be possible to make selections for each unit in the second belonging group in FIG. 5. Further, when selections are made for each unit, the talent ID of each individual talent belonging to the unit and the unit ID for identifying the unit may be associated with the content. Alternatively, only the unit ID may be associated.

[0346] (Regarding the evaluation history status update process) In the above-described embodiments, an example has been described in which, in step S406 and step 411 in FIG. 23, it is notified that permission or restriction of a specific action has been made. However, it is not limited to this, and the notification to the user in step S406 and step S411 may not be made. Alternatively, when an action is permitted in step S406, it may be notified, but when an action is restricted in step S411, only either one of them may be notified, such as not notifying. For example, by not notifying when a restriction is imposed, it is possible to avoid disturbing the user.

[0347] (Regarding other examples of the evaluation history status) In the above-described embodiments, as described with reference to FIG. 19, the user's level rises step by step according to the external evaluation from the initial setting level, and every time a specific situation (for example, level 60, level 80, etc.) is reached, a specific action that can be taken is permitted according to the level. However, it is not limited to this. For example, for all users, the specific action in FIG. 19 may be permitted in the initial setting, and as the level decreases, it may gradually disappear in a specific situation, and the ability to take a specific action may be restricted. Also, the initial setting level is not limited to the lower limit of 1 or the upper limit of 100, and may start from 80 or the like, and the ability to take a specific action may be gradually permitted or restricted according to the change in the level.

[0348] In the above-described embodiments, an example in which changes in the user's level and cumulative points are due to external evaluations from outside the user himself / herself has been described. However, in addition to this, the cumulative point count may increase when the user performs a tap action on the posts or comments of other users, or when the user comments on other users in addition to this. As a result, the user will become more active within the community, and the community will be activated.

[0349] In the above-described embodiments, an example in which when there is a non-display or report on the content or comments posted by the user, the points decrease and the actions are gradually restricted has been described. Instead of this, or in addition to this, separate from the points (fluctuating cumulative points) that affect the level, a reflection restriction point that is a criterion for regulating the reflection of actions within the community application may be defined for the evaluation history status. For example, for a user who has received a certain number (for example, 20 when any one or all are added together) of non-displays or reports from other users for the posted content, comments, etc., the actions may be restricted (reflection restricted). For example, the content, comments, etc. posted by a user subject to reflection restriction may not be displayed to other users for a certain period, or the posting of content, comments, etc. itself may not be possible for a certain period.

[0350] Note that the said reflection restriction may be executed according to the level that fluctuates according to the number of points in FIGS. 22, 23, etc. described above. For example, a negative level lower than 1 may be provided, and reflection restriction may be performed on a user who has reached a negative level. Alternatively, the default level at the start of the community application may be set to 10, and restrictions may be imposed as the level becomes lower than 10.

[0351] (Regarding the like action from a user in a predetermined situation) In the above-described embodiments, an example in which the action content such as special actions that can be taken for each level described with reference to FIG. 19 varies has been described. Instead of or in addition to this, it may be possible to make it possible for other users to recognize that a user has a high level. For high-level users, it is considered that they tend to take actions that make the atmosphere within the community positive and have a high level of reliability. Therefore, the display mode of content for which a high-level user (for example, level 90 or higher) has taken a favorable action (including tap actions and favorable comments) may be changed. Alternatively, the display mode may be changed only when favorable actions are received from a plurality of highly reliable users (for example, a predetermined number such as 5 people). For example, the display mode of the content heading 60 on the home screen in FIG. 10, the content heading 70 in FIG. 11(A), or the mode of the number of tap actions 78, etc., may be changed in color or a mark (for example, a special action 79, etc.) indicating that an action has been taken from a highly reliable user may be displayed. Alternatively, on the content screen illustrated in FIG. 13, a display (top display or color change) that makes the comment prominent may be performed. Also, when content or comments have received favorable actions from a plurality of highly reliable users, push notifications or displays in announcements may be made.

[0352] In addition, for the user who has posted content or comments for which a favorable action has been taken from the highly reliable user, it may be possible to notify that an action has been taken from the highly reliable user. For example, it may be possible to send a push notification to the user terminal of the corresponding user, or to display it in a notification within the application.

[0353] In the above-described embodiment, from a predetermined number (for example, 5) of users at level 70 or higher who are the targets of "report count" in FIG. 19, for the content or comment itself that is subject to restrictions such as non-display or reporting, or for the user, an example was described in which the content itself is made non-displayable to each of the user terminals 300 of a plurality of users, or the content posted by the restricted user is made non-displayable. For the restriction processing of the content or the like itself that is the target of these restrictions and the restriction processing of the user who posted the content or the like that is the target of the restrictions, the conditions for the number of users in a predetermined situation (for example, level 70 or higher) where non-display or reporting has been performed may be made different. For example, a restriction process is performed to make the content, comments, etc. that are the targets of restrictions non-displayable to all users from the first number (for example, 5) of users at level 70 or higher who are the targets of "report count", and from the second number (for example, 20) that is larger than the first number, for the users for whom non-display or reporting has been performed on the content, etc. they posted, a restriction process may be performed to make all the content, etc. posted by the user who has been reported, etc. non-displayable to all users.

[0354] Also, the content and comments posted by a user for whom a predetermined number of non-displayed or reported users has accumulated from users at level 70 or higher who are the targets of "report count" can be made non-displayable to all users. For example, the content and comments posted by a user who has been non-displayed or reported by 5 users at level 70 or higher can be made non-displayable to all users.

[0355] Note that the user to be made non-displayable may not include the user himself / herself who posted the comment or content. As a result, although the content and comments posted by the user himself / herself are reflected on the user's own terminal, for example, without an action from other users, it is possible to detect (make the user aware) that the content has become a target of restrictions.

[0356] (Regarding notification of information related to the evaluation history status) In the above-described embodiments, an example has been described in which each user can check their own "level" and "accumulated points" in the user evaluation history status 55 on the my page illustrated in FIG. 8. However, not limited to this, the level and accumulated points, which are information regarding the user's evaluation history status, may not be notified to any other user except the user himself / herself, while only the operator can check them on the administrator terminal 200 or the like. Thereby, while not notifying any user of the information related to the evaluation history status updated according to the external evaluation, the operator can be notified, so that it is possible to prevent the user's actions from being overly restricted, and the operator can grasp the information related to the user's evaluation history status and utilize it for operation. Also, the user can use the fan community more comfortably without being overly concerned about their own "level".

[0357] In the above-described embodiments, information related to the evaluation history status described with reference to FIG. 23 or the like may be notified to the user as feedback. For example, the increase or decrease in points updated according to the external evaluation during a predetermined period (for example, one day or one week), or the up or down of the level, etc., may be fed back to the user as the result of today's (or this week's) actions. Alternatively, instead of or in addition to this, for the text of the content or comment (action taken by the user) posted by the user during a predetermined period, for example, sentiment analysis by AI may be performed, and the ratio of positive words, the ratio of negative words, or the ratio of words not classified into either may be notified to the user (for example, displayed on a pop-up screen at a predetermined time, or displayed on a notification page, etc.). Thereby, the user can objectively know the tendency of the actions they have taken, and can be encouraged to take actions to improve the security within the community.

[0358] (Regarding external evaluation) In the above-described embodiments, an example was described in which a user's points decrease when there are actions such as hiding or reporting on content, comments, etc. posted by the user. In addition to this, for example, when hiding, the reason for hiding may be selectable on a screen such as Fig. 11(B), or input may be possible. This is because, as a reason for a user to hide or the like an action of another user, there may be cases where actions that do not have a negative impact on the community and do not deteriorate public order due to personal reasons such as being a rival user are hidden. Therefore, hiding or the like that does not substantially have a negative impact on the community may not affect the user's point count, and only hiding or the like that substantially has a negative impact may be made to affect the point count. For example, options for hiding that affect points and those that do not may be predetermined in advance, and the operator may check the reason for hiding and perform an operation to affect the point count for hiding determined to have a negative impact.

[0359] In the above-described embodiments, an example was described in which a user's points fluctuate according to external evaluations such as tap actions or comments on actions such as content and comments posted by the user. Regarding the content posted by this user, there may be a limit on the number of posts. For example, as an example of external evaluation that increases points, the number of views of a distribution video through the content posted by the user, the degree of contribution to the benefit of the support target such as the number of goods purchased, etc. were exemplified. However, since there is a risk that the posting of content will become chaotic in an attempt to increase points, for example, a limit such as once a day may be imposed on the posting of content. Also, for users with a high level and high reliability, the upper limit of the number of content posts per day may be increased.

[0360] (Regarding the user terminal on which the secondary use OK icon 701 is displayed) In the above-described embodiment, in the secondary use-related process described with reference to FIGS. 28 to 31, an example was 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, it is not limited to this, and it may be displayed on the user terminal 300 of a user who does not satisfy the specific condition. By displaying the secondary use OK icon 701, it can also serve as a mark that the talent is being supported, and it is likely to create a positive atmosphere and sense of unity in the entire fan community, such as a positive attitude of actively supporting the talent. In addition, the atmosphere within the community of actively supporting the talent can also motivate the user 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 the user does not satisfy the specific condition, the secondary use OK icon 701 may be displayed on the user terminal 300 of the poster himself / herself. This makes it easy to check the permission status of secondary use for each of his / her own posts.

[0362] (Regarding extraction of only posts for which secondary use is permitted) In the above-described embodiment, as exemplified in FIG. 28(B), etc., since the secondary use OK icon 701 is displayed for posts permitted for secondary use, an example has been described in which a talent or the like, who is a user satisfying specific conditions, can identify post content permitted for secondary use. However, instead of or in addition to the case where the secondary use OK icon 701 is displayed, based on information (suggestive information) that enables identification of the secondary use permission / non-permission status received together with post-related information in step S607 of FIG. 30 or step S607B of FIG. 31, by means of a filtering function or the like based on an operation on a predetermined icon by the user, it may be possible to switch from a state in which posts permitted for secondary use and those not permitted are mixed and displayed to a state in which only posts permitted for secondary use are extracted and displayed. Thereby, it becomes easier to identify post content permitted for secondary use, and the convenience for operators and talents who perform secondary use can be improved. Also, for example, when performing video distribution or the like, even if the screen of the fan community app is shown, it is possible to prevent non-permitted secondary use posts from being shown.

[0363] (Regarding other aspects of the secondary use OK icon 701) In the above-described embodiment, as exemplified in FIG. 28, etc., an example has been described in which the secondary use OK icon 701 is displayed for content permitted for secondary use by the user. However, not limited to this, a mark seemingly unrelated to secondary use (quotation) (for example, just a star mark, etc.) may be displayed, and it may be made possible for a user who knows that the seemingly unrelated mark is a secondary use permission mark to recognize that secondary use is possible.

[0364] (Regarding the sharing icon for secondary use) In the above-described embodiment, the secondary use OK icon 701 is displayed for the content posted by the user through the secondary use permission-related process described with reference to FIGS. 28 to 32 and the like. Thus, it has been described that it becomes easier for an operator, a talent, or the like to reuse the content in other media such as a distribution video. Instead of or in addition to this, not only for use in other media, but also for reuse by making it possible to quote in other posts within the fan community app, which is the same medium as the medium in which the post was made. For example, for the posted content for which secondary use is permitted, a post link (secondary use information) that enables transition to the posted content to be reused may be embedded in other posted content using a sharing icon for each post, so that it can be shared. Also, it may be possible to quote in posts outside the fan community app, which is the same medium as the medium in which the post was made. By pasting the URL generated by operating the sharing icon of the posted content for which secondary use is permitted into a post on another SNS or the like, it may be possible to quote the posted content for which secondary use is permitted. Also, the sharing icon may be displayed or operable only for users who satisfy specific conditions. As a result, it becomes easier for a user who performs a secondary use operation such as operating the sharing icon to reuse the posted content.

[0365] (Regarding the change of secondary use permission information for each content after posting) In the above-described embodiment, an example has been described in which reuse permission information for user information databases at the time of posting, which was described with reference to FIG. 30, and reuse permission information is associated with each piece of posting information for threads and comments based on the on / off state of the reuse permission button 501 selected at the time of posting, which was described with reference to FIG. 32. Instead of this, or in addition, for example, on the screen showing a list of threads and comments posted by the user, which is displayed when the user's own posting icon 32 in FIG. 12 is selected, a reuse permission button 501 may be displayed for each posting, and it may be possible to subsequently switch the on / off state of the reuse permission. Also, an icon that allows the on / off switching of the reuse permission status may be displayed only on the user terminal 300 of the user who is the poster, for each piece of posted content itself. Thereby, the user can subsequently change, for each piece of content, the information on whether to permit the reuse of the posted content without deleting the posting.

[0366] (Regarding the setting of reuse permission for each type of content) The setting of reuse permission described with reference to FIGS. 28 to 32 and the like in the above-described embodiment may not be applied to all content posted within the fan community, but only to some content. For example, it may be made possible to set according to the type of content, or it may be made possible to set for content posted to a specific channel with a high possibility of being reused. Content with a high possibility of being reused includes, for example, a channel for soliciting questionnaires and a dedicated channel for posting user's secondary creations.

[0367] Also, on a user setting screen such as a my page, it may be possible for the user to set whether to permit reuse according to the type of content. For example, it may be possible to set the permission for reuse for each channel, and it may be possible to set to permit reuse for channel X and not to permit reuse for channel Y.

[0368] (Regarding the permission setting for secondary use for each secondary user) In the above embodiment, the setting of permission for secondary use described with reference to FIGS. 28 to 32 and the like is an example in which, by turning the secondary use permission button 501 on or off, an operator, a talent, etc. are uniformly given the option to permit or not. However, it is not limited to this, and it may be possible to set whether to permit all those who perform secondary use or to individually permit secondary use 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 previously selected by the user as their favorite talents. In the user setting screen such as FIG. 28(A), the secondary use permission button 501 may be displayed together with each option such as "only for operators and talents", "only for talents", "only for specific talents", etc., and selection may be possible.

[0369] Although the case where the person performing secondary use is an operator or a talent has been described, other general users may also be included as those who perform secondary use. In this case, secondary use by other general users may be prohibited, and settings such as permitting secondary use for operators and talents may be individually possible.

[0370] (Regarding the display of secondary use having been completed) In the above-described embodiment, since permission was given in the setting of permission for secondary use with reference to FIGS. 28 to 32 and the like, information suggesting that the posted content has been secondarily used may be reflected in the content for the posted content secondarily used by an operator, a talent, or the like. For example, for the content that has been secondarily used, a predetermined setting (for example, operation of a predetermined icon or setting of a used flag) is made from the user terminal 300 operated by the talent, the administrator terminal 200 of the operator, or the like, so that an icon indicating that the content has been secondarily used may be displayed. Thereby, it is possible to notify the poster that the content has been used, and the motivation in the fan activities of the user can be improved. Further, the icon indicating that the content has been used may be displayed on the user terminal 300 of the poster himself / herself of the content, but not on the user terminals 300 of other users. Thereby, it is possible to prevent a sense of superiority or inferiority from arising between the user who has posted content that has been secondarily used and the user whose content has not been secondarily used.

[0371] (Regarding reflection of the state where secondary use is permitted) The information in which the secondary use permission / no permission information is updated to "permitted" by a user operation in steps S501 and S502 of FIGS. 30 and 31 described in the above embodiment may be made identifiable by other users after a certain period has elapsed after the update to permission (for example, after 5 minutes or after 1 day has elapsed). That is, even if the secondary use permission / no permission button 501 is turned on by a user operation, the secondary use OK icon 701 may not be displayed on, for example, the screen of the posted content illustrated in FIG. 28(B) until a certain period has elapsed. Thereby, it is possible to reduce the possibility that the user accidentally sets the secondary use permission / no permission state to "permitted" and the content is secondarily used (quoted) before an operation to cancel it (such as an operation to turn off the secondary use permission / no permission button 501).

[0372] (Regarding other application examples of secondary use permission / no permission related processing) In the above-described embodiment, an example in which the secondary use approval-related process described with reference to FIGS. 28 to 32 is executed in the distribution server 100 that provides the fan community application has been described. However, the present invention is not limited to this, and the secondary use approval-related process is applicable to a user-generated content (UGC) platform where a user posts comments, images, videos, etc. For example, in an image sharing platform, a user may be able to set to post such that a display indicating "OK to introduce on other media!" or "OK to freely use the image!" is made.

[0373] 〔Example of Realization by Software〕 The various control blocks of the control unit included in a computer such as the server and the terminal in the above-described embodiment may be realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or may be realized by software using a CPU (Central Processing Unit). When realized by software using a CPU, a computer provided with the control unit includes a CPU that executes instructions of a program that is software for realizing each function, a ROM (Read Only Memory) or a storage device (collectively referred to as a "recording medium") in which the program and various data are recordable in a readable manner by the computer (or the CPU), and a RAM (Random Access Memory) that expands the program. Then, when the computer (or the CPU) reads and executes the program from the recording medium, the object of the present invention is achieved. As the recording medium, a "non-transitory tangible medium", for example, a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like can be used. Further, the program may be supplied to the computer via any transmission medium (such as a communication network or a broadcast wave) capable of transmitting the program. Note that one aspect of the present invention can 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 illustrative in all respects and not restrictive. The scope of this invention is shown not by the above description but by the claims, and all modifications within the meaning and scope equivalent to the claims are intended to be included.

Explanation of Signs

[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 can reflect an action received from a user terminal operated by each of a plurality of users to the user terminal of each of the plurality of users so that each of the plurality of users can recognize it, causing a computer to means for setting whether to permit the secondary use of an action received from a user, according to an operation from the user; and functioning as means for being able to reflect suggestion information indicating that the action is available for secondary use when the user permits secondary use based on the setting of the acting user.

2. The program according to claim 1, wherein the means for being able to reflect reflects the suggestion information only on the user terminals of users who satisfy a specific condition and does not reflect it on the user terminals of users who do not satisfy the specific condition.

3. The program according to claim 1, wherein the means for setting can set whether to permit secondary use when setting information about the user according to an operation from the user.

4. causing a computer to function as means for managing action information for specifying an action received from a user, wherein the managing means manages the action information received when the user permits secondary use as action information for which secondary use is permitted, and the program according to claim 3, wherein the means for being able to reflect can reflect the suggestion information when reflecting an action specified from the action information for which secondary use is permitted.

5. The program according to claim 3, wherein the means for being able to reflect can reflect the suggestion information for an action from a user who permits secondary use based on the setting of the user who is the source of the action when reflecting an action received from a user.

6. The means for setting is capable of setting whether or not to permit secondary use when setting information about the user in response to an operation by the user, regardless of whether or not an action is reflected. The means for making it reflectable is capable of updating suggestion information based on the settings of the user who is the source of the action even when reflecting the action received from the user. The program according to claim 5.

7. The means for setting is capable of setting whether or not to permit secondary use of the action in response to an operation by the user when receiving the action from the user. The program according to claim 1.

8. A computer is caused to function as means for switching between a first state in which an action received from a user can be reflected regardless of whether or not secondary use is permitted, in response to a switching operation from the user, and a second state in which only an action for which secondary use is permitted among the actions received from the user can be reflected. The program according to claim 1.

9. A computer is caused to function as means for acquiring secondary use information to be used for secondary use of the action in response to a secondary use operation from the user with respect to the action. The program according to claim 1.

10. A method for controlling a computer that performs processing for making an action received from a user terminal operated by each of a plurality of users reflectable on the user terminals of the plurality of users so that each of the plurality of users can recognize it, a step of setting whether or not to permit the action received from the user to be secondarily used in response to an operation by the user, A method comprising steps for enabling reflection of suggestion information suggesting that an action is available for secondary use when the user who performed the action permits secondary use based on the settings of the user who performed the action.

11. A system comprising a computer that performs processing for enabling reflection of an action received from user terminals operated by respective ones of a plurality of users on the user terminals of the respective ones of the plurality of users so that the respective ones of the plurality of users can recognize the action, means for setting whether to permit or not that an action received from a user is used secondarily in response to an operation from the user, A system comprising means for enabling reflection of suggestion information suggesting that an action is available for secondary use when the user who performed the action permits secondary use based on the settings of the user who performed the action.

Images