Method and device for processing user privacy data
By assigning random publisher and commenter logos to users on social platforms, the problem of privacy data protection in information interaction is solved, and the mutual visible information is achieved by both parties and protecting user privacy.
Patent Information
- Application Number
- CN202510732369.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-03
- Publication Date
- 2025-08-15
AI Technical Summary
In information interaction scenarios that are both privacy and open, how to protect users' privacy data, especially on social platforms, let the information communicated between the two parties of the interaction not be viewed by third parties.
By determining whether the user is the publisher and commenter of the information, the system assigns a random publisher logo and a commenter logo to the user, and only displays the message or comment information on both parties to communicate, and uses the publisher code to identify the identity to ensure the public attributes and privacy protection of the information.
It realizes that the information of both parties interacting on social platforms is only visible to both parties, protecting the user's privacy data, and avoiding the leakage of personal information and unnecessary information display.
Smart Images
Figure CN120493312A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of user privacy technology, and in particular to a method and device for processing user privacy data. Background Art
[0002] Currently, users can communicate through various social platforms. Social platforms can be divided into two categories: one is the information exchange network formed by users' personal social networks, where users often interact with familiar people on a "point-to-point" basis; the other is the platform-based social network, where users view various images, audio, video, and text information on the platform, and then communicate with those who like, comment, collect, or forward the information, or directly perform social operations such as like, comment, collect, or forward the information.
[0003] At this time, information interaction on the user's personal social network is private, and information is exchanged within the circle of acquaintances; information interaction in platform-based social networks is public (non-private), and information is exchanged in a public environment.
[0004] However, there are some information interaction scenarios that require both privacy and publicity. In these scenarios, protecting user privacy becomes particularly important. For example, company user A lists a pre-owned property. Individual user A wants to know if the price can be reduced by 10%, individual user B wants to know if the price can be reduced by 5%, and individual user C wants to know if there is a discount for paying in full. Company user A wants individual users to only see information about their interactions with user A, and not information about other individual users interacting with user A. Individual users also want other individual users to not see their bargaining or purchase information. In these situations, protecting the privacy of both parties in publicly available information, while limiting communication to the two interacting parties and preventing third parties from viewing such information, becomes crucial.
[0005] Therefore, there is an urgent need for a method and device for processing user privacy data to solve one or more of the above problems. Summary of the Invention
[0006] The present application discloses a method and device for processing user privacy data, which enables two parties to communicate without the communication information being viewed by a third party, thereby protecting the privacy data of both parties.
[0007] In a first aspect, the present application discloses a method for processing user privacy data, which is applied to an information interaction platform, the method comprising: receiving a first message request for information sent by a first user, the information comprising one or more of text, audio, picture and video, the first message request being used to leave a message on the information; determining whether the first user is the publisher of the information; if the first user is not the publisher of the information, determining whether the first user has left a message on the information; if the first user has not left a message on the information, randomly assigning a message maker ID to the first user in a message maker ID library; wherein the message maker ID library comprises a message maker image and a message maker title preset by the information interaction platform; and displaying the message maker ID and the first message to the publisher and the first user.
[0008] In the above scheme, information is used in a wide range of scenarios, such as job postings, product supply and demand, entrepreneurial exchanges, and forums. All posted information is public, but this also involves the privacy of both parties. Existing methods often involve clicking on user images to communicate. For example, user A sees a product request posted by user B and clicks on user B's image to communicate. However, in actual use, it has been found that clicking on user B's image often reveals user B's personal information and private images, which are all private information. Furthermore, when user B posts multiple product requests, the small window communication method after clicking on user B's image is often inconvenient because it is impossible to determine which product request user A is communicating about. Therefore, after determining whether the user is the publisher and commenter of the information, the system assigns the user a preset publisher and commenter ID based on their identity. These IDs are random and universal, not unique to any one user. Furthermore, messages or comments are only displayed to the two communicating parties (also known as the interacting parties), thus protecting user privacy.
[0009] In one possible implementation, determining whether the first user is the publisher of the information specifically includes: obtaining a publisher code for the information, where the publisher code is a unique identifier assigned to the publisher by the information interaction platform when the publisher registers on the information interaction platform; and comparing the user code of the first user with the publisher code to determine whether the first user is the publisher of the information.
[0010] In the above solution, the publisher's identity is identified by the publisher code. Identifying the identity of the publisher or the commenter facilitates the display of targeted message or comment information.
[0011] In a possible implementation, after determining whether the first user is the publisher of the information, the method further includes: if the first user is the publisher of the information, randomly assigning a publisher identifier to the first user in a publisher identifier library; wherein the publisher identifier library includes a publisher image and publisher title preset by the information interaction platform; and displaying the first message to the first user.
[0012] In the above scheme, if a user has not left a message or comment on a specific message, the system will randomly assign an ID. Allocated IDs are in the assigned state, while IDs that are not currently assigned are in the unassigned state. The IDs assigned to the same user can be the same or different. In this manual, the IDs assigned to the same user are the same, using this as an example.
[0013] In one possible implementation, the method further includes: receiving a comment request from a second user regarding the first message, the comment request being used to comment on the first message, the second user being the publisher of the information; and displaying the first message and the comment on the first message to the second user and the first user.
[0014] In the above scheme, the publisher of the information can leave a message or comment on the information he or she publishes. Such message or comment is the publisher's further explanation of the information he or she publishes; such message or comment has the same public attribute as the information and can be seen by other users.
[0015] In one possible implementation, the method includes: receiving a second message request from a third user regarding the first message, the second message request being used to reply to the first message; determining whether the third user has already left a message on the information; if the third user has not left a message on the information, randomly assigning a message maker ID to the third user in the message maker ID library; and displaying the first message and the second message to the third user and the first user.
[0016] In the above scenario, the first message is posted by the publisher, and the third user, as the commenter, replies or comments on the first message. In this case, the first and second messages are visible only to the two parties. Since the first message is posted by the publisher and is public, it is visible to all users. The second message is an interaction between the first user (the publisher) and the third user (the commenter), and is visible only to the two parties.
[0017] In one possible implementation, determining whether the third user has left a message on the information specifically includes: obtaining the user code of the third user; and determining whether the message maker identification library has assigned a message maker identification to the user code of the third user, wherein the message maker identification library records the assigned message maker identification and the user code corresponding to the assigned message maker identification.
[0018] In the above solution, the purpose is to illustrate how to determine whether a third user has left a message. Similarly, the same method can also be used to determine whether a user is the publisher.
[0019] In one possible implementation, after determining whether the third user has left a message on the information, the method further includes: if the third user has left a message on the information, querying the message maker ID library for the user code of the third user corresponding to the assigned message maker ID; assigning the user code of the third user corresponding to the assigned message maker ID to the third user; and displaying the first message and the second message to the third user and the first user.
[0020] The above scheme illustrates that the same user's assigned ID is the same. The ID includes the user's image and title, and is system-preset. In this case, regardless of whether the user leaves a message on the same or different channels, the ID remains the same.
[0021] In one possible implementation, after determining whether the third user has left a message on the information, the method further includes: if the third user has left a message on the information, determining whether the message left by the third user and the second message request are in the same message loop; the same message loop is used to represent the same conversation loop, and the information includes one or more message loops; if the message left by the third user and the second message request are in the same message loop, querying the assigned message maker ID corresponding to the user code of the third user in the message maker ID library; assigning the assigned message maker ID corresponding to the user code of the third user to the third user; and displaying the first message and the second message to the third user and the first user.
[0022] The above solution discloses a method in which the same user's message ID remains the same in the same message loop. This allows the publisher of a message and the message recipient to communicate with each other multiple times in the same message loop, using the same message ID to indicate that their identities have not changed. For the publisher of the message, the publisher ID corresponding to the same message remains unchanged. However, the same user can set a different publisher ID for different messages; this setting also protects the user's privacy.
[0023] In one possible implementation, after determining whether the third user has left a message on the information, the method further includes: if the third user has left a message on the information, determining whether the message left by the third user and the second message request are in the same message loop; the same message loop is used to represent the same conversation loop, and the information includes one or more message loops; if the message left by the third user and the second message request are not in the same message loop, randomly assigning a message maker ID to the third user in the message maker ID library; and displaying the first message and the second message to the third user and the first user.
[0024] In the above solution, a user's message ID is different in different message loops. This facilitates multiple anonymous communications between the user and the message publisher, which is of practical significance in scenarios such as business negotiations.
[0025] The second aspect of the present application discloses a device for processing user privacy data, wherein the device is the information interaction platform, and the information interaction platform includes a receiving unit, a processing unit, and a display unit; wherein, The receiving unit receives a first message request for information sent by a first user, where the information includes one or more of text, audio, picture, and video, and the first message request is used to leave a message on the information; The processing unit determines whether the first user is the publisher of the information; if the first user is not the publisher of the information, determines whether the first user has left a message on the information; The processing unit randomly assigns a commenter ID to the first user from a commenter ID library if the first user has not left a comment on the information; wherein the commenter ID library includes a commenter image and a commenter title preset by the information interaction platform; The display unit displays the message author identifier and the first message to the publisher and the first user.
[0026] In the third aspect of the present application, an electronic device is provided, including a processor, a memory, a user interface and a network interface, the memory is used to store instructions, the user interface and the network interface are both used to communicate with other devices, and the processor is used to execute the instructions stored in the memory so that the electronic device performs any of the methods described above.
[0027] In a fourth aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores instructions. When the instructions are executed, any one of the methods described above is executed.
[0028] The beneficial effects of this application include: After determining whether the user is the publisher and commenter of the information, the system will assign the user a preset publisher ID and commenter ID based on the user's identity. These IDs are random and universal, and are not exclusive to any user. In addition, the message or comment information is only displayed to the two parties communicating, thereby protecting the user's personal privacy. Identify the publisher's identity through the publisher code. Identify the publisher or message sender to facilitate targeted message display; When a user has not left a message or comment on a specific message, the system will randomly assign an ID. An assigned ID is in the assigned state, and an ID that has not been assigned is in the unassigned state. The IDs assigned to the same user can be the same or different. In this manual, the IDs assigned to the same user are the same, and this is used as an example for explanation; Information publishers can leave messages or comments on their published information. Such messages or comments are further explanations of the information they publish. Such messages or comments are public like the information itself and can be seen by other users. The first message is posted by the publisher, and the third user, as the commenter, replies or comments on the first message. In this case, the first and second messages are visible only to the two users. Since the first message is posted by the publisher and is public, it is visible to all users. The second message is an interaction between the first user (the publisher) and the third user (the commenter), and is visible only to the two users. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Figure 1 A flowchart of a method for processing user privacy data disclosed in this application; Figure 2 A schematic diagram of a user interface for a publisher of information disclosed in this application; Figure 3 A schematic diagram of a user interface for a message leaver disclosed in this application; Figure 4A schematic diagram of a user interface for a message leaver disclosed in this application; Figure 5 A schematic diagram of a user interface for a message leaver of another type of information disclosed in this application; Figure 6 This is a schematic structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION
[0030] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments.
[0031] In the description of the embodiments of this application, words such as "for example" or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "for example" or "for instance" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "for example" or "for instance" is intended to present the relevant concepts in a concrete manner.
[0032] In the description of the embodiments of the present application, the term "multiple" means two or more. For example, multiple systems refer to two or more systems, and multiple screen terminals refer to two or more screen terminals. In addition, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the indicated technical features. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.
[0033] The information described in this specification covers many scenarios, such as recruitment information, product supply and demand, entrepreneurial exchanges, and forums. The information published is public, but it also involves the privacy of both parties. Existing methods often involve communication by clicking on user images. For example, after user A sees a product demand posted by user B, they click on user B's image to communicate. However, in actual applications, it has been found that after user B's image is clicked, user B's personal information and private images are often displayed, which are all user B's private information. In addition, when user B posts multiple product demands, the small window communication method after clicking on user B's image is inconvenient because it is impossible to know which product demand user A is communicating about. Therefore, after determining whether the user is the publisher and commenter of the information, the system assigns the user a preset publisher ID and commenter ID based on the user's identity. These IDs are random and universal, and are not exclusive to any one user. In addition, the message or comment information is only displayed to the two communicating parties, thereby protecting the user's personal privacy.
[0034] Therefore, the present application discloses a method for processing user privacy data, which is applied in an information interaction platform. The method includes steps S101-S105.
[0035] Step S101: receiving a first message request for information sent by a first user, where the information includes one or more of text, audio, picture, and video, and the first message request is used to leave a message on the information.
[0036] The information in the above steps is an enumeration of basic information forms; for example, text information may include files, and may also include other text types.
[0037] Step S102: Determine whether the first user is the publisher of the information.
[0038] In one example, determining whether the first user is the publisher of the information specifically includes: obtaining the publisher code of the information, where the publisher code is a unique identifier assigned to the publisher by the information interaction platform when the publisher registers on the information interaction platform; comparing the user code of the first user with the publisher code to determine whether the first user is the publisher of the information.
[0039] At this time, the publisher's identity is identified through the publisher code. The identity of the publisher or the message writer is identified to facilitate targeted message display.
[0040] It should be noted that information itself has an information code, which is also unique on the information exchange platform; an information code can distinguish the information itself from other information. Generally speaking, information is published by users, and there is a direct correspondence between the information code and the user code that published it. For ease of description in this specification, when determining whether the first user is the publisher of the information, the user code (i.e., the publisher code corresponding to the information) is directly compared with the user code of the first user.
[0041] Step S103: If the first user is not the publisher of the information, determine whether the first user has left a message on the information.
[0042] In one example, after determining whether the first user is the publisher of the information, the method further includes: if the first user is the publisher of the information, randomly assigning a publisher identifier to the first user in a publisher identifier library; wherein the publisher identifier library includes a publisher image and publisher title preset by the information interaction platform; and displaying the first message to the first user.
[0043] At this time, when the user has not left a message or comment on a specific information, the system will randomly assign an identifier. The assigned identifier is in the assigned state, and the identifier that is not currently assigned is in the unassigned state. The assigned identifiers for the same user can be the same or different. The identifiers assigned to the same user in this manual are the same, and this is used as an example for explanation. It should be noted that the publisher identification library in this manual and the commenter identification library below are both identification libraries of the information interaction platform; the distinction between the publisher identification library and the commenter identification library is for the convenience of description and is not to be understood as a restriction. That is, the information interaction platform has an identification library, and the identifier assigned to the commenter is the commenter identification, and the identifier assigned to the publisher is the publisher identification; no distinction is made. Of course, the commenter identification library and the publisher identification library can also be distinguished as needed.
[0044] Step S104: If the first user has not left a message on the information, a message reader ID is randomly assigned to the first user in a message reader ID library; wherein the message reader ID library includes message reader images and message reader titles preset by the information interaction platform.
[0045] Step S105: Display the message author identifier and the first message to the publisher and the first user.
[0046] At this time, the first user, as the message leaver, can directly leave a message on the message; or Figure 5 As shown, reply to the message posted by the information publisher (also known as: leave a message on the publisher's message), Figure 5For the sake of convenience in description, the first user is replaced by "I" and the description is made from the first-person perspective, but this is not limited to this.
[0047] In one example, the method further includes: receiving a comment request from a second user regarding the first message, the comment request being used to comment on the first message, the second user being the publisher of the information; and displaying the first message and the comment on the first message to the second user and the first user.
[0048] At this time, the publisher of the information can leave a message or comment on the information he or she has posted. This message or comment is a further explanation of the information posted by the publisher; this type of message or comment has the same public attributes as the information and can be seen by other users.
[0049] In the above example, the second user is the publisher of the information. Figure 2 As shown in the figure, the information publisher's display content is shown. As the publisher of the information, you can see the messages posted by all the commenters of the information (only three commenters are shown in the figure, namely commenter 1, commenter 2 and commenter 3). The message posted by the publisher of the information can be a supplementary explanation of the content of the information. Figure 2 The example of a publisher is "author image identifier, author name identifier, and content XX." However, commenter 1 can only see the content of commenter 1's comment and the content of the publisher's comment; commenter 2 can only see the content of commenter 2's comment and the content of the publisher's comment; and commenter 3 can only see the content of the publisher's comment and the content of commenter 3's reply to the publisher. Figure 2 In the example, the publisher of information replies to commenter 3 with “@”, and commenter 3 also displays “@” in response to the message of the publisher of information. In this way, both parties in the interaction cannot know the real information of the other party and can only see the logo.
[0050] In other words, the interactive information between a publisher and a commenter in this specification is visible only to the two parties involved. If multiple commenters in a comment loop for a publisher reply to a message posted by the publisher (also known as a message or comment), then a commenter will only see their own message and the publisher's message and replies. For example, publisher A posts a message under their own post (a post, article, job posting, product information, partnership information, etc., not limited to this). Commenters B and C (using only two commenters for this example, but the number of commenters is not limited) both reply to message a (as above, leave messages or comments). Commenter B may communicate with publisher A multiple times regarding message a, and these communications are only visible to commenter B and publisher A. At the same time, commenter C may also communicate with publisher A multiple times in the comment loop for message a, and these communications are only visible to commenter C and publisher A. Moreover, the information publisher A, the message poster B, and the message poster C do not know the identity of the other party they are communicating with, and can only see an image and logo distributed by the system.
[0051] It should be noted that unless otherwise specified, the aforementioned interactive information is visible only to the two parties interacting. However, the commenter will still be given the ability to make their comment public to other commenters, and they can choose to do so based on their needs. For example, in the aforementioned example, commenter B's comment on comment a is, by default, visible only to the poster A and commenter B. However, commenter B can also set the comment information to public when commenting on comment a, in which case commenter C (i.e., another commenter) will also be able to see commenter B's comment on comment a.
[0052] In addition, commenters B and C can reply to multiple messages posted by information publisher A. For example, if the information publisher posts multiple messages, including message a, message b, and message c, commenters B and C can reply to all of them (the terms "message" or "comment" have the same meaning elsewhere in this manual). Information publisher A does not know the identities of the multiple message authors, nor does it know whether the same author appears in different messages (for example, in messages b and c, commenter B replies to both messages b and c, but the information publisher does not necessarily know that they are the same author; for this discussion, please refer to the discussion of commenter identification in this manual).
[0053] In this example, the first user is the message leaver. Figure 3As shown in the figure, the first user is taken as an example from the perspective of commenter 1. For the first user, he can see his own comments and the reply of the publisher of the information (the "author image identifier, author name identifier" in the figure) to the first user's comments. The comments posted by the publisher of the information can be seen by all users; the comments posted by the publisher of the information can also become the publisher's first-level comments, which can be seen by all users. However, the publisher's reply to the commenter 1's comment can only be seen by Figure 3 Saw by commenter 1.
[0054] In one example, the method includes: receiving a second message request from a third user regarding the first message, the second message request being used to reply to the first message; determining whether the third user has already left a message on the information; if the third user has not left a message on the information, randomly assigning a message maker ID to the third user in the message maker ID library; and displaying the first message and the second message to the third user and the first user.
[0055] In this case, the first message is posted by the publisher, and the third user, as the commenter, replies or comments on the first message. The first and second messages are visible only to the two parties. Since the first message is posted by the publisher and is public, it is visible to all users. The second message is an interaction between the first user (the publisher) and the third user (the commenter), and is visible only to the two parties.
[0056] like Figure 4 As shown, the third user is represented by the commentator 2 as an example, showing the perspective of the commentator 2. The third user and the publisher of the information can communicate in different comment loops. Figure 4 The figure shows two message loops, i.e., two conversation loops. In the first message loop, message sender 2 leaves a message first, and then the information publisher “@”s the message sender 2. In the second message loop, message sender 2 replies to the information publisher after the information publisher leaves a message. Figure 4 As shown, the communication content in the two message loops can be seen by the information publisher and the message sender 2.
[0057] In one example, determining whether the third user has left a message on the information specifically includes: obtaining the user code of the third user; determining whether the message maker identification library has assigned a message maker identification to the user code of the third user, wherein the message maker identification library records the assigned message maker identification and the user code corresponding to the assigned message maker identification.
[0058] This is to illustrate how to determine whether a third user has left a message. Similarly, the same method can be used to determine whether a user is the publisher.
[0059] In one example, after determining whether the third user has left a message on the information, the method further includes: if the third user has left a message on the information, querying the message ID library for the user code of the third user corresponding to the assigned message ID; assigning the user code of the third user corresponding to the assigned message ID to the third user; and displaying the first message and the second message to the third user and the first user.
[0060] This is to illustrate that the same user's assigned ID is the same. The ID includes the user's image and title, and is system-preset. Regardless of whether the user leaves a message on the same or different channels, the ID remains the same.
[0061] In one example, after determining whether the third user has left a message on the information, the method further includes: if the third user has left a message on the information, determining whether the message left by the third user and the second message request are in the same message loop; the same message loop is used to represent the same conversation loop, and the information includes one or more message loops; if the message left by the third user and the second message request are in the same message loop, querying the user code of the third user corresponding to the assigned message maker ID in the message maker ID library; assigning the user code of the third user corresponding to the assigned message maker ID to the third user; and displaying the first message and the second message to the third user and the first user.
[0062] In this case, the same user's comment ID remains the same in the same message loop. This allows the publisher and commenter to communicate multiple times in the same message loop, using the same comment ID to indicate that their identities have not changed. For the publisher of the message, the publisher ID remains unchanged. However, the same user can use different publisher IDs for different messages; this approach also protects the user's privacy.
[0063] In one example, after determining whether the third user has left a message on the information, the method further includes: if the third user has left a message on the information, determining whether the message left by the third user and the second message request are in the same message loop; the same message loop is used to represent the same conversation loop, and the information includes one or more message loops; if the message left by the third user and the second message request are not in the same message loop, randomly assigning a message maker ID to the third user in the message maker ID library; and displaying the first message and the second message to the third user and the first user.
[0064] In this case, the same user's message ID is different in different message loops, which facilitates multiple anonymous communications between the user and the message publisher, and is of practical significance in scenarios such as business negotiations. This specification also discloses a device for processing user privacy data. The processing device is the information interaction platform, and the information interaction platform includes a receiving unit, a processing unit, and a display unit.
[0065] The receiving unit receives a first message request for information sent by a first user, where the information includes one or more of text, audio, picture, and video, and the first message request is used to leave a message on the information.
[0066] The processing unit determines whether the first user is the publisher of the information; if the first user is not the publisher of the information, determines whether the first user has left a message on the information.
[0067] The processing unit randomly assigns a commenter ID to the first user from a commenter ID library if the first user has not left a comment on the information; wherein the commenter ID library includes commenter images and commenter titles preset by the information interaction platform.
[0068] The display unit displays the message author identifier and the first message to the publisher and the first user.
[0069] In one example, determining whether the first user is the publisher of the information specifically includes: obtaining the publisher code of the information, where the publisher code is a unique identifier assigned to the publisher by the information interaction platform when the information is published; comparing the user code of the first user with the publisher code to determine whether the first user is the publisher of the information.
[0070] In one example, after determining whether the first user is the publisher of the information, the method further includes: if the first user is the publisher of the information, randomly assigning a publisher identifier to the first user in a publisher identifier library; wherein the publisher identifier library includes a publisher image and publisher title preset by the information interaction platform; and displaying the first message to the first user.
[0071] In one example, a comment request for the first message from a second user is received, where the comment request is used to comment on the first message, and the second user is the publisher of the information; the first message and the comment on the first message are displayed to the second user and the first user.
[0072] In one example, a second message request is received from a third user regarding the first message, wherein the second message request is used to reply to the first message; it is determined whether the third user has already left a message on the information; if the third user has not left a message on the information, a message maker ID is randomly assigned to the third user in the message maker ID library; and the first message and the second message are displayed to the third user and the first user.
[0073] In one example, determining whether the third user has left a message on the information specifically includes: obtaining the user code of the third user; determining whether the message maker identification library has assigned a message maker identification to the user code of the third user, wherein the message maker identification library records the assigned message maker identification and the user code corresponding to the assigned message maker identification.
[0074] In one example, after determining whether the third user has left a message on the information, the method further includes: if the third user has left a message on the information, querying the message ID library for the user code of the third user corresponding to the assigned message ID; assigning the user code of the third user corresponding to the assigned message ID to the third user; and displaying the first message and the second message to the third user and the first user.
[0075] In one example, after determining whether the third user has left a message on the information, the method further includes: if the third user has left a message on the information, determining whether the message left by the third user and the second message request are in the same message loop; the same message loop is used to represent the same conversation loop, and the information includes one or more message loops; if the message left by the third user and the second message request are in the same message loop, querying the user code of the third user corresponding to the assigned message maker ID in the message maker ID library; assigning the user code of the third user corresponding to the assigned message maker ID to the third user; and displaying the first message and the second message to the third user and the first user.
[0076] In one example, after determining whether the third user has left a message on the information, the method further includes: if the third user has left a message on the information, determining whether the message left by the third user and the second message request are in the same message loop; the same message loop is used to represent the same conversation loop, and the information includes one or more message loops; if the message left by the third user and the second message request are not in the same message loop, randomly assigning a message maker ID to the third user in the message maker ID library; and displaying the first message and the second message to the third user and the first user.
[0077] It should be noted that the above embodiments provide devices that implement their functions using only the division of the above functional modules as examples. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the device and method embodiments provided in the above embodiments are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.
[0078] The specification also discloses a computer-readable storage medium, which stores instructions. When the instructions are executed, any one of the above methods is executed.
[0079] This embodiment also discloses an electronic device, referring to Figure 6 The electronic device may include: at least one processor 601 , at least one communication bus 602 , a user interface 603 , a network interface 604 , and at least one memory 605 .
[0080] The communication bus 602 is used to implement the connection and communication between these components.
[0081] The user interface 603 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 603 may also include a standard wired interface and a wireless interface.
[0082] The network interface 604 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).
[0083] The processor 601 may include one or more processing cores. The processor 601 utilizes various interfaces and circuits to connect various components within the server. It executes instructions, programs, code sets, or instruction sets stored in the memory 605, as well as accesses data stored in the memory 605, to perform various server functions and process data. Optionally, the processor 601 may be implemented using at least one of the following hardware forms: a digital signal processing (DSP), a field-programmable gate array (FPGA), or a programmable logic array (PLA). The processor 601 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. The CPU primarily processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing content displayed on the display screen; and the modem handles wireless communications. It is understood that the modem may also be implemented as a separate chip, rather than integrated into the processor 601.
[0084] Memory 605 may include random access memory (RAM) or read-only memory (ROM). Optionally, memory 605 may include non-transitory computer-readable storage medium. Memory 605 may be used to store instructions, programs, code, code sets, or instruction sets. Memory 605 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, sound playback function, image playback function, etc.), instructions for implementing the aforementioned method embodiments, etc.; the data storage area may store data related to the aforementioned method embodiments, etc. Memory 605 may also optionally be at least one storage device located remotely from the processor 601. As shown in the figure, memory 605, as a computer storage medium, may include an operating system, a network communication module, a user interface module, and an application program for calculating construction cost.
[0085] exist Figure 6 In the electronic device shown, the user interface 603 is mainly used to provide an input interface for the user and obtain data input by the user; and the processor 601 can be used to call the application program of the method for calculating the engineering construction cost stored in the memory 605. When executed by one or more processors 601, the electronic device executes one or more methods as in the above-mentioned embodiments.
[0086] It should be noted that for the aforementioned method embodiments, for simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required for this application.
[0087] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0088] In the several embodiments provided in this application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are merely schematic, such as the division of units, which is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interface, and the indirect coupling or communication connection of devices or units can be electrical or other forms.
[0089] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0090] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0091] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory 605. Based on this understanding, the technical solution of this application, or the portion that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory 605 and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the method of this application. The aforementioned memory 605 includes various media capable of storing program code, such as a USB flash drive, a mobile hard drive, a magnetic disk, or an optical disk.
[0092] The above is only an exemplary embodiment of the present disclosure and cannot be used to limit the scope of the present disclosure. That is, any equivalent changes and modifications made according to the teachings of the present disclosure are still within the scope of the present disclosure. After considering the disclosure of the specification and the truth of practice, those skilled in the art will easily think of other embodiments of the present disclosure. This application is intended to cover any variation, use or adaptive change of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the art that are not recorded in the present disclosure. The description and examples are to be regarded as exemplary only, and the scope and spirit of the present disclosure are defined by the claims.
Claims
1. A method for processing user privacy data, characterized in that: Applied to an information interaction platform, the method includes: receiving a first message request from a first user for information, where the information includes one or more of text, audio, picture, and video, and the first message request is for leaving a message on the information; Determining whether the first user is the publisher of the information; If the first user is not the publisher of the information, determining whether the first user has left a message on the information; If the first user has not left a message on the information, a randomly assigned message ID is assigned to the first user in a message ID library; wherein the message ID library includes a message ID image and a message ID title preset by the information interaction platform; The message author identification and the first message are displayed to the publisher and the first user.
2. The processing method according to claim 1, characterized in that Determining whether the first user is the publisher of the information specifically includes: Obtaining a publisher code of the information, where the publisher code is a unique identifier assigned to the publisher by the information interaction platform when the publisher registers on the information interaction platform; The user code of the first user is compared with the publisher code to determine whether the first user is the publisher of the information.
3. The processing method according to claim 1 or 2, characterized in that After determining whether the first user is the publisher of the information, the method further includes: If the first user is the publisher of the information, a publisher identifier is randomly assigned to the first user from a publisher identifier library; wherein the publisher identifier library includes a publisher image and publisher title preset by the information interaction platform; The first message is displayed to the first user.
4. The processing method according to claim 1, characterized in that The method further comprises: receiving a comment request from a second user regarding the first message, wherein the comment request is for commenting on the first message, and the second user is the publisher of the information; The first message and comments on the first message are displayed to the second user and the first user.
5. The processing method according to claim 3, characterized in that: The method comprises: receiving a second message request from a third user in response to the first message, wherein the second message request is used to reply to the first message; Determining whether the third user has left a message on the information; If the third user has not left a message on the information, randomly assigning a message ID to the third user in the message ID database; The first message and the second message are displayed to the third user and the first user.
6. The processing method according to claim 5, characterized in that: The determining whether the third user has left a message on the information specifically includes: Obtaining a user code of the third user; It is determined whether the message reader identification library has allocated a message reader identification to the user code of the third user, wherein the message reader identification library records the allocated message reader identification and the user code corresponding to the allocated message reader identification.
7. The processing method according to claim 5 or 6, characterized in that: After determining whether the third user has left a message on the information, the method further comprises: if the third user has left a message on the information, searching the message identifier database for an assigned message identifier corresponding to the user code of the third user; assigning the user code of the third user corresponding to the assigned message author identifier to the third user; The first message and the second message are displayed to the third user and the first user.
8. The processing method according to claim 5 or 6, characterized in that: After determining whether the third user has left a message on the information, the method further includes: If the third user has left a message on the information, determining whether the message left by the third user and the second message request are in the same message loop; the same message loop is used to represent the same conversation loop, and the information includes one or more message loops; If the message already left by the third user is in the same message loop as the second message request, querying the assigned message ID corresponding to the user code of the third user in the message ID database; assigning the user code of the third user corresponding to the assigned message author identifier to the third user; The first message and the second message are displayed to the third user and the first user.
9. The processing method according to claim 5 or 6, characterized in that: After determining whether the third user has left a message on the information, the method further includes: If the third user has left a message on the information, determining whether the message left by the third user and the second message request are in the same message loop; the same message loop is used to represent the same conversation loop, and the information includes one or more message loops; If the message already left by the third user and the second message request are not in the same message loop, a randomly assigned message ID for the third user in the message ID database; The first message and the second message are displayed to the third user and the first user.
10. A device for processing user privacy data, characterized in that: The processing device is the information interaction platform, which includes a receiving unit, a processing unit and a display unit; wherein, The receiving unit receives a first message request for information sent by a first user, where the information includes one or more of text, audio, picture, and video, and the first message request is used to leave a message on the information; The processing unit determines whether the first user is the publisher of the information; if the first user is not the publisher of the information, determines whether the first user has left a message on the information; The processing unit randomly assigns a commenter ID to the first user from a commenter ID library if the first user has not left a comment on the information; wherein the commenter ID library includes a commenter image and a commenter title preset by the information interaction platform; The display unit displays the message author identifier and the first message to the publisher and the first user.