Programs, servers, and methods

Abstract

To provide a program, a server, and a method capable of suppressing unauthorized reprinting of submissions.SOLUTION: A program causes a computer to execute: submission acceptance processing for accepting a submission from a first user; first submission display processing for displaying the submission when a second user accesses a first URL; and restriction processing for accepting, from the first user, a designation of any second user to be restricted from viewing the first user's submission. The first URL (Uniform Resource Locator) includes user information of the second user. In the restriction processing, viewing is restricted in a mode according to attributes of the second user for a user including contact information shared with the second user designated by the first user.SELECTED DRAWING: Figure 17

Description

Technical Field

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

Background Art

[0002] Patent Document 1 discloses a technique for invalidating a direct link (hotlink) to content by generating a URL that is valid for access from a certain period or / and a certain address.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] According to the technique of Patent Document 1, by generating a URL with restricted access, the viewing of a post can be restricted when there is access to the URL that has been reproduced without permission. However, this technique has little effect in suppressing the act of reproducing the URL without permission itself.

Means for Solving the Problems

[0005] (1) According to one aspect of the present invention, a program is provided. This program causes a computer to execute a post reception process for receiving a post from a first user, and a first post display process for displaying the post when a second user accesses a first URL. The first URL (Uniform Resource Locator) includes the user information of the second user.

[0006] According to such an aspect, unauthorized reproduction of a post can be suppressed.

Brief Description of the Drawings

[0007] [Figure 1] This diagram shows the overall configuration of the submission management system 1. [Figure 2] This diagram shows the hardware configuration of the server device 10. [Figure 3] This diagram shows the hardware configuration of user terminal 20. [Figure 4] This diagram shows the functional configuration of the control unit for each device. [Figure 5] This figure shows an example of a user information database. [Figure 6] This figure shows an example of a user submission database. [Figure 7] This is an activity diagram showing an example of the posting process. [Figure 8] This figure shows an example of a page for setting restrictions. [Figure 9] This is an activity diagram showing an example of a browsing process. [Figure 10] This figure shows an example of the displayed list of posts page. [Figure 11] This figure shows an example of the displayed notification content. [Figure 12] This figure shows an example of the displayed notification content. [Figure 13] This figure shows an example of the displayed list of posts page. [Figure 14] This is an activity diagram showing an example of restriction processing. [Figure 15] This figure shows an example of a search page that is displayed. [Figure 16] This figure shows an example of the browsing restriction settings page that is displayed. [Figure 17] This diagram shows the overall structure of the post management system. [Figure 18] This figure shows an example of a restriction pattern table. [Modes for carrying out the invention]

[0008] Embodiments of the present invention will be described below with reference to the drawings. The various features shown in the embodiments below can be combined with each other.

[0009] Incidentally, the program for implementing the software appearing in this embodiment may be provided as a non-transitory computer-readable medium, or it may be provided so that it can be downloaded from an external server, or it may be provided so that the program is launched on an external computer and its functions are realized on a client terminal (so-called cloud computing).

[0010] Furthermore, in this embodiment, "part" may include, for example, hardware resources implemented by circuits in a broad sense, and the information processing of software that can be specifically realized by these hardware resources. In addition, various types of information are handled in this embodiment, and these types of information can be represented, for example, by the physical values ​​of signal values ​​representing voltage and current, the high or low values ​​of signal values ​​as a set of binary bits composed of 0s or 1s, or by quantum superposition (so-called qubits), and communication and calculations can be performed on circuits in a broad sense.

[0011] Furthermore, a circuit in a broad sense is a circuit realized by combining at least a suitable combination of circuits, circuits, processors, and memory. In other words, it includes application-specific integrated circuits (ASICs), programmable logic devices (for example, simple programmable logic devices (SPLDs), complex programmable logic devices (CPLDs), and field programmable gate arrays (FPGAs)), etc.

[0012] 1. Hardware Configuration In this section, the hardware configuration of the application-related system according to this embodiment will be described.

[0013] FIG. 1 is a diagram showing the overall configuration of the posting management system 1. In FIG. 1, an overview of each device included in the posting management system 1, the users who use those devices, and the information exchanged between the devices is shown. Each overview will be described as needed while referring to other figures.

[0014] The posting management system 1 is a system that executes processes for managing postings in a so-called SNS (Social Networking Service), which is a service that accepts postings by users and enables other users to view those postings. In this embodiment, the posting management system 1 provides all functions of the SNS to users. The posting management system 1 includes a communication line 2, a server device 10, and user terminals 20-1, 20-2, 20-3,... (hereinafter referred to as "user terminal 20" when not distinguishing them).

[0015] The communication line 2 includes the Internet and the like, and mediates the exchange of data between devices connected to the private line. The server device 10 and each user terminal 20 are connected to the communication line 2 either wired or wirelessly. The user terminals 20-1, 20-2, 20-3,... are terminals used by the SNS users U11, U12, U13,... (hereinafter referred to as "user U10" when not distinguishing them). The server device 10 is an information processing device that executes processes related to the SNS.

[0016] FIG. 2 is a diagram showing the hardware configuration of the server device 10. The server device 10 includes a control unit 11, a storage unit 12, a communication unit 13, and a bus 14. The bus 14 electrically connects each part included in the server device 10.

[0017] (Control Unit 11) The control unit 11 is, for example, a central processing unit (CPU) not shown. The control unit 11 is a computer that realizes various functions related to the submission management system 1 by reading predetermined programs stored in the memory unit 12. In other words, information processing by software stored in the memory unit 12 can be specifically realized by the control unit 11, which is an example of hardware, and can be executed as each functional unit included in the control unit 11. These will be described in more detail in the next section. Note that the control unit 11 is not limited to being a single unit, and may be implemented with multiple control units 11 for each function, or a combination thereof.

[0018] (Storage unit 12) The memory unit 12 stores various types of information as defined above. This can be done, for example, as a storage device such as a solid-state drive (SSD) that stores various programs related to the post management system 1 executed by the control unit 11, or as memory such as random access memory (RAM) that stores temporarily necessary information (arguments, arrays, etc.) related to program calculations. The memory unit 12 stores various programs and variables related to the post management system 1 executed by the control unit 11.

[0019] (Communications Section 13) The communication unit 13 is configured to transmit various electrical signals from the server device 10 to external components. The communication unit 13 is also configured to receive various electrical signals from external components to the server device 10. More preferably, the communication unit 13 has a network communication function, enabling the communication of various information between the server device 10 and external devices via the communication line 2.

[0020] Figure 3 shows the hardware configuration of the user terminal 20. The user terminal 20 comprises a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, an output unit 25, and a bus 26. The bus 26 electrically connects each part of the user terminal 20. The control unit 21, storage unit 22, and communication unit 23 are similar hardware to the control unit 11, storage unit 12, and communication unit 13 shown in Figure 2, although their specifications and models may differ.

[0021] (Input section 24) The input unit 24 has keys, buttons, a touchscreen, a mouse, etc., and accepts input from the user. (Output section 25) The output unit 25 has a display and a speaker, and displays visual information such as screens, images, icons, and text on its display surface in a manner that is visible to the user, and outputs sound including voice.

[0022] 2. Functional Configuration This section describes the functional configuration of this embodiment. As mentioned above, information processing by software stored in the memory unit of each device is concretely realized by the control unit, which is an example of hardware, and each functional unit included in the control unit can be executed. Hereafter, a user U10 who makes a post on SNS will be referred to as the "poster," and a user U10 who views a post will be referred to as the "viewer."

[0023] Figure 4 shows the functional configuration of the control unit of each device. The control unit 11 of the server device 10 includes a server display processing unit 111, a user storage unit 112, an authentication unit 113, a posting processing unit 114, a posting storage unit 115, a URL generation unit 116, an access reception unit 117, a URL input reception unit 118, a user extraction unit 119, and a viewing restriction unit 120.

[0024] The server display processing unit 111 performs processing to display the content of SNS posts on the user terminal 20. The user storage unit 112 stores a user information database that stores information about users U10 whose user information has been registered as SNS users. Note that SNS users include users U10 whose user information has been registered (hereinafter referred to as "members") and users U10 whose user information has not been registered (hereinafter referred to as "non-members").

[0025] Figure 5 shows an example of a user information database. In the example in Figure 5, the user storage unit 112 stores a user information database G1 that associates username, user ID, password, telephone number, whether or not telephone number authentication was performed, and follower information. The username is the name that the user registers and uses within the SNS, and is also called the account name. The username can be the user's real name, but generally, a nickname that the user wants to use within the SNS is registered. In the example in Figure 5, the usernames of members "User U11", "User U12", "User U13", "User U15", "User U16", "User U18", ... are registered. Note that "User U14" and "User U17", for which no username is registered, are assumed to be non-members.

[0026] The user ID and password are login information used when user U10 begins using the posting management system 1. In the example in Figure 5, for the sake of clarity, usernames such as "User U11," "User U12," etc., are associated with user IDs such as "UID011," "UID012," etc., and stored accordingly. In addition to user authentication using user ID and password (referred to as password authentication), the posting management system 1 also uses telephone number authentication.

[0027] Telephone number authentication is a mechanism that sends a temporary password to a registered telephone number and authenticates the user when that temporary password is entered. In the posting management system 1, the telephone number and whether or not telephone number authentication is enabled can be arbitrarily set by user U10. In the example in Figure 5, both user U12 and user U16 are associated with the telephone number "080-bbbb-bbbb", which indicates that one user U10 has registered two accounts with one telephone number.

[0028] A follower is when one member follows another member. Following is when a viewer registers in advance the posts of the posters whose posts they frequently view. In the example in Figure 5, user IDs such as UID012, UID013, UID016, and UID019 are stored as followers of user U11, indicating that users U12, U13, U16, and U19 are followers of user U11.

[0029] The authentication unit 113 performs user authentication when user U10 uses the SNS. The authentication unit 113 performs password authentication for all users and also performs telephone number authentication for users who have been set up. The posting processing unit 114 executes posting-related processing (posting processing) based on the operations of the authenticated user U10 on the user terminal 20. The posting storage unit 115 stores a posting information database that stores information used in the posting processing.

[0030] Figure 6 shows an example of a post information database. In the example in Figure 6, the post storage unit 115 stores a post information database G2 that associates post ID, post data, author ID, viewing restriction settings, viewer ID, URL, and block settings. The "Post ID" stores identification information assigned to each post. The "Post Data" stores, for example, HTML data (Hyper Text Markup Language data) and image data that describe the web page on which the post content is published. The "Author ID" stores the user ID of the person who posted the post.

[0031] The "Viewing Restriction Settings" section stores setting data indicating the viewing restrictions for the post. Viewing restrictions may be set for each viewer. In that case, the "Viewer ID" field stores the user ID of each viewer. The "URL" field stores the URL (Uniform Resource Locator) generated by the URL generation unit 116, which will be described later. The "Block Flag" field stores a flag indicating who the poster will block from seeing their post. Details of each post information will be explained in more detail later.

[0032] The URL generation unit 116 generates two URLs, for example, one that includes the viewer's user information (in Figure 6, for example, the URL "xxx.xxxx.UID012" associated with the post ID "D001" and viewer ID "UID012"), and another that does not include the viewer's user information (in Figure 6, for example, the URL "yyy.yyyy.yyyy" associated with the post ID "D002"). The details of these URLs will be explained in more detail later. The access reception unit 117 accepts access to the generated URLs. The server display processing unit 111 works in cooperation with the terminal display processing unit 211 to display the post corresponding to the accessed URL on the user terminal 20.

[0033] A poster may discover that their post has been published without their permission on a webpage or other site other than the social networking service where they originally posted it. The URL input reception unit 118 accepts the input of the URL to which such unauthorized reposted posts are accessed. The user extraction unit 119 extracts user information contained in the input URL. The access restriction unit 120 executes a restriction process to restrict the viewing of the post by user U10, indicated by the extracted user information.

[0034] Returning to Figure 4, the control unit 21 of the user terminal 20 will be described. The control unit 21 of the user terminal 20 comprises a terminal display processing unit 211, an operation reception unit 212, a post generation unit 213, an upload unit 214, and a post access unit 215.

[0035] The terminal display processing unit 211 performs the process of displaying the posted content on the display means (display) of the user terminal 20. The terminal display processing unit 211 works in cooperation with the server display processing unit 111 of the server device 10 to display the text and images, etc., that constitute the SNS post content in the display area of ​​the browser or dedicated SNS application. The server display processing unit 111 sends display data (e.g., an HTTP response) indicating the text and images to the user terminal 20, and the terminal display processing unit 211 displays the text and images, etc., indicated by the received display data.

[0036] The operation reception unit 212 receives operations from user U10. The post generation unit 213 generates post data based on user U10's operations. The upload unit 214 uploads the generated post data to the server device 10. Thus, post data can be generated on the server device 10 side based on user U10's operations, or it can be generated on the user terminal 20 side based on user U10's operations and then uploaded to the server device 10.

[0037] The post access unit 215 accesses the post indicated by the URL specified by user U10 when U10 performs an operation to specify the URL of the post that U10 wishes to view. The terminal display processing unit 211 displays the post indicated by the post data sent from the server device 10 in response to this access.

[0038] 3. Information Processing This section describes the information processing that the program causes the computer to execute in this embodiment. The posting management system 1 performs management processing to manage posts on the social networking service (SNS). The management processing includes posting processing, in which posters make posts; viewing processing, in which viewers view posts; and restriction processing, in which posters restrict others from viewing their posts.

[0039] Figure 7 is an activity diagram showing an example of the posting process. In the example in Figure 7, the user terminal 20 is used by the poster. First, at A11, the user terminal 20 displays the SNS login screen via the terminal display processing unit 211. As mentioned above, the display of the login screen, etc., is performed collaboratively by the server display processing unit 111 of the server device 10 and the terminal display processing unit 211 of the user terminal 20, but in the following description, it will be simplified and explained as the processing of the terminal display processing unit 211.

[0040] Next, at A12, the user terminal 20 receives a login operation from user U10 via the operation reception unit 212. The login operation is, for example, the operation of displaying the SNS login screen and entering the user ID and password assigned to user U10 as login information. The operation reception unit 212 transmits the login information entered on the login screen to the server device 10.

[0041] In A13, the server device 10 authenticates the user based on the transmitted login information using the authentication unit 113. For example, if the transmitted login information is stored in the user information database G1 stored in the user storage unit 112, the authentication unit 113 authenticates user U10, who is associated with that login information, as a user of the SNS provided by the server device 10.

[0042] Furthermore, if user U10 has set up phone number authentication, the authentication unit 113 also sends a temporary password to the registered phone number. The operation reception unit 212 of the user terminal 20 accepts the input of the temporary password as a login operation and sends the received temporary password along with the user ID to the server device 10. The authentication unit 113 authenticates the user if the user ID associated with the phone number that sent the received temporary password matches the user ID sent along with the temporary password. Once the server device 10 has authenticated the user, it notifies the user terminal 20 of the authentication result.

[0043] Once the user is authenticated, the user terminal 20 displays the SNS top page at A14 via the terminal display processing unit 211. In the example in Figure 7, user U10 performs an operation on the top page to open the posting page for making a post. As a result of this operation, the user terminal 20 displays the posting page at A21 via the terminal display processing unit 211. Next, the user terminal 20 receives a posting operation at A22 via the operation reception unit 212 to generate a post. Posting operations include, for example, operations to input text to post, operations to specify images to post, operations to specify sounds to post, and operations to specify videos to post.

[0044] Next, at A23, the user terminal 20 displays a restriction setting page via the terminal display processing unit 211. The restriction setting page is a page for setting restrictions on access to generated posts.

[0045] Figure 8 shows an example of a page for setting restrictions. In the example in Figure 8, the settings for the scope of publication C1 and other settings C2, and the post button B1 are shown. The setting for the scope of publication C1 corresponds to the "scope of publication" setting in "Viewing Restriction Settings" shown in Figure 6. In the setting for the scope of publication C1, one of five settings C11, C12, C13, C14 and C15 can be selected: "Visible to all members", "Visible to followers only", "Visible to mutual followers only", "Private", and "Visible to non-members".

[0046] As mentioned above, "members" and "non-members" can be distinguished by whether or not their user information is registered in the user information database. "Followers only" in this case means only user U10 who follows the poster. For example, if the poster is user U11, only users U12, U13, U16, and U19, whose user IDs are listed in user U11's follower information in the user information database G1, will be able to view the post.

[0047] Mutual followers are users U10 who follow each other. In the example in Figure 6, for example, users U11 and U12 are mutual followers because their user IDs are included in each other's follower information. "Private" indicates that only the poster can view the content, and even members cannot view it. "Public to non-members" indicates that both members and non-members can view the content.

[0048] Other settings in C2 include setting C21, which changes the URL of this post page for each viewer; setting C22, which makes it visible only to users with verified phone numbers; and setting C23, which blocks all users registered with the same phone number. When these settings are checked, the processing will be carried out in accordance with the settings. Settings C21, C22, and C23 will be explained in detail later, along with explanations of the related processes.

[0049] Note that all other settings in C2 assume that posts are publicly accessible to members and that viewer user information is registered. Therefore, if "Private" or "Public to Non-Members" is set in the access range setting C1, these settings cannot be applied. In other words, if access range setting C1 is set as the first viewing restriction, then other settings C2 can be applied as the second viewing restriction. This two-stage viewing restriction allows for greater flexibility in restricting access compared to a single-stage restriction.

[0050] The user terminal 20 receives the restriction setting operation at A24 via the operation reception unit 212, and the operation to the post button B1 at A25 is accepted as a post and setting confirmation operation. The operation reception unit 212 sends confirmation data indicating the post generation operation received at A22 and the setting operation received at A24 to the server device 10. At A26, the server device 10 stores the transmitted confirmation data via the post storage unit 115 and executes a post acceptance process to accept a post from the first user.

[0051] In A27, the server device 10 generates post data based on the post generation operation indicated by the confirmed data transmitted by the post generation unit 213. The post data includes HTML data that describes the web page showing the content of the post, text data, image data, sound data, and video data included in the post, a post ID assigned to each post, a timestamp indicating the date and time of the post, and tag information indicating the attributes of the post. The tag information is information that indicates, for example, the type of post (presence or absence of images, presence or absence of videos, etc.), the time of the post (new, etc.), or the attributes of the poster (hobbies, age, background, etc.), and is set, for example, by the poster themselves.

[0052] Furthermore, the post generation unit 213 generates setting data indicating restrictions on viewing the post based on the setting operations indicated by the confirmed data. The setting data is data indicating the settings checked by the poster from the setting C1 of the public access range and other settings C2 shown in Figure 8. Then, at A28, the server device 10 stores the generated post data and setting data in the post information database G2 by the post storage unit 115. Through the above posting process, the post created by user U10 is stored in the server device 10 and becomes viewable by other users U10.

[0053] The generation of post data and setting data may also be performed by the post generation unit 213 of the user terminal 20. In this case, the post generation unit 213 generates post data based on the post generation operation and setting data based on the setting operation. Then, in A25, the upload unit 214 uploads the post data and setting data to the server device 10. Regardless of whether the post data is generated on the server device 10 or the user terminal 20, the post ID is shared between both devices, and each post is identified by the shared post ID. Furthermore, the post data and setting data may be generated at the same time when the confirmation operation is performed, as in the example in Figure 7, or they may be generated at different times when the post generation operation is performed and when the setting operation is performed, respectively.

[0054] Figure 9 is an activity diagram showing an example of the browsing process. In the example in Figure 9, user terminal 20 is a terminal used by the viewer. The viewer may be a member or not. If the viewer is a member, first, processes A11 to A14 are performed as in Figure 7, the viewer is authenticated, and the SNS top page is displayed. If the viewer is not a member, an operation such as accessing the URL of the SNS top page is performed, and only process A14 is performed, and the SNS top page is displayed.

[0055] In the example shown in Figure 9, the viewer performs a list view operation on the top page to open the list of posts they wish to view. This list view operation involves specifying the conditions for the posts they wish to view. These conditions could include, for example, the type of post, the time of posting, or the attributes of the poster, and can be determined based on tag information.

[0056] The user terminal 20 receives a request to display a list of posts via the operation reception unit 212 at A31. The operation reception unit 212 sends list request data to the server device 10, which indicates the authenticated viewer's user ID, the conditions for posts specified by that viewer, and a request to display a list page of posts that meet those conditions.

[0057] In A32, the server device 10 uses the URL generation unit 116 to refer to the post data stored in the post information database G2 shown in Figure 6 and identifies posts that meet the conditions of the post indicated by the received list request data. Next, in A33, the server device 10 uses the URL generation unit 116 to generate a URL for accessing each identified post. The URL generation unit 116 refers to the post information database G2 and checks whether the setting C21 (setting to change the URL for each viewer) shown in Figure 8 is checked in the identified post.

[0058] The URL generation unit 116 generates a URL containing the viewer's user information for posts where setting C21 is checked. This user information includes at least information unique to each user, such as a user ID. Such a URL containing viewer-specific user information will vary for each viewer. In this embodiment, the URL generation unit 116 encrypts the user information and generates a URL containing the encrypted user information. Any well-known encryption technology can be used to encrypt the user information.

[0059] For posts where setting C21 is not checked, the URL generation unit 116 simply generates a URL (hereinafter referred to as the "storage URL") that indicates the path to the storage location of the HTML data describing the web page displaying the post content and the file name of said HTML data. The storage URL thus generated will be a URL that does not include the viewer's user information.

[0060] Furthermore, if a viewer views the list several times, the list may include posts for which URLs have already been generated. In this case, the URL generation unit 116 does not need to generate URLs again for URLs that have already been generated. This reduces the processing load on the server device 10 when generating URLs compared to when URLs are always generated.

[0061] Furthermore, the URL generation unit 116 may generate both the storage URL and a URL containing the viewer's user information for all posts, regardless of whether setting C21 (a setting that changes the URL for each viewer) is checked or not. In that case, it would not be necessary to regenerate the URL if setting C21 is changed. On the other hand, if only the storage URL and a URL containing the viewer's user information are generated depending on whether setting C21 is checked or not, as described above, the processing load on the server device 10 when generating URLs can be reduced compared to generating both.

[0062] The poster of a post is an example of a "first user" of the present invention, and the viewer of a post is an example of a "second user" of the present invention. A URL that indicates the destination for the first user's access to a post and also includes the user information of the second user is an example of a "first URL" of the present invention. Furthermore, a URL that indicates the destination for the first user's access to a post and does not include the user information of the second user is an example of a "second URL" of the present invention. The second URL is used to access a post when the first user has made a predetermined setting (a setting that does not check setting C21).

[0063] In A34, the server device 10 generates a post list page using the server display processing unit 111. For each post identified in A32, the server display processing unit 111 generates a post list page associating it with the URL generated in A33. The server display processing unit 111 sends the generated post list page to the user terminal 20. In A35, the user terminal 20 displays the transmitted post list page using the terminal display processing unit 211.

[0064] Figure 10 shows an example of a displayed list of posts page. In the example in Figure 10, user U11 is the viewer, and list page E10 is displayed, which includes posts D13-xx, D19-xx, D15-xx, and D18-xx posted by users U13, U19, U15, and U18. Post D13-xx indicates the xxth post by user U13. The URL for post D13-xx is "http: / / Domain / U13-xx / (U12 encrypted)".

[0065] (U12 encryption) indicates the encrypted string of the user ID of user U12, "U12". Therefore, when the encrypted part of the URL of post D13-xx is decrypted, it becomes the URL "http: / / Domain / U13-xx / U12". This "Domain / U13-xx / U12" indicates the path for user U12 to the post data of post D13-xx. The URL of post D13-xx will be "http: / / Domain / U13-xx / (U15 encryption)" if the viewer is user U15, and "http: / / Domain / U13-xx / (U18 encryption)" if the viewer is user U18.

[0066] On list page E10, the URL for post D15-xx includes the encrypted user ID of user U11, as in "http: / / Domain / U15-xx / (U12 encrypted)". On the other hand, the URL for post D19-xx is "http: / / Domain / U19-xx / Doc", and the URL for post D18-xx is "http: / / Domain / U18-xx / Doc", and these do not include the encrypted user ID of user U12. These URLs are generated even when the viewer is user U10, not user U12.

[0067] As shown in the example in Figure 10, posts D13-xx and D15-xx are configured by their authors, users U13 and U15, to check setting C21, meaning the URL of the post page is changed for each viewer. On the other hand, posts D18-xx and D19-xx are configured by their authors, users U18 and U19, to not check setting C21, meaning the URL of the post page is not changed for each viewer.

[0068] The viewer performs a specification operation to specify the post they want to view. For example, the viewer may select a post from the displayed list of posts as a specification operation. Alternatively, the viewer may directly enter the URL of the post they want to view as a specification operation. The URL may be entered by typing the string on the keyboard or by copying and pasting. At A36, the user terminal 20 receives the viewer's operation to specify a post via the operation reception unit 212.

[0069] At A37, the user terminal 20 generates post request data (e.g., an HTTP request) using the URL of the specified post, via the post access unit 215, requesting the submission of the post it wishes to view, and sends the generated post request data to the server device 10. If the viewer is a member and logged in, the post access unit 215 sends the post request data including the viewer ID (viewer's user ID) used for login; if the viewer is not a member and not logged in, it sends post request data without the viewer ID.

[0070] In A41, the server device 10 determines whether the URL indicated by the transmitted submission request data contains user information, based on the access reception unit 117. For example, in the submission management system 1, if the structure of the URL of the submission data does not contain user information, it is stipulated that "Doc" is placed in the last part of the URL separated by " / ", as shown in Figure 10 for submissions D19-xx and D19-xx.

[0071] In that case, the access reception unit 117 determines that if the last part of the URL is "Doc", the URL does not contain user information, and if the last part of the URL is not "Doc", it determines that the URL contains user information. In that case, the server device 10 extracts user information from the URL using the user extraction unit 119 at A42. The user extraction unit 119 decrypts the encrypted string represented in the last part of the URL and extracts the decrypted string as user information.

[0072] Next, if the transmitted submission request data includes a viewer ID, the server device 10, in A43, compares the extracted user information with the viewer ID using the access restriction unit 120. If the user indicated by the extracted user information differs from the user indicated by the viewer ID, the access restriction unit 120 sends notification data to the user terminal 20 indicating that access is not permitted. In A44, the user terminal 20, using the terminal display processing unit 211, displays the notification content indicated by the transmitted notification data.

[0073] Figure 11 shows an example of the displayed notification content. In the example in Figure 11, notification H11 is shown when user U10, other than user U11, attempts to access user U15's post D15-xx using a URL reposted by user U11. Notification H11 indicates the reason why post D15-xx cannot be viewed with the string "Caution: The accessed URL is for another user and cannot be used."

[0074] If the user information extracted in A43 matches the user indicated by the viewer ID, that is, if the viewer has accessed using their own correct URL, the server device 10 executes the process in A45. Also, if it is determined in A41 that the user information is not included, the server device 10 executes the process in A45.

[0075] At A45, the server device 10 uses the access restriction unit 120 to read the access settings associated with the post indicated by the submission request data from the submission information database G2. Then, at A46, the server device 10 uses the access restriction unit 120 to refer to the user information database G1 and the submission information database G2 to determine whether or not access is permitted.

[0076] When setting C11 (public to all members) as shown in Figure 8 is enabled, the viewing restriction unit 120 determines that viewing is permitted if the viewer ID is included in the posting request data, as this indicates the viewer is a member. If the viewer ID is not included in the posting request data, it determines that viewing is not permitted as this indicates the viewer is not a member.

[0077] If setting C12 (visible only to followers) is enabled, the access restriction unit 120 refers to the poster's follower information in the user information database G1 and determines that viewing is permitted if the viewer is a follower of the poster, and that viewing is not permitted if the viewer is not a follower of the poster.

[0078] When setting C13 (visible only to mutual followers) is enabled, the access restriction unit 120 refers to the follower information of both the poster and the viewer in the user information database G1. If the viewer is a follower of the poster and the poster is a follower of the viewer, it determines that the content is viewable. If the viewer is not a follower of the poster or the poster is not a follower of the viewer, it determines that the content is not viewable.

[0079] When setting C14 (private) is enabled, the viewing restriction unit 120 determines that viewing is permitted if the viewer is the poster themselves, and that viewing is not permitted if the viewer is a user U10 other than the poster. When setting C15 (open to non-members) is enabled, the viewing restriction unit 120 determines that viewing is permitted in all cases.

[0080] The access restriction unit 120 determines that access is permitted if setting C21 (setting to change the URL for each viewer) is enabled, because it has always gone through processing A42 and A43 to confirm that the viewer is using the correct URL.

[0081] If setting C22 (accessible only to users with verified phone numbers) is enabled, the access restriction unit 120 checks the user information database G1 to see if the viewer's phone number is verified. If phone number verification is enabled, it determines that the viewer is allowed because phone number verification must have been performed during login. If phone number verification is disabled, it determines that the viewer is not allowed because phone number verification must not have been performed during login.

[0082] If setting C23 (block all users registered with the same phone number) is enabled, the access restriction unit 120 first refers to the viewer's phone number in the user information database G1 and identifies other user IDs associated with the same phone number. Then, the access restriction unit 120 refers to the posting information database G2 and determines that viewing is possible if none of the identified user IDs have a block flag set, and that viewing is not possible if even one of the identified user IDs has a block flag set.

[0083] The access restriction unit 120 will make the same determination of whether access is denied in A46, regardless of whether the access is via the first URL which includes the viewer's user information or the second URL which does not include the viewer's user information. If the server device 10 determines that access is denied in A46, it will send notification data indicating that access is denied to the user terminal 20. In A47, the user terminal 20 will display the notification content indicated by the transmitted notification data using the terminal display processing unit 211.

[0084] Figure 12 shows an example of a displayed notification. In the example in Figure 12, notification H12 is shown to a viewer who has been unable to view post D19-xx by user U19 due to viewing restrictions. Notification H12 indicates the reason why post D19-xx cannot be viewed with the string, "This post has viewing restrictions set so that only followers can view it, and therefore you cannot view it." By notifying the viewer of the reason why they cannot view the post, they can take action to view it (in this case, by following the poster).

[0085] If the server device 10 determines that the content is viewable at A46, at A48, the server display processing unit 111 reads the posted data requested by the viewer and sends it to the user terminal 20. At A49, the user terminal 20 displays the post indicated by the transmitted posted data using the terminal display processing unit 211.

[0086] As described above, when a second user (viewer) accesses the first URL, the server device 10 executes a first post display process that displays the first user's (poster's) post. As mentioned above, the first URL is a URL containing the second user's user information, for example, the URLs of posts D12-xx and D15-xx shown in Figure 10. In other words, when a second user views a post made by the first user, the server device 10 executes a post display process that makes the post viewable on the second user's user terminal 20.

[0087] The server device 10 makes the posts available for display by accessing a first URL that indicates the storage location of the first user's posts and the identification information (user ID) of the second user. In this configuration, if the URL of a post is reposted, the user information contained in the URL can be used to identify who reposted it, thus suppressing unauthorized reposting of posts compared to when the post display process via the first URL is not performed.

[0088] Furthermore, as described above, the server device 10 does not display the post when someone other than the second user accesses the first URL. As a result, even if the URL of the post is reposted, other users will not be able to view the post from that URL, making reposting pointless and further deterring unauthorized reposting of posts.

[0089] Furthermore, the server device 10 is configured to perform a second post display process, which displays the first user's (poster's) posts when a second user (viewer) accesses the second URL. As mentioned above, the second URL is a URL that does not include the second user's user information, and is, for example, the URLs of posts D18-xx and D19-xx shown in Figure 10. The server device 10 performs either the first post display process or the second post display process. The server device 10 selects between the first post display process and the second post display process based on the first user's settings. In this embodiment, the first user's settings are those that do not check setting C21 shown in Figure 10. With this configuration, the poster can manage the scope of publication of their posts.

[0090] In the example shown in Figure 10, viewers cannot know whether a post is viewable or not unless they perform the action to view it. Therefore, the server display processing unit 111 may display a message that makes it impossible to select posts that are not viewable. Figure 13 shows an example of a displayed list of posts. In the example in Figure 13, posts D19-xx and D15-xx are deemed unavailable for viewing among posts D13-xx, D19-xx, D15-xx, and D18-xx.

[0091] In this case, the server display processing unit 111 overlays an unviewable image N1 on posts D19-xx and D15-xx that are not viewable, as shown in Figure 13(a). Alternatively, as shown in Figure 13(b), the server display processing unit 111 may display only the viewable posts D13-xx and D18-xx, without displaying the unviewable posts D19-xx and D15-xx. By displaying in this way, viewers can avoid the unnecessary effort of attempting to view posts that they cannot access.

[0092] Figure 14 is an activity diagram showing an example of a restriction process. In the example in Figure 14, user U10 is a poster who has discovered that the URL of their post, which has been configured with setting C21 (a setting that changes the URL of the post page for each viewer) as shown in Figure 8, has been reposted without permission on a webpage other than the SNS. In the restriction process, steps A11 to A14 are performed as in Figure 7, and user U10 is authenticated and the SNS top page is displayed.

[0093] In the example shown in Figure 14, user U10 performs an operation on the top page to display a search page for user information contained in the URL. At A51, the user terminal 20 displays the search page using the terminal display processing unit 211.

[0094] Figure 15 shows an example of a displayed search page. In Figure 15(a), a search page E20 is shown, which includes the text "Search for viewers from the URL of the post page," a URL input field F21, a search button B21, and a search results display field F22. In the example in Figure 15(a), the URL of post D13-xx shown in Figure 10, "http: / / Domain / U13-xx / (U12 encrypted)," is entered. In other words, the user U13, the poster of post D13-xx, entered this URL.

[0095] When the search button B21 is operated in the state shown in Figure 15(a), the user terminal 20 receives input of the URL displayed in the input field F21 via the operation reception unit 212 at A52. The operation reception unit 212 generates search data indicating the poster's user ID and the URL to be searched, and sends the generated search data to the server device 10. Upon receiving the search data, the server device 10 receives input of the URL of the post indicated by the received search data via the URL input reception unit 118 at A53.

[0096] Next, at A54, the server device 10 uses the URL input reception unit 118 to determine whether the person who entered the received URL is the poster. The URL input reception unit 118 determines that the URL was entered by the poster if, for example, the poster ID associated with the entered URL in the posting information database G2 matches the user ID indicated by the received search data. In addition to this method, for example, as shown in Figure 10, if the poster's username is indicated in the path information included in the URL, the URL input reception unit 118 may also determine that the URL was entered by the poster if the username indicated by the path included in the entered URL matches the poster's username indicated by the received URL data.

[0097] If the URL input receiving unit 118 determines that the searcher is not the poster, it sends notification data to the user terminal 20 indicating that user information cannot be extracted. At A55, the user terminal 20 displays the notification that extraction is not possible, as indicated by the received notification data, using the terminal display processing unit 211.

[0098] If the server device 10 determines that the searcher is the poster, the user extraction unit 119 extracts user information from the input URL at A56. The user extraction unit 119 extracts user information in the same manner as described above. In other words, in this embodiment, the user extraction unit 119 extracts the information represented in the last section of the URL separated by " / " (in the example of Figure 15(a), (U12 encrypted)) as user information.

[0099] In this embodiment, the user extraction unit 119 extracts encrypted user information and then decrypts it to extract the original user information before encryption. In the example shown in Figure 15(a), the user extraction unit 119 extracts the decrypted user ID "U11" and sends this user ID as the extraction result to the user terminal 20. At A57, the user terminal 20 displays the transmitted extraction result, which is the user information, using the terminal display processing unit 211.

[0100] In the example shown in Figure 15(a), the username "User U11" is displayed as the result in the extraction result display area F22. The search page E20 includes a settings button B2 for setting access restrictions. When the settings button B2 is pressed, the user terminal 20 displays the access restriction settings page at A61 via the terminal display processing unit 211.

[0101] The username may be hidden from the extraction results. In that case, the terminal display processing unit 211 will display a search page E21 that shows only the string "The reposter has been identified!" F23 as the extraction result, instead of the extraction result display field F22, as shown in Figure 15(b). The search page E21 includes a copy button B3 for copying user information that is not displayed (for example, the viewer's user ID). When the copy button B3 is pressed, the user terminal 20 copies the extracted user information and, at A61, the terminal display processing unit 211 displays the access restriction settings page. Alternatively, the user information may be displayed as the extraction result and the displayed user information may be copied. The copying method may be by operating the copy button B3, or by selecting the user information with a mouse or the like and performing the copy operation.

[0102] Figure 16 shows an example of a displayed access restriction settings page. In the example in Figure 16(a), the access restriction settings page E30 is shown, which includes a display field F31 for the poster, a display field F32 for the viewer, access restriction settings C33 and C34, and a confirmation button B4. The poster's username (user U13 in the example in Figure 16) is displayed in display field F31, and the viewer's username (user U12 in the example in Figure 16) is displayed in display field F32.

[0103] The poster (user U13 in the example of Figure 16(a)) looks at the displayed user information of the viewer (user U12 in the example of Figure 16(a)) and, if necessary, for example, because the user has reposted content without permission several times in the past, they can take action to restrict user U12's access. In the example of Figure 15, if user information is copied as described in Figure 15(b) (regardless of whether the user information is displayed or not), the operation reception unit 212 accepts an operation to paste the copied user information into the display field F32 that shows the viewer's username. Then, the terminal display processing unit 211 displays the pasted user information in the display field F32, as shown in Figure 16(b).

[0104] Setting C33 is a setting that prohibits viewers from viewing their own posts. Setting C34 is a setting that prohibits users registered with the same phone number as the viewer from viewing their own posts. At A62, the user terminal 20 receives an operation from the operation reception unit 212 to check these settings and press the confirmation button B4 as a viewing restriction operation. The operation reception unit 212 sends restriction data indicating the restricted settings based on the received operation to the server device 10. At A63, the server device 10, using the viewing restriction unit 120, executes a restriction process that reflects the content of the viewing restriction indicated by the transmitted restriction data.

[0105] If setting C33 is checked, the access restriction unit 120 performs a restriction process that sets all block flags associated with the poster's user ID (poster ID) and the viewer's user ID (viewer ID) in the posting information database G2. As a result, in A46 shown in Figure 9, if the viewer is user U12, the access restriction unit 120 will determine that not only the posts by user U13 that user U12 has reposted (in the examples of Figures 10 and 15, user U13's posts D13-xx) but also other posts by user U13 (posts other than user U13's posts D13-xx) are not viewable.

[0106] If setting C34 is checked, the access restriction unit 120 performs the following restriction process: In addition to setting all block flags associated with the poster's user ID (poster ID) and the viewer's user ID (viewer ID) in the posting information database G2, it also sets all block flags for user IDs associated with the same phone number as the viewer's user ID (viewer ID) in the user information database G1, treating those user IDs as viewer IDs.

[0107] As a result, in A46 shown in Figure 9, if the viewer is user U12, the viewing restriction unit 120 will determine that user U13's posts are not viewable not only when the viewer logs in as user U12, but also when the viewer logs in as user U16, who has the same phone number as user U12 (in the example in Figure 5, "080-bbbb-bbbb").

[0108] As described above, the server device 10 executes a URL reception process (process A53 shown in Figure 14) that accepts input of a first URL that indicates the access destination of the first user's (poster's) post and also contains the user information of the second user (viewer). The server device 10 also executes an extraction process (process A56 shown in Figure 14) that extracts the user information contained in the input first URL. With this configuration, the second user who reposted the first URL can be identified.

[0109] In the extraction process, the server device 10 extracts user information when the input of the received first URL is made by the first user (poster). This configuration allows the poster to manage the information of those who repost the content.

[0110] Furthermore, the server device 10 executes restriction processing (process A63 shown in Figure 14 and process A46 shown in Figure 9) that accepts the designation of a second user (viewer) from the first user (poster) to restrict viewing of the first user's posts. With this configuration, viewing of posts other than the reposted post is also restricted, thereby improving the deterrent effect against unauthorized reproduction.

[0111] As described above, when the server device 10 receives user information that includes contact information (in this embodiment, the user's telephone number information), the restriction process restricts access for users indicated by user information that includes the same contact information as the second user (viewer) specified by the first user (poster). Note that the contact information may include an email address or an SNS account other than those provided by the posting management system 1. In either case, access can be restricted for multiple users registered in association with the same contact information.

[0112] Figure 17 shows the overall picture of post management by the post management system 1. First, as shown in Figure 17(a), the server device 10 receives a post α to SNS by poster A and a setting to change the URL for each viewer. Next, as shown in Figure 17(b), the user terminal 20 receives an operation by viewer B, who has viewed post α, to repost the URL of post α to another web page. This reposting is to be done without obtaining permission from poster A.

[0113] Next, as shown in Figure 17(c), the server device 10 accepts the input of the URL of the unauthorizedly reposted post α into the SNS search page by poster A, who has found the URL of the reposted post α. Then, the server device 10 extracts the user information of viewer B from the input URL and accepts an operation to restrict viewer B's access based on poster A's actions. As a result, as shown in Figure 17(d), the server device 10 executes a restriction process so that viewer B cannot view any of poster A's posts.

[0114] <Other Embodiments>

[0115] In the restriction process, the server device 10 may restrict access in a manner appropriate to the attributes of the second user (viewer) using the access restriction unit 120. User attributes refer to properties and characteristics common to multiple users, such as preferences, residential area, number of followers, posting frequency, viewing frequency, viewing application usage time, and language used.

[0116] The term "type of access restriction" refers not only to simply prohibiting access, but also to varying the scope or degree of restriction, such as the number of views, the frequency of views, the viewing time (continuous time, total time), the number of images that can be viewed, the number of pages that can be viewed, the number of posts that can be viewed, the number of colors and resolution of images that can be viewed, etc. The access restriction unit 120 determines the type of access restriction using, for example, a restriction type table that associates the viewer's attributes with the type of access restriction.

[0117] Figure 18 shows an example of a restriction pattern table. In the example in Figure 18, the number of followers (an example of viewer attributes) such as "less than Th1", "Th1 or more but less than Th2", and "Th2 or more" are associated with the number of pages that can be viewed (an example of viewing restriction patterns) such as "less than N1", "N1 or more but less than N2", and "N2 or more". The viewer attributes and the number of pages viewed are stored in the user storage unit 112 as the viewer's user information.

[0118] The browsing restriction unit 120 identifies the browsing restriction pattern associated with the number of followers of the viewer indicated by the user information read in A44, as shown in Figure 9, at A45. For example, if the viewer has fewer than 1 followers, the browsing restriction unit 120 allows viewing until the number of viewed pages reaches N1, and then prohibits viewing once the number of viewed pages reaches N1. Furthermore, the browsing restriction unit 120 does not impose any browsing restrictions on viewers with 2 or more followers.

[0119] The access restriction unit 120 may similarly restrict access in the case of other attributes and characteristics. In the example in Figure 18, the values ​​indicating the attributes are divided into three ranges, but it may also be divided into two ranges or four or more ranges. Furthermore, if the viewer's attribute is "language used," the access restriction unit 120 may determine whether or not to restrict access based, for example, whether or not the viewer's language used is the same as the language used in the post.

[0120] For posters, viewing restrictions serve to prevent unauthorized reposters from reposting their content further. However, depending on the post, they may want it to be reposted without their permission so that many people can see it. Even in such cases, if the reposting destination is inappropriate, the value and image of the post may be damaged. Therefore, for example, in the example in Figure 18, viewers with a large number of followers are more likely to handle posts appropriately, so the degree of viewing restrictions can be made lighter for viewers who are likely to repost appropriately, allowing them to spread the post through proper reposting. Conversely, the degree of viewing restrictions can be made heavier for viewers who are unlikely to repost appropriately, suppressing inappropriate reposting.

[0121] Similarly, viewers with similar tastes to the poster are more likely to view web pages related to the poster's interests, making it more likely that the content will be reposted to a suitable site. Viewers living near the poster are also more likely to view web pages containing information about their local area, making it more likely that the content will be reposted to a suitable site. Furthermore, posting frequency, viewing frequency, and time spent using the viewing app indicate the degree of SNS usage (heavy or light user). The closer the SNS usage level is to that of the poster, the easier it is for the poster to understand when content will be reposted. Additionally, if the language used by the poster and the viewer are the same, the web pages reposted to are more likely to be appropriate (web pages in the same language) than if the languages ​​are different. In all cases, a balance can be struck between spreading the content and preventing inappropriate reposting.

[0122] The viewing restriction unit 120, in its restriction process for restricting the viewing of a post, may restrict not only the viewing of the post itself, but also any accompanying information that may be viewed in conjunction with the post. This accompanying information may include, for example, direct messages or chats related to the post, the user U10's (poster's) profile, and recommended images related to the post. Furthermore, the viewing restriction unit 120 may restrict viewing of all posts and accompanying information, or it may restrict viewing of only some of them (for example, only the post and chats).

[0123] In this embodiment, the condition for displaying a post by accessing a second URL that does not contain user information, rather than a first URL that contains user information, was a condition that is met when the first user has made a predetermined setting, but it is not limited to this. For example, a condition that is met when the attributes of the poster described above are predetermined attributes may be used. Predetermined attributes include, for example, specific preferences, a specific residential area, a specific number of followers, a specific posting frequency, a specific viewing frequency, a specific time spent using a specific browsing app, and a specific language used.

[0124] For example, if the poster's interests are such as camping or jogging, which are unlikely to involve copyright, the conditions for using the second URL may be met. However, if the interests are such as watching movies or creating fanzines, which are likely to involve copyright, the conditions for using the second URL may not be met. With this approach, unauthorized reproduction can be suppressed for posts that are more likely to involve copyright, thus preventing unnecessary trouble.

[0125] In this embodiment, the URL input receiving unit 118 accepts input of the entire URL, but it is not limited to this. For example, the URL input receiving unit 118 may accept input of only a portion of the URL, such as the user information portion or the encrypted user information portion. The encrypted user information portion is, in the example of Figure 10, the string that is not "Doc" located in the last section of the section separated by " / " (the "(U12 encrypted)" portion in the example of Figure 10). Furthermore, since the string becomes meaningless when encrypted, it can be easily distinguished from the unencrypted portion.

[0126] In the example shown in Figure 9, the URL generation unit 116 generated a URL when list request data was sent from the user terminal 20, but the timing of URL generation is not limited to this. For example, the URL generation unit 116 may pre-generate a URL for all users when a post is made. Alternatively, the URL generation unit 116 may generate a URL not when the list of posts is displayed, but when a post that the user wants to view is selected from the list.

[0127] The overall configuration shown in Figure 1 is just one example and is not limited to it. For example, the server device 10 may be distributed across two or more devices. Specifically, the server device 10 may be divided into, for example, a device that has functions as a web server (mainly server display processing unit 111, user storage unit 112, authentication unit 113, post storage unit 115, access reception unit 117, and viewing restriction unit 120) and a device that has functions for managing posts (mainly post processing unit 114, URL generation unit 116, URL input reception unit 118, user extraction unit 119, and viewing restriction unit 120).

[0128] Furthermore, the server device 10 may be replaced by a cloud computing system. Also, the functional configuration shown in Figure 4 is just one example and is not limited to it. For example, the functions of the server device 10 may be distributed and implemented across two or more devices. In addition, some of the functions of the server device 10 (for example, the URL input reception unit 118 or the access restriction unit 120) may be implemented by the user terminal 20.

[0129] Furthermore, the operation performed by one function (for example, the URL generation unit 116 or the access restriction unit 120) may be distributed among two or more functions, or two or more functions (for example, the posting processing unit 114 and the posting storage unit 115) may be integrated into a single function. In short, as long as the posting management system 1 as a whole realizes each of the functions shown in Figure 4, the devices that realize those functions can be configured in any way.

[0130] The embodiments described above were information processing systems such as a post management system 1 equipped with a server device 10, but they may also be information processing methods. The information processing method comprises the steps of each process performed by the information processing system. Furthermore, the embodiments described above may also be programs. The programs cause a computer to perform each process that a similar information processing system would perform.

[0131] <Note> Furthermore, they may be provided in the following embodiments.

[0132] (2) The program that causes the computer to perform a URL reception process for receiving input of the first URL, and an extraction process for extracting user information contained in the input first URL.

[0133] In this manner, the second user who reposted the first URL can be identified.

[0134] (3) The program that extracts user information when the input of the first URL is made by the first user.

[0135] In this manner, the poster can manage the information of those who repost the content.

[0136] (4) The program is configured to perform a second post display process in addition to the first post display process, which displays the post when the second user accesses a second URL that does not contain the second user's user information, and performs one of the first post display process and the second post display process.

[0137] In this manner, the visibility of posts can be varied.

[0138] (5) The first post display process and the second post display process are programs selected based on the settings of the first user.

[0139] In this configuration, the poster can control the visibility of their posts.

[0140] (6) The program that causes the computer to execute a restriction process that accepts the designation of a second user from the first user to restrict the viewing of posts made by the first user.

[0141] In this manner, access to posts other than the one that was reposted will also be restricted, thus improving the deterrent effect against unauthorized reposting.

[0142] (7) The program wherein the user information includes contact information, and in the restriction process, it restricts access for users whose contact information is common to the second user specified by the first user.

[0143] This configuration allows for restricting access for multiple users at once.

[0144] (8) The program that performs the restriction process in a manner corresponding to the attributes of the second user.

[0145] This approach allows for a balance between the advantages and disadvantages of reproduction.

[0146] (9) A server comprising a submission reception unit that accepts submissions from a first user, and a first submission display unit that displays the submission when a second user accesses a first URL, wherein the first URL (Uniform Resource Locator) contains the user information of the second user.

[0147] (10) A method wherein a computer performs a submission acceptance process for accepting submissions from a first user and a first submission display process for displaying the submission when a second user accesses a first URL, wherein the first URL (Uniform Resource Locator) includes the user information of the second user. Of course, this is not always the case. Furthermore, the embodiments and modifications described above may be implemented in any combination.

[0148] Finally, various embodiments of the present invention have been described, but these are presented as examples only and are not intended to limit the scope of the invention. Novel embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. Embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents. [Explanation of Symbols]

[0149] 1: Post Management System 2: Communication lines 10: Server device 11: Control Unit 20: User terminal 21: Control Unit 111: Server display processing unit 112: User memory unit 113: Authentication Department 114: Submission Processing Section 115: Submission Memory Section 116 :URL generation part 117: Access Reception Department 118: URL Input Reception Section 119: User Extraction Unit 120: Restricted Access Section 211: Terminal display processing unit 212: Operation Reception Section 213: Post Generation Department 214: Upload section 215: Post Access Section

Claims

1. On the computer, A submission acceptance process that receives submissions from the first user, A first post display process that displays the aforementioned post when a second user accesses the first URL, URL reception processing upon receiving the first URL from the user terminal of the first user, An extraction process for extracting user information of the second user contained in the received first URL, Based on the extracted user information, a restriction process is performed to restrict the second user from viewing the post, Make it run, The first URL (Uniform Resource Locator) includes the user information of the second user, The extraction process is performed when the first URL is received by the first user. program.

2. In the restriction process, if the user information of the second user included in the first URL does not match the user information included in the access request to the first URL, a notification process is performed to notify the second user's user terminal that the first URL is a URL for another user. The program according to claim 1.

3. In addition to the first post display process described above, The system is configured to enable a second post display process that displays the post when the second user accesses a second URL that does not contain the second user's user information. Perform either the first post display process or the second post display process. The program according to claim 1 or claim 2.

4. The first post display process and the second post display process are selected based on the settings of the first user. The program according to claim 3.

5. To the aforementioned computer, A restriction process that allows the first user to specify a second user who will restrict the second user from viewing the first user's posts. To execute The program according to claim 1 or claim 2.

6. The user information includes contact information, The restriction process restricts access for users whose contact information is shared with the second user specified by the first user. The program according to claim 5.

7. In the aforementioned restriction process, access is restricted in a manner that corresponds to the attributes of the second user. The program according to claim 5.

8. A submission reception section that accepts submissions from first users, A first post display unit that displays the aforementioned post when a second user accesses the first URL, A URL receiving processing unit that receives the first URL from the user terminal of the first user, An extraction processing unit that extracts user information of the second user contained in the received first URL, A restriction processing unit that restricts the viewing of the post by the second user based on the extracted user information, Equipped with, The first URL (Uniform Resource Locator) includes the user information of the second user, The processing by the extraction processing unit is performed when the first URL is received by the first user. server.

9. Computers A submission acceptance process that receives submissions from the first user, A first post display process that displays the aforementioned post when a second user accesses the first URL, URL reception processing upon receiving the first URL from the user terminal of the first user, An extraction process for extracting user information of the second user contained in the received first URL, Based on the extracted user information, a restriction process is performed to restrict the second user from viewing the post, Execute, The first URL (Uniform Resource Locator) includes the user information of the second user, The extraction process is performed when the first URL is received by the first user. method.

Images