JP7683078B1 - Program, method, and system - Google Patents

Abstract

The present invention provides a program, method, and system that enable communication with other users according to the type of language.
[Solution] A program for causing a computer to execute a sharing process for accepting posts including messages and sharing the messages among a plurality of users allows posts to be accepted in any of a plurality of languages, associates a language type with a post, transmits post information for identifying the accepted post and the associated language type to an external device, and receives post list information from the external device to display a list of posts. The post list information includes information for identifying the content of the post and the language type associated with each post, and displays a list of posts that are narrowed down to those associated with a language type specified by a user from a plurality of languages.
[Selection] Figure 34

Description

The present invention relates to a program, a method, and a system.

Today's SNS and the like allow users to communicate with overseas users who speak other languages. For example, even if a comment is posted in a language that is different from the language set in the OS or other device, the user can convert it into the language that they normally use by using machine translation or the like and view it (see, for example, Non-Patent Document 1). In addition, to facilitate smooth communication with overseas users, comments and the like are sometimes posted in a language that is different from the language that the user normally uses.

“[Solved in 3 seconds] Can you translate comments in foreign languages on YouTube (registered trademark)?!” [online], [searched on March 1, 2024], Internet <https://crobo.world/column/youtube-foreignlanguage/>

However, as mentioned above, even though conventional SNS and the like allow users to interact with overseas users who speak other languages, because a variety of languages and comments are mixed together, even if a comment is posted that is aimed at a user group that speaks a specific language (for example, a topic in a region that speaks a specific language), it may get buried and may not reach the user group that the poster originally targeted.

The present invention was conceived in light of this situation, and provides a program, method, and system that enables communication with other users according to the type of language.

(1) A program according to an aspect of the present invention is a program for causing a computer (e.g., user terminal 300) to execute a process for accepting a post including a message (e.g., text, an image, etc.) and sharing the message among a plurality of users (e.g., a process for acquiring posted content associated with a content data table such as that shown in FIG. 14 by an information acquisition unit 351, and displaying the acquired posted content on a display unit of the user terminal 300 by a display control unit 352),
The computer,
A means for accepting posts in any of a plurality of languages (for example, a display control unit 352, an input unit 330, etc., that displays a posting screen such as that shown in FIG. 32 and accepts text input in any language);
A means for associating a language variant with a post (e.g., steps S321 and S325 of FIG. 35 );
a means for transmitting posted information for identifying the accepted post and the associated language type (e.g., posted information including a poster ID, posted date and time, posted content information, language information, etc., associated with the content data table of FIG. 33 ) to an external device (e.g., the distribution server 100, etc.) (e.g., in step S313 of FIG. 35 and FIG. 18 , the input information transmitting unit 353 transmits the posted information to the distribution server 100);
functioning as a means (e.g., steps S702 and S706 in FIG. 34, the information acquisition unit 351, the display control unit 352, etc.) for receiving post list information (e.g., information for displaying a list of posted contents such as those in FIG. 30, FIG. 10, and FIG. 11) from an external device and displaying a list of posts (e.g., a list screen of posted contents such as those in FIG. 30, FIG. 10, and FIG. 11);
The post list information includes information for identifying the content of the post (e.g., the post content information of FIG. 33 such as text or an image) and the type of language associated with each post (e.g., the language information associated with each post of FIG. 33),
The means for displaying the list of posts narrows down and displays a list of posts associated with a language type specified by the user from among multiple languages (e.g., a language specified by operating the language switching icon LS displayed on the list screen of posted content in FIG. 30, or a language specified by initial settings such as in FIG. 31 or a default setting by user operation on My Page, etc.) (e.g., as shown in FIG. 30, a list of posted contents associated with language information in a language specified by the user displayed on the language switching icon LS is displayed, steps S702 and S706 in FIG. 34, etc.).

This configuration allows posts to be made in any of a number of different languages, and posts associated with a language type specified by the user can be narrowed down and displayed in a list, making it possible to communicate with other users according to the language.

(2) In the above (1), the computer is
When a post is entered, it functions as a means for displaying information that can identify the type of language associated with the post (for example, displaying a language switching icon LS showing the currently associated language on the post screen in Figure 32, display control unit 352, etc.).

With this configuration, the type of language associated with a post can be identified at the time of posting, making it easier for users to check the type of language associated with the post.

(3) In the above (1), the means for displaying the list of posts displays, together with the list of posts, information that can identify the type of language that has been narrowed down (for example, a language switching icon LS that displays the currently narrowed down languages in FIG. 30).

This configuration makes it easier for the user to check the type of language specified.

(4) In (1) above, the means for associating the language type with the post associates the language type according to a user operation (for example, the default language type selected during initial setup in FIG. 31 or by a user operation from My Page, or the like, or the language type selected by an operation on the language switching icon LS as in FIG. 32(B), steps S321 and S325 in FIG. 35, etc.).

This configuration allows users to communicate by associating the type of language they intend.

(5) In the above (1), the means for associating the language type with the post presets a predetermined language type as a candidate for association (for example, as illustrated in FIG. 31, the language set in the OS of the user terminal 300 is initially set as the default language type), and can change to another language type and associate it in response to a change operation by the user (for example, as in the case of the push notification language in FIG. 31, a language type different from the default can be associated and posted by changing from the initial setting language to another language type, or by changing the default language type from My Page, or by changing the language type from the language set by default as in FIG. 32 (B), steps S322 to S325 in FIG. 35, etc.).

This configuration simplifies the operations for associating, while allowing the type of language to be associated to be changed as needed, improving user convenience.

(6) In the above (5), the computer is
functioning as a means for allowing the type of language available to the user when executing the sharing process to be set in advance in response to an operation by the user (for example, a default setting operation for the type of display language such as the application display language set by the user at the time of initial setting in FIG. 31 or from My Page, the language of the content or posts to be displayed, the memory unit 320, the control unit 350, etc.);
a predetermined language type set as a candidate to be associated by the means for associating the language type with a post (for example, a language type displayed on a language switching icon LS displayed as a language of a post when the posting screen of FIG. 32 is displayed) is a language type previously set by the setting means,
The means for associating the language type with the post can associate another language type with the post in response to an operation from the user (for example, an operation to switch the language type from the default Japanese to English based on an operation on the language switching icon LS on the post screen of Figure 32 (B), steps S322 to S325 of Figure 35, etc.).

With this configuration, the type of language associated with a post can be preset in response to a user operation, and a different language type from the preset language type can be associated in response to a user operation. This allows the user to associate a language type depending on the content of the post, improving user convenience.

(7) In the above (5), the computer is
Functioning as a means for identifying the type of language used in the message included in the post (for example, the control unit 350 identifies the type of language of the text entered on the post screen through automatic determination by AI),
the predetermined language type set as a candidate is a language type identified by the language type identifying means,
The means for associating the language type with the post can associate other language types with the post in response to a user operation (for example, the language type identified by automatic determination can be displayed as the language of the post in the language switching icon LS in Figure 32 (A), see the modified example (combination with automatic language determination)).

With this configuration, the language type is identified based on the information contained in the actual post, making it easy to associate the language type, while also allowing the user to associate other language types if desired, allowing the user to associate the language they intend.

(8) In the above (1), the computer is
functioning as a means for allowing the type of language available to the user when executing the sharing process to be set in advance in response to an operation by the user (for example, a default setting operation for the type of display language such as the application display language set by the user at the time of initial setting in FIG. 31 or from My Page, the language of the content or posts to be displayed, the memory unit 320, the control unit 350, etc.);
The means for displaying the list of posts can narrow down the list of posts to those associated with the language type previously set by the setting means, and then switch the list to display those associated with other language types specified by the user (for example, if the default language type is set to Japanese, a list screen of posted contents associated with Japanese as the language information as shown in Figure 30 (A) is displayed, and by operating the language switch icon LS and selecting English, a list of posted contents associated with English as the language information as shown in Figure 30 (B) is displayed; steps S702 to S706 in Figure 34).

With this configuration, posts can be displayed in a language that is different from the default, and can be switched between the default language and a different language depending on the user's operation, allowing the user to communicate in the language of their choice depending on the situation.

(9) In the above (1), the means for displaying the list of posts displays a list of posts that satisfy a specific condition (e.g., posted content posted by a special user such as a celebrity, or posted content posted under a specified situation such as within 24 hours after posting) regardless of the type of language specified by the user (for example, see the modified example (Posts displayed regardless of specified language)).

With this configuration, posts that meet certain conditions are displayed without being filtered out, reducing the possibility that useful information for the user will not be displayed due to filtering.

(10) A method according to an aspect of the present invention is a method for controlling a computer (e.g., user terminal 300) that executes a process for accepting a post including a message (e.g., text, an image, etc.) and sharing the message among a plurality of users (e.g., a process for acquiring posted content associated with a content data table such as that shown in FIG. 14 by an information acquisition unit 351, and displaying the acquired posted content on a display unit of the user terminal 300 by a display control unit 352), the method comprising:
A step of accepting posts in any of a plurality of languages (for example, displaying a posting screen such as that shown in FIG. 32 and accepting text input in any language);
Associating a language variant with the post (e.g., steps S321, S325 of FIG. 35 );
a step of transmitting posted information for identifying the accepted post and the associated language type (e.g., posted information including a poster ID, posted date and time, posted content information, language information, etc., associated with the content data table of FIG. 33 ) to an external device (e.g., the distribution server 100, etc.) (e.g., in step S313 of FIG. 35 and FIG. 18 , the input information transmitting unit 353 transmits the posted information to the distribution server 100);
receiving post list information (e.g., information for displaying a list of posted contents such as those in FIG. 30, FIG. 10, FIG. 11, etc.) from an external device and displaying a list of posts (e.g., a list screen of posted contents such as those in FIG. 30, FIG. 10, FIG. 11, etc.) (e.g., steps S702 and S706 in FIG. 34);
The post list information includes information for identifying the content of the post (e.g., the post content information of FIG. 33 such as text or an image) and the type of language associated with each post (e.g., the language information associated with each post of FIG. 33),
The step of displaying the list of posts narrows down and displays the list of posts associated with a language type specified by the user from among multiple languages (e.g., a language specified by operating the language switching icon LS displayed on the list screen of posted content in FIG. 30, or a language specified by initial settings such as in FIG. 31 or a default setting by user operation on My Page, etc.) (e.g., as shown in FIG. 30, a list of posted contents associated with language information in a language specified by the user displayed on the language switching icon LS is displayed, steps S702 and S706 in FIG. 34, etc.).

This configuration allows posts to be made in any of a number of different languages, and posts associated with a language type specified by the user can be narrowed down and displayed in a list, making it possible to communicate with other users according to the language.

(11) A system according to an aspect of the present invention is a system (e.g., communication system 1) having a computer (e.g., user terminal 300) that executes a process for accepting a post including a message (e.g., text, an image, etc.) and sharing the message among a plurality of users (e.g., a process for acquiring posted content associated with a content data table such as that shown in FIG. 14 by an information acquisition unit 351 and displaying the posted content on a display unit of the user terminal 300 by a display control unit 352),
A means for accepting posts in any of a plurality of languages (for example, a display control unit 352, an input unit 330, etc., that displays a posting screen such as that shown in FIG. 32 and accepts text input in any language);
A means for associating a language variant with a post (e.g., steps S321 and S325 of FIG. 35 );
a means for transmitting posted information for identifying the accepted post and the associated language type (e.g., posted information including a poster ID, posted date and time, posted content information, language information, etc., associated with the content data table of FIG. 33 ) to an external device (e.g., the distribution server 100, etc.) (e.g., in step S313 of FIG. 35 and FIG. 18 , the input information transmitting unit 353 transmits the posted information to the distribution server 100);
a means (e.g., steps S702 and S706 in FIG. 34, an information acquisition unit 351, a display control unit 352, etc.) for receiving post list information (e.g., information for displaying a list of posted contents such as those in FIG. 30, FIG. 10, and FIG. 11) from an external device and displaying a list of posts (e.g., a list screen of posted contents such as those in FIG. 30, FIG. 10, and FIG. 11, etc.);
The post list information includes information for identifying the content of the post (e.g., the post content information of FIG. 33 such as text or an image) and the type of language associated with each post (e.g., the language information associated with each post of FIG. 33),
The means for displaying the list of posts narrows down and displays a list of posts associated with a language type specified by the user from among multiple languages (e.g., a language specified by operating the language switching icon LS displayed on the list screen of posted content in FIG. 30, or a language specified by initial settings such as in FIG. 31 or a default setting by user operation on My Page, etc.) (e.g., as shown in FIG. 30, a list of posted contents associated with language information in a language specified by the user displayed on the language switching icon LS is displayed, steps S702 and S706 in FIG. 34, etc.).

This configuration allows posts to be made in any of a number of different languages, and posts associated with a language type specified by the user can be narrowed down and displayed in a list, making it possible to communicate with other users according to the language.

FIG. 2 is a diagram illustrating an example of a hardware configuration of a communication system. FIG. 2 is a diagram for explaining the configuration of a distribution server. FIG. 2 is a diagram illustrating a configuration of an administrator terminal. FIG. 2 is a diagram for explaining the configuration of a user terminal in detail. 1 is an example of a database relating to attributes. 13 is an example of an attribute selection screen. 2 is an example of a database relating to users. 13 is an example of a user confirmation screen for information related to a user. FIG. 11 is a flowchart for explaining an attribute selection process. 13 is an example of a display mode of content information related to content provided by a distribution server. 13 is an example of a display mode of content information related to content provided by a distribution server. 13 is a diagram showing an example of a display mode relating to classification of contents for each attribute. 1 is a diagram illustrating an example of a display mode of content provided by a distribution server. 2 is an example of a database relating to content provided by a distribution server. 13 is an example of a display mode of content information related to a content in response to a switching operation. FIG. 11 is a diagram for explaining a flowchart of an attribute extraction process. 13 is an example of a display aspect of a user posting screen. FIG. 11 is a diagram for explaining a flowchart of a user posting process. This is an example of an action that can be taken depending on the user's evaluation history status. 13 is an example of a display aspect of a user posting screen according to a rating history status. FIG. 13 is a diagram for explaining a flowchart of a user posting process according to a rating history status. This is an example of changes in the evaluation history status due to external evaluation. FIG. 13 is a diagram for explaining a flowchart of an evaluation history status update process. This is an example of a tap action presentation when a tap action is received from a user. 13 is an example of a database relating to tap action effects for each content. FIG. 13 is a diagram for explaining a flowchart of a tap action production process. 13 is an example of a display form of content information and the like related to externally posted content. 1 is an example of a database related to reaction information for content provided by a distribution server and action information to be reserved. FIG. 11 is a diagram for explaining a flowchart of a reaction notification process. 13 is a diagram illustrating an example of a display mode of content information or the like according to language information. 13 is a diagram showing an example of a display mode when language information is set in advance by a user operation. 13 is a diagram illustrating an example of a display mode of a user posting screen when posting in association with language information. 1 is an example of a database regarding language information about content provided by a distribution server. 13 is a diagram for explaining a flowchart of a post list display process for displaying content information and the like according to language information. FIG. FIG. 11 is a diagram illustrating a flowchart relating to association of language information in a user posting process.

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

In the communication system according to the present invention, it is possible to provide a user with multiple types of content associated with attributes. The attributes include multiple types of first attributes (e.g., communities) and multiple types of second attributes (e.g., talents), and content information (e.g., headlines of news posts) related to content associated with attributes (e.g., news posts related to talents) can be displayed. The content information can be displayed by switching between multiple display states, including a first display state (favorite filter off) that displays content information associated with a community, etc., previously selected by the user, so that the user can identify it, and a second display state (favorite filter on) that displays content information associated with both a community, etc., previously selected by the user, and a talent, etc., so that the user can identify it, by a user's switching operation on a specific icon, etc.

The multiple types of content provided in the communication system according to the present invention are provided via a fan community, which is a group of users who support a specific target (e.g., a celebrity). In the community space of the fan community, the actions taken by each user are reflected so that other users can recognize them, allowing users to interact with each other. Users who use the community are associated with an evaluation history status that changes depending on external evaluations, which are evaluations from sources other than the user himself/herself. The actions that users may take within the community are controlled by external evaluations being made of the actions taken by the users within the community (e.g., content and comments posted by the users).

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

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

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

The distribution server 100 is, for example, a computer such as a workstation or a personal computer with communication capabilities. The distribution server 100 manages multiple pieces of content that can be provided to users, and manages the community to which the content is provided. The distribution server 100 provides the content in response to a request from a user via the network 2.

The content provided by the distribution server 100 is managed and set by type, as described later with reference to FIG. 14. Content informs viewers of specific information, and includes information such as video, audio, and text. Content managed by the distribution server 100 includes, for example, news and announcements by the operator (manager), user posts (including comments), and distributed video provided by external web services obtained by using a web API. The content can be provided to users by displaying it on the user terminal 300 via a medium such as a browser or a dedicated smartphone application. The medium on which the content is provided also functions as a fan community for supporting a specific target.

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

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

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

The user terminal 300 is used by a user who wants to view and experience the content. The user terminal 300 may be, for example, a computer with operation input functions and communication functions, such as a personal computer, a tablet terminal, or a smartphone.

In response to operations on the terminal, the user terminal 300 communicates with the distribution server 100 and receives content data for the content selected by the user. Based on the received content data, the user terminal 300 also constructs, in the memory area of the user terminal 300, posted information for the content selected by the user from among the contents managed by the distribution server 100, and displays images and text of the posted information (the images and text contained in this posted information are also referred to as messages). This allows the user to identify and recognize the content information via the user terminal 300.

The user terminal 300 also accepts action operations on the displayed content and content posting operations by the user himself. The user terminal 300 can transmit information corresponding to the operation on the terminal (for example, information for identifying the action or the posted content) to the distribution server 100, and can reflect the action or the posted content on multiple user terminals via the distribution server 100. Action operations include, for example, tap actions (such as the so-called "like" function) that show a favorable expression of intent such as liking or sympathy for the content, and reactions to the content such as posting a reply comment. Hereinafter, user actions, such as the user's own content posting operation, are collectively referred to as "actions." Additionally, user tap actions and favorable comments are also referred to as "like actions."

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

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

<Configuration of 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.

The communication unit 110 is a communication interface equipped with a network interface card controller (NIC) for wired or wireless communication. The communication unit 110 communicates with other computers via the network 2.

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

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

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.

The data transmission/reception unit 131 receives various information transmitted from the user terminal 300 and transmits various 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 information transmitted and received by the data transmission/reception unit 131 includes, for example, information related to the content managed in the content management unit 132, various notifications, etc.

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

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

<Administrator terminal configuration>
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, etc., an output unit 240 for outputting images, sounds, etc., 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 connected to each other by a bus line.

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

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

The control unit 250 is composed of a CPU and the like. The control unit 250 controls the overall operation of the administrator terminal 200 by executing the programs stored in the storage unit 220.

The functional configuration of the control unit 250 will be described below. 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.

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

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

The action authority setting unit 253 stores and updates information on the authority to perform actions such as content posting actions and actions showing reactions to content within the provided community space, which are managed as the action information 123 and action authority information 124 of the distribution server 100 in response to operations on the administrator terminal 200. This makes it possible to, for example, add or change actions that are set for each user's evaluation history status, which will be described later, and to store and update in the storage unit 120 the settings of action restrictions for individual users by the administrator.

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

<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, etc., an output unit 340 for outputting images, etc., 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 connected to each other by a bus line.

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

The input unit 330 includes an input device (e.g., a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, a microphone, etc.) for receiving input operations and voice from the user.

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

The functional configuration of the control unit 350 will be described below. 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.

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

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

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

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

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

<About the fan community content provision function>
(Overview of the fan community)
The fan community that allows the content provided by the distribution server 100 according to the present embodiment to be viewed will be described in more detail below. The content provided by the distribution server 100 is provided by a dedicated application (program (e.g., a program for a native application, etc.)) that runs on a terminal such as a smartphone or tablet. The dedicated application functions as a so-called fan community used by users who support a common target (e.g., a talent, a character, goods, etc.). In the fan community, content related to the common target is provided (made viewable by the user), which facilitates the fan activities of the user. In addition to the interaction between the users who are fans, the user can also interact with the target that the user supports. The content may be provided not only by a dedicated application, but also by a WEB application via a browser. The content may also be provided through a fan community provided by a WEB application via a browser.

In this embodiment, the cheering target can be, for example, a character, object, or other object that the user can feel fondness for, be interested in, or be concerned about. Characters include, for example, real people such as celebrities and famous people (3D), and fictional beings such as anime characters and mascot characters (2D, 2.5D). Other cheering targets include objects such as trains, animals, etc.

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

The units (attributes) that users of a fan community support may not only be one talent, but may also include multiple talents, a small group (unit), or a large group. For example, supporting (becoming a fan of) a large group is also known as "box pushing." In the fan community of this embodiment, users can set (select) in advance the units (attributes) they support of their choice.

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

Each belonging group 1 is associated with a "talent ID" and "talent name" as information for identifying the belonging talent. Furthermore, each talent is associated with information for identifying the "belonging group 2" to which the talent belongs. Belonging group 2 is a small group made up of fewer people than belonging group 1. For example, they are classified according to the time when they joined the group, such as "1st generation," "2nd generation," etc., or groups made up of a specific concept (for example, "Gamers," made up of talents who mainly do live game broadcasts).

Regarding the belonging group, some talents may belong to multiple belonging groups. Also, there may be a talent who belongs to belonging group 1 but does not belong to any belonging group 2. In addition, there may be belonging group 2 that is made up of talents who belong to different belonging groups 1 (made up across different belonging groups 1, for example, group A and group B).

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

<Specific example of attribute selection processing>
(Screen example for attribute selection)
Next, with reference to FIG. 6 to FIG. 9, an example of a screen in which a user who uses a fan community selects an attribute (group or talent) to support and a process flow will be described. The selection (setting) screen of the attribute to support illustrated in FIG. 6 is displayed on the user terminal 300 when the use of the fan community application is started or when a setting change is requested from My Page or the like. In the fan community in this embodiment, a user can participate in a community (first attribute) corresponding to the group 1 (first attribute) to which the talent described with reference to FIG. 5 belongs. FIG. 6(A) is an example of a participation community setting screen, and a user can select (set) a community (first attribute) to participate in from 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. The participation community selection area 50 displays an icon for each community that the user can participate in. The user can select a participation community by selecting the icon of the community in which the user wishes to participate. A check mark or the like is displayed on a community that the user can select to participate in.

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

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

In the talent selection area 53, the icon and name of each talent are displayed, but as shown in FIG. 6(B), for example, they may be displayed in the order of their units. A favorite talent can be selected by selecting the icon of each talent. A check mark or the like is displayed on the icon of the selected talent.

All of the talents in a group may be selected as the favorite talent by operating the icons in the group selection area 52. Alternatively, a "select all" icon may be displayed, allowing all displayed talents to be selected by the selection operation. Favourite talents may also be selected not only on a talent-by-talent basis, but on a unit basis (2 groups to which the talent belongs), and the most favorite (the talent that is most favored among the favourite talents) may be selected.

(Example of a user information database for selected attributes)
FIG. 7 is an example of a user information database stored as the account information 125. In the user information database, a "user ID", "level", "accumulated points", "participating community", "favorite talent ID", and the like for identifying the user are associated with each user. The "participating community" and the "favorite talent ID" are associated with information for identifying the attributes selected by the user in the setting screen illustrated in FIG. 6. For example, the setting screen in FIG. 6 is the setting screen for the user ID "u1" in FIG. 7, and the user ID "u1" selects the participating community "community A" in FIG. 6(A) and the talents "AAA", "BBB", and "EEE" in FIG. 6(B), so that the user ID "u1" is associated with the belonging community "community A" and the favored talent IDs "t1", "t2", and "t5" corresponding to each talent. Hereinafter, the user ID is also simply referred to as a user. The "level" and "accumulated points" change depending on the user's actions in the fan community, but details will be described later.

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

The My Page screen in FIG. 8 is a screen displayed on the user terminal 300 of user "u1," and the name area 54 displays the name "userA" used within the fan community of user "u1," and an icon image. The icon image can be, for example, a fan mark of a talent. A fan mark is a symbol or the like used by a talent to represent the talent, and fans can publicly indicate which talent they are fans of by using the same fan mark. For example, the icon image can be edited by tapping the image editing icon displayed at the bottom right, or can be selected and set on the initial setting screen.

In the user evaluation history status 55, the "level" and "accumulated points" associated with each user in the user information database of FIG. 7 are displayed so that the user can check them. Details of the evaluation history status will be described later.

In the favorite talent information 56, the talent previously selected by the user is displayed so that the user can identify (confirm/recognize) the talent. For example, the icon and name of each talent are displayed so that the user "u1" can confirm the talents "AAA", "BBB", and "EEE" that he selected and set on the favorite talent setting screen of FIG. 6(B). In addition, the favorite talent can be changed as appropriate by operating the edit icon displayed in the favorite talent information 56, etc., and the screen of FIG. 6(B) is displayed.

When a selection operation is performed on the participating community setting 57, the participating community setting screen in FIG. 6(A) is displayed, allowing the participating community to be changed as appropriate.

When operations are performed on notification settings 58 and settings/app information 59, push notification settings and various settings of the fan community app can be performed. The My Page in FIG. 8 may be one that allows the user to confirm and edit their own information. For example, a list of participating communities may be displayed on the first screen of the My Page (such as the screen displayed when the My Page icon 16 is operated) in the same way as for the favorite talent information 56. Also, the screen for changing participating communities and favorite talent (FIG. 6) may be displayed together by operating a single edit icon.

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

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

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

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

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

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

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, a selection is determined to have been made by receiving information (including information that can identify the selected participating community and favorite talent) transmitted by a selection operation on the display of each participating community in FIG. 6(A) or the display of each talent in FIG. 6(B) on the user terminal 300.

When it is determined in step S107 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 a selected attribute, and the process ends. For example, in the distribution server 100, the user information database of FIG. 7, which is stored as account information 125, is updated and stored based on information corresponding to the attribute selection operation received from the user terminal 300.

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

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

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

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

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 in the app, or may be hidden on a specific screen (for example, when the contents of the content are displayed as in FIG. 13). As described above, the home icon 13 is an icon for displaying the home screen of FIG. 10 when 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 on which various notifications can be confirmed, such as when a post is made regarding a selected attribute (for example, a talent set by the user as a favorite talent) when a selection operation is performed, a reply comment to the user's own post, and a mention for the user. The my page icon 16 is an icon for displaying the my page exemplified in FIG. 8 when a selection operation is performed.

(Home screen overview)
At the top of the home screen in Fig. 10, a favorite filter 20 and a language switching icon LS are displayed. The favorite filter 20 is a filter icon that can narrow down the list of headlines of the displayed content so that only headlines of content associated with a favorite talent previously selected by the user are displayed, and details will be described later with reference to Figs. 15 and 16. The language switching icon LS is an icon that, when selected, switches the language information associated with the content from, for example, Japanese to English, thereby making it possible to display the content according to the language information. The language switching icon LS may be configured to display the language currently selected as the display language.

The content provided by the distribution server 100 can be classified into one of a number of categories, and the home screen can display the content for each classified category. The content list (heading) screen on the home screen displays content headings 60 (content information) for content (also called articles/threads) for each category, such as features 61, recommended topics 62, popular user posts 63, commemorative broadcasts 64, and goods 65. For example, the feature 61 displays announcements set by the content setting unit 251, such as announcements from the administrator, that the user wants to inform all users of. The content displayed in the feature 61 is displayed regardless of which participating community and which recommended talent the user has selected. In addition, when a heading or image displayed in the feature 61 is selected, the screen may transition to a screen showing detailed information or an external website.

For categories from Recommendation Topic 62 onwards, content posted within the participating community is displayed. In this embodiment, the "community" referred to in the app refers to communities A to C corresponding to the groups to which the talent belongs, as exemplified in FIG. 6, and community P in which the user is always a participating member.

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

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

The channel list screen in FIG. 12 displays a community bar 81, favorite confirmation icon 31, your own post icon 32, get started icon 33, notification setting icon 34, etc. The communities displayed in the community bar 81 include communities in which the user participates (selected by the user). By selecting the open/close icon displayed in the community bar 81, a channel list 82 for each community is displayed. For example, the channel list 82 corresponding to community A displays each channel name. A selection bar 83 displayed next to each channel name indicates which channel is selected.

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

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

The favorite confirmation icon 31 in FIG. 12 is an icon that, when selected, allows the user to check the content (also called posts) that is stored as the account information 125 or that is stored in the storage unit 320 and that the user has registered as a favorite. The own post icon 32 is an icon that, when selected, allows the user to check the content (threads created) that the user himself has posted in the community, and the comments that the user himself has made on the content (threads created). The introduction icon 33 is an icon that, when selected, allows the user to recheck the tutorial that is displayed at the time of initial login, and to display how to use the app, mental preparations, etc. The notification setting icon 34 is an icon that, when selected, allows the user to display a screen for setting various notifications (such as selecting information to be notified by push). For example, the same screen as when the notification setting 58 illustrated in the My Page in FIG. 8 is selected may be displayed.

(About the Community screen)
The community screen in Fig. 11(A) displays a favorite filter 20, a language switching icon LS, a sorting icon 22, a posting icon 23, and the like, in the same manner as the home screen exemplified in Fig. 10. The sorting icon 22 is an icon that, when selected, allows the order of the displayed content headings to be sorted in order of new arrivals or popularity (for example, in order of the most liked actions). The posting icon 23 is an icon that, when selected, allows a user to post content (create a thread) within the community.

Each piece of content posted within a 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. Each content heading 70 displays the poster 71, a report icon 72, a favorite icon 73, content information 74, etc.

Contributor 71 displays the icon, name, etc. of the person who contributed the corresponding content. For example, if the contributor is an administrator or a special user (described later), the icon, name, etc. are displayed together with an official mark, etc.

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

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

Content information 74 displays the title and part of the description of the content posted.

Furthermore, in the content heading 70, if the posted content is posted together with an image, the image 75 is displayed, and if there are comments on the content, the comments (e.g., the latest comment or some of the most popular comments) are displayed in featured comments 76. Furthermore, the number of comments on the content is displayed in the number of comments 77, and the number of tap actions on the content is displayed in the number of tap actions 78. The number of tap actions on the content is displayed, for example, as the total number of times that all users have tapped on a heart icon 708 displayed together with the number of tap actions 78 in the content heading (60, 70) or on an icon 708 displayed together with the number of tap actions 78 displayed on the content screen in FIG. 13 described later.

In addition, users who use the fan community app include special users, and when there is a comment or tap action from a special user, the fact that there is a comment or tap action from the special user can be displayed as a special action 79 together with the icon of the special user in the content heading 70. A special user is, for example, a user who corresponds to the talent himself/herself as illustrated in FIG. 5. Therefore, by the special action 79 being displayed, the user can recognize that there has been an action such as a comment or tap action from the talent himself/herself. This can promote interaction with the target of support in the fan community app, and increase user satisfaction.

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

In addition, the special action 79 to be displayed in the content heading 70 may be displayed in the content heading 60 of the home screen in FIG. 10.

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

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

When the back icon 10b is selected, the screen that was displayed by the user immediately before is displayed again. For example, if the user has transitioned to this content screen from the community screen in FIG. 11(A), the screen returns to the community screen in FIG. 11(A), and if the user has transitioned to this content screen from the home screen in FIG. 10, the screen returns to the home screen in FIG. 10.

Category 85 displays the name of the associated category if a category is associated with the content. Content 74b displays posted text information such as the title and description of the content.

Related talent 88 is displayed when a talent in FIG. 5 is associated with the content, and displays the icon and name of the associated talent. Special action 79 is displayed to indicate that when an action has been taken on the content by a special user corresponding to the talent in FIG. 5, the special user has taken action on the content.

Each comment 87 displays a poster 71b that displays the comment poster, a report icon 72b that allows the comment to be reported or hidden as shown in FIG. 11(B), a reply icon 86 that allows a reply to the comment, and a reply list 89 that displays a list of replies. Note that the user's own icon may also be displayed in the comment posting field 84.

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

Next, referring 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 a content database for "Community A." The content database stores information such as "channels," "posting authority" for each channel, and "article ID" for each piece of content.

"Channels" are classified by topic, and the screen of each channel can be selected and displayed by a selection operation on the channel list 82 illustrated in FIG. 12. For example, the "official channel" is a channel where official announcements from the administrator are posted, and the "group A chat" is a channel with the theme of chatting about "group A" of the group 1 in FIG. 5 corresponding to "community A". In addition, "cutout" is a channel with the theme of sharing links to cutout videos recommended by users (for example, videos posted on a video distribution site, which are videos in which parts of videos already posted on the video distribution site have been cut out). "Past recommendations" is a channel with the theme of recommending videos related to group A (for example, videos posted in the past by a talent belonging to the group). When a selection operation is performed on "all channels" in the channel list 82 in FIG. 12, all the contents of the channels in FIG. 14 are displayed together. In addition, these channels are only examples, and for example, temporary special channels may be set up.

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

An "article ID" is an ID that identifies each piece of content, and is assigned to each piece of content. In addition, each "article ID" is associated with a "category," "contributor ID," and "talent ID."

"Category" is a category that can be associated when content is posted. For example, "Events," "Goods," "Streams/Videos," "Fan Art," "Clips," "Music," "Commemorative Streams," etc. can be associated to easily recognize the theme of the content itself. When a "Category" is associated, the category name will be displayed in category 85 on the example content screen in Figure 13.

"Contributor ID" is an ID that identifies the contributor of the content.

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

For example, article ID "a1" is associated with the category "events", the poster is "ou1", and the talent IDs "t1", "t2", "t6", and "t14" are associated with it. The above-mentioned FIG. 13 is an example of the display of article ID "a1", and poster 71 displays the name of "Staff S" corresponding to user ID "ou1" and an official mark indicating that it is an official account. Also, category 85 displays the category "events" associated with article ID "a1".

In the related talents 88, icons and names of the talents "AAA", "BBB", "FFF", and "MMM" corresponding to the talent IDs "t1", "t2", "t6", and "t14" associated with the article ID "a1" are displayed. In this way, since the related talents can be set when posting, the related talents can be displayed in the content, and the user can easily identify which talent the post is about. Note that the related talents 88 may also be displayed in the content heading 70 of the community screen shown as an example in FIG. 11 (A).

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

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

(Example of home screen)
Returning to FIG. 10, the details of the contents displayed on the home screen will be described. On the home screen of each user terminal 300, the contents stored in the content database corresponding to the "participating community" associated in the user information database illustrated in FIG. 13 stored as the account information 125, among the content database illustrated in FIG. 14 stored as the content data 122, are displayed. That is, for the category of the recommended topic 62 and subsequent categories on the home screen of each user, only the content headings of the contents posted in the community in which the user participates are displayed. For example, if the communities pre-selected in FIG. 6, FIG. 9, etc. are "community A" and "community B", the home screen displays the contents posted in "community A", "community B", and "community P" in which the user always participates. If there is no community in which the user always participates, the home screen displays the contents posted in the community pre-selected by the user. On the other hand, the contents posted in "community C" in which the user does not participate are not displayed. Also, for the category of the recommended topic 62 and subsequent categories, the content headings 60 displayed change according to the on/off operation of the recommended filter 20 described later.

In any category, the number of contents that can be displayed on the home screen may be one, or the content headings 60 of a predetermined number of the latest contents (e.g., 2, 5, 7, etc.) may be displayed. Alternatively, the content headings 60 of a predetermined number of contents in order of popularity may be displayed. In addition, the content headings 60 for each category may be switched by performing a left-right sliding operation on the touch panel of the user terminal 300. For example, by performing an operation of sliding the content heading 60 (e.g., the most recent date) displayed in the commemorative distribution 64 of FIG. 10 to the left (e.g., a flick operation), an older content heading 60 may appear from the right side of the screen. In addition, for example, only half of the content heading 60 may be displayed on the right side of the screen, or it may not appear unless a sliding operation is performed.

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

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

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

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

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

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

(Specific Example of Content Attribute Extraction Process Related to Selected Attribute)
Next, a filter function that narrows down the content to be displayed so that it is associated with a favorite talent (second attribute) previously selected by the user will be described with reference to Figures 15 and 16. In the fan community app of this embodiment, the content displayed on the user terminal 300 can be further narrowed down to the favorite talent (second attribute) previously selected by the user when a predetermined condition based on the user's intention is met, since each content data is stored together with the meta information of the talent, in addition to narrowing down the content to the participating community (first attribute) previously selected by the user.

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

Figure 15 shows example screens when the favorite filter 20 is on and off on the content screen of Figure 11 (A). Figure 15 (A) shows an example screen when the favorite filter 20 is on and the filtering to favorite talents preset by the user is active. Figure 15 (B) shows an example screen when the favorite filter 20 is off and the filtering to favorite talents preset by the user is not active.

15 is an example of a screen displayed on the user terminal 300 of the user "u1" in FIG. 7, for example. In FIG. 15(A), the favorite filter 20 is on, so only the content associated with the talent selected in advance as the favorite talent by the user "u1" is extracted. That is, in the user information database stored as the account information 125, the talent IDs associated with the user "u1" are the talent ID "t1" of the talent "AAA", the talent ID "t2" of the talent "BBB", and the talent ID "t5" of the talent "EEE", so 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" and the content (content headings 60, 70) of the article ID "a7" associated with "t5" in the content information database of the community A in FIG. 14 are displayed.

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

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

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

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

In step S203, information about the participating community selected by the user of the user terminal 300 that sent the display request operation is extracted and transmitted to the user terminal 300, and the process ends. The selected participating community includes the "belonging community" for each user that is stored as account information 125 by the user having previously selected it as illustrated in FIG. 6(A) or FIG. 9, and the community that is always in the participating state, if there is such a community. For example, the user "u2" in FIG. 7 participates in "community A" and "community B". Therefore, in step S203, the user terminal 300 of the user "u2" displays the contents posted in "community A", "community B", and the "community P" in which the user always participates on the home screen, and the community bars 81 of "community A", "community B", and "community P" are displayed on the channel list screen in FIG. 12.

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

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

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

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

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

(Specific examples of associations between categories, talents, etc. posted by users)
Next, a specific example of a user posting process when a user posts content will be described with reference to Figs. 17 and 18. Fig. 17 is an example of a user posting screen. For example, when a content screen of a channel in which "posting authority" is set to "user" in the community content database of Fig. 16 is displayed, the posting icon 23 illustrated in Fig. 11(A) is selected to display it. Note that for a channel in which posting authority is such that only official accounts can post, such as an official channel, an unauthorized user may not be able to select the posting icon 23 on the content screen. For example, the display mode may be changed, such as by displaying it in gray, or the posting icon 23 itself may not be displayed.

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

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

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

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

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

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

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

When it is determined in step S305 that character input has been completed, a category selection screen is displayed in step S307. For example, this is a screen that allows the selection of categories and related talents as shown in FIG. 17(B).

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

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

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

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

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

<About the behavior control function based on user ratings within fan communities>
(Overview of behavior control function)
Next, a behavior control function based on the evaluation of a user in a fan community of this embodiment will be described. In the fan community of this embodiment, the user himself can post content in the community and share it with other users. In this way, while the community is activated by interacting with other users, if there are no restrictions on the actions that users can take, there is a risk that the public order and atmosphere in the community will deteriorate as users who post content that other users may feel uncomfortable with will be left unchecked. For this reason, a level that serves as an index of trustworthiness, sincerity, etc. is set for each user, and the behavior that can be taken in the community is changed according to the level. In this embodiment, the evaluation history status of the user is updated by an external evaluation other than the user himself depending on the behavior taken by the user in the community, and the behavior that can be taken in the community is changed according to the evaluation history status. As a result, the actions that can be taken by users with high indices such as trustworthiness and sincerity are increased, and the actions that can be taken by users with low indices are restricted. In other words, the evaluation history status changes by taking actions that are acceptable in the fan community.

(Summary of user level fluctuations)
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" changes according to the "accumulated points". The "accumulated points" change according to external evaluation, which will be described later. For example, the user's level is 1 in the initial setting, and when the accumulated points reach 10, the level becomes 2. To increase from level 2 to level 3, a number of points greater than the number of points required to increase from level 1 to level 2 is required, and when the accumulated points reach 21, for example, the user reaches level 3. In this way, as the level increases, the number of points required increases, making it more difficult to increase the level. In addition, the "accumulated points" may decrease according to external evaluation, so that, for example, when the accumulated points of a user who was at level 2 fall below 20, the level decreases from 2 to 1.

In addition, each user can check their own "level" and "accumulated points" in the user evaluation history status 55 on their My Page, as shown in the example of Figure 8. This allows users to be mindful of taking actions that will raise their level. On the other hand, they cannot check the "level" and "accumulated points" of other users. In this way, by not disclosing a user's own level to other users, it is possible to prevent low-level users in the community from feeling inferior and high-level users from behaving arrogantly. Note that only one of the "level" and "accumulated points" may be displayed on the My Page.

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

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

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

A "moderator invitation" is the ability to act as an administrator of content posted within a community, and is available to users who are level 90 or above. For example, it is the ability to delete content or comments that have been visually determined to be inappropriate, or to make them invisible (also known as censorship), something that is normally done by administrators. It may also be the authority to take measures to suspend (for example, for a certain period of time) the accounts of malicious users. Content that has been censor'd by a user of level 90 or above will no longer be displayed on the user terminals 300 of users of level 89 or below.

"Community creation" means that a new community can be created that a user can participate in, as exemplified in FIG. 6(A) and is an action permitted only to users with the highest level of trust, level 100. For example, a "community A2" can be created as a community created by fans of group A (corresponding to community A) to support group A. The created community A2 will be displayed in the participating community selection area 50 in the participating community setting screen in FIG. 6(A). Alternatively, it may be possible to create a new "channel." For example, a channel with a new theme can be added to the channels of "community A." The newly added channel will be displayed in the channel list 82 in FIG. 12. Users at level 99 or lower can also participate in and select communities and channels created by a level 100 user.

In addition, the level of a user in this embodiment can not only be raised, but can also be lowered. Therefore, even if the specific actions shown in FIG. 19 are permitted as a result of an increase in level, they are restricted and cannot be taken as a result of a decrease in level. For example, a user at level 80 or higher can create plans within a community, but if the level drops to 79, they will no longer be able to create plans. In addition, if a created plan or community is reported by other users on the display screen of the created plan or community as being inappropriate in the fan community app, this is also an external evaluation that can lower the level of the user who created the plan or community.

Figure 20 is an example of a posting screen on the user terminal 300 of a user who does not have "no posting link restrictions." In this embodiment, it is assumed that the only URLs that can be posted by a user who has restrictions on posting links up to level 59 are links to "video sharing site A" and "SNS-B." In this case, when 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 URLs "video sharing site A" and "SNS-B" can be posted" is displayed, as shown in the example of Figure 20. In addition, if the next icon 38 is displayed in a different manner depending on whether it is possible to post or not, the next icon 38 may be displayed in a manner that does not allow posting, so that a selection operation cannot be performed. Thus, while it is relatively easy to hide inappropriate images (images that may be violent or otherwise offensive) by automatically determining through image recognition when uploading images, it is not easy to determine if a URL refers to a malicious website (for example, a fake site, a fraudulent site, or a page with other offensive content), and administrators must take the time to hide the URL. Therefore, by allowing only high-level users (users with high trust) to post content that is difficult to determine whether it is inappropriate or not (here, URL links), the burden on administrators can be reduced and public order within the community can be stabilized by suppressing inappropriate posts.

Note that "Video Sharing Site A" and "SNS-B," which are open to users who do not have "no posting link restrictions," are websites where streaming videos of celebrities who are the target of support in fan community apps are posted, for example, and relatively safe link destinations are specified.

The flow of the process for determining whether a user has posting link restrictions in the user posting process will be described with reference to Figure 21. Figure 21 is a flowchart for the case where a determination of whether or not a user has posting link restrictions (processing surrounded by a dotted line) is added to the user posting process described with reference to Figure 18, so a description of the same processes as Figure 18 will be omitted.

When the posting screen in FIG. 17(A) is displayed in step S303, a determination is made in step S316 as to whether or not a link other than the specified link has been pasted. If it is not determined that a link other than the specified link has been pasted, the process proceeds to step S304, where a determination is made as to whether or not "Next" has been selected.

On the other hand, if it is determined that a link other than the specified link has been pasted, the process proceeds to step S317, where it is determined whether the user is permitted to paste links other than the specified 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 obtained from the distribution server 100 and stored in the memory unit 320.

If it is determined in step S317 that the user is permitted to post links other than the specified link, the process proceeds to step S304, where it is determined whether or not Next has been selected. On the other hand, if it is not determined in step S317 that the user is permitted to post links other than the specified link, a notice is issued in step S318 that posting is not permitted, and the process returns to step S316. For example, if the user is at level 10, the user is not permitted to post links other than the specified link, and so a notice is issued that links other than the specified link cannot be pasted, as shown in the example of FIG. 20.

Returning to FIG. 19, "report count" is a permission that can affect whether or not a particular piece of content is hidden from all users. In this embodiment, content that has accumulated a certain number of hidden or reported pieces of content by users with a level of 70 or higher can be hidden from all users. For example, content that has been hidden or reported by five users with a level of 70 or higher can be hidden from all users.

In addition, content or comments posted by a user who has accumulated a certain number of hidden or reported content by users with a level of 70 or higher, which is subject to the "report count," can be made hidden from all users. For example, content or comments posted by a user who has been hidden or reported by five users with a level of 70 or higher can be made hidden from all users.

Note that the users who are hidden may not include the user who posted the comment or content. This allows the user to know (be aware) that the content or comment they posted is subject to restriction, for example, by the lack of action from other users, even though the content or comment they posted is reflected on their own device.

Different benefits are associated with the "benefits" as the benefit given depending on the level. For example, when there is a giveaway project, items that are more beneficial to fans, such as rarer items, may be given depending on the level. For example, if the benefits are stamps that can be used when posting comments, or items that can be used at a talent's live performance, the amount of money spent on stamps or items will be higher for benefit D given to users at levels 60-69 than for benefit E given to users at levels 50-59, and the equivalent amount of the benefit given increases as the level increases.

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

External evaluations are evaluations from other users other than the user himself/herself. For example, if a content or comment posted by a user receives "likes" from other users, the user will receive 5 points for each "like" (each tap action).

Alternatively, points may be awarded in response to a high evaluation from the administration, for example, if the administration is left with a favorable impression of a user as being highly trustworthy based on the content posted by the user or the content of the comments. The number of points awarded by the administration may be a predetermined number, or may be changed by the administration as appropriate.

Points may also be awarded according to the degree of propagation of the target of support. That is, points are awarded according to the degree of profit contribution to the target of support by the act of promoting content (videos, goods, etc.) related to the target of support. For example, the act of promotion includes the act of spreading the link of the streaming video of the talent who is the target of support, and the act of introducing the goods of the talent who is the target of support. For example, if a video link of a streaming video related to the talent or the group to which the talent belongs is attached to the content posted by the user, points are awarded according to the number of video views from the posted content. In addition, if a link to a goods page related to the talent or the group to which the talent belongs is attached, points can 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 target of support in the fan community, or a sales page of a collaborative product with another company, and a dedicated URL for community posting may be issued for tallying. Alternatively, if a product is purchased via the dedicated URL for community posting of the goods page on the official website, points may be awarded to the user who posted the URL.

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

As an example of external evaluation, the text of comments made on content may be evaluated, and if the text contains positive words predetermined by the administrator or the like, the points may be increased, and if the text contains negative words predetermined by the administrator or the like, the points may be decreased. The text may also be evaluated automatically by AI. For example, the proportion of positive and negative words may be automatically determined for the content posted by the user himself, or for comments from other users on the content posted by the user, and points may or may not be awarded depending on which element is more prevalent. Positive and negative words are not determined by the user, but are criteria based on external factors (for example, criteria by the administrator (including AI judgment)).

(About the evaluation history status update process)
Next, the flow of the evaluation history status update process of a user will be described with reference to FIG. 23. FIG. 23 is a diagram for explaining a flowchart of the process of updating the evaluation history status of a user that changes 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 some action (for example, an action that is subject to external evaluation such as a tap action, a comment, a report, or a non-display) is performed on the content or comments posted by each user in the fan community app. Note that the evaluation history status indicates the result of evaluation of a user by external factors other than the user himself/herself, including the "level" and "accumulated points" in the user information database of FIG. 7 stored as account information.

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

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 was a "point increase" evaluation. For example, if the external evaluation is a "like from another user" (a tap action from another user) as exemplified in FIG. 22, the number of points increases by 5, and therefore in step S402, it is determined that the external evaluation was a "point increase" evaluation.

When it is determined in step S402 that the external evaluation was 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, suppose a user is at level 59 and reaches the number of points required to reach level 60 by adding 5 to their accumulated points due to the external evaluation, and their level rises to 60. At that time, in the user information database, the level is 60 and the number of accumulated points is updated to the value after adding 5 and is stored.

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

After the permitted action information is updated and stored in step S405, in step S406, information is sent to the user to inform him or her that the specific action has been permitted, and the process ends. For example, the user terminal 300 may send a push notification with a message saying "Due to leveling up, there are no more restrictions on posting links," or a notification may be displayed within the app, or a pop-up may be displayed the next time the user posts.

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

When it is determined in step S407 that the external evaluation was a "point reduction" evaluation, in step S408 the number of points is reduced for each user according to the external evaluation, and the evaluation history status is updated and stored. For example, suppose a user was at level 60, but had their accumulated points reduced by 5 due to an external evaluation, so that their accumulated points no longer meet the number of points required for level 60, and their level is reduced to 59. In this case, in the user information database, the level is updated to 59, and the accumulated points are updated to the value after 5 is subtracted, and stored.

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

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

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

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

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

24(A) shows an example of three consecutive taps (continuous taps). At the first tap (48th tap), the thumbs-up mark 41a is displayed popping out from the icon 708 with a tap action count of 78. At the second tap (49th tap), the thumbs-up mark 41b is displayed popping out from the icon 708. At the third tap (50th tap), the fan mark 42 is displayed popping out from the icon 708. The fan mark 42 is a fan mark of a related talent associated with the content in which the icon 708 was operated. In this way, when the performance time (from popping out to disappearing) of the mark that popped out from the previous tap overlaps with the performance time of the mark that popped out from the next tap, multiple marks are displayed. In this way, the marks are displayed one after another by the continuous tap, so that the user can feel a sense of exhilaration in the feel of the tap action (operability), and further tap actions can be encouraged. Note that the effect of the marks popping out may be such that multiple marks are not displayed at the same time as in the example shown in FIG. 24(A), but rather that only one mark is displayed at a time.

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

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 a user on the content, but instead, or in addition, each time the number displayed in the number of tap actions 78, which is the total number of tap actions performed by users in the fan community, reaches a predetermined value (e.g., 100 times), a performance may be given to the user who performed the 100th action.

Next, with reference to FIG. 25, an example of the type of effect executed by accepting a tap action will be described. FIG. 25 is an example of a content-specific effect data table of the effect display by a 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 related to the effect display is associated with each content (posted article).

In the content-specific effect data table, an effect type is defined for each article ID. Also, 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 a predetermined number, or when the predetermined number of times has been reached. If the predetermined number of times is 100, the upper limit for which a tap action is possible, then 1 to 99 is less than the predetermined number of times.

For effects that are less than a predetermined number of times, a default effect and, if a related talent is set for the content, a fan mark effect are set. For example, the default effects include marks such as applause, thumbs up, hearts, and rare marks. A mark corresponding to the related talent is associated with the fan mark. For example, as illustrated in FIG. 14, for article ID "a1", talent IDs "t1", "t2", "t6", and "t14" are associated with the related talents. Therefore, "mark_t1", "mark_t2", "mark_t6", and "mark_t14", which are fan marks corresponding to each related talent, are associated. The same probability may be set for the lottery probability that each mark is used for the effect, and the appearance probability of the fan mark or rare mark may be set to be small. In this way, if a related talent is associated with the content, a fan mark appears by performing a tap action. This can encourage the user to perform a tap action, and further, when posting content, the user can be encouraged to select a related talent before posting. As a result, it becomes easier for other users to obtain information about their favorite talent, and user actions can help revitalize the fan community.

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

In addition, when no related talent is set for the content, as shown in the example of article ID "a99" in Figure 25, the type of performance is not set to fan mark or talent performance, and if the number is less than the specified number, a default performance is performed, and when the specified number is reached, a luxurious performance is performed.

For each of the effects, multiple effect patterns may be defined for the luxurious effects, for example, and there may be one default effect when the predetermined number is not reached. Also, only one of the fan mark effects when the predetermined number is not reached, or the talent effects when the predetermined number is reached, may be defined. For example, even if a related talent is selected for the content, the performance when the predetermined number is reached may be only the luxurious effect.

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

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

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

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

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

When it is determined in step S505 that there is an associated talent, in step S506, tap actions less than a predetermined number are determined by lottery based on the content-specific performance table of FIG. 25. After the performance is determined in step S506, the performance of the tap action determined in step S507 is executed, and tap action count update information is sent to the distribution server 100, and the process ends. For example, when "mark_t1" of the performance type fan mark for article ID "a1" in FIG. 25 is determined by lottery, the number of tap actions 78 and the number of individual tap actions 48 are updated, and a performance is executed in which a fan mark corresponding to "mark_t1" pops out.

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

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

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

When it is determined in step S510 that there is an associated talent, in step S511, a tap action presentation for when the predetermined number is reached is determined by lottery. In step S512, the tap action presentation for when the predetermined number is reached determined in step S511 is executed, and tap action count update information is sent to the distribution server 100, and the process ends. For example, when "special_t1" of the presentation type talent presentation for article ID "a1" in FIG. 25 is determined by lottery, the number of tap actions 78 and the number of individual tap actions 48 are updated, and the presentation corresponding to "special_t1" is executed.

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

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

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

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

In this embodiment, by utilizing an API provided by the external web service system 400, information on the video distributor and the person with whom the distributor is co-distributing (also called collaboration) 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 displayed to the user, it is possible to extract and allow the user to identify broadcasts of the participating community (first attribute) and favorite talent (second attribute) that the user has pre-selected.

Figures 27 (A) and (B) are examples of distribution schedule screens displayed on the user terminal 300. For example, the distribution schedule icon 18 may be displayed at the bottom of the application screen, and the distribution schedule icon 18 may be displayed when a selection operation is performed on the distribution schedule icon 18. Alternatively, the distribution schedule may be selectable on the channel list screen exemplified in Figure 12, or may be displayed in the channel list display 82 for each community.

Figure 27 (C) is an example of a video content screen provided by the external web service system 400, and the user can transition to the video content screen by performing a specific operation from the screen of Figure 27 (A) or Figure 27 (B).

The distribution schedule screens of Fig. 27(A) and Fig. 27(B) display a favorite filter 20, a distribution period selection area 91, a group selection area 92, a distribution date and time 93, a content heading 90, a channel account 98, and related talents 94. For example, a user may select the content heading 90 to transition to a distribution page in an external web service of Fig. 27(C). The transition destination is the video distribution channel of the account displayed in the channel account 98. The related talents 94 display icons of the talents appearing in the corresponding distribution. For example, the content heading 90a in Fig. 27(A) displays that there is a distribution by the account of the official channel of group A, and the content heading 90b displays that there is a distribution by the channel of talent BBB.

In the distribution period selection area 91, for example, icons such as "Upcoming distribution" which displays a list of content headings 90 (content information) identifying the most recent past distributions (contents), "Currently distributing" which displays a list of content headings 90 identifying the currently distributed distributions (contents), and "Upcoming schedule" which identifies the distributions (contents) scheduled for the future are displayed, and the list of content headings 90 displayed can be switched by the user selecting each icon. FIG. 27(A) is an example of a 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 a distribution schedule screen when the "Upcoming schedule" icon is selected, and a list of content headings 90 for identifying the future scheduled distributions is displayed.

In the group selection area 92, icons for selecting the group 1 to which the talent illustrated in FIG. 5 belongs are displayed. Only groups corresponding to the communities in which the user participates are displayed in the group selection area 92. For example, FIG. 27(A) and FIG. 27(B) are screens displayed on the user terminal 300 of the user "u2" in FIG. 7, and in FIG. 27(A) and FIG. 27(B), icons for "group A" and "group B" corresponding to the communities A and B in which the user "u2" participates are displayed. By operating each icon, content headings 90 of broadcasts related to talents belonging to any of the groups (or both may be selectable) are displayed. In FIG. 27(A) and FIG. 27(B), the icon for "group A" is selected, so that content headings 90 for identifying broadcasts in which talents belonging to group A appear are extracted and displayed. Whether or not a talent belonging to group A is appearing in a broadcast can be identified by the user because the content heading 90 is associated with the performing talent 94 (talent ID in FIG. 5) by the broadcast server 100. Note that, in this example, the groups displayed in the group selection area 92 are only those groups that correspond to the communities in which the user participates, but this is not limiting, and all groups may be displayed regardless of the community in which the user participates.

Also, as described above with reference to FIG. 9, by selecting the favorite filter 20 on the distribution schedule screen, distributions in which the favorite talent previously selected by the user appears can be extracted and displayed.

The talents displayed in the appearance related talent 94 in FIG. 27(A) and FIG. 27(B) are displayed based on information acquired using the API of the video distribution site. For example, the distribution screen in FIG. 27(C) (including posts during distribution, after distribution, and before distribution) is provided with a summary section 95, and the poster of the distribution can edit the text of the summary section 95 as appropriate. By embedding attribute specific information 96 in the summary section 95, the distribution server 100 acquires the attribute specific information 96 and generates the content heading 90. The attribute specific information 96 is, for example, a channel account on the video distribution site. Since FIG. 27(C) is a distribution by a channel account corresponding to the talent "CCC", the distribution server 100 can acquire attribute specific information 96a, which is the channel account. In addition to the icon of the talent, the appearance related talent 94 may also display the name of the talent. Also, the appearance related talent 94 may be displayed as the related talent 88 described with reference to FIG. 13, etc.

In addition, in the summary field 95, attribute specific information 96b (also called handle), which is information (identifier) that identifies 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 joint distribution is performed with a talent other than the talent corresponding to the channel account that performs the distribution, a handle that identifies the joint distribution partner is input. This input action is also called mentioning another channel by inputting text information with an @ mark before the other channel. For example, when the distribution by the channel of the talent "CCC" is a so-called collaborative distribution with the talent "AAA", a handle for identifying the channel account of the talent "AAA" is embedded in the summary field 95 of the distribution. By inputting the handle, which is the attribute specific information 96b, in the summary field 95, the distribution server 100 can obtain the attribute specific information 96b, which is information on the collaboration partner, in addition to the distribution account itself.

As described above, the distribution server 100 acquires the attribute identification information 96 to generate a content heading 90 in which the talent ID of the talent corresponding to the channel account (attribute identification information 96a) performing the distribution is associated with the talent ID of the talent corresponding to the joint distribution partner entered in the handle (attribute identification information 96b). For example, assume that the information acquired from the external web service system 400 includes attribute identification information 96 corresponding to the talents "CCC" and "AAA". In this case, in a database that manages the content headings 90 that can be displayed on the distribution schedule screen stored as content data 122, information for identifying the content heading 90 associated with the talent IDs "t3" and "t1" of the talents "CCC" and "AAA" is generated and stored by the content management unit 132, thereby generating the content heading 90. In addition, the distribution server 100 acquires the text information of the title 97 of the distribution screen in FIG. 27(C) (e.g., "A Friendly Broadcast with AAA") and the thumbnail image 99, and displays the text information and thumbnail image in the content heading 90. This makes it possible to identify which talent from the talent information database stored as the attribute information 121 exemplified in FIG. 5 will appear in the broadcast, and allows the user to identify a broadcast associated with an attribute previously selected by the user.

For example, in the following, it is assumed that FIG. 27(B) is the screen of user "u1" in FIG. 7. In addition, if FIG. 27(B) is the screen of user "u1", user "u1" does not participate in community B, but 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, or only the icon of the participating community may be displayed (the icon of community B may not be displayed). The talents selected by user "u1" as his/her favorite talents are talents "AAA", "BBB", and "EEE" corresponding to talent IDs "t1", "t2", and "t5", but talent "CCC" has not been selected as his/her favorite talent. However, even if there is a joint distribution with a favorite talent in a distribution by the channel account of "CCC", who is not a favorite talent, information on the joint distribution partner can also be obtained by the attribute identification information 96b. Therefore, even if the favorite filter 20 is on, the content heading 90 for identifying the distribution of the talent "CCC" is displayed, and the related talents appearing 94 are displayed, so the user will not miss information about the favorite talent.

In addition, for example, if a joint broadcast suddenly occurs in the middle of a broadcast, and editing is performed to add new attribute specification information 96b (handle) to the summary field 95 of the broadcast screen in the external web service system 400, it will be extracted as needed. Therefore, even if a joint broadcast suddenly begins, the content heading 90 of that broadcast will be displayed in the broadcast schedule of the current broadcast in FIG. 27 (A). In addition, if the content heading 90 is associated with a favorite talent selected in advance by the user, a push notification can be sent, so the user will not miss a sudden broadcast of their favorite talent.

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

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

<Regarding reaction notification processing>
(Outline of reaction notification process)
The reaction notification process in this embodiment will be described with reference to Fig. 28 and Fig. 29. In the reaction notification process, it is possible to notify other users of the fact that there has been a reaction from a specific user (e.g., a user with a special account previously determined by the administrator) who satisfies a specific condition, such as being in a special position different from general users in the community. Hereinafter, an example will be described in which a reaction from a special user, such as a celebrity described with reference to Fig. 5, is notified as an example of a specific user who satisfies a specific condition.

10, 11, 13, etc., in the community app of this embodiment, a special action 79 is displayed on content (e.g., content/article posted by a user) to which a special user has reacted with a comment, tap action, etc., indicating that a special user has reacted. In addition, in this embodiment, when a special user has reacted, other users, including the user who posted the content that was the subject of the reaction (posting user), are notified of the reaction (e.g., a push notification or a notification list in the app). In this way, in the reaction notification process of this embodiment, other users (general users) are notified of the reaction from an influential special user by the display of the special action 79 or a push notification, etc., so that the post to which the reaction has occurred attracts more attention, and the general user can feel closer to the special user. This can promote the entire community and improve the satisfaction of users who use the community app. In addition, for the posting user, receiving a reaction from a special user on his/her post can be a particularly happy thing, which contributes to improving motivation for fan activities.

On the other hand, it is also conceivable that a special user may mistakenly perform a reaction operation. In that case, even if the reaction is canceled (deleted, etc.) after the reaction is reflected (shared) on the screen of the user terminal 300 of other users and the fact that a reaction has been made is notified, there is a possibility that the reaction may have already been seen by other users before it was canceled. In this case, even if the reaction is canceled after the fact, other users will already know that the reaction had been made, and it may be too late to cancel it after the fact. In particular, reactions of influential special users attract a lot of attention from other users, so misunderstandings based on the reaction before it was canceled are likely to spread.

Therefore, in the reaction notification process of this embodiment, a reflection condition is set for reactions made by special users. If a cancellation operation is received from the special user who made the reaction before the reflection condition is met, it is possible to determine that the reflection condition was not met, and the fact that the reaction was made is not reflected and not notified to other users. On the other hand, when the reflection condition is met without a cancellation operation being performed, the fact that the reaction was made is reflected and notified to other users. This allows the special user to cancel the reaction before it is shared with other users, allowing them to react with peace of mind.

The reflection conditions include those that are satisfied (established) when the cancellation time has elapsed or when a confirmation operation has been performed on a confirmation screen. For example, if a special user who performed a reaction operation such as a comment or tap action does not perform a cancellation operation within the cancellation time, it may be determined that the reflection conditions are satisfied. Alternatively, when a reaction operation is performed, a confirmation screen for executing the reaction such as a dialog box may be displayed on the display unit of the user terminal 300 of the special user who performed the reaction, and the reflection conditions may be determined to be satisfied when a confirmation button for executing the reaction is operated.

Note that, when the reflection condition is the lapse of the cancellation time, it may be determined that the reflection condition is met if a special user performs a confirmation operation to reflect the reaction, even if the cancellation time has not passed. For example, an icon for a confirmation operation may be displayed near the list display of reactions during the cancellation time period or near comments that are reactions, and the reflection condition may be determined to be met when the distribution server 100 receives information that an operation has been performed on the icon.

The cancellation time in the reaction notification process may be set to, for example, five minutes after the talent performs a reaction operation such as a tap action. However, the cancellation time is not limited to this, and may be set to several hours or several days after the reaction operation. The cancellation time may be variable, and the user may be able to set the cancellation time individually in advance through the operation of each special user.

The reflection condition may be set in advance by the user through an operation performed by each special user. For example, the reflection condition may be set to the lapse of the cancellation time, or the reaction confirmation operation may be performed by displaying a confirmation screen for executing the reaction, or the reflection condition may be set to both the lapse of the cancellation time and the reaction confirmation operation.

Examples of reaction cancellation operations include performing a predetermined operation (e.g., a long press operation or a flick operation) on an icon that performs a tap action operation, such as the heart icon 708 described with reference to FIG. 11, or displaying a delete icon on the comment to be cancelled and performing an operation on the delete icon. This allows the tap action operation to be cancelled (the number of tap actions performed by the special user on the content to be cancelled is reset to 0) and the comment to be deleted. A menu icon or the like that can display the delete operation as an option may be displayed on the comment. In addition, a list page of cancelable reactions that can be accessed from My Page or the like may be provided, and comments and tap action reactions that are in the cancelable period may be displayed in a list. For example, a delete icon or the like may be displayed for each reaction, and the comment or tap action for which the delete icon was selected may be cancelled on the list screen, or when any reaction is selected from the list screen, a transition may be made to a screen that displays the target posted content. Also, when a confirmation screen for executing a reaction, such as a dialog box, is displayed, the cancellation operation may be determined to have been performed by pressing the cancel button on the confirmation screen, or by closing the confirmation screen without pressing the confirm button.

(Example of data table related to reaction notification processing)
Next, an example of a data table associated with information related to reaction notification processing will be described with reference to Fig. 28. Fig. 28(A) is an example of information associated with the content database (table, etc.) described with reference to Fig. 14. The post ID in Fig. 28(A) corresponds to the article ID in Fig. 14. In addition, hereinafter, the poster of the post (article) is also referred to as the posting user. In the content data of Fig. 14 etc. stored as content data 122 of the distribution server 100, "reaction related information" is associated with each post (article) ID, as exemplified in Fig. 28(A).

The "reaction-related information" for each post ID includes the "total number of tap actions" which is a count of the number of tap actions made by users on the post, the "total number of comments" which is a count of the number of comments made by users on the post, and if there is a reaction from a special user such as a celebrity on the post, information on "special action" is associated with the post. The "special action" information is associated with the ID of the celebrity who performed the special action, and information on the presence or absence of a tap action or the presence or absence of a comment as information specifying the type of the special action performed. The "total number of tap actions" and the "total number of comments" are displayed in the number of tap actions 78 and the number of comments 77 displayed for each content, as exemplified in the content screen examples in Figures 10, 11, and 13. In addition, based on the information associated as the "special action", an icon corresponding to the celebrity ID and an icon corresponding to the type of special action are displayed as special actions 79 on the content screen, etc. The icon corresponding to the type of special action may be, for example, a heart mark displayed along with the celebrity's icon if it is a tap action, or a speech bubble mark displayed along with the celebrity's icon if a comment has been made.

Figure 28 (B) shows an example of a data table relating to special action reflection pending data stored in the storage unit 120 of the distribution server 100 (e.g., as action information 123, etc.). In the reaction notification process in this embodiment, a cancellation operation can be performed by the special user who made the reaction before the fact that the special user made the reaction is reflected and can be shared with other users. Figure 28 (B) shows data for identifying reactions for which the reflection conditions are not met and for which the cancellation operation can be performed.

In the distribution server 100, as a process for reflecting a reaction operation received from a user, in response to receiving information on a reaction operation from the user terminal 300, the information on the reaction is associated with the post (article) ID in FIG. 14 or FIG. 28 (A). For example, in the case of a tap action, as illustrated in steps S507, S512, S513, etc. in FIG. 26, tap action count update information is sent from the user terminal 300 to the distribution server 100, and if the user who performed the tap action is a user other than the special user, the total number of tap actions in FIG. 28 (A) is updated and reflected as the tap action count 78 without determining whether the reflection condition is satisfied (even if it is not satisfied). In addition, when a comment is posted, the comment posting information is sent to the distribution server 100, and if the user who performed the comment is a user other than the special user, the total number of comments in FIG. 28 (A) is updated and reflected in the comment count 77 without determining whether the reflection condition is satisfied (even if it is not satisfied). In addition, the comment will be reflected as a comment 87 on the content screen, such as FIG. 13, and will be shared with other users.

On the other hand, if the information on which the reaction operation was performed is information sent from the user terminal 300 of a special user, it will be associated with the post (article) ID and reflected to other users when the reflection conditions are met. In other words, if the reaction is from a general user other than a special user, the reaction will be shared with other users immediately regardless of whether the reflection conditions are met, but reactions from special users will not be reflected until the reflection conditions are met, and will be reflected (shared) after waiting for the reflection conditions to be met.

When the distribution server 100 receives information on which a reaction operation has been performed from the user terminal 300 of a special user, the received information is associated with the special action reflection pending data table of FIG. 28 (B). For example, a pending number is assigned to each received information, and each pending number is associated with the "sender user ID" which identifies the special user who performed the reaction operation, the "sent date and time" when it was sent, the "action content", the "post (article) ID" which was the subject of the reaction, and so on. The "action content" is the content of the reaction, and is associated with information such as the number of tap actions update information and the content of the comment.

For example, if a cancellation period of 5 minutes is set as a reflection condition, when the distribution server 100 receives information on which a cancellation operation has been performed within 5 minutes from the transmission date and time, the received information on which the cancellation operation has been performed is deleted from the special action reflection pending data so that it is not reflected in the content database (for example, a data table managed for each post (article) ID such as FIG. 14). On the other hand, received information on which a cancellation operation has been performed is not received and for which 5 minutes have passed since the transmission date and time, is reflected in the content database and associated, for example, as reaction-related information in FIG. 28 (A). As a result, the talent ID corresponding to the sending user ID is associated as a special action, and a special action 79 is displayed on the content screen, etc. In addition, the received information that no longer requires reservation due to a cancellation operation or the establishment of the reflection condition is not necessarily deleted from the special action reflection pending data, and a flag may be set on the received information that no longer requires reservation so that it is not included in the determination of whether or not a cancellation operation has been received.

Note that, although examples have been given in which the target of a reaction is the posted content for each post (article) ID exemplified in Figures 14 and 28 (A), reactions to comments 87 for each posted content in Figure 13 (tap actions on comments and reply comments) may also be included as reaction targets for special actions.

(Regarding the manner of notification to the poster)
In the reaction notification process, after a reaction made by a special user becomes shareable with other users due to the fulfillment of a reflection condition, the user who posted the content that was the subject of the reaction can be notified that there was a reaction from the special user. The notification mode is not limited to a mode common to other users, such as a notification by displaying a talent icon such as special action 79 on the posted content itself, but also includes notification by displaying a notice on a notice screen such as the poster's My Page, or by a push notification to the poster.

Note that notifications (such as push notifications) when a special user talent makes a reaction (favorable action) such as a comment or tap action may be sent to the special user regardless of whether the poster has previously selected the special user as a favorite talent, or only reactions from special users who have previously been selected as favorite talents may be sent.

In addition, the push notification for notifying that the special user, such as a talent, has performed a tap action or the like by the reaction notification process in this embodiment may be notified in a manner that corresponds to the special user who performed the action. For example, the message notified may be a voice message from the talent who is the special user, a part of the melody of a song or the like of the talent, an image related to the talent (for example, a photo or illustration of the talent himself), or a different message depending on the talent. For example, a notification message expressing the talent's catchphrase or tone of voice may be notified.

(Example of reaction notification process flow)
Next, the flow of the reaction notification process will be described with reference to Fig. 29. Fig. 29 is a flowchart for explaining an example of the reaction notification process described with reference to Fig. 28 etc. The reaction notification process is repeatedly executed by the content management unit 132 of the distribution server 100 etc.

In step S601, it is determined whether or not reaction information for a post (for example, information specifying a tap action operation on content or the posting of a comment) has been received. If it is determined that reaction information for a post has been received, then in step S602, it is determined whether or not the user who sent the information is a special user. For example, when a reaction operation such as a tap action or a comment is performed on the user terminal 300 for any of the posted contents exemplified in Figures 10, 11, 13, etc., reaction information such as tap action count update information and comment posting information is sent to the distribution server 100, and it is determined that the reaction information has been received.

In step S602, if the sender of the received information is a user (e.g., a general user) other than a special user such as a talent exemplified in FIG. 5, etc., a received information reflection process is executed in step S603. For example, based on the received reaction information, a process is executed to associate comment information (such as the body of the comment and the user ID) with the post ID that is the target of the reaction stored in a data table for each content such as FIG. 14 or FIG. 28(A) and to update the total number of tap actions, and a reflection process is executed to update the number of comments 77 and the number of tap actions 78 in FIG. 11 and FIG. 13, for example, so that they are displayed as comment 87. This allows the reaction to be shared on the user terminals 300 of other users as well.

When the received information reflection process is executed in step S603, default notification information is sent to the user who posted the post that is the target of the reaction in step S604, and the process ends. The default notification information is, for example, information for displaying the fact that a reaction has occurred by push notification or in the notifications on My Page. For example, when a reaction to the content with post ID "a3" in FIG. 14 or FIG. 28(A) is displayed (shared) on the user terminal 300 of another user by the reflection process, information for informing user "u1" who posted "a3" that a reaction has occurred is sent to the user terminal 300 of "u1", and a push notification or the like is performed.

On the other hand, when it is determined in step S602 that the user who sent the reaction information is a special user, a process of suspending reflection of received information is executed in step S605, and the process is terminated. For example, the reception information of the reaction received from the special user is associated with the special action reflection suspension data table illustrated in FIG. 28(B) and managed as information for which reflection is suspended, and the process is terminated. The reception information is associated with information identifying the sender user, the transmission date and time, the content of the action, and information identifying the post that was the subject of the reaction. At this time, until the reflection process is executed in step S609 described later, the reaction is not shared (not displayed) on the user terminals 300 of users other than the special user who performed the reaction operation, but is reflected and displayed in a shared form on the user terminal 300 of the special user himself.

Returning to step S601, if it is determined that no reaction information for the post has been received, then in step S606 it is determined whether or not a request to cancel reaction-related information corresponding to the received information reserved in step S605 has been received. For example, on the user terminal 300 of a special user, an operation such as a long press on the icon 708 to perform a tap action or an operation to delete a comment is performed, and thus a reaction cancellation request (deletion request) information is sent to the distribution server 100.

If it is determined in step S606 that a request to cancel a reaction corresponding to the received information managed as a pending target in FIG. 28(B) has been received, then in step S607, a process to not reflect the corresponding pending received information is executed, and the process ends without reflecting it to other users. The process to not reflect is, for example, a process to delete the pending received information in FIG. 28(B), and by deleting the received information, the process ends without the received information being associated as reaction-related information for each posted content in FIG. 14 or FIG. 28(A).

On the other hand, if it is not determined in step S606 that a request to cancel reaction information corresponding to the pending received information has been received, then in step S608 it is determined whether there is pending received information for which the reflection condition is met. For example, if a cancellation time period has been set (e.g., 5 minutes), the reflection condition is determined to be met (satisfied) when the cancellation time period has elapsed from the transmission date and time, or when a reaction confirmation operation has been performed. On the other hand, if it is not determined that the reflection condition is met, the process is terminated.

If it is determined in step S608 that there is pending received information for which the reflection conditions are met, then in step S609, a received information reflection process is executed for the pending reaction for which it is determined in step S608 that the reflection conditions are met. That is, the reaction information received in step S601 is reflected and can be shared with other users. The received information reflection process is a process for associating the received information as reaction-related information for each posted content, such as in a content data table in FIG. 14 or FIG. 28(A), so that it can be shared with other users. As a result, the reaction made by the special user will also be displayed on the screens of the user terminals 300 of other users.

Next, in step S610, a process is executed to transmit notification information in a form corresponding to the special user who is the sender of the reflected received information to the user who posted the post to be reacted to, and the process is terminated. For example, as illustrated in FIG. 28(B), the information of the tap action operation on the posted content with post (article) ID "a3" in FIG. 28(A) etc., which is the reaction made by the special user with talent ID "t5" in FIG. 5, which was managed as information to be withheld in step S605, is reflected in step S609 so as to be shareable with other users since the revocable time has elapsed since the date and time (sent date and time) when the tap action was made, and in step S610, notification information is transmitted to the user terminal 300 of poster "u1", who is the user who posted. The notification information includes information of a push notification that is sent together with a voice message or image of the talent "EEE" corresponding to "t5" in FIG. 5, information for displaying the special action 79 of the icon corresponding to "t5", etc.

Even if the reflection conditions are not met, the reaction may be reflected and displayed in a shared manner on the user terminal 300 of the special user who performed the reaction operation, but until the reflection conditions are met, an icon, annotation, etc. indicating that the reaction has not been shared with other users (it is a provisional display) may be displayed so that the special user can recognize that the reaction can be canceled before being reflected. Alternatively, the display manner of the reaction itself may be a manner different from the reflected and shared manner. For example, the text color of the comment and the color of the heart icon 708, etc. may be displayed in a lighter color than when reflected.

<About language association processing>
(Overview of Language Association Processing)
The language association process in this embodiment will be described with reference to Figures 30 to 35. The fan community provided via the communication system in this embodiment is a global community that can be accessed from various regions around the world. Therefore, for example, even if a user primarily uses Japanese as a language, he or she can communicate with users who use other languages (for example, users living overseas), not limited to users who also use Japanese as their primary language.

By the way, in today's fan activity situation, there are cases where fan users use a different type of language on a daily basis from the language used by the target of support (so-called oshi). In addition, fan users may use different languages depending on the situation (time, place, scene). For example, a fan may enjoy the content (including various information such as video content such as live broadcasts, music, SNS information, etc.) sent by the target of support such as a talent in a language that is different from his/her native language and that is used by the target of support, and send messages to the target of support in a language that is different from his/her native language and that is used by the target of support, while communicating with local fans in the area (country, etc.) where he/she lives in his/her native language. Furthermore, there may be cases where the native language, the language used when using the content, the language of messages to the target of support, and the language used when communicating with fan users are all different. In this way, it is possible to communicate using automatic translation using machine translation, etc. without having to use multiple languages, but there are cases where the accuracy is lacking, such as mistranslations. In addition, popular expressions, images, commonly used words, and the atmosphere of each language region (the so-called mood or tone of the place) may differ from language to language, and simply machine-translating may not convey nuances to users who speak other languages. Regional topics are also likely to be posted in the language used in that region. Therefore, the language of the information you want to receive and the language used by the person you want to receive the information you send may differ depending on the situation.

Therefore, in the present invention, it is possible to achieve communication according to language. In this embodiment, not only can content posted by a user be posted in any of a plurality of languages, but language information is associated with the posted content itself (for each post ID) as exemplified in FIG. 14, regardless of the type of language actually entered in the posted content. In this way, by associating language information with each posted content, posts associated with language information specified by the user can be extracted and displayed on the user terminal 300 based on the language information associated with the posted content (hereinafter also simply referred to as a post). Furthermore, the language information can be associated with the post when the content is posted, and the associated language information can be the type of language selected by the poster.

Furthermore, simply displaying a list of posted content in various languages may result in the content being lost in the flurry of comments and may not be read by the intended recipient. However, the language association process in this embodiment makes it possible to display content in a language specified (selected) by the user based on the language information associated with the post itself, making it easier for users to find the post they are looking for and for the post to be read by the recipient they wish to communicate with.

It is also possible to automatically associate the language associated with a post with, for example, the language set in the OS of the user device or the language set as the display language of the app. However, if the display language of the app is Japanese, but the post is written in English for English-speaking users to read, even if the posted content is narrowed down to be displayed by specifying English, there is a risk that the post will be excluded from the display as a post associated with Japanese due to the influence of the OS language settings, etc. However, in this embodiment, the language associated with the post can be selected by user operation, so that the language can be narrowed down to the language intended by the user.

(Example of screen display according to language information)
FIG. 30 is an example of a screen in which the content screen described with reference to FIG. 10, FIG. 11, FIG. 13, etc. is displayed according to language information associated with a post. FIG. 30 is an example of a community screen of the same type as FIG. 11, which displays a list of content headings (hereinafter, collectively referred to as content) of content posted to all channels of community A. For example, it is displayed by being selected from the channel list 82 of community A on the channel list screen of FIG. 12, etc. In the content screens of FIG. 10, FIG. 11, FIG. 13, etc., an example has been described in which the language associated with the currently displayed post is not displayed on the language switching icon LS, but hereinafter, an example will be described in which the language associated with the currently displayed post is displayed on the language switching icon LS as shown in the content screen of FIG. 30. In addition, by selecting the language switching icon LS, a language selection field LSR is displayed in which a language selection button and the like are displayed.

In FIG. 30(A), the language switching icon LS displays "Japanese" because the selection (designation) is made to display posts associated with Japanese as the language type. FIG. 30(B) is an example of a screen in which "English" is selected in the language selection field LSR displayed when the language switching icon LS is selected in FIG. 30(A), causing "English" to be displayed in the language switching icon LS, and a list of contents associated with English as the language information is displayed. Note that the language selection field LSR in FIG. 30(B) displays two options, Japanese and English, but as shown in FIG. 32(C) described later, three or more language types may be displayed, and multiple languages may be selected simultaneously by selecting an option that allows all languages to be selected, or by checking a check box. Also, a check button that fixes the selected language as the default may be displayed.

(Example of default settings screen)
31 is an example of a default language information setting screen, which is a part of a user information registration screen when using the community app for the first time in this embodiment. In the community app in this embodiment, a different language can be set for each item related to the use of the community app as the type of default language to be displayed. Examples of items that can be set include the app display language, push notification language, official content posts to be displayed, and user posts to be displayed.

The application display language is, for example, information about the language displayed on a setting screen such as My Page, various icons, etc. For example, the screen example of FIG. 30 etc. illustrated in this embodiment is an example of a screen when the application display language is set to Japanese. The push notification language is the language of the characters and images sent by push notification. The official content posting language to be displayed is a language associated with official content posted by a user who displays an official mark, such as the administrator or a special user in FIG. 5. The user posting language to be displayed is a language associated with content posted by a general user other than the official content posted.

In this embodiment, when the application is started to be used, the language is initially set based on the language setting of the OS of the user terminal 300. For example, in FIG. 31, the language setting of the OS of the user terminal 300 of the user who displays the screen is "Japanese", so it is displayed that the initial setting is Japanese. Also, since the user has performed an operation to change only the push notification language to English on the setting screen, "English" is displayed as the push notification language and "Japanese" is displayed as the other languages. Also, the default language setting can be changed later from My Page or the like even if it is not at the time of initial setting. In this way, the preset default language information is stored in association with information for each user, such as a user information database stored as account information 125 exemplified in FIG. 7, or as user information in the storage unit 320 of the user terminal 300.

As shown in FIG. 32(C) and other examples, the language that can be set for each item may be provided with a choice of all languages, or multiple languages may be set in advance. In addition, the default language associated with a user posting may also be set in advance.

It is also possible to allow more detailed settings than those exemplified in FIG. 31. For example, the default language displayed may be different for posts by special users such as celebrities and for posts by administrators. In addition, the display language may be set to the user's preference in response to user operations, so long as a certain level of categorization is possible, for example, by community, channel, category, etc. Since the topics users want to talk about change depending on the topic, and the nature of the users who gather may also change, communication in a language appropriate to the situation becomes possible.

(Screen example when posting with language association)
FIG. 32 is an example of a user posting screen, and is an example of a screen in which a language switching icon LS is further displayed on the posting screen of FIG. 17. The posting screen of FIG. 32 is displayed when a user operates the posting icon 23 displayed on the content screen, etc., as in FIG. 17. As shown in FIG. 32(A), a default language is selected in advance as the posting language. The default language is selected from the initial setting language based on the OS setting of the user terminal 300, the language of the application display language set in advance on the language setting screen, etc., exemplified in FIG. 31, etc., or a language set in advance as the default posting language by the user. FIG. 32(B) is an example of a screen when switching the language associated with the posting, and is an example of a screen in which English is selected in the language selection field LSR displayed by selecting the language switching icon LS in FIG. 32(A). As a result, English is associated with the posting as language information. Also, as exemplified in FIG. 32(B), since the language information can be associated with the posting regardless of the actual language of the text to be input, for example, even if the text is input in Japanese, English can be associated as language information.

Figure 32 (C) is another example of the display mode of the language selection field LSR displayed when the language switching icon LS is selected. In Figure 32 (B), an example is shown in which two options, Japanese and English, are displayed as language options, but as shown in Figure 32 (C), three or more language options may be displayed, or there may be an option of "all languages". When "all languages" is selected, a list will be displayed regardless of which language is displayed in the language switching icon LS in Figure 30, that is, regardless of which language is selected (specified) as the language to be displayed. Furthermore, a check box or the like may be displayed so that multiple languages can be selected. For example, three languages, Japanese, English, and Chinese, can be specified at the same time. Also, in the language selection field LSR displayed when posting, a check button or the like for fixing the setting may be arranged, and the default language at the time of posting may be set based on whether the check button is on or off.

(Example of a data table with associated language information)
Next, an example of a content data table associated with language information will be described with reference to FIG. 33. FIG. 33 is an example of information associated with a content database (table, etc.) stored as content data 122 of the distribution server 100 described with reference to FIG. 14 and the like. The post ID in FIG. 33 corresponds to the article ID in FIG. 14. As in FIG. 14, a "poster ID" is associated with each "post (article) ID". In addition, although not shown in FIG. 14, a "posting date and time" and "posting content information" are associated with each "posting content information". The posting content information includes information such as the main text of the content to be posted, the headline title, and an attached image. Furthermore, in FIG. 33, "language information" is associated with each post ID. The language information associated with each post ID, that is, each piece of content, is associated with the language associated at the time of posting, as illustrated in FIG. 32. As a result, posts associated with a type of language specified by the user in advance or by operating the language switching icon LS can be extracted according to the language and displayed in a list. As shown in FIG. 32(C), when "all languages" is selected or when multiple languages are selected, the language information may not be limited to one language information, but multiple languages may be associated with the language information.

Examples of information stored as content data include (1) a case where the language included in the posting content information (e.g., a message such as text or image) matches the language information associated with the posting, and (2) a case where the language included in the posting content information does not match the language information associated with the posting. For example, the posting ID "a20" in FIG. 33 corresponds to the content heading 70d1 in FIG. 30(A) (hereinafter, the content heading 70 will also be referred to as content 70) and the posting ID "a30" corresponds to the content 70f in FIG. 30(A). The text and images of the posting content information of the content 70d1 and the content 70f are posted in Japanese, and the language information is also associated with Japanese. Also, the posting ID "a21" in FIG. 33 corresponds to the content 70d2 in FIG. 30(B), and the posting ID "a25" corresponds to the content 70g in FIG. 30(B). The text and images of the posts of content 70d2 and content 70g are posted in English, and the language information is also associated with English.

On the other hand, post ID "a35" in FIG. 33 corresponds to content 70h in FIG. 30(B), and although the text of the post is in Japanese, the language information associated with it is English. In this way, for example, if a user who deals with Japanese wishes to communicate with other users in Japanese, but wishes to bring up a topic related to an event in an English-speaking country and wants to be noticed by users living in that country, they can deliberately associate other types of language information with the Japanese post.

In addition, even if the same poster posts similar content, by associating different language information with the posts, it is possible to post articles about the same event in Japanese and English separately. For example, post ID "a20" corresponds to the content of content heading 70d1 in FIG. 30(A), and post ID "a21" corresponds to the content of content heading 70d2. Both content 70d1 and content 70d2 were posted by the same official account of the administrator (poster ID "ou"), and the contents of both are articles about the birthday of talent AAA. Even if a user wants to post content about the same AAA's birthday, the post can be made in Japanese for Japanese people and in English for English-speaking countries, rather than simply being machine translated, and the post can be made with nuances appropriate to the language region.

(Example of the process flow for displaying a list of posts with associated language information)
Next, the flow of the post list display process when displaying a list of posted contents associated with language information will be described with reference to a flowchart in Fig. 34. The post list display process displays a content screen or the like that displays the list of posted contents described with reference to Fig. 30. The post display process is repeatedly executed in the distribution server 100 in response to receiving display request information from the user terminal 300 (e.g., a request to display a screen that displays a list of contents exemplified in Figs. 10, 11, 30, etc.).

In step S701, it is determined whether or not a request to display a list of posted contents has been made. When it is determined that a request to display a list of posted contents has been made, in step S702, a process is performed in which list display information of posted contents associated with the set language is transmitted to the user terminal 300 according to the set language of the requesting user. For example, when an application is started and a request to display a home screen such as FIG. 10 is made, or when an operation to select a channel to be displayed is performed in FIG. 12, etc., the user information database stored in the account information 125 is referenced to identify information of a language that is pre-associated as a default with the requesting user. For example, if the language set by the initial setting or a change operation by the user on the language setting screen or my page of FIG. 31 is Japanese, the posted contents associated with Japanese are extracted from the content database of FIG. 33, and information for displaying the extracted posted contents on the user terminal 300 is transmitted to the user terminal 300. As a result, in the user terminal 300, as shown in FIG. 30(A), the language switching icon LS is Japanese, and a list of posted contents associated with Japanese language information is displayed. For example, if different language settings are used for official content posts and user posts, and a screen displaying both official content posts and user posts is requested, one of the default settings may take precedence, such as giving priority to the settings for official content posts.

Returning to step S701, when it is determined that a list display request has not been made, or after list display information has been sent based on the list display request in step S702, it is determined in step S703 whether a display language switching request has been made. For example, it is determined whether an operation to switch the display language has been performed on a posted content list screen such as FIG. 30 displayed on the user terminal 300 based on the information sent in step S702, or on the list display information stored in the memory unit 320 of the user terminal 300 (for example, received at the time of the previous login, etc.). When it is determined that a display language switching request has not been made, the process is terminated. On the other hand, when it is determined that a display language switching request has been made, it is determined in step S704 whether the switching request is to switch the default language setting. For example, if the request is for a temporary language change due to an operation to change the display language from Japanese to English (language specification operation) based on an operation on the language change icon LS in FIG. 30, it is not determined that the default language setting has been changed, and in step S706, list display information of posted contents associated with the changed language is sent to the user terminal 300, and the process ends.

On the other hand, for example, when a language switching operation (language specification operation) is performed based on an operation on the language switching icon LS in FIG. 30 and a language setting fixing operation is performed as shown in FIG. 32 (C) or when the default display language setting for content on My Page, etc. is changed, it is determined that the default language setting has been switched.

If it is determined in step S704 that the default language setting has been switched, in step S705 the switched language is associated with the user information as a default, updated, and stored. Thereafter, in step S706, in accordance with the switched language, list display information of posted contents associated with the language is transmitted to the user terminal 300, and the process ends. For example, when the default language is switched from Japanese to English, the user information stored as the account information 125 is referenced, and the default language associated with the requesting user information is changed to English, updated, and stored. In addition, posted contents associated with English as the language information stored in the content data table of FIG. 33 are extracted, and information for displaying the extracted posted contents in a list is transmitted to the user terminal 300. As a result, it is possible to switch from the screen displaying a list of posts with Japanese associated with the language information of FIG. 30(A) to a screen displaying a list of posts with English associated with the language information of FIG. 30(B).

Although an example has been described in which the post list display process in FIG. 34 is executed by the distribution server 100, it may also be executed by the user terminal 300. For example, of the content data exemplified in FIG. 14 etc., data for displaying the posted content for each channel selected from the channel list screen in FIG. 12 is received together with data associated with language information other than the specified language (for example, data for all posted content associated with the channel for which a display request has been made). After receiving the data, the posted content associated with the corresponding language may be extracted and displayed according to the default language setting stored in the memory unit 320 of the user terminal 300 or a language designation operation based on a switching operation, etc.

(Example of user submission process flow for associating language information)
Next, referring to Fig. 35, a process flow in the user terminal 300 when a user post associated with language information is made will be described. Fig. 35 is a flowchart in which a process of associating language information (mainly the process surrounded by a dotted line) is added to the user post process described with reference to Fig. 18 etc. A description of the same process as in Fig. 18 will be omitted. Also, assuming that the posting operation is performed on a channel where user posting is permitted, a description of step S302 in Fig. 18 will also be omitted. Also, although steps S304 to S311 and steps S314 to S315 are not shown in Fig. 35, explanations and illustrations will be omitted assuming that the processes are performed in parallel.

In step S301, when it is determined that a posting icon has been selected, for example, by selecting the posting icon 23 displayed on a content screen, a default setting language that has been set in advance is associated with the posting information in step S321, and a posting screen is displayed in step S303. For example, a posting screen is displayed in which the language switching icon LS displays the default language, as illustrated in FIG. 32(A), so that the posting language information set as a default for each user is associated with the posting. The default language information for posting is, for example, stored as account information 125, and is the type of language included in the default user information received from the distribution server 100 or the default information stored in the user information stored in the storage unit 320 of the user terminal 300. For example, it may be the display language of the app, or it may be the type of posting language that has been set in advance by initial setting or user selection, with a posting language item being provided in the items of language types that can be set by default.

In step S322, it is determined whether or not an operation to change the posting language has been performed. If it is not determined that an operation to change the posting language has been performed, then when it is determined in step S312 (which proceeds in response to an operation to input character information, etc., as described in FIG. 18, etc.) that a posting confirmation operation has been performed, in step S313, the posting information associated with the default language information is sent to the distribution server 100. On the other hand, if it is not determined in step S312 that a posting confirmation operation has been performed, the process returns to step S322, and the determination of whether or not an operation to change the posting language has been performed is repeated. Note that, as described in FIG. 18, if a posting confirmation operation is not performed in step S312 and a selection to close the posting screen is made in step S314 of FIG. 18, the process may be terminated without posting.

When it is determined in step S322 that an operation to change the posting language has been performed, it is determined in step S323 whether or not an operation to fix the changed language as the default has been performed. For example, as illustrated in FIG. 32, Japanese was associated as the default, but when another language is selected in the language selection field LSR of FIG. 32(B) or (C) displayed by operating the language switching icon LS, it is determined that an operation to change the posting language has been performed. Also, as illustrated in FIG. 32(C), it is determined that an operation to fix the default of the changed language has been performed when an input operation is performed in a checkbox to fix the setting of the selected language. When it is not determined in step S323 that an operation to fix the default of the changed language has been performed because, for example, no particular operation to fix the language has been performed and only a change operation has been performed, the process proceeds to step S325.

If it is determined in step S323 that an operation to fix the changed language as the default has been performed, the changed setting language is updated and stored in association with the user information. For example, if the default was Japanese, and an operation to change the posting language to English and an operation to fix the setting are performed, English is associated with and stored in the memory unit 320 of the user terminal 300 as the default language at the time of posting. Note that when the posted information is sent to the distribution server 100 in step S313, information in which the user's default language at the time of posting has been updated may also be sent, and the default language at the time of posting for each user information managed in the distribution server 100 may be updated.

In step S325, the changed setting language is associated with the posted information, and if it is determined in step S312 that a posting confirmation operation has been performed, the posted information with the changed setting language associated as language information is sent to the distribution server 100, and the process ends.

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

Furthermore, as described with reference to Figures 10, 11, 14 to 16, 27, etc., the distribution server 100 or the user terminal 300 switches between one of a number of display states in response to an operation on the favorite filter 20, including a first display state in which content headings (60, 70, 90) as exemplified in Figure 15 (B) when the favorite filter 20 is off are displayed on the display unit of the user terminal 300 so as to be identifiable by the user from among the content associated with the participating community that has been pre-selected and stored by the user (e.g., content stored in the content database of community A in Figure 14), and a second display state in which the favorite filter 20 is on, such as Figure 15 (A), in which content headings (60, 70, 90) relating to content associated with both the participating community and the favorite talent that has been pre-selected and stored by the user are extracted and displayed so as to be identifiable by the user. This allows the display to be switched between content headings that are posted in a community previously selected by the user (participation) and are displayed regardless of whether the content is associated with a favorite talent, and content headings related to content posted in a community previously selected by the user (participation) and associated with a favorite talent. This allows the user to easily identify information that they like. For example, if a user participates in community A and selects talent "AAA" with talent ID "t1" as their favorite talent, content headings of content that is associated with talent ID "t1" from among the content stored in the content database of community A in FIG. 14 are extracted and displayed on the home screen in FIG. 10, the community screen in FIG. 11(A), the distribution schedule screen in FIG. 27, and the like. The favorite 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.

(1-2) Furthermore, the on/off operation of the favorite filter 20 is a different operation from the series of operations when the user preselects a participating community or favorite talent, and is established in response to the user's operation on the favorite filter 20 icon displayed on the user terminal 300. As a result, when displaying the home screen of FIG. 10, the community screen of FIG. 11(A), the distribution schedule screen of FIG. 27, etc., the user does not need to perform an operation to select a participating community or favorite talent again, or an operation to transition to a screen for selection, but can switch to display content headings related to a preselected community, or content associated with both a community and a talent, thereby improving operability and user convenience.

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

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

(1-5) The multiple types of content that can be provided to the user include content that is not associated with a related talent, but is associated only with a participating community (e.g., article ID a99 in Figures 14 and 25), and when the display state of the favorite filter 20 is on, the content headings of content that is associated only with a participating community and not with a related talent are not displayed. As a result, when the favorite filter 20 is on, the content headings of content that is not associated with a favorite talent are not displayed, making it easy for the user to identify information associated with a favorite community and talent.

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

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

(1-8) As described with reference to the example home screen of FIG. 10, the multiple types of content that can be provided to the user can be classified into one of multiple categories including the recommended topic 62, and can be displayed on the user terminal 300 by classifying them into multiple categories as shown in FIG. 10. In the recommended topic 62, whether the recommended filter 20 is on or off, the content headings 60 related to a predetermined number of contents associated with both the participating community and the recommended talent that have been selected and stored in advance by the user are displayed so that the user can identify them. In categories other than the recommended topic 62, such as popular user posts 63, commemorative broadcasts 64, and goods 65, the content headings 60 corresponding to whether the recommended filter 20 is on or off are displayed so that the user can identify them, as described with reference to FIG. 16. By displaying the recommended topic 62, some of the content associated with the participating communities and recommended talents that the user has previously selected can be displayed without switching the display state, so the user can identify the content associated with their preferred communities and talents without the trouble of switching operations.

(1-9) In addition, the content headings 60 of the recommended topic 62 on the home screen illustrated in FIG. 10 can be displayed with priority, for example, above the content headings 60 related to content classified into other categories, regardless of whether the recommended filter 20 is on or off. This makes it easier for users to identify content associated with their favorite communities and talents.

(1-10) As described with reference to FIG. 12, by the user selecting the community bar 81 on the channel list screen of FIG. 12 from among the communities to participate in that the user has preselected, it becomes possible to display a content screen for each community, as exemplified in FIG. 11(A). This allows the user to further select preferred communities from among the communities to participate in that the user has preselected, and to display content headings 70 for each of the selected communities, allowing the user to further extract any information as necessary, even from among preferred information, improving convenience.

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

(1-12) In addition, when a tap action is received from the user a predetermined number of times (e.g., 100 times), a special effect such as a luxurious effect or a talent effect as exemplified in FIG. 24(B) is performed. This makes it possible to encourage the user to take a tap action, since a special effect is performed when the tap action is performed a predetermined number of times.

(1-13) The multiple types of content that can be provided to the user include content that is associated with a talent ID in the content database of FIG. 14 by being associated with a related talent, and for content that is associated with a related talent, related talent 88 is displayed, displaying the icon and name of the talent associated with the content, regardless of whether the recommended filter 20 is on or off. This allows the user to identify the related talent associated with the content, regardless of whether the recommended filter 20 is on or off, improving user convenience. It can also provide an opportunity to learn about new talents, etc.

(1-14) As described with reference to Figures 14, 17, and 18, the multiple types of content that can be provided to users include posted content posted by users. When a related talent is associated with the posted information in steps S310 and S311 of Figure 18, for example, by a selection operation on the related talent bar 40 in Figure 17 when the user posts, a talent ID is associated with the content generated from the posted information, as exemplified in the content database in Figure 14. This makes it possible to associate a talent with a user post, making it easier for users to share information they like.

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

(1-16) Based on the user information database in FIG. 7 and the content database in FIG. 14, when content associated with a favorite talent that has been selected and stored in advance by the user is posted, the distribution server 100 and the user terminal 300 send the user a push notification that content associated with the favorite talent has been posted. This makes it easier for the user to identify content information related to the favorite talent. Furthermore, if a specific user takes an action on the content posted by the user, the user can feel a sense of specialness.

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

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

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

(2-3) As described with reference to FIG. 19, the specific actions that can be taken are determined in stages according to the level. For example, if the user is at level 60 or above, there is no restriction on links to the content posted as a specific action, and if the user is at level 80 or above, the user can create a plan as a specific action. As exemplified in steps S404 to S406 of FIG. 23, these specific actions allow users who have leveled up from 59 to 60 to be free of link restrictions on the content they post, and allow users who have leveled up from 79 to 80 to create plans, so that users who have not reached a certain level are restricted from taking specific actions. As a result, by allowing specific actions to be allowed for users who have reached a certain level and are in a certain situation in stages according to the level, it is possible to encourage users to take actions aimed at a higher level, and it is possible to maintain good public order within the community.

(2-4) As explained in steps S407 to S411 of FIG. 23, the account management unit 133 restricts a user whose level has dropped and who is no longer in a specific situation from taking specific actions that were permitted according to the level. This restricts a user whose level has dropped and who is no longer in a specific situation according to external evaluation from taking specific actions, so that the user can be encouraged to take actions that can maintain or improve the specific situation, and public order within the community can be stabilized.

(2-5) As described with reference to FIG. 19, the specific actions that can be taken are determined in stages according to the level. For example, if the level is 59 or lower, the link restriction on the posted content, which is a specific action, is not permitted to be lifted, so there is a link restriction on the posted content. If the level is 79 or lower, the specific action of creating a plan is not permitted, so there is a restriction on creating a plan. As exemplified in steps S409 to S411 of FIG. 23, these specific actions restrict the links of the posted content that were permitted for a user who has leveled down from 60 to 59. In addition, for a user who has leveled down from 80 to 79, the creation of a plan that was permitted is restricted, so that a user who is no longer at a specified level is restricted from performing a specific action. In this way, by gradually restricting the specific actions permitted for a user who is no longer in a specific situation, it is possible to prevent the number of actions that can be taken from becoming extremely small, while encouraging actions that can maintain and improve the specific situation, and it is possible to maintain good public order in the community.

(2-6) As described with reference to FIG. 8, the user evaluation history status 55, which displays the level and accumulated points, which are information related to the user's evaluation history status, is not made public to other users, but can be viewed by the user himself on the My Page screen. This makes it possible to notify the user of information related to the evaluation history status that is updated in response to external evaluations, so that the user can be made aware of his own situation and be encouraged to make efforts to improve the public safety of the community.

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

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

(2-9) As explained with reference to FIG. 19 etc., restriction processing such as hiding is performed on the user terminal 300 etc. of each of multiple users for content and comments that are restricted by, for example, hiding or reporting, from users who are permitted to take the specific action of "moderator invitation" at level 90 or higher, or users who are permitted to take the specific action of "report count" at level 70 or higher. This restricts user actions to those actions that are restricted by users whose evaluation history status is in a specified status, making it possible to prevent restriction processing from being performed indiscriminately on user actions.

(2-10) In addition, actions that are subject to regulation from a specific action permitted by a specified number of users in the "report count" described with reference to FIG. 19 etc. are restricted from being reflected on the user terminal 300 of each of the multiple users. As a result, since an action subject to regulation is accepted by a specified number of users whose evaluation history status is in a specified status, the action is deemed to be a nuisance and its reflection is restricted, so that nuisance behavior can be efficiently restricted without impeding free interaction and communication.

(2-11) As described with reference to FIG. 19 etc., depending on the level, which is the evaluation history status of each of multiple users, for example, if the user is at level 50-59, a bonus E may be awarded, and if the user is at level 100, a bonus S, which is rarer than bonuses A-E, may be awarded. With this configuration, bonuses may be awarded depending on the evaluation history status, so that users can be conscious of reaching an evaluation history status that will award a bonus.

(2-12) Multiple users belong to the same fan community, and actions that users can take include, for example, promotional activities such as posting content related to the group they support or the talent belonging to the group, such as streaming videos and merchandise. The distribution server 100 changes the external evaluation according to the number of views of the streaming video and the profit contribution to merchandise sales due to the promotional activities, and updates the evaluation history status of the user. This can motivate users to promote themselves, thereby revitalizing the community.

(3-1) In the above-described embodiment, in response to a tap action from a user to posted content displayed on the screen of the user terminal 300 in FIG. 10, FIG. 11, FIG. 13, etc., or a response to a comment, etc., being accepted in step S601 in FIG. 29, the reaction is reflected in the content data table for each posted content in steps S603, S609, etc., so that the reaction can be displayed on the screen of the user terminal 300 of another user and shared. Also, in response to a reaction to the posted content in step S602 in FIG. 29 being a reaction from a special user who satisfies a specific condition, such as a special user such as a talent in FIG. 5 or a user of a special account previously determined by the administrator, in step S610 in FIG. 29, a push notification is sent to the user terminal 300 of the user who is the poster of the posted content to which the reaction operation was performed, or a special action 79, which is an icon indicating that a talent has reacted, is displayed, so that the fact that a reaction has been accepted from a special user can be notified. This allows the user who posted the reaction to be notified that they have received a reaction from a special user such as a celebrity (a specific user who meets the specific conditions in the embodiment described above), which can increase the satisfaction of the user who posted the reaction.

(3-2) With regard to a reaction operation performed by a specific user, in step S608 in FIG. 29, it is determined that the reflection conditions are met because the cancellation time has elapsed without a cancellation operation being performed, or because a reaction confirmation operation has been performed, and so on. In this way, reactions from a specific user are shared when the reflection conditions are met, so it is possible to prevent reactions from being shared indiscriminately without the reflection conditions being met.

(3-3) With regard to a reaction operation performed by a specific user, if, within the cancellation period, the tap action is cancelled by a long press on the icon (icon 708, etc.) on which the tap action operation is performed, a deletion operation is performed on the comment to be cancelled, or a cancel operation is performed on the reaction list screen, the reaction information on which the cancellation operation has been performed is deleted so that it is not shared with other users in step S607 of FIG. 29, and the reflection condition is not met. Alternatively, the reaction information may be not sent to the distribution server 100 due to a cancel operation being performed on the reaction execution confirmation screen, and the reflection condition may not be met. In this way, a cancel operation is performed to prevent the reaction from being shared with other users. As a result, the reaction is not shared due to the cancel operation, and the specific user can react with peace of mind.

(3-4) When the distribution server 100 receives reaction information from a general user who is different from a specific user, the reaction can be reflected immediately and shared with other users in steps S602 to S604 in FIG. 29. This reduces the processing load on the computer because reactions from users who are different from specific users can be shared even if the reflection conditions are not met.

(3-5) As information suggesting the number of reactions to a shared action (e.g., posted content), the number of tap actions 78 and the number of comments 77 for each piece of content in Figures 10, 11, 13, etc. are displayed, and for reactions from specific users, special suggestion information different from the information suggesting the number of reactions is displayed, such as special action 79, which is an icon suggesting that the post has received a tap action or comment from a special user displayed for each piece of content in Figures 10, 11, 13, etc. This makes it easy to identify whether a reaction to an action in posted content, etc. is a reaction from a specific user.

(3-6) The manner in which the poster (posting source) user is notified of the posted content that has received a reaction from a specific user in step S610 of FIG. 29 is a manner that corresponds to the specific user who made the reaction. For example, a push notification can be sent in the form of a voice message from the celebrity who is a special user, or an image related to the celebrity. This increases the user's interest when notified, since the user is notified that a reaction has been received in a manner that corresponds to the specific user.

(4-1) In the above-described embodiment, the user terminal 300 can accept text input in any of a plurality of languages on the posting screen of FIG. 32, and in steps S321 and S325 of FIG. 35, language information specifying the language type is associated with the posting information transmitted to the distribution server 100, and in step S313 of FIG. 35, the posting information including the poster ID, posting date and time, posting content information, language information, etc. associated with the content data table of FIG. 33 is transmitted to the distribution server 100. In addition, the user terminal 300 receives information for displaying a list of posted contents such as FIG. 30, FIG. 10, and FIG. 11 transmitted from the distribution server 100 in steps S702 and S706 of FIG. 34, and displays the list of posted contents. In addition, the posting list information includes information for identifying the posting content information of FIG. 33 such as text and images, and the language information associated with each post of FIG. 33. Based on the post content information and language information for each post, as shown in Fig. 30, posted contents associated with language information of a language specified by an operation on the language switching icon LS displayed on the list screen of posted contents in Fig. 30, or a language specified by initial settings such as Fig. 31 or a default setting by a user operation on My Page, etc. are displayed in a list. This makes it possible to post in any of a number of languages, and also allows the posts associated with a language type specified by the user to be narrowed down and displayed in a list, making it possible to communicate with other users according to the language.

(4-2) As shown in FIG. 32, a language switching icon LS indicating the currently associated language can be displayed on the post screen. This makes it easier for users to check the type of language associated with a post, since the type of language associated with the post can be specified at the time of posting.

(4-3) In addition, the posted content list display screen in FIG. 30 and the like displays a language switching icon LS that displays the currently narrowed down language in FIG. 30. For example, as shown in FIG. 30(B), if the display language has been narrowed down to English, the language switching icon LS displays "English." This makes it easier for the user to check the type of language specified when displaying a list of posts.

(4-4) Steps S321 and S325 in FIG. 35 allow the language type selected during the initial settings in FIG. 31 or by a user operation on My Page, etc., or the language type selected by an operation on the language switching icon LS as in FIG. 32(B), to be associated with the posted information and posted. This makes it possible for the user to communicate by associating the language type they intend.

(4-5) As shown in FIG. 31, the language set in the OS of the user terminal 300 can be initially set as the default language type, but the initially set language type can be changed from the initial setting to another language type, as in the push notification language in FIG. 31, or the default language type can be changed from My Page, etc. Also, in steps S322 to S325 in FIG. 35, it is possible to post by associating a language type different from the default by changing the language type from the language set by default, as in FIG. 32 (B). This simplifies the operation for associating, while allowing the associated language type to be changed as necessary, improving user convenience.

(4-6) The display language when using the community app can be set in advance in response to a user operation, for example, by setting the app display language set by the user at the initial setting in FIG. 31 or from My Page, or by setting the default display language type for the language of the content or post to be displayed. In addition, the language type displayed on the language switching icon LS displayed as the posting language when the posting screen in FIG. 32 is displayed may be associated with the posting information as the default display language of the app, and the language associated when the posting screen is displayed can be switched to another language type based on an operation on the language switching icon LS as shown in FIG. 32 (B) in steps S322 to S325 in FIG. 35. This makes it possible to set the language type associated with the post in advance in response to a user operation, and also makes it possible to associate a language type different from the previously set language type in response to a user operation. This allows the user to associate the language type depending on the content of the post, improving user convenience.

(4-7) From the initial setting or My Page in FIG. 31, it is possible to set the default language to be displayed, such as the application display language when using the community application or the language of the content to be displayed, in response to a user operation. Also, in step S702 in FIG. 34, a list screen of posted contents associated with language information of a preset default language type can be displayed, and in steps S703 to S706, in response to a request to switch the display language, a list screen of posted contents associated with language information of the switched language type can be displayed. For example, if the default of the application display language or the language type of the content to be displayed is set to Japanese, a list screen of posted contents associated with Japanese as the language information in FIG. 30(A) can be displayed, and by operating the language switching icon LS and selecting English, it is possible to list posted contents associated with English as the language information as shown in FIG. 30(B). This allows posts to be displayed by switching between the default language type and a language type different from the default in response to a user operation, enabling the user to communicate based on a desired language type depending on the situation.

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

(About content information)
In the above-described embodiment, the content headings (60, 70, 90) in Fig. 10, Fig. 11, Fig. 27, etc. are exemplified as content information related to content (e.g., news articles, information posted by users, etc.). However, without being limited thereto, the content information related to the content may be, for example, explanatory information on the screen of the content itself exemplified in Fig. 13. For example, the information includes the contributor 71, the contents 74b, the related talent 88, the special action 79, the number of tap actions 78, etc., which are various information displayed on the content screen itself in Fig. 13.

(About attribute selection processing)
In the above-described embodiment, an example was described in which a participating community and a favorite talent can be selected at the time of initial login in steps S102 to S104 in FIG. 9. The selection of participating communities and favorite talent at the time of initial login may require selection of both in step S103, or may allow operation of selecting neither (selecting zero attributes). Also, only either participating communities or favorite talent may be selected, or selection of either one may be required. For example, even if a favorite talent is selected, if the user does not participate in a participating community corresponding to the group 1 to which the favorite talent belongs, information about the favorite talent may not be extracted and displayed on the content screen. In other words, even if the favorite filter 20 is turned on, the content heading of a talent belonging to a group corresponding to a community in which the user does not participate is not displayed. Alternatively, the user may not be able to select a favorite talent unless a participating community is selected. For example, the user may not be able to proceed to the screen for selecting a favorite talent unless one of the participating communities is selected.

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

In the above-described embodiment, in steps S101 and S102 in FIG. 9, an example was described in which an attribute selection screen is displayed on the user terminal 300 in step S102 if it is the first login, but it may not be displayed on the screen at the first login, and the initial attribute selection may be performed later from My Page or the like. Also, until the user later edits from My Page or the like, at the time of the first login, the user may be in a state of participating in all communities.

In the above embodiment, when the user is not logging in for the first time (step S101 NO in FIG. 9), the determination that the participating community or the favorite talent has been selected in step S107 after the setting editing screen in FIG. 6 is displayed is based on the timing of the selection operation on the icon or the like. However, the present invention is not limited to this. By operating the home icon 13 or the like displayed at the bottom of the application screen to move to another screen, the attribute selected on the attribute selection screen in FIG. 6 may be considered to have been selected by transmitting and receiving information that is deemed to have been determined, and the process may proceed to step S108. Alternatively, instead of or in addition to an operation on the display of each participating community or each talent on the attribute selection screen in FIG. 6, a confirmation icon or the like may be displayed, and it may be determined that a selection has been made when an operation is performed on the confirmation icon (when information transmitted in response to the operation is received). Also, when an operation is performed on the confirmation icon, a special effect may be performed on the user terminal 300.

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

(Regarding the display of comments on the content screen)
In the above-described embodiment, an example was described in which, 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, the display mode or the display order can be changed. Instead of or in addition to this, when a talent (special user) who has made a comment on the content is a favorite talent previously set by the user, the display mode of the favorite talent's comment 87 may be displayed in a different manner than when the talent who performed the action is not the favorite talent. Or, the comment may be displayed at the top of each comment 87. Or, when a talent who has made a comment on the content is a related talent associated with the content, the display mode of the related talent's comment 87 may be displayed in a different manner than when the talent who performed the action is not the related talent. The different manner may be, for example, a manner in which the color is different, the content of the message is different, or the presence or absence of a message. Or, the comment may be displayed at the top of each comment 87.

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

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

(Notification to users)
In the above-described embodiment, an example was described in which a notification (display on a notice screen, push notification, etc.) is given to general users when content associated with a favorite talent previously selected by a user is posted, or when a comment is made on the content from the talent himself/herself who is a special user. Regarding this notification, when a comment is made from a favorite talent previously set by a user, the notification mode may be different from when a comment is made from a talent who is not a favorite talent. When the notification mode is changed, for example, when a notification is made from a favorite talent, the notification icon 15 displayed at the bottom of the app screen may be highlighted.

Also, an example has been described in which, when a post (content or comment) made by a user receives a favorable action (reaction) such as a comment or tap action from other users, including special users, a notification may be sent to the user who made the post (such as displaying the notification screen or sending a push notification). In this case, for example, notifications are normally sent once an hour, but when an action is taken by a special user who is a celebrity or a special user who is a favorite celebrity, a notification may be sent in real time.

If a user has selected a favorite talent for each unit, the user may be notified by push notification when content associated with one of the talents in the unit is posted, or when content associated with the unit is posted, etc.

(About attribute extraction processing)
In the above embodiment, when the favorite filter 20 is turned on, the content headings (60, 70) associated with the favorite talent selected by the user in advance are extracted and displayed. However, if multiple people are selected as favorite talents, the talents may be further narrowed down for each favorite talent. For example, if the talents with the talent IDs "t1", "t2", and "t3" are selected, when the favorite filter 20 is turned on, "t1", "t2", and "t3" may be individually selected. Alternatively, if the favorite talents are selected in advance by unit, the unit may be individually selected. Furthermore, by selecting a more special talent (the most favorite talent) from among the favorite talents in advance, further filtering may be performed by the most favorite talent. In this way, after extracting all the favorite talents with the favorite filter 20, it may be possible to select them individually (further narrow down) by operating a specific icon or the like, and multiple filtering steps such as first, second, and third filtering may be possible.

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

It should be noted that it may be possible to associate any of the talents even if the talent belongs to a community different from the community corresponding to the group to which the talent belongs. For example, the talent ID "t1" is a talent belonging to "Group A" of the group 1, but the talent "t1" may be associated with content posted in "Community B" corresponding to "Group B". Therefore, if a user who has selected the talent ID "t1" also participates in "Community B", turns on the favorite filter 20 on the home screen or the content screen in "Community B", the content associated with the talent ID "t1" will be extracted and displayed. This allows the user to obtain information about the favorite talent without missing it, even if there is a collaboration project between different groups and the posting is only made in the community corresponding to one of the groups. It should be noted that even if the user does not participate in "Community B", the content associated with the favorite talent may be displayed on the home screen.

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

(Regarding the memory state of the favorite filter 20 in the attribute extraction process)
In the above embodiment, an example was described in which the on state of the favorite filter 20 is stored and maintained after an operation on the favorite filter 20 is performed, even when the content screen in FIG. 13 is displayed after the application is started and the screen returns to the content screen or home screen on which the favorite filter 20 was on. However, the present invention is not limited to this, and the favorite filter 20 may always be in either the on or off state when moving to a different screen. For example, after the community screen in FIG. 13 is displayed from the community screen in FIG. 11 (or the home screen in FIG. 10) with the favorite filter 20 in the on or off state, the favorite filter 20 may be off or on when returning to the community screen in FIG. 11 (or the home screen in FIG. 10). Alternatively, the favorite filter 20 may be turned on in the home screen of FIG. 10 (or the community screen of FIG. 11), the community screen of FIG. 11 (or the home screen of FIG. 10) may be displayed, and then when the user returns to the home screen of FIG. 10 (or the community screen of FIG. 11), the favorite filter 20 may be in an off or on state.

(User submission processing)
In the above embodiment, an example was described in which the user posting screen example of FIG. 17 is divided into FIG. 17(A), which is a posting screen for inputting characters and uploading images, and FIG. 17(B), which is a screen for selecting categories and related talents. However, this is not limited to this, and FIG. 17(A) and FIG. 17(B) may be displayed on one screen for input or selection. For example, scrolling may be possible, and transition to another screen may not be required. Also, posting may be possible even without inputting characters or posting images. Or, even if there is no title, posting may be possible as long as characters are input or an image is uploaded.

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

(Regarding evaluation history status update processing)
In the above-described embodiment, an example has been described in which a notification is given in steps S406 and S411 in Fig. 23 that a specific action has been permitted or restricted. However, this is not limiting, and the user may not be notified in steps S406 and S411. Alternatively, a notification may be given only in one of two ways, such as a notification being given when an action is permitted in step S406, but not a notification being given when an action is restricted in step S411. For example, by not notifying the user when a restriction is imposed, it is possible to avoid upsetting the user.

(Other examples of evaluation history status)
In the above-described embodiment, as described with reference to FIG. 19, an example has been described in which the level of a user increases step by step from the initial setting level according to external evaluation, and each time a specific situation (e.g., level 60, level 80, etc.) occurs, a specific action that can be taken is permitted according to the level. However, this is not limited to this, and for example, the specific actions in FIG. 19 may be permitted in the initial setting for all users, and as the level decreases, the specific situation gradually disappears and the specific action that can be taken may be restricted. In addition, the initial setting level is not limited to a lower limit of 1 and an upper limit of 100, but may start from 80, etc., and the specific action that can be taken may be permitted or restricted in stages according to the change in level.

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

In the above-described embodiment, an example was described in which when content or comments posted by a user are hidden or reported, the points are reduced, and actions are gradually restricted. Alternatively or in addition to this, a reflection restriction point may be set in the evaluation history status as a standard for restricting the reflection of actions in the community app, separate from the points that affect the level (variable cumulative points). For example, a user whose posted content, comments, etc. have been hidden or reported by other users a predetermined number (for example, 20 in either case or in total), may have their actions restricted (reflection restriction). For example, content, comments, etc. posted by a user subject to reflection restriction may not be displayed to other users for a certain period of time, or content, comments, etc. may not be posted at all for a certain period of time.

The reflection restriction may be performed according to the level that changes depending on the number of points as shown in FIG. 22, FIG. 23, etc., described above. For example, a negative level lower than 1 may be set, and reflection restrictions may be performed on users who reach a negative level. Alternatively, the default level at the start of the community app may be set to 10, and restrictions may be imposed each time the level becomes lower than 10.

(Regarding favorable actions from users in a given situation)
In the above-described embodiment, an example in which the action contents such as the special action that can be taken according to the level described with reference to FIG. 19 change has been described. Instead of or in addition to this, it is also possible to make it possible for other users to recognize that the user is a high-level user. It is considered that a high-level user has a high tendency to take actions that make the atmosphere in the community positive and has a high degree of reliability. Therefore, the display mode of the content in which a favorable action (including a tap action or a favorable comment) has been performed by a high-level user (for example, level 90 or higher) may be changed. Alternatively, the display mode may be changed only when a favorable action is received from a plurality of users with high reliability (for example, a predetermined number such as five users). For example, the display mode of the content heading 60 in the home screen of FIG. 10, the content heading 70 in FIG. 11(A), or the mode of the number of tap actions 78 may be changed in color or a mark (for example, a special action 79, etc.) indicating that an action has been taken by a user with high reliability. Alternatively, a display that makes the comments stand out (higher display or color change) may be performed on the content screen illustrated in FIG. 13. In addition, when content that has received favorable actions from multiple highly reliable users or when there is a comment, a push notification or a notice may be displayed.

In addition, a user who has posted content or a comment that has received a favorable action from a highly trustworthy user may be notified that a highly trustworthy user has taken an action. For example, a push notification may be sent to the user device of the user in question, or a notification may be displayed within the app.

In the above embodiment, an example was described in which the content itself is hidden from the user terminal 300 of each of the multiple users, or the content posted by the restricted users is hidden from the user terminal 300 of each of the multiple users, for the content or comments themselves that are subject to restriction such as hiding or reporting from a predetermined number of users (e.g., 5 people) of level 70 or higher who are the target of the "report count" in FIG. 19, or for the users. The condition of the number of users in a predetermined situation (e.g., level 70 or higher) who have hidden or reported the content or comments themselves that are subject to restriction may be different between the restriction process of the content or comments themselves that are subject to restriction and the restriction process of the users who posted the content or comments that are subject to restriction. For example, a restriction process may be performed in which the content or comments that are subject to restriction are hidden from all users from a first number of users (e.g., 5 people) of level 70 or higher who are the target of the "report count", and a restriction process may be performed in which all content posted by the users who have been reported is hidden from all users for the users who have hidden or reported the posted content from a second number (e.g., 20 people) that is greater than the first number.

In addition, content or comments posted by a user who has accumulated a certain number of hidden or reported content by users with a level of 70 or higher, which is subject to the "report count," can be made hidden from all users. For example, content or comments posted by a user who has been hidden or reported by five users with a level of 70 or higher can be made hidden from all users.

Note that the users who are hidden may not include the user who posted the comment or content. This allows the user to know (be aware) that the content or comment they posted is subject to restriction, for example, by the lack of action from other users, even though the content or comment they posted is reflected on their own device.

(Notification of information related to evaluation history status)
In the above embodiment, an example was described in which each user can check their own "level" and "accumulated points" in the user evaluation history status 55 of the My Page exemplified in FIG. 8. However, the present invention is not limited to this, and the level and accumulated points, which are information related to the evaluation history status of the user, may be notified not only to the user himself or any other users, but may be checked only by the administrator on the administrator terminal 200 or the like. In this way, information related to the evaluation history status updated according to external evaluation is not notified to any users, but is notified to the administrator, so that the user's actions are not excessively suppressed, and the administrator can grasp the information related to the user's evaluation history status and use it for management. In addition, the user can use the fan community more comfortably without getting excited or depressed about his or her own "level".

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

(Regarding external evaluation)
In the above embodiment, an example was described in which the points of a user are reduced when an action such as a content or comment posted by a user is hidden or reported. In addition to this, for example, when hiding, a reason for hiding may be selected or input on a screen such as FIG. 11(B). A user may hide an action of another user due to personal reasons such as being a rival user, because the action may be hidden if it is not likely to have a negative impact on the community or to worsen public order. Therefore, a non-display that does not have a negative impact on the community may not affect the number of points of the user, and only a non-display that has a negative impact may affect the number of points. For example, the non-display options may be determined in advance as having an impact on points and not having an impact on points, and an administrator may check the reason for hiding and operate to affect the number of points for a non-display that is determined to have a negative impact.

In the above-described embodiment, an example was described in which a user's points fluctuate according to external evaluations such as tap actions or comments made on content or comments posted by the user. The number of posts of content posted by this user may be limited. For example, as an example of external evaluations that increase points, the number of views of a distributed video through content posted by the user and the profit contribution to the support target, such as the number of goods purchased, have been exemplified. However, since there is a risk that content will be posted in a profusion in an attempt to increase points, a limit may be imposed on content posting, such as once a day. Furthermore, for users with higher levels and higher trust, the upper limit on the number of content posts per day may be increased.

<Regarding reaction notification processing>
(For specific users)
In the above embodiment, the specific user who satisfies the specific condition for which the reflection of the reaction is suspended until the reflection condition is satisfied is a special user such as a celebrity in Fig. 5, and an example has been described in which the reaction of a user other than the special user is reflected regardless of whether the reflection condition is satisfied or not. However, without being limited to this, for example, even if it is a special user such as a celebrity or a user of a special account predetermined by the administrator, for example, a general user who satisfies a condition predetermined by the administrator (for example, a user with a predetermined number of friends or more, a user with a predetermined number of followers or more) may be regarded as a specific user, and a setting may be possible in which the reaction is not reflected until the reflection condition is satisfied.

(Actions that are reflected when the reflection conditions are met)
In the above embodiment, an example was described in which the action that is not reflected until the reflection condition is satisfied is a tap action or a reaction such as a comment that is a reply to the posted content. However, the present invention is not limited to this, and the action that is not reflected to other users until the reflection condition is satisfied may include content posted by the special user himself as a poster (such as an article that is the subject of a reaction and is assigned an article (post) ID as exemplified in the content database in FIG. 14). This makes it possible for the special user to delete content before it is seen by other users, even if the special user accidentally posts content.

(Regarding reactions that are reflected regardless of whether the reflection conditions are met)
In the above embodiment, an example has been described in which, when it is determined in step S608 of FIG. 29 that the reflection condition is satisfied, the reflection process is performed to make the information of the reaction made by the special user sharable to other users. However, the present invention is not limited to this. Regardless of whether the reflection condition is satisfied, the information of the reaction made by the special user may be subjected to the received information reflection process in steps S609 and S610 or notification information may be sent to the posting user by the operation of the special user. For example, the special user may perform a setting operation in advance to set the cancellation time not to be set or to set the screen for performing the confirmation operation to be hidden, so that the reaction operation is immediately reflected (shared) and notified, etc., in the same way as when a general user performs a reaction. Alternatively, when a cancellation time is set as a reflection condition, a checkbox or the like that allows an operation to allow immediate reflection without waiting for the cancellation time may be displayed on the comment posting screen when making a reaction, and when the distribution server 100 receives the posting information of a comment with the checkbox checked, the posting information may be immediately shared and notified to other users in the same way as a general user.

(Regarding the manner in which reactions are notified to the poster user)
In the above embodiment, the special action 79 is not limited to the notification to the posting user in step S610, but may also be sent to other users so that the special action 79 is displayed on the user terminals 300 of the other users. However, the present invention is not limited to this, and the special action 79 may be displayed only to the posting user. This can prevent a ranking of users in the community based on whether or not they have received a reaction from a special user. In addition, when a special user makes a reaction, the fact that there has been a reaction from users other than the posting user may be notified, but the notification mode for the posting user may be different from the notification mode for other users to provide a more special presentation. For example, the posting user may be given a push notification in a mode corresponding to the special user, such as a voice message.

(Reactions from general users)
In the above embodiment, an example has been described in which, when a reaction to a post is a reaction from a general user, default notification information is sent to the user terminal 300 of the posting user in step S604. However, this is not limiting, and when there is a reaction from a general user, the process of step S604 may not be performed. For example, in step S603, a reaction such as a comment from a general user may be shared with other users, but a push notification or the like may not be sent to the posting user.

In addition, when executing step S604 in FIG. 29, a push notification or the like may not be sent when the received information reflection process (when a reaction is shared with other users) is performed, but a notification pop-up or the like may be displayed, for example, when the user logs in, such as when the app is launched. In other words, while a notification may be sent in real time when a reaction from a special user becomes shareable, a notification may not be sent in real time when a reaction from a general user becomes shareable.

(Determining whether the reflection conditions are met on the user terminal side)
In the above embodiment, as illustrated in Fig. 28(B), an example has been described in which the reserved information of the special action is managed by the distribution server 100, but the invention is not limited to this, and the reserved information may be managed by the special user's user terminal 300. For example, the user terminal may determine whether a reflection condition is met, and if the reflection condition is met, the reserved reaction information may be transmitted to the distribution server 100, and the information received by the distribution server 100 may be reflected on a content screen or the like.

(Regarding the process of reflecting received information)
In the above-described embodiment, an example was described in which the received information reserved in the special action reserved data table in FIG. 28(B) is associated with the post (article) ID, etc., in the content data table in FIG. 28(A), FIG. 14, etc., when the reflection condition is satisfied, thereby displaying or notifying that a special action has been performed. However, the present invention is not limited to this, and the information may be shared with other users depending on whether the reflection flag is set to on or off in the content data table. For example, when reaction information is received from a special user, the received information may be associated with the content data table in FIG. 14, etc., for each post ID, the reflection flag may be set to off, and the reflection flag may be set to on and shared with other users when the reflection condition is satisfied. In addition, as the non-reflection process in step S607 in FIG. 29, for example, a process may be performed in which the corresponding reaction-related information associated with the reflection flag in the off state in the data table for each posted content in FIG. 14 or FIG. 28(A) is deleted. In addition, the received information reflection process in step S608 may be, for example, to share the received information with other users by turning on the reflection flag of the corresponding reaction-related information that was associated with the reflected flag in the data table for each posted content in Figure 14 or Figure 28 (A) when the reflection flag was off.

<About language association processing>
(Posts that are displayed regardless of the language specified)
In the above-described embodiment, an example has been described with reference to Figures 30, 34, etc., in which language information associated with each post is extracted and the narrowed-down content is displayed. The posted content that can be displayed in a list may include posts that are not excluded even when narrowed down by selecting (specifying) the display language. For example, with respect to posted content posted by a special user such as a talent who is the target of support in the community, as described with reference to Figure 5, etc., the posted content may be displayed regardless of what language is associated with the posted content or what language is specified by the user.

In addition, posts other than those of special users may be displayed under certain circumstances regardless of the language associated with them. For example, new posted content posted within the last 24 hours may be displayed regardless of the language information associated with it.

(Combined with automatic language detection)
In the above-mentioned embodiment, an example in which a preset default language is associated at the time of posting has been described with reference to FIG. 32, FIG. 35, etc. However, the present invention is not limited to this, and the language of the input text may be determined by automatic determination by AI, and the determined language may be associated, and a suggestion of a language to be associated may be made to the user. In this case, even if the language is determined automatically and the language is automatically selected, the language may be changed to an intended language by a user's operation. For example, if emoticons contain characters used in a language other than the originally intended language, a language other than the intended language may be associated (for example, an emoticon used by a Japanese-speaking user contains characters used in Russian). Note that even if information other than text, such as an image, is associated with the posted information, the language may be determined from characters contained in the image, etc.

Also, the automatic language determination by AI may be used to allow management so that users whose posted content information contains a language different from the associated language information can be identified in the distribution server 100. For example, it becomes easier to identify and deal with users who have maliciously posted content information in a language different from the associated language.

(Regarding data of content posted with the same purpose under the same account)
In the above embodiment, in the example of content data in FIG. 33, the content 70d1 in FIG. 30(A) and the content 70d2 in FIG. 30(B) are posted from the same official account with similar contents in text in different languages, and are managed as different article IDs such as post (article) IDs "a20" and "a21", and different language information, Japanese and English, is associated with each of them. However, the data management method is not limited to this. For example, the data may be managed as one post ID "a20", and both post content information associated with Japanese language information (e.g., mainly including Japanese text and Japanese images) and post content information associated with English language information (e.g., mainly including English text and English images) are associated with the "a20", and the post content information associated with the selected language information may be displayed according to a user's operation to select (specify) a display language. Also, when a specification is made to display all languages, a post in one of the post IDs "a20" associated with the two posts may be preferentially displayed. For example, if the app display language is set to English, posts in English may be displayed preferentially.

[Software implementation example]
The various control blocks of the control unit of a computer such as a server or a terminal in the above-mentioned 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, the computer equipped with the control unit includes a CPU that executes instructions of a program, which is software that realizes each function, a ROM (Read Only Memory) or storage device (these are referred to as "recording medium") in which the program and various data are recorded so as to be readable by the computer (or CPU), and a RAM (Random Access Memory) in which the program is expanded. The object of the present invention is achieved by the computer (or CPU) reading and executing the program from the recording medium. As the recording medium, a "non-transient tangible medium", for example, a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, etc. can be used. The program may also 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 may also be realized in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission.

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

1 Communication system, 2 Network, 100 Distribution server, 200 Administrator terminal, 300 User terminal, 400 External web service system

Claims (11)

A program for causing a computer to execute a process for accepting a post including a message and sharing the message among a plurality of users,
The computer,
A means for accepting submissions in any of a plurality of languages;
A means to associate a language variant with a post;
means for transmitting posted information to an external device to enable identification of the type of posted information and associated language;
functioning as a means for receiving post list information from an external device and displaying a list of posts;
The post list information includes information for identifying the content of the post and the type of language associated with each post,
The means for displaying the list of posts is a program for displaying a list of posts that are narrowed down to posts associated with a language type specified by a user from among a plurality of languages. The computer,
The program according to claim 1 , further comprising: a means for displaying, when a post is entered, information capable of identifying a type of language associated with the post. The program according to claim 1, wherein the means for displaying the list of posts displays information that can identify the type of language being narrowed down together with the list of posts. The program according to claim 1, wherein the means for associating the language type with the post associates the language type according to an operation by a user. The program according to claim 1, wherein the means for associating the language type with the post pre-sets a predetermined language type as a candidate for association, and can change the association to another language type in response to a change operation by the user. The computer,
a means for allowing a user to set in advance the types of languages available to the user when executing the process for sharing the language in response to an operation by the user;
the predetermined language type set as a candidate to be associated by the means for associating the language type with the post is a language type that is preset by the setting means,
The program according to claim 5 , wherein the means for associating the language type with the post is capable of associating another language type with the post in response to an operation by a user. The computer,
Serve as a means to identify the type of language used in the messages contained in the posts;
the predetermined language type set as a candidate is a language type identified by the language type identifying means,
The program according to claim 5 , wherein the means for associating the language type with the post is capable of associating another language type with the post in response to an operation by a user. The computer,
a means for allowing a user to set in advance the types of languages available to the user when executing the process for sharing the language in response to an operation by the user;
The program according to claim 1, wherein the means for displaying the list of posts is capable of narrowing down and displaying the list of posts associated with a language type that has been preset by the setting means, and then switching the list to display posts associated with other language types specified by the user. The program according to claim 1, wherein the means for displaying the list of posts displays a list of posts that satisfy a specific condition regardless of the type of language specified by the user. 1. A method for controlling a computer that executes a process for accepting a post including a message and sharing the message among a plurality of users, comprising:
accepting submissions in any of a plurality of languages;
Associating a language variant with the post;
transmitting post information to an external device to enable identification of the received post and associated language type;
receiving post list information from an external device and displaying a list of posts;
The post list information includes information for identifying the content of the post and the type of language associated with each post,
The step of displaying the list of posts comprises displaying a list of posts that are narrowed down to posts associated with a language type specified by a user from among a plurality of languages. A system having a computer that executes a process for accepting a post including a message and sharing the post among a plurality of users,
A means for accepting submissions in any of a plurality of languages;
A means to associate a language variant with a post;
means for transmitting posted information to an external device to enable identification of the type of posted information and associated language;
means for receiving post list information from an external device and displaying a list of posts;
The post list information includes information for identifying the content of the post and the type of language associated with each post,
The means for displaying the list of posts is a system that displays a list of posts that are narrowed down to those associated with a language type specified by a user from among a plurality of languages.

Images