Program, method, and system

Abstract

Provided are a program, a method, and a system that enable communication with other users according to the language type. 【Solution means】By a program for causing a computer to execute sharing processing for receiving a post including a message and sharing it among a plurality of users, it is possible to receive a post in any of a plurality of types of languages, associate the language type with the post, and transmit post information for identifying the received post and the associated language type to an external device, and receive post list information from the external device and 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 filters and displays a list of posts associated with the language type specified by the user from among the plurality of types of languages.

Description

Technical Field

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

Background Art

[0002] In recent SNSs and the like, it is possible to communicate with overseas users who use other languages. For example, even comments posted in a language different from the set language such as the OS can be converted into the language used by the user in daily life by machine translation or the like and viewed (see, for example, Non-Patent Document 1). In addition, in order to facilitate smooth communication with overseas users, comments etc. may be posted in a language different from the language used in daily life.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, as described above, although it is possible to communicate with overseas users who handle other languages even in conventional SNSs and the like, due to the mixture of various languages and comments, even if a comment targeted at a user group handling a specific language (for example, a topic in a region handling a specific language) is posted, it may be buried and there is a risk that it will not reach the user group that the posting user originally targets.

[0005] The present invention has been conceived in view of such circumstances, and provides a program, method, and system that enable communication with other users according to the type of language.

Means for Solving the Problems

[0006] (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 (e.g., a process of acquiring posted content associated with a content data table such as FIG. 14 by information acquisition unit 351 and displaying it on the display unit of user terminal 300 by display control unit 352, etc.) for receiving a post including a message (e.g., text, image, etc.) and sharing it among a plurality of users, said computer being caused to have means for receiving posts in any of a plurality of types of languages (e.g., display a post screen such as FIG. 32 and be able to receive text input in any language, such as display control unit 352, input unit 330, etc.), have means for associating the type of language with the post (e.g., steps S321, S325 in FIG. 35), have means for transmitting posting information (e.g., posting information including a poster ID, posting date and time, posting content information, language information, etc. associated with a content data table such as FIG. 33) for identifying the received post and the associated type of language to an external device (e.g., distribution server 100, etc.) (e.g., in step S313 of FIGS. 35 and 18, the input information transmission unit 353 transmits the posting information to the distribution server 100), function as means for receiving posting list information (e.g., information for displaying a list of posted content such as FIGS. 30, 10, 11, etc.) from an external device and displaying a list of posts (e.g., a list screen of posted content such as FIGS. 30, 10, 11, etc.) (e.g., steps S702, S706 in FIG. 34, information acquisition unit 351, display control unit 352, etc.), The submission list information includes information for specifying the content of the submission (e.g., the submission content information such as text or image in FIG. 33) and the type of language associated with each submission (e.g., the language information associated with each submission in FIG. 33). The means for displaying the list of submissions filters and displays in a list the submissions associated with the type of language specified by the user from among multiple types of languages (e.g., the language specified by an operation on the language switch icon LS displayed on the list screen of submission contents in FIG. 30, or the language specified by the default setting by user operations in the initial settings or my page in FIG. 31, etc.). (For example, as shown in FIG. 30, the submission contents associated with the language information of the language specified by the user and displayed on the language switch icon LS are displayed in a list, steps S702, S706 in FIG. 34, etc.).

[0007] According to such a configuration, it is possible to submit in any of multiple types of languages, and since it is possible to filter and display in a list the submissions associated with the type of language specified by the user, it becomes possible to communicate with other users according to the language.

[0008] (2) In the above (1), cause the computer to function as means for displaying information that can specify the type of language associated with the submission when inputting the submission (e.g., displaying the language switch icon LS on the submission screen in FIG. 32 where the currently associated language is shown, the display control unit 352, etc.).

[0009] According to such a configuration, since the type of language associated with the submission can be specified at the time of submission, it becomes easier for the user to confirm the type of language associated with the submission.

[0010] (3) In the above (1), the means for displaying the list of submissions displays information that can specify the type of language being filtered together with the list of submissions (e.g., the language switch icon LS that displays the currently filtered language in FIG. 30, etc.).

[0011] According to such a configuration, it becomes easier to check the type of language specified by the user.

[0012] (4) In the above (1), the means for associating the type of language with the post associates the type of language according to an operation by the user (for example, the type of default language selected by a user operation at the initial setting in FIG. 31, from the my page, etc., or the type of language selected by operating the language switching icon LS as shown in FIG. 32(B), etc., steps S321, S325, etc. in FIG. 35).

[0013] According to such a configuration, it becomes possible to associate the type of language intended by the user and achieve communication.

[0014] (5) In the above (1), the means for associating the type of language with the post preliminarily sets a predetermined type of language 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 type of default language), and can be changed to another type of language according to a change operation by the user and associated (for example, an operation to change from the initially set language to another type of language like the push notification language in FIG. 31, or an operation to change the type of default language from the my page, etc., or an operation to change to a type of language different from the default language as shown in FIG. 32(B), etc., and it is possible to associate and post a different type of language from the default, steps S322 to S325 in FIG. 35).

[0015] According to such a configuration, while simplifying the operation for association, the type of language to be associated can be changed as necessary, thus improving the convenience for the user.

[0016] (6) In the above (5), the computer is Means (such as, for example, at the time of initial setting in FIG. 31, the app display language set by the user from the my page or the like, the default setting operation of the type of display language such as the language of the content to be displayed and the language of the post, the storage unit 320, the control unit 350, etc.) that can be preset according to the operation from the user the type of language that is available to the user when executing the process for sharing, The type of predetermined language set as a candidate for association by the means for associating the type of language with the post (for example, the type of language displayed in the language switch icon LS displayed as the language of the post when the post screen in FIG. 32 is displayed) is the type of language preset by the means that can be set, The means for associating the type of language with the post can associate other types of languages with the post according to the operation from the user (for example, an operation to switch the type of language from the default Japanese to English based on an operation on the language switch icon LS on the post screen in FIG. 32(B), steps S322 to S325 in FIG. 35, etc.).

[0017] According to such a configuration, it is possible to preset the type of language associated with the post according to the user operation, and it is also possible to associate a type of language different from the preset type of language according to the user operation. As a result, the user can associate the type of language according to the content of the post, thus improving the convenience for the user.

[0018] (7) In the above (5), cause the computer to Function as means for identifying the type of language used in the message included in the post (for example, identifying the type of language of the text input on the post screen by automatic determination by AI, the control unit 350), The type of predetermined language set as a candidate is the type of language identified by the means for identifying the type of language, The means for associating the type of language with a post can associate other types of language with a post according to an operation by the user (for example, it is possible to display the type of language specified by automatic determination as the language of the post in FIG. 32(A) on the language switch icon LS; refer to the modification example (in combination with automatic language determination)).

[0019] According to such a configuration, since the type of language is specified based on the information included in the actual post, it facilitates the association of the type of language, and also enables the association of other types of language according to the user's wish, so that the language intended by the user can be associated.

[0020] (8) In the above (1), the computer is configured to be able to preset, according to an operation by the user, the types of languages that the user can use when executing the process for sharing (for example, at the time of initial setting in FIG. 31, the application display language set by the user from the my page or the like, the default setting operation of the type of display language such as the language of the content or post to be displayed, the storage unit 320, the control unit 350, etc.), the means for displaying the list of posts, after narrowing down and displaying in a list the posts associated with the type of language preset by the means that can be set, can narrow down and switch the display of the list of posts associated with other types of language specified by the user (for example, if the default type of language is set to Japanese, a list screen of post contents associated with Japanese as the language information in FIG. 30(A) is displayed, and an operation is performed on the language switch icon LS and English is selected, then a list of post contents associated with English as the language information is displayed as in FIG. 30(B); steps S702 to S706 in FIG. 34).

[0021] According to such a configuration, it is possible to switch between the default type of language and a type of language different from the default according to an operation by the user and display the posts, so that it enables the user to communicate based on the type of language desired according to the situation.

[0022] (9) In the above (1), for the means of displaying the list of the posts, for posts that satisfy specific conditions (for example, post contents posted by special users such as talents, or post contents under predetermined circumstances such as within 24 hours after posting), regardless of the type of language specified by the user, they are displayed in a list (for example, refer to (posts displayed regardless of the specified language) in the modified example).

[0023] According to such a configuration, for posts that satisfy specific conditions, they are displayed without being excluded by filtering, so it is possible to reduce the possibility that useful information for the user will not be displayed due to filtering.

[0024] (10) A method according to an aspect of the present invention is a method for controlling a computer (for example, a user terminal 300) that executes processing (for example, processing for acquiring post contents associated with a content data table such as FIG. 14 by an information acquisition unit 351 and displaying them on a display unit of the user terminal 300 by a display control unit 352, etc.) for receiving a post including a message (for example, text, image, etc.) and sharing it among a plurality of users, a step of enabling reception of posts in any of a plurality of types of languages (for example, displaying a post screen such as FIG. 32 and enabling reception of text input in any language), a step of associating the type of language with the post (for example, steps S321 and S325 in FIG. 35), a step of transmitting post information (for example, post information including a poster ID, a posting date and time, post content information, language information, etc. associated with a content data table such as FIG. 33) for identifying the received post and the associated type of language to an external device (for example, a distribution server 100, etc.) (for example, in step S313 of FIGS. 35 and 18, the input information transmission unit 353 transmits the post information to the distribution server 100), Receiving submission list information (for example, information for displaying a list of submission contents such as FIGS. 30, 10, and 11) from an external device and displaying a submission list (for example, a list screen of submission contents such as FIGS. 30, 10, and 11) (for example, steps S702 and S706 in FIG. 34). The submission list information includes information for specifying the content of the submission (for example, the submission content information in FIG. 33 such as text or an image) and the type of language associated with each submission (for example, the language information associated with each submission in FIG. 33). The step of displaying the submission list filters and displays a list of submissions associated with the type of language specified by the user from among a plurality of types of languages (for example, the language specified by an operation on the language switching icon LS displayed on the list screen of the submission contents in FIG. 30, or the language specified by the default setting by the user operation in the initial setting or the my page such as FIG. 31) (for example, as shown in FIG. 30, a list of submission contents associated with the language information of the language specified by the user displayed on the language switching icon LS, steps S702 and S706 in FIG. 34, etc.).

[0025] According to such a configuration, it is possible to submit in any of a plurality of types of languages, and it is possible to filter and display a list of submissions associated with the type of language specified by the user, so that it is possible to communicate with other users according to the language.

[0026] (11) A system according to an aspect of the present invention is a system (for example, a communication system 1) having a computer (for example, a user terminal 300) that executes processing for receiving a submission including a message (for example, text or an image) and sharing it among a plurality of users (for example, processing for acquiring submission contents associated with a content data table such as FIG. 14 by an information acquisition unit 351 and displaying them on a display unit of the user terminal 300 by a display control unit 352, etc.). Means for accepting submissions in any of multiple languages (for example, a display control unit 352, an input unit 330, etc. that display a submission screen such as Figure 32 and can accept text input in any language), Means for associating the type of language with the submission (for example, steps S321 and S325 in Figure 35), Means for transmitting submission information (for example, submission information including a submitter ID, submission date and time, submission content information, language information, etc. associated with a content data table such as Figure 33) for identifying the received submission and the associated type of language to an external device (for example, a distribution server 100, etc.) (for example, in step S313 of Figures 35 and 18, the input information transmission unit 353 transmits the submission information to the distribution server 100), Means for receiving submission list information (for example, information for displaying a list of submission contents such as Figures 30, 10, and 11) from an external device and displaying a list of submissions (for example, a list screen of submission contents such as Figures 30, 10, and 11) (for example, steps S702 and S706 in Figure 34, an information acquisition unit 351, a display control unit 352, etc.), The submission list information includes information for identifying the content of the submission (for example, the submission content information in Figure 33 such as text or an image) and the type of language associated with each submission (for example, the language information associated with each submission in Figure 33), The means for displaying the list of submissions filters and displays in a list the submissions associated with the type of language specified by the user from among the multiple types of languages (for example, the language specified by an operation on a language switch icon LS displayed on the list screen of submission contents in Figure 30, or the language specified by the default setting by a user operation in the initial settings or my page such as Figure 31) (for example, as shown in Figure 30, displays in a list the submission contents associated with the language information of the language specified by the user displayed on the language switch icon LS, steps S702 and S706 in Figure 34, etc.).

[0027] According to such a configuration, it is possible to post in any of multiple types of languages, and it is also possible to narrow down and display a list of posts associated with the language type specified by the user, thus enabling communication with other users according to the language.

Brief Description of Drawings

[0028]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Embodiments for Carrying Out the Invention

[0029] Hereinafter, embodiments of a communication system according to the present invention will be described with reference to the drawings. It should be noted that the present invention is not limited to the following examples, but is defined by the claims, and all modifications within the meaning and scope equivalent to the claims are intended to be included in the present invention. In the following description, the same reference numerals are given to the same elements in the description of the drawings, and duplicate descriptions will not be repeated.

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

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

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

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

[0034] In addition, the distribution server 100, the administrator terminal 200, and the user terminal 300 can be communicatively connected to an external web service system 400 via the network 2. The external web service system 400 is, for example, a sharing service (such as Youtube (registered trademark)) for videos, texts, images, etc. by user submissions, and provides information (such as texts, images, videos, posting dates, account names, etc.) according to access from other terminals such as the distribution server 100, the administrator terminal 200, and the user terminal 300 to the terminal. The external web service system 400 is a system operated and managed by a third party different from the administrator and operator of this communication system 1.

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

[0036] The contents provided by the distribution server 100 are managed and set for each type as will be described later with reference to FIG. 14. The content is something that notifies a viewer of predetermined information and includes the content of information such as videos, voices, and texts. The contents managed by the distribution server 100 are, for example, news and notice articles by an operator (administrator), user submissions (including comments), and distribution videos provided by an external web service obtained by using a Web API. The content can be provided to the user by being displayed on the user terminal 300 via a medium such as a browser or a dedicated application for a smartphone. In addition, the medium through which the content is provided also functions as a fan community that supports a predetermined support target.

[0037] The distribution server 100 stores in the storage unit 120 information such as text and images corresponding to the content that can be provided to the user, and sound information for outputting sound for displaying on the user terminal. Further, the distribution server 100 provides the user with content (service) by distributing content data including display information for displaying text, images, etc. of the corresponding content and sound information for outputting sound in response to an access from the user terminal 300.

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

[0039] In the present embodiment, the distribution server 100 and the administrator terminal 200 are each an independent computer (device), but they may be realized by one computer, or the function of one of these computers (for example, the distribution server 100) may be realized by a plurality of computers (for example, a plurality of servers).

[0040] The user terminal 300 is used by a user who views and experiences content. The user terminal 300 may be, for example, a computer having an operation input function and a communication function such as a personal computer, a tablet terminal, or a smartphone.

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

[0042] Furthermore, the user terminal 300 accepts action operations on the displayed content and content posting operations by the user himself / herself. The user terminal 300 can transmit information corresponding to the operation on the terminal (for example, information for identifying the action or the posted content) to the distribution server 100 and reflect the action or the posted content on a plurality of user terminals via the distribution server 100. The action operations include, for example, tap actions (such as a 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 of a reply comment. Hereinafter, actions by users, such as content posting operations by the users themselves, are collectively referred to as "actions." Furthermore, tap actions by users and favorable comments are also referred to as "like actions."

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

[0044] Note that a special user may be a general user who browses etc. the content distributed using a terminal having the same configuration as the user terminal 300, or may be a general user using a separate terminal having a configuration different from that of the user terminal 300. Therefore, the user terminal used by the special user and the user terminal 300 used by the general user may be terminals having the same configuration as each other or may be different terminals.

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

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

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

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

[0049] Hereinafter, the functional configuration of the control unit 130 will be described. 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.

[0050] 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 regarding content managed by the content management unit 132, various notifications, and the like.

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

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

[0053] <Configuration of the Administrator Terminal> Next, the configuration of the administrator terminal 200 will be described. As shown in FIG. 3, the administrator terminal 200 includes a communication unit 210 that communicates with other computers, a storage unit 220 that stores various data, an input unit 230 for inputting operations and the like, an output unit 240 for outputting images, sounds, 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 interconnected by a bus line.

[0054] The communication unit 210 is a communication interface equipped with a NIC for performing 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 (for example, a program for managing content provided to the user by the distribution server 100), various data, etc.

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

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

[0057] Hereinafter, the functional configuration of the control unit 250 will be described. The control unit 250 functions at least as a content setting unit 251, an attribute setting unit 252, an action authority setting unit 253, and a user evaluation information update unit 254.

[0058] The content setting unit 251 stores and updates information regarding the content managed by the content management unit 132 of the distribution server 100 in response to an operation on the administrator terminal 200. Thereby, for example, information for specifying the content, category classification regarding the content, settings and edits regarding the effects when the content is provided, etc. can be stored and updated in the storage unit 120 of the distribution server 100.

[0059] The attribute setting unit 252 is configured to store and update attribute information related to attributes stored as the attribute information 121 of the distribution server 100 in response to an operation on the administrator terminal 200. Thereby, for example, when a new attribute is added or the composition of the attributes is changed, the storage unit 120 can store and update the information related to the attributes.

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

[0061] The user evaluation information update unit 254 can perform external evaluations on users that can affect the evaluation history status for each user stored as the account information 125 of the distribution server 100, or store and update the evaluation history status itself for each user, in response to an operation on the administrator terminal 200. Thereby, the evaluation history status for each user is changed by the evaluation from the operator, and the actions (actions) that the user can take based on the action permission information 124 are controlled.

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

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

[0064] The input unit 330 includes input devices (for example, pointing devices such as touch panels, touch pads, mice, etc., keyboards, microphones, etc.) for receiving input operations and voices from the user.

[0065] The output unit 340 includes output devices (displays, speakers, etc.) for presenting and outputting information (text, images, voices, 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 storage unit 320.

[0066] Hereinafter, the functional configuration of the control unit 350 will be described. The control unit 350 functions as an information acquisition unit 351, a display control unit 352, an input information transmission unit 353, and a user management unit 354.

[0067] The information acquisition unit 351 acquires content data, etc. from the distribution server 100 via the communication unit 310, and stores in the storage unit 320 information for displaying text and images (messages included in the posting information) related to the content based on the content data. The posting information includes information for causing the user terminal 300 to display actions performed on other user terminals 300 with respect to the content.

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

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

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

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

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

[0073] The support target in this embodiment can be applied to various targets such as characters and objects as long as the user can have affection, interest, concern, etc. For example, the character includes real people such as talents and famous people (3D), and fictional existences such as anime characters and mascot characters (2D, 2.5D). In addition, the support target includes objects such as railways and animals.

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

[0075] As a unit (attribute) for which a user who uses a fan community supports, there may be cases where the user supports not only one talent but also a plurality of talents, a small group (unit) unit, or a large group unit. For example, supporting (becoming a fan) in a large group unit is also called so-called box pushing. In the fan community in this embodiment, the user can set (select) in advance the target to be supported by the user for each preferred unit (each attribute).

[0076] Referring to FIG. 5, an example of the talent information database stored as the attribute information 121 in this embodiment will be used to describe the talents in the fan community in this embodiment. In this embodiment, talents are classified into groups classified as "affiliated group 1". Affiliated group 1 is a large group and is classified into, for example, group A, group B, and the like.

[0077] For each affiliated group 1, "talent ID", "talent name", etc. are associated as information for identifying the talents belonging to the group. Further, for each talent, information for identifying the "affiliated group 2" to which each talent belongs is associated. Affiliated group 2 is a small group composed of a smaller number of people than affiliated group 1. For example, it is "first-generation students", "second-generation students", etc. classified in units of the time of joining the group, or a group composed of a predetermined concept (for example, "Gamers" composed of talents mainly engaged in live game broadcasts).

[0078] Regarding the affiliated group, some talents may belong to multiple affiliated groups. Also, there may be talents who belong to affiliated group 1 but do not belong to any affiliated group 2. Additionally, there may be an affiliated group 2 composed of talents belonging to different affiliated groups 1 (spanning different affiliated groups 1. For example, group A and group B, etc.).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0100] Return to step S107. When it is determined that the selection of the participating community or the favorite talent has not been made, it is determined whether the selection to return is made in step S109. For example, on the attribute selection screen of FIG. 6, a return icon 10 is displayed, and it is determined whether there is a selection operation for the return icon 10. When it is determined that there is a selection operation for the return icon 10, the process ends. Alternatively, the process may end by moving to another screen by operating the home icon 13 or the like displayed at the bottom of the application. On the other hand, when it is not determined in step S107 that the selection to return is made, return to step S107.

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

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

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

[0104] Also, the home icon 13, community icon 14, notification icon 15, and my page icon 16 displayed at the bottom of the app may be displayed on any screen within the app, or may be hidden on a predetermined screen (for example, when the content is displayed as in FIG. 13). The home icon 13 is an icon for displaying the home screen of FIG. 10 when a selection operation is performed, and the community icon 14 is an icon for displaying a screen for each community such as FIG. 11(A) described later when a selection operation is performed. The notification icon 15 is an icon for displaying a screen where various notifications can be confirmed, such as when there is a post related to the selected attribute (for example, the talent set by the user as the favorite talent), a reply comment to the user's own post, or a mention to the user. The my page icon 16 is an icon for displaying the my page illustrated in FIG. 8 when a selection operation is performed.

[0105] (Overview of the Home Screen) At the upper part of the home screen in Fig. 10, a favorite filter 20, a language switch icon LS, etc. are displayed. The favorite filter 20 is a filter icon that can narrow down the list of content headings to be displayed so that only the headings of the content associated with the favorite talents preselected by the user are displayed. For details, refer to Figs. 15, 16, etc. which will be described later. The language switch icon LS is an icon that enables the content to be displayed according to the language information by switching the language information associated with the content, for example, from Japanese to English, etc., when a selection operation is performed. Note that the currently selected language as the display language may be displayed on the language switch icon LS.

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

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

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

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

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

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

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

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

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

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

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

[0117] When the report icon 72 is selected, a screen as shown in Fig. 11(B) is displayed (for example, pop-up displayed on the current screen). By selecting the characters displayed in Fig. 11(B), the user can, for example, report content that makes the user feel uncomfortable to the operator, hide it on the user terminal 300, or block the content contributor itself within the fan community app (prevent actions such as posts by the blocked user from being displayed on the user's own user terminal 300 after the operation). Note that operations such as hiding and blocking cannot be performed on content contributed by operators or special users, and may be operations that can only be performed on other general users.

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

[0119] The content information 74 displays the title of the posted content of the content and a part of the description text.

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

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

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

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

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

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

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

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

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

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

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

[0131] 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 the content database of "Community A". The content database stores information such as "channels", "posting permissions" for each channel, and "article IDs" for each piece of content.

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

[0133] "Posting permission" is information about users who have the right to post content in each "channel". For example, for the "Official Channel" and "Past Recommendations", only official accounts (such as special users like operators or talents) can post. Posts from official accounts can be made using, for example, a user ID that can be identified as an official account, whether it is a post from the administrator terminal 200 or a terminal with the same configuration as the user terminal 300. Also, for "Group A Chat" and "Clip", all users can post. For example, in the channel list 82 in Figure 12, official marks are displayed for channels where only official accounts can post, and speech bubble marks or the like are displayed for channels where all users can post. This allows users to easily identify whether a channel allows posting or not.

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

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

[0136] "Poster ID" is an ID that identifies the poster of the content.

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

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

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

[0140] In this way, related talents can be associated with the content. Therefore, if the related talents include the user's favorite talent selected in advance, the distribution server 100 can notify the user of a post related to the favorite talent by push notification based on the information in the user information database stored as the account information 125. For example, when there is a post of content in which the favorite talent is associated with the related talent, or every time a predetermined time elapses (for example, every 5 minutes, every 15 minutes, etc.), the user is pushed a notification that there is a post of content in which the favorite talent is associated with the related talent. When a push notification is received, by operating on the push notification from the user, it is possible to transition to the content screen (such as FIG. 13) of the content associated with the favorite talent. When there is a post of content in which the favorite talent is associated with the related talent means 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).

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

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

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

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

[0145] Also, in the favorite topic 62, a predetermined number of pieces of content associated with a pre-selected favorite talent exemplified by the user in FIGS. 6, 9, etc. among the content posted within the community the user participates in are displayed. For example, in the favorite topic 62 of a user who participates in "Community A" and has selected the talent "AAA" as the favorite talent, among the content stored in the content database of Community A in FIG. 14, the content associated with the talent ID "t1" corresponding to the talent "AAA" is extracted and displayed.

[0146] Among the popular user posts 63, a predetermined number of the contents posted by general users other than the official accounts of the communities the users belong to, which are considered popular, are displayed. For example, they may be in the order of the most frequent like actions (tap actions and / or comments), or in the order of the highest engagement rate (such as contents with a high ratio of like actions to the number of views).

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

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

[0149] Also, 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 it may be such that if it is displayed in the recommended topic 62, it is not displayed in the content headings 60 of other categories. Note that the recommended topic 62 is not displayed for users who have not selected any talent as a recommended talent in advance.

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

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

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

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

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

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

[0156] In step S201, it is determined whether there has been a content display request operation from the user terminal 300. The display request operation includes an operation for causing the user terminal 300 to read display data, and a selection operation for turning the recommended filter 20 on or off when a predetermined condition is satisfied. The operation for causing the user terminal 300 to read display data includes, for example, logging in to the application (inquiring to the server at the timing of opening the application), a reload operation (re-reading operation), or a selection operation for the home icon 13 of the application screen, the community icon 14, or the channels displayed in the channel list 82 of FIG. 12. The satisfaction of the predetermined condition is, for example, that the user taps the icon of the recommended filter 20 displayed on the user terminal 300 to switch it.

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

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

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

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

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

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

[0163] Note that even if the favorite filter 20 is not in the on state (regardless of whether the favorite filter is on or off), the related talent 88 can be displayed on the home screen of FIG. 10, the community screen of FIG. 11(A), or the content screen itself of FIG. 13. Therefore, even without individually setting the favorite talent, the user can recognize who in the group is associated with the content, and the interest will be improved.

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

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

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

[0167] (Regarding the flow of user posting process) Next, with reference to FIG. 18, the flow of the user posting process when the user posts content will be described. 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.

[0168] In step S301, it is determined whether a post icon has been selected. For example, it is determined whether a selection operation has been performed on the post icon 23 on the content screen such as FIG. 11(A). When it is determined that the post icon 23 has not been selected, the process ends. On the other hand, when it is determined that the post icon 23 has been selected, in step S302, it is determined whether the channel to which the post is to be made is a channel in which user posting is permitted. For example, for the channels "Group A Chat" and "Clip" in FIG. 14, posting is permitted for all users, so in step S303, the post screen of FIG. 17(A) is displayed. Thereby, for example, input of character information and attachment of an image by operating the image icon 37 can be performed.

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

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

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

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

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

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

[0175] When 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 there has been a posting confirmation operation. For example, it is determined whether there is a selection operation for the post icon 41 in FIG. 17(B). When it is determined in step S312 that there has been a posting confirmation operation, the posting information (for example, information specifying the input character information, attached image information, selected category, selected related talent, ID of the poster, etc.) is sent to the distribution server 100 for processing. Thereby, for example, in "Group A Chat", when the category "Event" is selected and the related talent "DDD" is selected, it is stored in the distribution server 100 as the article ID "a4" illustrated in FIG. 14.

[0176] Returning to step S312, when it is not determined that there has been a posting confirmation operation, it is determined in step S314 whether a close selection has been made. The close selection is, for example, a selection operation for the close icon 35 on the screen in FIG. 17(B). When it is determined in step S314 that the close selection has been made, the process ends.

[0177] On the other hand, when it is not determined that "close" is selected in step S314, it is determined whether "return" is selected in step S315. For example, it is a selection operation for the "return" icon 36 in FIG. 17(B). In step S315, when it is determined that "return" is selected, the process returns to step S303, and the display returns to the character input posting screen in FIG. 17(A). Thereby, it is possible to re-edit the characters and image information input on the posting screen before the selection of "next" in step S304. On the other hand, when it is not determined that "return" is selected in step S315, in step S307, the category selection screen or the like is continuously displayed. Although an example in which the user posting process is executed on the user terminal 300 has been described, it may be executed on the distribution server 100 and the display information may be transmitted to the user terminal 300.

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

[0179] (Overview of User Level Changes) 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" varies according to the "cumulative points". The "cumulative points" vary according to the external evaluation described later. For example, if the initial setting has the user level at 1 and the cumulative points reach 10, the level becomes 2. To go from level 2 to level 3, a larger number of points than the number of points required to go from level 1 to 2 is needed. For example, when the cumulative points reach 21, the level becomes 3. Thus, as the level rises, the number of points required increases, making it more difficult to increase the level. Also, since the "cumulative points" may decrease according to the external evaluation, for example, when the cumulative points of a user at level 2 drop below 20, the level drops from 2 to 1.

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

[0181] (Actions Available by Level) Referring to FIGS. 19, 20, and 21, the actions that can be taken according to the user level in this embodiment will be described. FIG. 19 is a table showing examples of the action contents permitted (obtainable) according to the level. For example, it is divided into levels "1 to 49", "50 to 59", "60 to 69", "70 to 79", "80 to 89", "90 to 99", and "100". The actions permitted for each level are stored as the action permission information 124 of the distribution server 100 and the like.

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

[0183] "Creating a plan" is the right to start a plan (event) within a community, and can be created by users with a level of 80 or higher. For example, it is possible to start an event plan such as a so-called offline meeting where people gather in a real or virtual space at a predetermined date and time, or a questionnaire plan. That is, it becomes possible to take actions as a leader. Also, users with a level of 79 or lower can participate in the plans created by users with a level of 80 or higher.

[0184] "Moderator invitation" means becoming able to serve as an administrator of the content posted within the community, which can be achieved by becoming a user with a level of 90 or higher. For example, it involves tasks usually performed by an operator, such as deleting inappropriate posted content or comments by visual inspection, and setting them to non-display (also referred to as restriction). It may also be the authority to take measures to suspend accounts of malicious users, etc. (for example, for a certain period). Content restricted by a user with a level of 90 or higher will not be displayed on the user terminal 300 of users with a level of 89 or lower either.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0206] In step S402, when it is determined that the external evaluation is a "point increase" evaluation, in step S403, the number of points is added for each user according to the external evaluation, and the evaluation history status is updated and stored. For example, assume a user at level 59 reaches level 60 because 5 points are added to the cumulative points by the external evaluation and reaches the number of points required to reach level 60. At that time, in the user information database, the level is 60, and the cumulative number of points is updated and stored to the value after 5 points are added.

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

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

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

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

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

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

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

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

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

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

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

[0218] Note that the predetermined number of times is not limited to the number of individual tap actions 48, which is the number of individual tap actions performed by the user on the content. Instead of this, or in addition to this, each time the number displayed as the number of tap actions 78, which is the number of tap actions of all users in the fan community, reaches a predetermined value (for example, 100 times), an effect may be performed on the user who performed the 100th action.

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

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

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

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

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

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

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

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

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

[0228] 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 the predetermined number. In step S503, the tap action counter (a counter for specifying the total number of tap actions) stored in the storage unit 320 is incremented by 1. When the tap action counter is incremented in step S503, in step S504, it is determined whether the total number of tap actions after the increment is equal to the predetermined number. For example, if the total number of tap actions is 50, after being incremented by 1 in step S503, the total number of tap actions becomes 51, and in step S504, it is not determined to be equal to the predetermined number of 100.

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

[0230] In step S505, when it is determined that there is relevant talent, in step S506, based on the content-specific production table in FIG. 25, less than a predetermined number of tap actions are randomly selected and determined. After the production is determined in step S506, in step S507, the production of the tap action determined in step S507 is executed, and the tap action number update information is transmitted to the distribution server 100 to end the process. For example, when "mark_t1" of the production type fan mark with the article ID "a1" in FIG. 25 is determined by random selection, the number of tap actions 78 and the number of individual tap actions 48 are updated, and the production in which the fan mark corresponding to "mark_t1" pops up is executed.

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

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

[0233] In step S510, it is determined whether relevant talents are associated with the content for which a tap action operation has occurred. For example, if the content for which a tap action operation has occurred is the article "a1" in FIG. 14, it is determined that there are relevant talents.

[0234] In step S510, when it is determined that there are relevant talents, in step S511, a tap action effect for when a predetermined number is reached is selected and determined by lottery. In step S512, the tap action effect for when the predetermined number is reached determined in step S511 is executed, and tap action number update information is transmitted to the distribution server 100 to end the process. For example, when "special_t1" of the production type talent production of article ID "a1" in FIG. 25 is determined by lottery, the number of tap actions 78 and the number of individual tap actions 48 are updated, and the production corresponding to "special_t1" is executed.

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

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

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

[0238] <Use of API provided by external service> Next, with reference to FIG. 27, an example will be described in which content provided by the external web service system 400 is made available to the user by using an API provided by the external web service system 400. The external web service system 400 is, for example, a video distribution site. It is assumed that the talent who is the support target of the fan community in this embodiment is distributing videos on the video distribution site. In this embodiment, the user can easily confirm the distribution schedule for the talent to distribute videos on the video distribution site.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0253] <Regarding reaction notification processing> (Overview of reaction notification processing) With reference to FIGS. 28 and 29, the reaction notification processing in this embodiment will be described. In the reaction notification processing, it is possible to notify other users that there has been a reaction from a specific user (for example, a user of a special account predetermined by the operator, etc.) who satisfies specific conditions such as having a special position different from that of ordinary users in the community. Hereinafter, as an example of a specific user who satisfies the specific conditions, an example in which a reaction by a special user such as a talent described with reference to FIG. 5 is notified will be described.

[0254] As described above with reference to FIGS. 10, 11, 13, etc., in the community app of this embodiment, for the content (e.g., the content and articles posted by users) to which reactions such as comments and tap actions are made by special users, a special action 79 indicating that there is a reaction from the special user is displayed. Also, in this embodiment, when there is a reaction from a special user, other users including the user (posting source user) who posted the content etc. that is the target of the reaction are notified of that fact (e.g., by push notification or notification in the app's notification list). In this way, in the reaction notification process of this embodiment, the fact that there is a reaction from an influential special user is notified to other users (general users) by displaying the special action 79 and push notifications etc., so the attention of the posted content with a reaction increases, and general users can feel closer to the special user. As a result, the entire community can thrive, and the satisfaction of users using the community app can be improved. Also, for the posting source user, receiving a reaction from a special user for their own post can be extremely gratifying, which contributes to improving the motivation for fan activities.

[0255] On the other hand, it is also assumed that a special user may accidentally perform a reaction operation. Then, even if the reaction is reflected on the screen of another user's user terminal 300 (becomes a shared state) and after the fact that there is a reaction is notified, if the reaction is cancelled (deleted, etc.), there is a possibility that it has already been noticed by other users before the cancellation. In this case, even if the cancellation is done afterwards, the fact that the reaction was made is already known to other users, and there is also a risk that it is too late even if a subsequent cancellation operation is performed. In particular, for the reaction of a special user with high influence, since the attention from other users is high, misunderstandings etc. based on the reaction before cancellation are likely to spread.

[0256] Therefore, in the reaction notification process of this embodiment, reflection conditions are set for the reactions performed by special users. Before the reflection conditions are met, if a cancellation operation (cancel operation) is received from the special user who performed the reaction, it is considered that the reflection conditions are not met, and the fact that the reaction was performed is not reflected and not notified to other users. On the other hand, when the reflection conditions are met without a cancellation operation, the fact that the reaction was performed can be reflected and notified to other users. As a result, since the reaction can be cancelled before being shared with other users, special users can perform reaction operations with confidence.

[0257] The reflection conditions include those satisfied (established) by the elapse of the cancellable time or the confirmation operation by the confirmation screen. For example, after a reaction operation such as a comment or a tap action, if no cancellation operation is received from the special user who performed the reaction operation within the cancellable time, it may be determined that the reflection conditions are satisfied. Alternatively, when a reaction operation is performed, a confirmation screen for reaction execution such as a dialog box is displayed on the display unit of the user terminal 300 of the special user who performed the reaction, and when an operation such as a reaction execution confirmation button is performed, it may be determined that the reflection conditions are satisfied.

[0258] In addition, when the elapse of the cancellable time is set as a reflection condition, even if the cancellable time has not elapsed, if a confirmation operation to reflect the reaction is performed by the special user, it may be determined that the reflection condition is established. For example, an icon for the confirmation operation is displayed near the list display of reactions during the cancellable period or near a comment that is a reaction, and when the distribution server 100 receives information on an operation on the icon or the like, it may be determined that the reflection condition is established.

[0259] As the cancelable time in the reaction notification process, for example, it may be set to 5 minutes after the talent performs a reaction operation such as a tap action. However, it is not limited to this, and several hours or several days after the reaction operation may be set as the cancelable time. In addition, the cancelable time may be variable, and the user may be able to set the cancelable time individually in advance by the operation of each special user.

[0260] Also, regarding which reflection conditions to use, it may be possible for the user to set them in advance by the operation of each special user. For example, it may be possible to select in advance to use the elapse of the cancelable time as the reflection condition, or to use the display of the reaction execution confirmation screen and the fact that the reaction confirmation operation is performed as the reflection condition, or to use both the elapse of the cancelable time and the reaction confirmation operation as the reflection conditions.

[0261] As for the reaction cancellation operation, a predetermined operation (such as 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 the like is performed, or a deletion icon or the like is displayed on the comment to be cancelled, and an operation on the deletion icon is included. etc. As a result, it becomes possible to cancel the tap action operation (the number of tap actions performed by the special user on the content to be cancelled, etc. is reset to 0) and delete the comment. Note that a menu icon or the like that can be displayed as an option for the deletion operation may be displayed on the comment. In addition, a list page of reactions that can be cancelled and can be transitioned from the my page or the like may be provided, and comments and reactions of tap actions that are within the cancellable period may be listed. For example, a deletion icon or the like may be displayed together for each reaction, and comments and tap actions for which the deletion icon is selected may be made cancellable on the list screen, or when any reaction is selected from the list screen, the screen may be transitioned to a screen that displays the target posted content. Further, when a confirmation screen for reaction execution such as a dialog box is displayed, the cancellation operation may be regarded as having been performed when the cancel button is operated on the confirmation screen, or when the confirmation button is not operated and the confirmation screen is closed.

[0262] (Example of data table related to reaction notification processing) Next, with reference to FIG. 28, an example of a data table in which information related to reaction notification processing is associated will be described. 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. Also, hereinafter, the poster of the post (article) will also be referred to as the posting source user. In the content data such as that shown in FIG. 14 stored as the content data 122 of the distribution server 100, as illustrated in FIG. 28(A), "reaction-related information" is associated with each post (article) ID.

[0263] As "reaction-related information" for each submission ID, there is a "total number of tap actions", which is the aggregated result of the number of tap actions made by users for the submission, a "total number of comments", which is the aggregated result of the number of comments made by users for the submission, and if there is a reaction from a special user such as a talent for the submission, information on "special actions" is associated. In the information on "special actions", the ID of the talent who performed the special action and information identifying the type of special action performed, such as the presence or absence of a tap action or the presence or absence of a comment, are associated. The "total number of tap actions" and the "total number of comments" are displayed as the number of tap actions 78 and the number of comments 77, etc., displayed for each content as exemplified in content screen examples such as those in FIGS. 10, 11, 13, etc. Also, based on the information associated as "special actions", on the content screen, etc., as special actions 79, an icon corresponding to the talent ID and an icon corresponding to the type of special action are displayed. For the icon corresponding to the type of special action, for example, if it is a tap action, a heart mark can be displayed together with the icon of the talent, and if there is a comment, a speech bubble mark can be displayed together with the icon of the talent.

[0264] An example of a data table regarding the special action reflection hold data stored in the storage unit 120 (for example, as action information 123, etc.) of the distribution server 100 in FIG. 28(B) will be described. In the reaction notification process in this embodiment, before the fact that a special user has reacted is reflected and can be shared with other users, it is possible to perform a cancellation operation by the operation of the special user who reacted. FIG. 28(B) is data for identifying a reaction for which the reflection condition is not satisfied and for which the cancellation operation can be performed.

[0265] In the distribution server 100, as a process for reflecting the reaction operation received from the user, in response to receiving the information that a reaction operation has been performed from the user terminal 300, the information of the reaction is associated with the post (article) ID such as FIG. 14 or FIG. 28(A). For example, in the case of a tap action, as exemplified in steps S507, S512, S513, etc. of FIG. 26, the tap action count update information is transmitted from the user terminal 300 to the distribution server 100. If the user who performed the tap action is a user different from the special user, without determining the success or failure of the reflection condition (even if it is not satisfied), the total tap action count in FIG. 28(A) is updated and reflected as the tap action count 78. Also, when a comment is posted, the comment posting information is transmitted to the distribution server 100. If the user who made the comment is a user different from the special user, without determining the success or failure of the reflection condition (even if it is not satisfied), the total comment count in FIG. 28(A) is updated and reflected as the comment count 77. Also, it is reflected as a comment 87 etc. on the content screen such as FIG. 13 and shared with other users.

[0266] On the other hand, if the information that a reaction operation has been performed is information transmitted from the user terminal 300 of the special user, when the reflection condition is satisfied, it is associated with the post (article) ID and reflected to other users. That is, for a reaction from a general user different from the special user, regardless of whether the reflection condition is satisfied, the reaction is immediately shared with other users. However, for a reaction from the special user, it is not reflected until the reflection condition is satisfied, and it is reflected (shared) after waiting for the reflection condition to be satisfied.

[0267] 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 hold data table in Fig. 28(B). For example, a hold number is assigned to each piece of received information, and for each hold number, information such as the "sender user ID" which is information identifying the special user who performed the reaction operation, the "transmission date and time" that was transmitted, the "action content", and the "post (article) ID" which is the target of the reaction are associated. The "action content" is the content of the reaction, and information such as tap action count update information and the content of the comment is associated.

[0268] As a reflection condition, for example, when a cancelable time of 5 minutes is set, if the distribution server 100 receives information on which a cancel operation has been performed within 5 minutes from the transmission date and time, the received information targeted by the cancel operation is deleted from the special action reflection hold 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 for which 5 minutes has elapsed from the transmission date and time without receiving information on which a cancel operation has been performed is reflected in the content database and is associated, for example, as reaction-related information in Fig. 28(A). As a result, the talent ID corresponding to the sender user ID is associated as a special action, and special action 79 is displayed on the content screen or the like. Also, it is not limited to deleting received information that no longer requires holding due to a cancel operation being performed or the reflection condition being satisfied from the special action reflection hold data, but a flag may be set for received information that no longer requires holding so as not to include it in the determination target for the presence or absence of receiving a cancel operation.

[0269] Although an example in which the target of the reaction is post content for each post (article) ID exemplified in Fig. 14 or Fig. 28(A) has been shown, reactions (tap actions on comments or reply comments) to the comments 87 for each post content in Fig. 13 may also be included as targets of special action reactions.

[0270] (Notification Method to the Original Submitting User) In the reaction notification process, after the reaction made by a special user becomes shareable with other users due to the fulfillment of the reflection conditions, the user who submitted the content that is the target of the reaction can be notified that there has been a reaction from the special user. The notification method is not limited to the same method as that for other users, such as displaying an icon of a talent such as a special action 79 on the submitted content itself, but also includes notifications by displaying on the notification screen such as the original submitting user's my page, and notifications by push notifications to the original submitting user.

[0271] Note that the notification (such as a push notification) due to a reaction (favorable action) such as a comment or a tap action made by a talent who is a special user may be notified regardless of whether the original submitting user has pre-selected the talent as a favorite, or only the reaction from a special user pre-selected as a favorite talent may be notified.

[0272] Also, the push notification for notifying that a talent or the like who is a special user has performed a tap action or the like by the reaction notification process in this embodiment may be notified in a manner corresponding to the special user who performed the action. For example, it may be made such that the voice message of the talent who is the special user himself / herself, a part of the melody such as the music of the talent or the like, an image related to the talent (such as a photo / illustration of the talent himself / herself), or the message notified according to the talent or the like is different. For example, it may be made such that a notification message representing the catchphrase or tone of the talent or the like is notified.

[0273] (Example of the Flow of Reaction Notification Process) Next, with reference to FIG. 29, the flow of reaction notification processing will be described. FIG. 29 is a flowchart for explaining an example of the reaction notification processing described with reference to FIG. 28 and the like. The reaction notification processing is repeatedly executed by the content management unit 132 of the distribution server 100 and the like.

[0274] In step S601, it is determined whether reaction information for a post (for example, information specifying a tap action operation on content or that a comment has been posted) has been received. If it is determined that reaction information for a post has been received, then in step S602, it is determined whether the user who is the source of 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 with respect to any of the posted content illustrated in FIGS. 10, 11, 13, etc., reaction information such as tap action count update information and comment posting information is transmitted to the distribution server 100, and it is determined that reaction information has been received.

[0275] In step S602, if the source of the received information is a user different from a special user such as a talent illustrated in FIG. 5 (for example, a general user), then in step S603, received information reflection processing is executed. For example, based on the received reaction information, processing such as associating comment information (the text of the comment, the user ID, etc.) with the post ID that is the reaction target stored in the data table for each content such as FIGS. 14 and 28(A), and updating the total count of tap actions is performed. For example, the comment count 77 and the tap action count 78 in FIGS. 11, 13, etc. are updated, and reflection processing is executed so as to be displayed as comment 87. As a result, the reaction is also shared on the user terminals 300 of other users.

[0276] When the received information reflection process is executed in step S603, in step S604, a process of transmitting default notification information to the posting source user of the post targeted for reaction is performed, and the process ends. The default notification information is, for example, information for displaying, by push notification or otherwise, that there has been a reaction to the notification on the my page. For example, when a reaction to the content with the 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 notifying the user "u1", who is the poster of the "a3", that there has been a reaction is transmitted to the user terminal 300 of "u1", and a push notification or the like is performed.

[0277] On the other hand, when it is determined in step S602 that the user who is the source of the reaction information is a special user, in step S605, a received information reflection hold process is executed and the process ends. For example, in the special action reflection hold data table illustrated in FIG. 28(B), a process of associating the received information of the reaction received from the special user and managing it as information for holding the reflection is performed, and the process ends. The received information is associated with information for identifying the source user, the transmission date and time, the content of the action, and information for identifying the post that was the target of the reaction. At this time, until the reflection process is performed in step S609, which will be described later, the reaction is not shared (not displayed) on the user terminal 300 of other users other than the special user who performed the reaction operation, but is reflected and displayed in a shared manner on the user terminal 300 of the special user himself / herself.

[0278] Return to step S601. When it is determined that reaction information for the post has not been received, at step S606, it is determined whether a cancellation request for reaction-related information corresponding to the received information held in step S605 has been received. For example, on the user terminal 300 of a special user, a long-press operation on the icon 708 for executing a tap action, a comment deletion operation, etc. are performed, and cancellation request (cancellation request) information for the reaction is transmitted to the distribution server 100.

[0279] At step S606, when it is determined that a cancellation request for the reaction corresponding to the received information managed as a hold target in FIG. 28(B) has been received, at step S607, an unreflected process for the corresponding held received information is executed, and the process ends without being reflected to other users. The unreflected process is, for example, a process of deleting the received information held in FIG. 28(B). When the received information is deleted, the process ends without being associated as reaction-related information for each post content in FIGS. 14 and 28(A).

[0280] On the other hand, if it is not determined at step S606 that a cancellation request for the reaction information corresponding to the held received information has been received, at step S608, it is determined whether there is any held received information for which the reflection condition is satisfied. For example, when a cancellable time is provided (e.g., 5 minutes, etc.), when the cancellable time has elapsed since the transmission date and time, or when there is a confirmation operation for the reaction, it is determined that the reflection condition is satisfied (met). On the other hand, when it is not determined that the reflection condition is satisfied, the process ends.

[0281] In step S608, if it is determined that there is pending received information for which the reflection condition is satisfied, then in step S609, received information reflection processing is executed for the pending reaction for which it was determined in step S608 that the reflection condition is satisfied. That is, the reaction information received in step S601 is reflected and can be shared with other users. The received information reflection processing is, for example, a process of associating the received information as reaction-related information for each piece of posted content in a content data table such as 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 is also displayed on the screen of the user terminal 300 of other users.

[0282] Next, in step S610, a process is executed to transmit notification information in a manner corresponding to the special user who is the sender of the reflected received information to the posting source user of the post targeted for the reaction, and the process ends. For example, as illustrated in FIG. 28(B), the information on the tap action operation for the posted content with the post (article) ID "a3" such as FIG. 28(A), which is the reaction made by the special user with the talent ID "t5" in FIG. 5 and was managed as the information to be held in step S605, becomes shareable with other users in step S609 because the cancelable time has elapsed from the date and time (transmission date and time) when the tap action was performed. In step S610, notification information is transmitted to the user terminal 300 of the poster "u1", who is the posting source user. The notification information includes, for example, the information of a push notification accompanied by a voice message or an image of the talent "EEE" corresponding to "t5" in FIG. 5, and the information for displaying the special action 79 of the icon corresponding to "t5".

[0283] Even if the reflection condition is not satisfied, on the user terminal 300 of a special user who has performed a reaction operation, the reaction may be displayed in a mode where it is reflected and shared. However, until the reflection condition is satisfied, an icon, annotation, etc. that suggest that it is not shared with other users (is a provisional display) may be displayed, so that the special user can recognize that the reaction is one that can be canceled before reflection. Alternatively, the display mode of the reaction itself may be different from the mode where it is reflected and shared. For example, the character color of the comment, the color of the heart icon 708, etc. may be displayed in a lighter color than when it is reflected.

[0284] <Regarding language association processing> (Overview of language association processing) With reference to FIGS. 30 to 35, the language association processing in this embodiment will be described. 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 a user who mainly uses Japanese as a language can communicate not only with users who mainly use the same Japanese as a language, but also with users who use other languages (for example, users living overseas, etc.).

[0285] By the way, in today's fan activities, there may be fan users who routinely use other types of languages different from the languages handled (so-called "oshi") by the object of support. Also, fan users may use different languages according to the situation (time, place, scene). For example, they enjoy the content transmitted by the object of support such as a talent (including various information such as video content such as live distribution, music, and SNS information) in a language different from their mother tongue and used by the object of support, and also send messages to the object of support in a language different from their mother tongue and used by the object of support. When communicating with local fans in the region (country, etc.) where they live, they may communicate in their mother tongue. Furthermore, there may be cases where all of the mother tongue, the language used when using the content, the language of the message to the object of support, and the language when communicating with other fan users are different. In this way, even without using multiple languages, it is possible to communicate by using automatic translation such as machine translation, but there may be cases where the accuracy is lacking, such as mistranslations occurring. Also, for each language, trendy expressions, images, commonly used words, and the atmosphere (so-called "the mood of the place") may differ between language spheres. Simply being machine-translated may not convey nuances to users who use other languages. Also, topics for each region are likely to be posted using the language used in that region. Therefore, the language of the information one wants to receive, the language of the person one wants to receive the information sent, etc. can vary according to the situation.

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

[0287] Also, simply displaying a list of posted contents posted in various languages may result in the posts being buried even if they are posted in the midst of various comments and the like, and there is a risk that the intended recipient will not read them. However, according to the language association process in this embodiment, it is possible to perform a filtered display in the language specified (selected) by the user based on the language information associated with the post itself, so that it becomes easier to find the posts required by the user and it becomes easier for the posts to be read by the intended recipient.

[0288] Regarding the language to be associated with the post, for example, it is also possible to automatically associate the language setting of the OS of the user terminal or the language set as the display language of the application and post it. However, if this is done, even if the application display language is Japanese but the post is deliberately made in English in order for English-speaking users to read it, there is a risk that even if the filtered display of the posted content specified to be displayed in English is performed, the post associated with Japanese may be excluded from the display target due to the influence of the OS language setting and the like. However, in this embodiment, since the language to be associated with the post can be selected by a user operation, it is possible to narrow it down to the language intended by the user.

[0289] (Example of Screen Display According to Language Information) FIG. 30 is an example of a screen when displaying a content screen or the like, which has been described with reference to FIGS. 10, 11, 13, etc., according to the language information associated with the post. FIG. 30 is an example of a community screen of the same type as FIG. 11 that displays a list of content headings (hereinafter, also simply referred to as content collectively) of the content posted to all channels of community A. For example, it is displayed when selected from the channel list 82 of community A on the channel list screen of FIG. 12 or the like. In the content screens of FIGS. 10, 11, 13, etc., an example where the language associated with the currently displayed post is not displayed on the language switch icon LS has been described. Hereinafter, as shown in the content screen of FIG. 30, an example where the language associated with the currently displayed post is displayed on the language switch icon LS will be described. Further, when the language switch icon LS is selected and operated, a language selection bar LSR that displays buttons for language selection or the like is displayed.

[0290] In FIG. 30(A), since a selection (specification) to display a post associated with Japanese as the language type is made, "Japanese" is displayed on the language switch icon LS. FIG. 30(B) is an example of a screen where, when "English" is selected in the language selection bar LSR displayed by selecting the language switch icon LS in FIG. 30(A), "English" is displayed on the language switch icon LS, and a list of contents associated with English as the language information is displayed. Note that although a selection between Japanese and English is displayed in the language selection bar LSR of FIG. 30(B), as shown in FIG. 32(C) described later, three or more types of languages may be displayed, and multiple languages may be selectable simultaneously by means of options that allow selection of all languages or by checking check boxes or the like. Also, a check button or the like for fixing the selected language as the default may be displayed.

[0291] (Example of Default Setting Screen) FIG. 31 is an example of a screen for setting default language information and is a part of a user information registration screen when the community app in this embodiment is used for the first time. In the community app in this embodiment, for the type of default language to be displayed, different languages can be set for each item related to the use of the community app. As items, for example, an app display language, a push notification language, official content posts to be displayed, user posts to be displayed, etc. can be provided.

[0292] The app display language is, for example, the language information displayed on setting screens such as the my page and various icons. For example, the screen examples such as FIG. 30 illustrated in this embodiment are screen examples when the app display language is set to Japanese. The push notification language is the language of characters, images, etc. to be push-notified. The official content post language to be displayed is the language associated with official content posted by users such as operators and special users in FIG. 5 where an official mark is displayed. The user post language to be displayed is the language associated with content posted by general users different from the posting of official content.

[0293] In this embodiment, at the start of app use, first, an initial language setting is made based on the language setting of the OS of the user terminal 300. For example, in FIG. 31, since the language setting in the OS of the user terminal 300 of the user who displays the screen is "Japanese", it is displayed that the initial setting has been made to Japanese. Also, on the setting screen, since the user has performed an operation to change only the push notification language to English, "English" is displayed for the push notification language, and "Japanese" is displayed for the other languages. Also, the default language setting can be changed later from the my page or the like even when it is not the initial setting. In this way, the preset default language information is stored as user information such as in the user information database for each user stored as the account information 125 illustrated in FIG. 7 or the like, or is stored in association with the user information in the storage unit 320 of the user terminal 300.

[0294] In addition, as exemplified in FIG. 32(C), for each item, all language options may be provided, or multiple languages may be preset. Also, the default language associated with user submissions may be preset.

[0295] In addition to the items exemplified in FIG. 31, more detailed settings may be possible. For example, the default displayed language may be made different between the languages of submissions by special users such as talents and the languages of submissions by operators. Additionally, for example, within the range where certain categorizations are possible, such as for each community, each channel, each category, etc., the display language preferred by the user may be set according to user operations. Since the content the user wants to talk about changes for each topic content, and the nature of the users gathering may also change, communication in a language according to the situation becomes possible.

[0296] (Example screen when associating a language with a submission) FIG. 32 shows an example of a user submission screen, which is an example of a screen in which a language switch icon LS is further displayed on the submission screen of FIG. 17. Similar to FIG. 17, the submission screen of FIG. 32 is displayed when there is an operation from the user for the submission icon 23 displayed on the content screen or the like. As shown in FIG. 32(A), a default language is selected in advance as the submission language. The default language is selected from the initial setting language based on the settings of the OS of the user terminal 300, the language of the app display language preset on the language setting screen exemplified in FIG. 31 or the like, or the language that the user has preset in advance as the default of the submission language. FIG. 32(B) is an example of a screen when performing a switching operation of the language associated with the submission. It is an example of a screen in which English is selected in the language selection bar LSR displayed by selecting the language switch icon LS in FIG. 32(A). As a result, English is associated with the submission as language information. Also, as exemplified in FIG. 32(B), since the association of such language information is possible regardless of the actual language of the text to be input, for example, even if the input is in Japanese text, it is also possible to associate English as language information.

[0297] FIG. 32(C) is another display example of the language selection bar LSR that is displayed when the language switch icon LS is selected. In FIG. 32(B), an example is shown in which a selection between Japanese and English is displayed as language options. However, as shown in FIG. 32(C), options for three or more languages may be displayed, and there may be an option for "all languages". When "all languages" is selected, regardless of which language is displayed on the language switch icon LS in FIG. 30, that is, regardless of which language is selected (designated) as the language to be displayed, a list display will be provided. Further, check boxes or the like may be displayed so that multiple types of languages can be selected. For example, it is possible to simultaneously specify three languages: Japanese, English, and Chinese. Also, in the language selection bar LSR displayed at the time of posting, a check button or the like for fixing the settings may be arranged, and the default language at the time of posting may be set based on the on / off state of the check button.

[0298] (Example of a data table associated with language information) Next, with reference to FIG. 33, an example of a content data table associated with language information will be described. FIG. 33 is an example of information associated with a content database (such as a table) 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. Similar to FIG. 14, a "poster ID" is associated with each "post (article) ID". Although not shown in FIG. 14, "post date and time", "post content information", etc. are associated. The post content information includes information such as the text of the content of the post, the title, and the attached image. Further, in FIG. 33, "language information" is associated with each post ID. The language information associated with each post ID, that is, each content, is the language associated at the time of posting, as exemplified in FIG. 32. As a result, posts associated with the type of language specified by the user's previous settings or an operation on the language switch icon LS can be extracted according to the language and displayed in a list. Note that, as exemplified in FIG. 32(C), when "all languages" are selected or when a plurality of languages are selected, not only one language information but also a plurality of languages may be associated as the language information.

[0299] Examples of information stored as content data include (1) cases where the language included in the posted content information (for example, a message such as text or an image) matches the language information associated with the post, or (2) cases where the language included in the posted content information does not match the language information associated with the post. For example, the post 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 for explanation), and the post ID "a30" corresponds to the content 70f in FIG. 30(A). For content 70d1 and content 70f, the text and images of the posted content information are each posted in Japanese, and Japanese is also associated with the language information. Also, the post ID "a21" in FIG. 33 corresponds to the content 70d2 in FIG. 30(B), and the post ID "a25" corresponds to the content 70g in FIG. 30(B). For content 70d2 and content 70g, the text and images of the posted content are each posted in English, and English is also associated with the language information.

[0300] On the other hand, the post ID "a35" in FIG. 33 corresponds to the content 70h in FIG. 30(B). The text of the posted content is in Japanese, but English is associated with the language information. Thus, for example, in the case of a user who handles Japanese and wishes to communicate with other users in Japanese, but wants to mention a topic related to an event in the English-speaking area and wants to catch the eye of local users, it is also possible to deliberately associate other types of language information with a Japanese post and post it.

[0301] Also, even for posts with similar content by the same poster, by associating different language information with the posts, for example, posts about an article on the same event can be separated into a Japanese post and an English post. For example, the post ID "a20" corresponds to the content of the content heading 70d1 in FIG. 30(A), and the post ID "a21" corresponds to the content of the content heading 70d2. Both the content 70d1 and the content 70d2 are contents posted by the poster from the same official account (poster ID "ou") by the operator, and both contents are articles about the birthday of the talent AAA. Even when wanting to post the same content about the birthday of AAA, instead of simply being machine-translated, it can be posted in Japanese for Japanese speakers and in English for English-speaking regions, and furthermore, it can be posted with nuances according to the language region.

[0302] (Example of the flow of the list display process for posts associated with language information) Next, with reference to FIG. 34, the flow of the post list display process when displaying a list of post contents associated with language information will be described using a flowchart. By the post list display process, a content screen or the like for displaying the list of post contents described with reference to FIG. 30 is displayed. The post display process is repeatedly executed in the distribution server 100 in response to receiving display request information from the user terminal 300 (for example, a request to display a screen for displaying a list of contents exemplified in FIGS. 10, 11, 30, etc.).

[0303] In step S701, it is determined whether there is a request to display a list of posted contents. When it is determined that there is a request to display a list of posted contents, in step S702, in accordance with the set language of the user who is the request source, a process is performed of transmitting to the user terminal 300 the list display information of the posted contents associated with the set language. For example, when the application is launched and there is a request to display a home screen such as FIG. 10, or when an operation is performed to select a channel to be displayed as in FIG. 12, the user information database stored in the account information 125 and the like are referred to, and the information of the language that is pre-associated as the default for the user who is the request source is specified. For example, if the language set by the initial setting or the user's change operation is Japanese in the language setting screen or the my page of FIG. 31, the posted contents associated with Japanese are extracted from the content database of FIG. 33, and the information for causing the user terminal 300 to display the extracted posted contents is transmitted to the user terminal 300. As a result, on the user terminal 300, as shown in FIG. 30(A), a list of posted contents in which the language switch icon LS is Japanese and Japanese language information is associated is displayed. In addition, for example, when the settings of the languages to be displayed are different between official content posts and user posts, and when a request is made to display a screen on which both official content posts and user posts are displayed, one of the default settings may be prioritized, such as prioritizing the settings of official content posts.

[0304] Return to step S701. When it is determined that there is no list display request, or after the list display information is transmitted based on the list display request in step S702, it is determined in step S703 whether there is a display language switching request. For example, it is determined whether an operation to switch the display language is performed on a post content list screen such as FIG. 30 displayed on the user terminal 300 based on the information transmitted in step S702 or based on the list display information stored in the storage unit 320 of the user terminal 300 (for example, received at the time of the previous login). When it is determined that there is no display language switching request, the process ends. On the other hand, when it is determined that there is a display language switching request, it is determined in step S704 whether the switching request is a switch of the default language setting. For example, when it is a temporary language switching request due to an operation to switch the display language from Japanese to English (language designation operation) based on an operation on the language switching icon LS in FIG. 30, it is determined that there is no switch of the default language setting, and in step S706, list display information of post contents associated with the switched language is transmitted to the user terminal 300 and the process ends.

[0305] On the other hand, for example, when a language switching operation (language designation operation) is performed based on an operation on the language switching icon LS in FIG. 30 and a language setting fixing operation as illustrated in FIG. 32(C) is performed, or when the default display language setting of the content on the my page or the like is changed, it is determined that there is a switch of the default language setting.

[0306] In step S704, if it is determined that there has been a switch in the default language setting, then in step S705, the switched language is associated with the user information as the default and updated and stored. Thereafter, in step S706, according to the switched language, list display information of the posted content associated with the language is transmitted to the user terminal 300 to end the process. For example, when the default language is switched from Japanese to English, referring to the user information stored as account information 125, the default language associated with the user information of the requester is changed to English and updated and stored. Also, the posted content associated with English as the language information stored in the content data table of FIG. 33 is extracted, and information for the extracted posted content to be displayed in a list is transmitted to the user terminal 300. Thereby, it is possible to switch and display from the screen for listing the posts associated with Japanese in the language information of FIG. 30(A) to the screen for listing the posts associated with English in the language information of FIG. 30(B).

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

[0308] (Example of the flow of the user posting process for associating language information) Next, with reference to FIG. 35, the processing flow in the user terminal 300 when a user post associated with language information is made will be described. FIG. 35 is a flowchart when 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 and the like. The description of the same processes as those in FIG. 18 will be omitted. Also, assuming that the posting operation is performed in a channel where user posting is permitted, the description of step S302 in FIG. 18 will also be omitted. Also, steps S304 to S311 and steps S314 to S315 are not shown in FIG. 35, but the description and illustration will be omitted assuming that they are processed in parallel.

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

[0310] In step S322, it is determined whether there has been an operation to change the posting language. When it is determined that there has been no operation to change the posting language, and when it is determined in step S312 (proceeding according to the input operation of character information described in FIG. 18 etc.) that a posting confirmation operation has been performed, in step S313, posting information associated with default language information is transmitted 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 as to whether there has been an operation to change the posting language is repeated. As described in FIG. 18, when a posting confirmation operation is not performed in step S312 and a selection such as closing the posting screen in step S314 of FIG. 18 is made, the process may end without making a post.

[0311] When it is determined in step S322 that there has been an operation to change the posting language, in step S323, it is determined whether there has been a default fixing operation for the changed language. For example, as illustrated in FIG. 32, although Japanese is associated by default, when another language is selected in the language selection bar LSR such as in FIGS. 32(B) and (C) displayed by operating the language switching icon LS, it is determined that there has been an operation to change the posting language. Also, as illustrated in FIG. 32(C), when an input operation is performed on the checkbox for fixing the setting of the selected language, etc., it is determined that there has been a default fixing operation for the changed language. When it is not determined in step S323 that there has been a default fixing operation for the changed language due to no particular fixing operation being performed and only a changing operation being performed, etc., the process proceeds to step S325.

[0312] In step S323, if it is determined that there is a default fixing operation for the changed language, the changed set language is updated and stored in association with the user information. For example, although the default is Japanese, when an operation to change the posting language to English is performed along with an operation to fix the setting, English is associated and stored as the default language at the time of posting in the storage unit 320 of the user terminal 300. When the posting information is transmitted to the distribution server 100 in step S313, information indicating that the default language at the time of the user's posting has been updated may also be transmitted so that the default language at the time of posting for each user information managed in the distribution server 100 is updated.

[0313] In step S325, the changed set language is associated with the posting information. If it is determined in step S312 that there is a posting confirmation operation, the posting information associated with the changed set language as language information is transmitted to the distribution server 100 and the process ends.

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

[0315] Furthermore, as described with reference to FIGS. 10, 11, 14 to 16, 27, etc., the distribution server 100 or the user terminal 300, in response to an operation on the recommendation filter 20, displays, on the display unit of the user terminal 300, content headings (60, 70, 90) in a state where the recommendation filter 20 is off, such as those illustrated in FIG. 15(B), among the content (e.g., content stored in the content database of community A in FIG. 14) associated with the participating communities preselected and stored by the user, so that the user can identify them, and a second display state such as FIG. 15(A) in which content headings (60, 70, 90) regarding content associated with both the participating communities and the recommended talents preselected and stored by the user are extracted and displayed so that the user can identify them. The display is switched to one of a plurality of types of display states including the first display state and the second display state. Thereby, it becomes possible to switch between the content headings that are displayed regardless of whether the recommended talent is associated with the content posted in the (participating) community preselected by the user, and the content headings regarding the content posted in the (participating) community preselected by the user and associated with the recommended talent. Thereby, the user can easily identify the information of their preference. For example, for a user who has joined community A and selected the talent "AAA" with talent ID "t1" as the recommended talent, among the content stored in the content database of community A in FIG. 14, the content headings of the content associated with "t1" in the talent ID are extracted and displayed on the home screen of FIG. 10, the community screen of FIG. 11(A), the distribution schedule screen of FIG. 27, etc. Note that the recommendation filter 20 can be turned on and off regardless of the level of the evaluation history status of each of the plurality of users stored in the user information database illustrated in FIG. 7.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0339] (2-8) As described with reference to FIG. 22 and the like, external evaluations that can update the user's evaluation history status include evaluations such as favorable actions and reports from other users different from the user who took the action among multiple users who use the community app. Thus, since external evaluations include evaluations from other users different from the user who took the action, the public order within the community can be made to conform to the intentions of all users.

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

[0341] (2-10) Also, the reflection of actions subject to restrictions from a predetermined number of users who are allowed the specific action of "report count" described with reference to FIG. 19 and the like is restricted on each user terminal 300 of multiple users. Thereby, since an action received as an action subject to restrictions by a predetermined number of users whose evaluation history status is in a predetermined status is regarded as a nuisance action and the reflection of the action is restricted, nuisance behaviors and the like can be efficiently restricted without hindering free communication and interaction.

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

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

[0344] (3-1) In the above-described embodiments, in response to receiving a tap action from a user on posted content or the like displayed on the screen of the user terminal 300 such as in FIGS. 10, 11, and 13, or a reaction such as a reply to a comment at step S601 in FIG. 29, at steps S603, S609, etc., by reflecting it in the content data table for each posted content, the reaction can be displayed on the screens of the user terminals 300 of other users and made shareable. Also, at step S602 in FIG. 29, in response to the reaction to the posted content being a reaction from a specific user who satisfies specific conditions such as a special user like a talent in FIG. 5 or a user of a special account predetermined by the operator or the like, at 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 on which the reaction operation was performed, or a special action 79 which is an icon suggesting that there has been a reaction from the talent is displayed, etc., so that it is possible to notify that a reaction has been received from a special user. As a result, the user who is the source of the posted content where a reaction has occurred is notified that a reaction has been received from a special user (a specific user who satisfies the specific conditions in the above-described embodiments), so that the satisfaction of the user who is the source of the post can be improved.

[0345] (3-2) Regarding the reaction operation performed by a specific user, at step S608 in FIG. 29, when it is determined that the reflection conditions are satisfied because the cancellation time has elapsed without a cancellation operation or a reaction confirmation operation has been performed, etc., it is reflected so as to be shareable with other users at step S609. As a result, regarding the reaction from a specific user, since it is shared when the reflection conditions are satisfied, it is possible to prevent the reaction from being shared arbitrarily without the reflection conditions being satisfied.

[0346] (3-3) For a reaction operation performed by a specific user, within the cancelable period, the tap action can be canceled by a long-press operation on an icon (such as icon 708) for performing a tap action, a deletion operation for the comment to be canceled can be performed, a cancel operation can be performed on the reaction list screen, etc. Thus, in step S607 of FIG. 29, the reaction information for which the cancel operation has been performed is deleted so that it is not shared with other users, and it can be assumed that the reflection condition is not satisfied. Alternatively, it may be assumed that the reflection condition is not satisfied because the reaction information is not transmitted to the distribution server 100 when a cancel operation is performed on the reaction execution confirmation screen. In this way, by performing a cancel operation, the reaction can be prevented from being shared with other users. As a result, since the reaction is not shared by performing a cancel operation, the specific user can react with confidence.

[0347] (3-4) For a reaction from a general user who is a user different from the specific user, when the distribution server 100 receives the reaction information, in steps S602 to S604 of FIG. 29, the reaction can be immediately reflected and shared with other users. Thus, for a reaction from a user different from the specific user, it can be shared even if the reflection condition is not satisfied, so the processing load on the computer is reduced.

[0348] As information suggesting the number of reactions to actions (e.g., posted content) shared among (3-5), display the number of tap actions 78 and the number of comments 77 for each content such as in FIGS. 10, 11, 13, etc. For reactions from a specific user, as special suggestion information different from the information suggesting the number of reactions, display a special action 79, which is an icon indicating that it is a post with a tap action or a comment from a special user displayed for each content such as in FIGS. 10, 11, 13, etc. This makes it easy to identify whether a reaction to an action such as posted content is from a specific user or not.

[0349] (3-6) The mode of notification to the user of the poster (source) of the posted content with a reaction from a specific user according to step S610 in FIG. 29 is a mode according to the specific user who made the reaction. For example, it can be arranged to perform a push notification by a voice message of the talent himself / herself who is a special user or an image related to the talent or the like. Thereby, since it is notified that a reaction has been received in a mode according to the specific user, the user's interest at the time of notification is improved.

[0350] (4-1) In the above-described embodiment, the user terminal 300 can accept input of text in any of a plurality of languages on a posting screen such as FIG. 32, and associates language information specifying the type of language with the posting information transmitted to the distribution server 100 by steps S321 and S325 in FIG. 35. Posting information including the poster ID, posting date and time, posting content information, language information, etc. associated with the content data table in FIG. 33 is transmitted to the distribution server 100 in step S313 of FIG. 35. Further, the user terminal 300 receives information for displaying a list of posting contents such as FIGS. 30, 10, and 11 transmitted from the distribution server 100 by steps S702 and S706 in FIG. 34, and displays a list of posting contents. Further, the posting list information includes information for specifying the posting content information such as text and images in FIG. 33 and the language information associated with each posting in FIG. 33. Based on the posting content information and language information for each of these postings, as shown in FIG. 30, the language specified by an operation on the language switch icon LS displayed on the list screen of the posting contents in FIG. 30 or the language information of the language specified by the default setting by a user operation on the initial setting or the my page in FIG. 31 or the like is associated. The posting contents are displayed in a list. As a result, it is possible to post in any of a plurality of languages, and it is possible to narrow down and display in a list the postings associated with the type of language specified by the user, so that it is possible to communicate with other users according to the language.

[0351] (4-2) Also, as illustrated in FIG. 32, on the posting screen, it is possible to display a language switch icon LS or the like on which the currently associated language is displayed. As a result, since the type of language associated with the posting can be specified at the time of posting, it becomes easier for the user to confirm the type of language associated with the posting.

[0352] (4-3) Also, on the list display screen of posted content such as FIG. 30, a language switch icon LS for displaying the currently filtered language in FIG. 30 is displayed. For example, as shown in FIG. 30(B), if the display language is narrowed down to English, "English" is displayed on the language switch icon LS. This makes it easier for the user to confirm the type of language specified when displaying the post list.

[0353] (4-4) By steps S321 and S325 in FIG. 35, the type of default language selected by user operation at the time of initial setting in FIG. 31 or from the my page, etc., or the type of language selected by operating the language switch icon LS as shown in FIG. 32(B) can be associated with the posted information and posted. This enables communication while associating the type of language intended by the user.

[0354] (4-5) As illustrated in FIG. 31, the language set in the OS of the user terminal 300 can be initially set as the type of default language. However, the initially set type of language can be changed from the initial setting language to another type of language, such as the push notification language in FIG. 31, or the type of default language can be changed from the my page, etc. Also, in steps S322 to S325 in FIG. 35, as shown in FIG. 32(B), it is possible to associate and post a type of language different from the default by an operation such as changing the type of language from the default language. This improves the convenience of the user because it simplifies the operation for association while allowing the type of associated language to be changed as needed.

[0355] When initially setting up as shown in Fig. 31, or through default setting operations for types of display languages such as the app display language set by the user from the My Page or the like, the language for content to be displayed, the language of posts, etc., it is possible to set the display language and the like when using the community app in advance according to user operations. Also, the types of languages displayed in the language switch icon LS that is displayed as the language for posts when the post screen of Fig. 32 is displayed may have the default app display language associated with the post information. When the post screen is displayed, the language associated at that time can be switched to other types of languages as shown in Fig. 32(B) based on operations on the language switch icon LS in steps S322 to S325 of Fig. 35 and the like. As a result, it is possible to preset the types of languages associated with posts according to user operations, and it is also possible to associate other types of languages different from the preset types of languages according to user operations. Thus, the user can associate the types of languages according to the content of the post, improving the convenience for the user.

[0356] (4-7) When initializing as shown in Fig. 31 or from the My Page etc., according to user operations, it is possible to set the default for the language to be displayed, such as the app display language or the language of the content to be displayed when using the community app. Also, in step S702 of Fig. 34, a list screen of posted content associated with language information of the type of the default language set in advance is displayed, and in steps S703 to S706, according to the request for switching the display language, it is possible to display a list screen of posted content associated with language information of the type of the switched language. For example, if the default of the app display language or the type of the language of the content to be displayed is set to Japanese, a list screen of posted content associated with Japanese as the language information in Fig. 30(A) is displayed, and by operating on the language switch icon LS and selecting English, it is possible to display a list of posted content associated with English as the language information as shown in Fig. 30(B). Thus, according to the operation from the user, it is possible to switch between the type of the default language and the type of a language different from the default and display the posts, enabling the user to communicate based on the type of language desired according to the situation.

[0357] <Modification Example> Modification examples and the like for the embodiments described above are listed below.

[0358] (Regarding Content Information) In the above-described embodiments, as content information regarding content (for example, news articles, posted information from users, etc.), content headings (60, 70, 90) in Figs. 10, 11, 27, etc. were exemplified. However, it is not limited to this, and the content information regarding the content may be, for example, explanatory information on the screen of the content itself exemplified in Fig. 13. For example, it includes the poster 71, the content 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.

[0359] (Regarding Attribute Selection Processing) In the above-described embodiment, an example in which at the time of the first login, in steps S102 to S104 of FIG. 9, a participation community and a favorite talent can be selected was described. At the time of the first login, it is not necessary to select both the participation community and the favorite talent in step S103, and it is also possible to perform an operation of not selecting either (the selected attributes are zero). Also, only one of the participation community or the favorite talent may be selected, and it may be necessary to select one of them. For example, even if a favorite talent is selected, if the user has not joined the participation community corresponding to the group 1 to which the favorite talent belongs, information regarding the favorite talent may not be extracted and displayed on the content screen. That is, even if the favorite filter 20 is turned on, the content headings of talents belonging to a group corresponding to a community that the user has not joined are not displayed. Alternatively, it may be possible to select a favorite talent only after selecting a participation community. For example, if a user does not select any participation community, it may not be possible to proceed to the screen for selecting a favorite talent.

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

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

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

[0363] (Regarding the display mode of special actions on the home screen, community screen, etc.) In the above-described embodiments, as described with reference to FIG. 11(A) and the like, for the content with comments or tap actions from special users corresponding to talents, an example was described in which a special action 79 is displayed together with the icon of the special user within the content heading 70. When the talent who performed an action on the content is the favorite talent preset by the user, the display mode of the special action 79 displayed within the content heading 70 and the like may be displayed in a mode different from the case where the talent who performed the action is not the favorite talent, and the content heading 70 itself may be displayed in a mode different from the case where the talent who performed the action is not the favorite talent. Alternatively, when the talent who performed an action on the content is the relevant talent himself / herself associated with the content, the display mode of the special action 79 displayed within the content heading 70 may be displayed in a mode different from the case where the talent who performed the action is not the relevant talent himself / herself, and the content heading 70 itself may be displayed in a mode different from the case where the talent who performed the action is not the relevant talent himself / herself. Different modes include, for example, modes with different colors, modes with different message contents, modes with different presence or absence of messages, and the like.

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

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

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

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

[0368] Also, an example has been described in which, when there are favorable actions (reactions) such as comments or tap actions from other users including special users for a post (content or comment) made by the user, a notification (display on the notification screen or push notification, etc.) is sent to the user who made the post. At this time, for example, normally, notifications are sent once an hour in a batch, but when there is an action from a special user who is a talent, or when there is an action from a special user who is a favorite talent, the notification may be sent in real time.

[0369] In addition, when the user selects their favorite talents for each unit, push notifications may be sent when content associated with any of the talents included in the unit is posted, or when content associated with the unit is posted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0384] In the above-described embodiments, from a predetermined number of users (e.g., 5 users) at level 70 or above who are the targets of "report count" in FIG. 19, for the content or comment itself that is subject to restrictions such as non-display or reporting, or for the user, an example of making the content itself non-display on each user terminal 300 of a plurality of users, or making the content posted by the restricted user non-display, has been described. For the restriction processing of the content or the like itself that is subject to these restrictions and the restriction processing of the user who posted the content or the like that is subject to restrictions, the number conditions of users in a predetermined situation (e.g., level 70 or above) where non-display or reporting has been performed may be made different. For example, from the first number of users (e.g., 5 users) at level 70 or above who are the targets of "report count", a restriction process of making the content or comment etc. that is subject to restrictions non-display to all users is performed, and from the second number (e.g., 20 people) that is more than the first number, for the user who has had non-display or reporting etc. done to the content etc. they posted, a restriction process of making all the content etc. posted by the user who has had such reporting etc. done non-display to all users may be performed.

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

[0386] Note that the user to be made non-display may not include the user himself / herself who posted the comment or content. Thereby, although the content or comment posted by oneself is reflected on the user's own terminal, for example, without an action from other users, it can be perceived (noticed) that it has become a target of restrictions.

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

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

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

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

[0391] <Regarding Reaction Notification Processing> (Regarding a Specific User) In the above-described embodiments, the specific user who satisfies the specific conditions under which the reaction is withheld until the reflection conditions are met is a special user such as the talent in FIG. 5. For users other than special users, an example in which the reaction is reflected regardless of whether the reflection conditions are met was described. However, the present invention is not limited to this. For example, even for users other than special users such as talents and users of other special accounts predetermined by the operator, general users who satisfy the conditions predetermined by the operator (for example, users with a predetermined number or more of friends, users with a predetermined number or more of followers, etc.) may also be regarded as specific users, and a setting may be possible such that the reaction is not reflected until the reflection conditions are met.

[0392] (Regarding actions reflected due to the establishment of reflection conditions) In the above-described embodiments, an example was described in which an action that is not reflected until the reflection conditions are met is a reaction such as a tap action or a comment that is a reply to posted content or the like. However, the present invention is not limited to this. An action that is not reflected to other users until the reflection conditions are met may include content (such as an article that is the target of a reaction and is assigned an article (post) ID as exemplified in the content database of FIG. 14) posted by the special user himself / herself as a poster. This makes it possible to delete the content before it is seen by other users even if the special user accidentally posts the content.

[0393] (Regarding reactions that are reflected regardless of the success or failure of the reflection conditions) In the above-described embodiment, an example was described in which information on the reaction performed by the special user is subjected to a reflection process that enables sharing with other users when it is determined in step S608 of FIG. 29 that the reflection condition is satisfied. However, not limited to this, regarding the information on the reaction performed by the special user, regardless of whether the reflection condition is satisfied or not, by the operation of the special user, the reception information reflection process according to steps S609 and S610 and the transmission of notification information to the posting source user may be performed. For example, by performing a setting operation in advance by the special user not to provide a cancelable time or a setting operation to make the screen for performing the confirmation operation non-displayed, similar to when a general user performs a reaction, if a reaction operation is performed, it may be immediately reflected (shared) and notified. Alternatively, when a cancelable time is provided as a reflection condition, a check box or the like that enables an operation to permit immediate reflection without waiting for the cancelable time is displayed on a comment posting screen or the like when reacting, and when the distribution server 100 receives the posting information of the comment checked in the check box, it may be immediately shared and notified to other users in the same manner as a general user.

[0394] (Regarding the notification mode of the reaction notified to the posting source user) In the above-described embodiment, an example was described in which the special action 79 can transmit notification information to other users so that the special action 79 is also displayed on the user terminals 300 of other users, not limited to the notification to the posting source user in step S610. However, not limited to this, the special action 79 may be displayed only for the posting source user himself / herself. Thereby, it is possible to suppress the occurrence of superiority or inferiority within the community depending on whether the user has received a reaction from the special user. Further, when the special user performs a reaction or the like, it may be notified that there has been a reaction in addition to the posting source user, but the notification mode for the posting source user may be made different from the notification mode for other users so as to be a more special effect. For example, for the posting source user, a push notification in a manner corresponding to the special user such as a voice message may be performed.

[0395] (Regarding reactions from general users) In the above-described embodiment, when the reaction to the post was a reaction from a general user, an example was described in which default notification information was transmitted to the user terminal 300 of the post source user in step S604. However, the present invention is not limited to this, and when there is a reaction from a general user, the process of step S604 may not be performed. For example, in step S603, reactions such as comments from general users are shared with other users, but push notifications to the post source user may not be performed.

[0396] Also, when executing step S604 in FIG. 29, push notifications etc. are not sent at the timing when the received information reflection process (when the reaction is shared with other users) is performed, etc., and for example, a notification pop-up etc. may be displayed at the timing of login such as when the application is started. That is, when a reaction from a special user becomes shareable, it is notified in real time, while for a reaction from a general user, it may not be notified in real time when it becomes shareable.

[0397] (Determination of the success or failure of the reflection condition on the user terminal side) In the above-described embodiment, as illustrated in FIG. 28(B), an example of managing the hold information of the special action by the distribution server 100 was described. However, the present invention is not limited to this, and the hold information may be managed by the user terminal 300 of the special user. For example, on the user terminal side, it is determined whether the reflection condition is satisfied, and when the reflection condition is satisfied, the information of the held reaction is transmitted to the distribution server 100, and the information received by the distribution server 100 can be reflected on the content screen etc.

[0398] (Regarding the received information reflection process) In the above-described embodiment, an example was described in which the received information stored in the special action hold data table of FIG. 28(B) is associated with the post (article) ID, etc. of the content data tables of FIGS. 28(A), 14, etc. when the reflection condition is satisfied, so that a display or notification indicating that there was a special action is made. However, not limited to this, depending on whether the reflection flag is set on or off in the content data table, it may be shared with other users. For example, when receiving reaction information from a special user, the received information may be associated with the content data tables such as FIG. 14 for each post ID, the reflection flag may be set to off, and when the reflection condition is satisfied, the reflection flag may be set to on and shared with other users. Also, as the non-reflection process in step S607 of FIG. 29, for example, in the data table for each post content of FIGS. 14 and 28(A), a process may be performed to delete the corresponding reaction-related information that was associated with the reflection flag off. Also, as the received information reflection process in step S608, for example, in the data table for each post content of FIGS. 14 and 28(A), the reflection flag of the corresponding reaction-related information that was associated with the reflection flag off may be set to on so as to be shared with other users.

[0399] <Regarding language association processing> (Posts that are displayed regardless of the specified language) In the above-described embodiment, an example was described in which, with reference to FIGS. 30, 34, etc., content obtained by extracting and narrowing down the language information associated with each post is displayed. The post content that can be displayed in a list may include posts that are not excluded even if they are narrowed down by the selection (specification) operation of the display language. For example, for the post content posted by a special user such as a talent who is the target of support in the community, as described with reference to FIG. 5, etc., it may be displayed regardless of what language is associated with the post content and what language is specified by the user.

[0400] In addition to the accounts of special users, for posts under certain circumstances, they may be displayed regardless of the associated language. For example, for new post content within 24 hours of being posted, it may be displayed regardless of the associated language information.

[0401] (Combined with automatic language determination) In the above-described embodiments, with reference to FIGS. 32, 35, etc., an example where a preset default language is associated at the time of posting has been described. However, it is not limited to this, and the language of the text input by automatic determination by AI may be determined, the determined language may be associated, and a proposal for the associated language may be made to the user. In this case, even if the language is automatically determined and automatically selected, it is possible to change it arbitrarily to the intended language by user operation. For example, this is because there is a possibility that a language different from the intended language may be associated due to the inclusion of characters used in a language different from the originally intended language in emoticons, etc. (for example, when emoticons used by users in the Japanese-speaking area include characters used in Russian). Note that even when information other than text, such as an image, is associated with the post information, the language may be determined from the characters included in the image or the like.

[0402] In addition, it may be managed so that the delivery server 100 can identify users for whom the language included in the posted post content information is different from the associated language information by automatic determination of the language by AI. For example, it becomes easy to identify a user who maliciously posts with a different language from the language included in the post content information and the associated language, and it becomes possible to take countermeasures.

[0403] (Regarding data of post content of the same purport by the same account) In the above-described embodiment, in the example of the content data in FIG. 33, regarding the content 70d1 in FIG. 30(A) and the content 70d2 in FIG. 30(B) which are posts with similar gists in different language texts etc. from the same official account, an example was explained in which they are managed as different article IDs such as post (article) IDs "a20" and "a21", and different language information of Japanese and English is associated with each of them. However, the data management method is not limited to this. For example, it may be managed as one post ID "a20", and post content information associated with Japanese language information (for example, mainly including Japanese text and Japanese images) and post content information associated with English language information (for example, mainly including English text and English images) are both associated with the "a20", and in response to a selection (specification) operation of the display language from the user, the post content information associated with the selected language information may be displayed. Also, when a specification to display all languages is made, among the post IDs "a20" to which the two posts are associated, the...

Claims

1. 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 those associated with a language type specified by a user from among a plurality of languages.

2. The computer, The program according to claim 1 , further comprising: a means for displaying, when a post is entered, information that can identify a type of language associated with the post.

3. The program according to claim 1 , wherein the means for displaying the list of posts displays information capable of identifying the type of language being narrowed down together with the list of posts.

4. The program according to claim 1 , wherein the means for associating the language type with the post associates the language type with the post in response to an operation by a user.

5. 2. The program according to claim 1, wherein the means for associating the language type with the post presets a predetermined language type as a candidate for association and is capable of changing the association to another language type in response to a change operation by a user.

6. 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.

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

8. 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.

9. 2. 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 designated by the user.

10. 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.

11. 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 narrows down the posts to those associated with a language type specified by a user from among a plurality of languages, and displays the list.

Images