Method, device and storage medium for processing relationship in social platform
Patent Information
- Application Number
- CN202610795661.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-03
- Publication Date
- 2026-09-15
Smart Images
Figure CN122756554A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, device and storage medium for handling relationships in a social platform. Background Technology
[0002] On social media platforms, when a user triggers a relationship termination action such as unfollowing or deleting a target, the existing system usually pops up a simple secondary confirmation pop-up. This pop-up generally only contains basic options such as "confirm" and "cancel" and does not provide the user with any additional reference information.
[0003] In the absence of such information, users find it difficult to make an objective judgment on the value of the relationship between the two parties, and are prone to making irrational decisions to terminate the relationship due to momentary impulse or lack of information, resulting in unnecessary breakdowns in social relationships. Summary of the Invention
[0004] To address the aforementioned technical issues, a method for handling relationships on social platforms is provided.
[0005] A first aspect of the present invention provides a relationship processing method in a social platform, comprising: displaying a relationship confirmation interface in response to triggering a relationship termination operation against a target object; displaying historical interaction data between a user and the target object on the relationship confirmation interface, so that the user re-evaluates whether to continue performing the relationship termination operation based on the historical interaction data.
[0006] In one embodiment, the historical interaction data includes first interaction data with the target object and / or second interaction data related to the content published by the target object; wherein, the first interaction data includes at least one of the date the user met the target object, the number of interactions, and the number of chat days; and the second interaction data includes at least one of the number of likes, comments, and favorites the user has given to the content published by the target object.
[0007] In one embodiment, the relationship confirmation interface includes an interactive entry point; the method further includes: in response to a trigger operation on the interactive entry point, jumping to a relationship details page, and displaying detailed historical interaction data between the user and the target object on the relationship details page, wherein the detailed historical interaction data has more dimensions than the historical interaction data.
[0008] In one embodiment, displaying detailed historical interaction data between the user and the target object on the relationship details page includes: obtaining an intimacy value between the user and the target object; when the intimacy value is greater than a preset threshold, displaying key node data in the detailed historical interaction data; and when the intimacy value is not greater than the preset threshold, displaying overall statistical data in the detailed historical interaction data.
[0009] In one embodiment, displaying detailed historical interaction data between the user and the target object on the relationship details page includes: dynamically visualizing the detailed historical interaction data on the relationship details page.
[0010] In one embodiment, the method further includes: displaying at least one permission adjustment option on the relationship confirmation interface; in response to a triggering operation on one of the permission adjustment options, performing a corresponding permission adjustment operation, and closing the relationship confirmation interface.
[0011] In one embodiment, displaying at least one permission adjustment option on the relationship confirmation interface includes: obtaining an intimacy value between the user and the target object; displaying a first set of permission adjustment options when the intimacy value is greater than a preset threshold; and displaying a second set of permission adjustment options when the intimacy value is not greater than the preset threshold, wherein the first set of permission adjustment options and the second set of permission adjustment options contain different types or numbers of permission adjustment options.
[0012] In one embodiment, the permission adjustment options include at least one of the following: reducing the content recommendation weight of the target object; blocking the display content of the target object; reducing the content visibility permission of the target object; and disabling message notifications from the target object.
[0013] In one embodiment, the relationship undoing operation includes at least one of the following operations: unfollowing, undoing the friend relationship, or leaving the group.
[0014] A second aspect of the present invention provides a relationship processing apparatus in a social platform, comprising: an interface display unit configured to display a relationship confirmation interface in response to triggering a relationship termination operation against a target object; and a data display unit configured to display historical interaction data between a user and the target object on the relationship confirmation interface, so that the user can re-evaluate whether to continue performing the relationship termination operation based on the historical interaction data.
[0015] A third aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the relationship processing method in a social platform provided in any implementation of the first aspect.
[0016] A fourth aspect of the present invention provides an electronic device, including: one or more processors; and a memory associated with the one or more processors, the memory being used to store program instructions, which, when read and executed by the one or more processors, perform the steps of the relationship processing method in the social platform provided in any implementation of the first aspect.
[0017] A fifth aspect of the present invention provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the relationship processing method in a social platform provided in any implementation of the first aspect.
[0018] According to the specific embodiments provided in this application, the following technical effects are disclosed: This application's embodiments display a relationship confirmation interface upon detecting a relationship termination operation targeting a target object. This interface directly displays historical interaction data between the user and the target object, embedding previously unused relationship-accumulating data into the relationship termination decision-making process. This allows users to reassess the current relationship status based on historical interaction information before performing actions such as unfollowing or unfriending. This approach effectively improves the completeness and depth of user perception when making relationship decisions, thereby mitigating the tendency for erroneous operations due to information gaps and enhancing the effectiveness of relationship processing interactions and the quality of user-driven decision-making.
[0019] Of course, any product implementing this application does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description
[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0021] Figure 1 This is a schematic diagram of the system architecture to which the embodiments of this application apply.
[0022] Figure 2 This is a flowchart of a relationship processing method in a social platform provided in an embodiment of this application.
[0023] Figure 3This is a schematic diagram illustrating the implementation of hierarchical display of historical interactive data after the trigger relationship is released, as provided in this application embodiment.
[0024] Figure 4 This is a schematic diagram of the structure of the relationship processing device in the social platform provided in the embodiments of this application.
[0025] Figure 5 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0026] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.
[0027] The terminology used in the embodiments of this invention is for the purpose of describing particular embodiments only and is not intended to limit the invention. The singular forms “a,” “the,” and “the” as used in the embodiments of this invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.
[0028] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.
[0029] In relationship management interactions on social platforms, to facilitate users' severance of relationships with target individuals and reduce the risk of accidental actions, a common practice is to display a secondary confirmation interface after a user triggers actions such as unfollowing, unfriending, or leaving a group. This secondary confirmation interface typically only includes basic options like "confirm" and "cancel," without providing any additional information. In this lack of information, users struggle to objectively assess the value of the relationship and are prone to making irrational decisions to sever ties due to impulsiveness or insufficient information, leading to unnecessary breakups in social relationships.
[0030] In view of this, this application provides a new approach. To facilitate understanding of this application, the system architecture on which this application is based will first be described. Figure 1 An exemplary system architecture that can be applied to embodiments of this application is shown, such as Figure 1 As shown, the system architecture may include: user terminal, terminal device and server terminal.
[0031] In this embodiment, the user terminal is set on the terminal device. The user terminal involved can be a client running on the terminal device, a mini-program, or a web application running through a browser, etc., and is used to provide users with functions such as social relationship management, friend interaction, relationship termination confirmation, and display of historical interaction data.
[0032] Terminal devices can include, but are not limited to, smart mobile terminals, wearable devices, PCs (Personal Computers), and smart home devices. Smart mobile devices can include devices such as mobile phones, tablets, laptops, PDAs (Personal Digital Assistants), and connected car terminals. Wearable devices can include devices such as smartwatches, smart glasses, smart bracelets, VR (Virtual Reality) devices, AR (Augmented Reality) devices, and mixed reality devices (devices that support both virtual and augmented reality). Smart home devices can include devices such as smart TVs and smart refrigerators with displays.
[0033] The user can interact with the server via the network. The server can be a single server, a server cluster consisting of multiple servers, or a cloud server. A cloud server, also known as a cloud computing server or cloud host, is a host product in the cloud computing service system, designed to address the shortcomings of traditional physical hosts and Virtual Private Servers (VPS) services, such as high management difficulty and weak service scalability.
[0034] One possible approach is for the user to obtain historical interaction data between the user and the target object through interaction with the server, and display the corresponding relationship confirmation interface when the relationship is terminated, providing the user with decision-making reference.
[0035] It should be understood that Figure 1 The number of client terminals, terminal devices, and servers shown is merely illustrative. Depending on implementation needs, there can be any number of client terminals, terminal devices, and servers.
[0036] Figure 2 This is a flowchart illustrating a relationship processing method in a social platform provided in an embodiment of this application. This method can be... Figure 1 The user-side execution in the system shown is as follows. Figure 2 As shown, the method may include the following steps: Step 201: In response to triggering the relationship termination operation for the target object, display the relationship confirmation interface.
[0037] Step 202: Display the historical interaction data between the user and the target object on the relationship confirmation interface so that the user can re-evaluate whether to continue the relationship termination operation based on the historical interaction data.
[0038] As can be seen, by displaying a relationship confirmation interface after detecting a relationship termination action against a target object, and directly showing the user's historical interaction data with the target object on this interface, previously unused relationship data is embedded into the relationship termination decision-making process. This allows users to reassess the current relationship status based on historical interaction information before performing actions such as unfollowing or unfriending. This approach effectively improves the completeness of information and the depth of perception when users make relationship decisions, thereby reducing the tendency for erroneous operations due to information gaps, and improving the effectiveness of relationship processing interactions and the quality of user-driven decision-making.
[0039] The following describes in detail each step of the above process and the effects that can be further produced, with reference to the embodiments.
[0040] It should be noted that the terms "first," "second," etc., used in this disclosure do not imply any limitation in size, order, or quantity; they are merely used to distinguish between them in name. For example, "first group of permission adjustment options" and "second group of permission adjustment options" are used to distinguish between two different groups of permission adjustment options in name. And so on.
[0041] First, the above step 201, namely "displaying a relationship confirmation interface in response to triggering a relationship termination operation for the target object", will be described in detail with reference to the embodiments.
[0042] In this embodiment, the relationship termination operation refers to a type of operation instruction or interactive event used to terminate or exit an existing social relationship. It can be triggered by the user from any entry point, such as the friend list, following list, personal profile, chat session page, or group information page. Triggers may include, but are not limited to, clicking, long-pressing, swiping to select, voice command confirmation, shortcut key triggering, or triggering through accessibility services.
[0043] As a specific implementation method, the user client can detect the triggering of the relationship unfollowing entry at the bottom in the settings floating window of the friends / following list page, and generate a request to display the relationship confirmation interface accordingly; for example, after the user clicks the unfollowing entry, the user client does not immediately submit the relationship unfollowing instruction, but first presents the relationship confirmation interface to carry out the display of historical interaction data and secondary decision-making.
[0044] In this application embodiment, the relationship confirmation interface refers to a type of interface used to display decision information and provide an entry point for operation before the termination of the relationship. It can be a pop-up window, a bottom drawer, a half-screen page, a full-screen page, or a stacked page.
[0045] The following describes step 202, namely, "displaying historical interaction data between the user and the target object on the relationship confirmation interface so that the user can re-evaluate whether to continue the relationship termination operation based on the historical interaction data," in detail with reference to the embodiments.
[0046] In one implementation, after displaying the relationship confirmation interface, the user sends a request for historical interaction data to the server. Request parameters may include user identifier, target object identifier, relationship type identifier, and time window parameters. The server generates and returns historical interaction data based on social relationship data, interaction log data, or message session data. Upon receiving the returned data, the user displays it in structured fields on the relationship confirmation interface, allowing the user to intuitively understand the status of the relationship between the two parties.
[0047] More generally, historical interaction data can be generated from various data sources and through various calculation methods. For example, data sources may include records of follower relationships, friend relationships, chat session metadata, interaction behavior logs (such as likes, comments, reposts, @mentions, mutual visits to profiles, etc.), and group participation records; calculation methods may include deduplicating logs, aggregating by time, weighted summing by interaction type, or statistical analysis by calendar day. On the user side, the display can utilize text fields, icons with numerical values, progress bars, or card-based components to achieve readable output of relationship-related information within a limited space. By incorporating historical interaction data into the relationship confirmation interface after relationship termination is triggered, the system allows users to obtain decision-making references based on existing interaction data before terminating the relationship, thereby improving the problem of interactions that rely solely on secondary confirmation but lack sufficient information support.
[0048] In the embodiments of this application, historical interaction data refers to a data set or any subset thereof that can reflect the accumulation of past interactions and the formation of relationships between users and target objects. It can be a direct mapping of the original records or a statistical result after processing the original records.
[0049] In some embodiments, historical interaction data may include time-based fields, count-based fields, or frequency-based fields; these fields can be calculated and distributed by the server or calculated by the user based on local cache or offline index.
[0050] It should be noted that displaying historical interaction data does not mean that all data dimensions must be displayed. Users can selectively present some dimensions based on screen size, entry scenario, and display strategy, and then carry higher-dimensional information through subsequent pages to balance the efficiency of the main process decision-making and the integrity of information.
[0051] To further optimize the feasibility and readability of historical interaction data in the relationship confirmation interface, the historical interaction data in this application embodiment may include first interaction data with the target object, and / or second interaction data related to the content published by the target object.
[0052] The first interaction data, or direct interaction data, refers to the direct social interactions established between a user and a target object. It characterizes the degree of direct connection between the two parties within their social relationship and may include at least one of the following: the date the user and the target object first met, the number of interactions, and the number of chat days. The date of meeting can be any of the following: the date the two parties first established a follow relationship, the date they first became friends, the date they first followed each other, the date the first effective interaction occurred, or the date they first appeared in the same group. The number of interactions can be a cumulative count of a preset set of interaction types, which may include one or more of the following: likes, comments, private messages, sharing, mutual visits to each other's homepages, etc. The number of chat days can represent the number of natural days in which the two parties had effective message exchanges.
[0053] Secondary interactive data, also known as indirect interactive data, refers to data generated by users interacting with the content published by the target object. It is used to characterize the degree of recognition of the value of the target object's content by users, and may include at least one of the number of likes, comments, and favorites of the content published by the target object.
[0054] The aforementioned first interaction data can characterize the time span and interaction density of the relationship between the two parties, while the second interaction data effectively supplements the accumulation of emotional interaction between users and the target content assets during fragmented time. By clearly dividing historical interaction data into first interaction data and / or second interaction data, the displayed content has clear and diverse data sources and display dimensions.
[0055] In order to expand the depth of relationship information display without significantly increasing the burden on the relationship confirmation interface, the relationship confirmation interface in this embodiment may further include an interactive entry point; in this case, it may further include: in response to the triggering operation of the interactive entry point, jumping to the relationship details page, displaying detailed historical interaction data between the user and the target object on the relationship details page, and the detailed historical interaction data having more dimensions than the historical interaction data.
[0056] In some embodiments, the interactive entry point can be located in the area containing historical interaction data. For example, the entire area containing historical interaction data can be set as a clickable card, or an icon button to enter details can be set on its right. After the user triggers it, the user's terminal performs page routing and loads the relationship details page. The term "historical interaction detailed data has more dimensions than historical interaction data" means that it is richer in terms of the number of fields, field types, or statistical granularity compared to historical interaction data. For example, historical interaction data only displays one or more of the following: date of acquaintance, number of interactions, and number of chat days, while historical interaction detailed data further displays interaction trends by month / week, distribution of different interaction types, key date nodes, or chat activity intervals, etc.
[0057] Through the aforementioned layered display mechanism, the interface remains simple and user decision-making efficiency is improved in the main process of relationship confirmation. At the same time, richer and more granular interactive data is presented on the relationship details page, thereby providing users with complete reference information while ensuring smooth operation.
[0058] As an example, see Figure 3 Figure 3 illustrates the implementation of hierarchical display of historical interaction data after the trigger relationship is terminated. Figure 3 Figure 3(a) shows the relationship confirmation interface, which displays historical interaction data including the date of acquaintance, number of interactions, and number of chat days. The area containing this historical interaction data serves as an interactive entry point, allowing users to jump to the relationship details page by clicking on this area. Figure 3(b) shows the start and end pages of the relationship details page in sequence. This relationship details page adopts an immersive dynamic visualization format to comprehensively display detailed historical interaction data: the opening prominently displays the cumulative number of days the two parties have spent together since they met, while the closing page summarizes and displays in-depth statistical information such as the total number of messages and the total number of chat days throughout the year. The overall page is equipped with an atmospheric visual design, fully reviewing the two parties' relationship journey.
[0059] It should be noted that after the relationship details page fully displays all historical interaction data and evokes the user's emotional response and rational reflection, the bottom of the page will directly reveal... "Think about it again" and "Unfollow" Two core operation options: If a user is still reluctant to sever the relationship, they can directly click "Think about it again" to abandon the unfollowing operation and return to the social list page; if the user still decides to terminate the relationship after a complete review, they can click "Unfollow" to finally complete the relationship termination operation. Through this layered and progressive, emotionally charged + clear operation conclusion, the system provides users with ample space for calm reassessment while also ensuring the convenience of the final operation, greatly reducing the occurrence of irreversible actions such as impulsive unfollowing and misunderstandings leading to unfriending.
[0060] To further improve the matching between the data display and the relationship status on the relationship details page, when displaying detailed historical interaction data on the relationship details page, the intimacy value between the user and the target object can be obtained first; when the intimacy value is greater than a preset threshold, key node data in the detailed historical interaction data can be displayed; when the intimacy value is not greater than the preset threshold, the overall statistical data in the detailed historical interaction data can be displayed.
[0061] The intimacy value refers to a numerical indicator that quantifies the strength of the relationship between the two parties. It can be calculated by the server based on factors such as attention duration, interaction frequency, interaction type weight, chat activity, and shared participation scenarios, or it can be approximated by the user based on cached data.
[0062] As a specific implementation method, the intimacy value can be an integer score from 0 to 100, and the preset threshold can be 60, 70 or other configurable thresholds; the above value range and threshold are only examples, and floating-point numbers from 0 to 1 or other scaling systems can also be used.
[0063] Key node data may include the date of first meeting, the date of first interaction, peak interaction periods, dates of specific events jointly participated in, or nodes of relationship change; overall statistics may include the cumulative number of interactions, the cumulative number of chat days, the number of interactions in the past 30 days, and the percentage of interaction types.
[0064] Through this branch control mechanism, high-intimacy relationships can highlight key nodes to emphasize the process of the relationship, while low-intimacy relationships can highlight overall statistics to quickly summarize the relationship strength, thereby improving the fit between the displayed content and the relationship status.
[0065] To enhance the temporal and procedural representation of multidimensional historical interaction data, dynamic visualizations can be used to display detailed historical interaction data on the relationship details page. Dynamic visualizations can include timeline animations, frame-by-frame card expansion, dynamic data curve plotting, or highlighting and flashing key nodes. For example, when a user enters the relationship details page, the dynamic visualization area sequentially presents the acquaintance date nodes, the growth process of the cumulative interaction curve, and the transition effects of the interaction type distribution, enhancing the user's perception of the relationship's development.
[0066] To provide an alternative relationship handling path during the relationship termination process, the relationship confirmation interface may further include at least one permission adjustment option. Furthermore, it may include: in response to a triggering operation on one of the permission adjustment options, performing the corresponding permission adjustment operation and closing the relationship confirmation interface.
[0067] For example, still refer to Figure 3As shown, the relationship confirmation interface displays historical interaction data, and at the bottom operation area, it displays options such as "Don't look at him" or "Don't let him see him," which are used to adjust the content reception or visibility range without severing the relationship. After the user triggers a certain option, the user's client submits the corresponding permission change request to the server and updates the local state. Then, the relationship confirmation interface is closed and the user returns to the original page, thus forming a closed loop of alternative processing.
[0068] The so-called permission adjustment options refer to an interactive entry point used to trigger content distribution control, display control, visibility control, or message notification control related to the target object. These options can be buttons, switches, radio buttons, multiple options, or secondary confirmation items. The so-called closure confirmation interface can include a direct closure pop-up or a notification that refreshes the page status before closure.
[0069] By integrating permission adjustment options into the relationship confirmation interface, the system can expand the means of relationship handling in the relationship termination process, reducing the rigidity of the path that users can only achieve negative relationship handling through relationship termination, thereby improving the effectiveness of relationship handling interaction.
[0070] To further improve the compatibility between permission adjustment options and relationship status, this application also proposes a mechanism for grouping and displaying permission adjustment options based on intimacy values.
[0071] In a preferred embodiment, displaying at least one permission adjustment option on the relationship confirmation interface includes: obtaining the intimacy value between the user and the target object; displaying a first set of permission adjustment options when the intimacy value is greater than a preset threshold; and displaying a second set of permission adjustment options when the intimacy value is not greater than the preset threshold, wherein the first set of permission adjustment options and the second set of permission adjustment options contain different types or numbers of permission adjustment options.
[0072] For example, when the intimacy level is high, the operation area can display a more gentle or finer-grained set of permission adjustment options, such as only showing options to turn off message notifications from the target object or reduce the content recommendation weight, in order to reduce the abrupt impact on strong relationships; when the intimacy level is low, the operation area can display a more or stronger set of permission adjustment options, such as adding options to block displayed content or reducing content visibility permissions, in order to meet the more direct negative processing needs under weak relationships.
[0073] The aforementioned grouping strategy can be configured by the server or selected by the user based on a local policy table. Through group-based display control, the system can match the content of the permission adjustment interface with the strength of the relationship between the parties, improving the rationality and usability of the option configuration.
[0074] To ensure that the permission adjustment path has a clear execution target and execution content, the permission adjustment options in this application embodiment may include at least one of the following: reducing the content recommendation weight of the target object; blocking the display content of the target object; reducing the content visibility permission of the target object; and disabling message notifications from the target object.
[0075] Specifically, reducing the content recommendation weight can be manifested by applying a negative coefficient to the exposure probability of content related to the target object in the recommendation system or by reducing the ranking score; blocking the display of content can be manifested by filtering the content of the target object during the information flow rendering stage; reducing the content visibility permission can be manifested by adjusting the visibility range of the target object's content from public to partially visible or restricting access; and turning off message notifications can be manifested by turning off notification reminders for the target object's message channel or by silently handling session pushes.
[0076] The above permission adjustment operations can either take effect on the server side and be synchronized to multiple terminals, or they can take effect locally on the user side first and be reconciled with the server side asynchronously.
[0077] By predefining permission adjustment option types, users can directly execute the corresponding control logic after the relationship confirmation interface is triggered, thereby improving the feasibility of alternative relationship processing operations.
[0078] To improve the versatility of this relationship handling method across different business scenarios within social platforms, the relationship undoing operation in this application embodiment may include at least one of the following operations: unfollowing, undoing friend relationship, or leaving a group.
[0079] For example, when a user triggers unfollowing in the following list, the user's client displays a relationship confirmation interface and shows the historical interaction data of both parties; when a user triggers unfriending at the friend relationship entry, the relationship confirmation interface can also be reused and the corresponding historical interaction data can be displayed; when a user triggers leaving a group on the group information page, the target object can be the group object or the group administrator object, and the historical interaction data can correspond to the user's participation time in the group, number of days of speaking, number of interactions, etc., which can still be used to support the user to re-evaluate whether to leave the group.
[0080] It should be noted that the entry point and interactive controls for relationship termination are not limited to the examples above; for different relationship types, the field sets of historical interaction data and historical interaction details data can also be expanded or trimmed according to business attributes.
[0081] Those skilled in the art will understand that combining the aforementioned relationship confirmation interface, historical interaction data display, and optional relationship details page and permission adjustment options can form a consistent decision support chain in different social relationship termination scenarios, thereby directly incorporating historical interaction data into the relationship termination interaction process and improving the effectiveness and information support of relationship processing interactions.
[0082] The following describes the implementation process of the relationship management method for a social platform provided in this application embodiment, using a specific scenario as an example.
[0083] In a social platform focused on content consumption and social interaction, users have a following list to manage their followed targets. User A has been following target B for a long time, and the two have interacted on the platform through likes, comments, and private messages. One day, while browsing the following list, User A, due to a change in their information feed preferences, intends to stop receiving content related to target B and attempts to unfollow target B through a floating window in the following list settings.
[0084] When user A triggers the action to terminate the relationship with target object B, the user's client does not directly submit an unfollow command, but immediately displays a relationship confirmation interface. This relationship confirmation interface is displayed as a pop-up window overlaid on the current page, serving as a display of decision information and an entry point for the operation before the relationship is terminated.
[0085] After the relationship confirmation interface appears, the user sends a request for historical interaction data to the server. The request parameters include the user identifier, target object identifier, and relationship type identifier. The server generates and returns historical interaction data based on social relationship data, interaction behavior log data, and message session data. Upon receiving the returned data, the user displays the historical interaction data between user A and target object B in structured fields on the relationship confirmation interface. This allows user A to intuitively understand the development of their relationship and avoids the tendency to make mistakes due to insufficient information support and reliance on secondary confirmation.
[0086] In this scenario, historical interaction data includes at least one of the following data items: date of acquaintance, number of interactions, and number of chat days. The date of acquaintance can be the date the two parties first established a following relationship or the first effective interaction event occurred; the number of interactions is the cumulative count of a preset set of interaction types such as likes, comments, private messages, shares, and mutual visits to profiles; and the number of chat days is the number of natural days in which the two parties had effective message exchanges. Through these definable data items, the content displayed on the relationship confirmation interface has a clear data source and display dimension, allowing user A to form a calculable and identifiable judgment of the current relationship status based on the acquaintance time and accumulated interactions.
[0087] If user A wants more comprehensive information to aid decision-making within the relationship confirmation interface, an interactive entry point can be triggered. This interactive entry point is located in the area containing historical interaction data; for example, the entire area could be set as a clickable card or an icon button for entering details could be placed on the right. In response to this trigger, the user's device will be redirected to the relationship details page, which displays detailed historical interaction data between user A and target B. This detailed historical interaction data has more dimensions than the basic historical interaction data. For example, in addition to the date of acquaintance, number of interactions, and chat days, it further displays more granular information such as interaction trends by month or week, the distribution of different interaction types, key date points, or chat activity intervals. This expands the depth of information display without increasing the load on the relationship confirmation interface.
[0088] Upon entering the relationship details page, the client or server retrieves the intimacy score between user A and target B and compares it to a preset threshold. When the intimacy score is greater than the preset threshold, the relationship details page displays key node data from historical interaction details to highlight the relationship's progression, such as the date of acquaintance, the date of the first interaction, peak interaction periods, or points of relationship change. When the intimacy score is not greater than the preset threshold, the relationship details page displays overall statistics from historical interaction details to quickly overview the relationship strength, such as cumulative number of interactions, cumulative chat days, number of interactions in the last 30 days, or the percentage of interaction types. This branching control ensures that the displayed content matches the relationship status, reducing the discrepancy between information presentation and the user's focus.
[0089] Meanwhile, the relationship details page provides a dynamic visualization of historical interaction data to enhance its chronological and process-oriented presentation. This dynamic visualization can employ techniques such as timeline animation, frame-by-frame card expansion, dynamic data curve plotting, or highlighting key nodes. This allows user A to see key interaction milestones and accumulated changes from acquaintance to the present as the animation progresses, making it easier to develop a perceptual understanding of the relationship's development. Upon returning to the relationship confirmation screen, user A can then make a more informed decision about whether to proceed with the relationship termination process.
[0090] After User A returns to the relationship confirmation screen, the operation area at the bottom of the screen simultaneously provides at least one permission adjustment option to complete alternative relationship processing without terminating the relationship. If User A simply does not wish to continue receiving content related to Target B, they can trigger the permission adjustment option to reduce the recommendation weight of Target B's content or block the display of Target B's content; if they wish to reduce the other party's access to their own content, they can trigger to reduce the visibility permission of Target B's content; if the main concern is message notifications, they can trigger to disable message notifications from Target B. In response to User A's triggering of one of the permission adjustment options, the user's client executes the corresponding permission adjustment operation, closes the relationship confirmation screen, returns to the original page and updates the local state, and simultaneously submits the permission change request to the server for multi-device effect or asynchronous reconciliation, thus forming a closed-loop processing path that does not depend on relationship termination.
[0091] In this scenario, the user interface can also group and control the display of permission adjustment options based on the intimacy level. When the intimacy level is greater than a preset threshold, the relationship confirmation interface displays the first group of permission adjustment options, making their type or quantity more moderate or granular, such as prioritizing disabling message notifications from the target object or reducing the content recommendation weight of the target object. When the intimacy level is not greater than the preset threshold, the relationship confirmation interface displays the second group of permission adjustment options, making their type or quantity more direct or stronger in terms of control, such as adding blocking of the target object's displayed content or reducing the target object's content visibility permissions. Through this display strategy, the permission adjustment entry is more matched to the strength of the relationship between the two parties, reducing abrupt operations in strong relationships and meeting the need for rapid processing in weak relationships.
[0092] Ultimately, User A re-evaluates the relationship based on historical interaction data on the relationship confirmation screen: if it is confirmed that the relationship needs to be terminated, then the user continues to perform the unfollow operation on the screen to complete the unfollowing process; if the user believes that the relationship still has value after evaluation, then the user chooses to keep following and closes the screen; if the user only wants to change the content reception or visibility range, then the user directly completes the alternative processing through the permission adjustment option and the screen automatically closes.
[0093] In this scenario, the method incorporates historical interaction data into the relationship unfollowing decision-making process, which significantly improves the user experience. Specifically, user A receives visual information about the relationship before unfollowing, reducing impulsive unfollowing and misoperations due to insufficient information. At the same time, even without unfollowing, user A can still achieve fine control over content distribution, display, visibility, and message notifications through permission adjustments, thereby improving the effectiveness and quality of relationship handling interactions.
[0094] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.
[0095] According to another embodiment, a relationship processing device for a social platform is provided. Figure 4 A schematic block diagram of a relationship processing apparatus for a social platform according to one embodiment is shown, the apparatus being disposed in... Figure 1 The user end in the illustrated architecture. For example... Figure 4 As shown, the device 400 includes an interface display unit 410 and a data display unit 420. The main functions of each component are as follows: The interface display unit 410 is configured to display a relationship confirmation interface in response to triggering a relationship termination operation for a target object. The data display unit 420 is configured to display historical interaction data between the user and the target object on the relationship confirmation interface, so that the user can re-evaluate whether to continue the relationship termination operation based on the historical interaction data.
[0096] In one embodiment, the historical interaction data includes first interaction data with the target object and / or second interaction data related to the content published by the target object; wherein, the first interaction data includes at least one of the date the user met the target object, the number of interactions, and the number of chat days; and the second interaction data includes at least one of the number of likes, comments, and favorites the user has given to the content published by the target object.
[0097] In one embodiment, the relationship confirmation interface includes an interactive entry point; the device further includes: The page jump unit is configured to jump to the relationship details page in response to the trigger operation of the interactive entry, and the relationship details page displays the historical interaction details data between the user and the target object. The historical interaction details data has more dimensions than the historical interaction data.
[0098] In one embodiment, the page navigation unit is specifically configured as follows: Obtain the intimacy value between the user and the target object; when the intimacy value is greater than a preset threshold, display key node data in the detailed historical interaction data; when the intimacy value is not greater than the preset threshold, display the overall statistical data in the detailed historical interaction data.
[0099] In one embodiment, the page navigation unit is specifically configured as follows: The relationship details page displays the detailed historical interaction data in a dynamic and visual manner.
[0100] In one embodiment, the interface display unit 410 is further configured to: display at least one permission adjustment option on the relationship confirmation interface; and in response to a triggering operation on one of the permission adjustment options, perform a corresponding permission adjustment operation and close the relationship confirmation interface.
[0101] In one embodiment, the interface display unit 410 is specifically configured to: obtain the intimacy value between the user and the target object; when the intimacy value is greater than a preset threshold, display a first set of permission adjustment options; when the intimacy value is not greater than the preset threshold, display a second set of permission adjustment options, wherein the first set of permission adjustment options and the second set of permission adjustment options contain different types or numbers of permission adjustment options.
[0102] In one embodiment, the permission adjustment options include at least one of the following: reducing the content recommendation weight of the target object; blocking the display content of the target object; reducing the content visibility permission of the target object; and disabling message notifications from the target object.
[0103] In one embodiment, the relationship undoing operation includes at least one of the following operations: unfollowing, undoing the friend relationship, or leaving the group.
[0104] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or device embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the description of the method embodiments. The system and device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The 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 the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.
[0105] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.
[0106] In addition, embodiments of this application also provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the method described in any of the foregoing method embodiments.
[0107] And an electronic device, comprising: One or more processors; and A memory associated with the one or more processors, the memory being used to store program instructions that, when read and executed by the one or more processors, perform the steps of the method described in any of the foregoing method embodiments.
[0108] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in any of the foregoing method embodiments.
[0109] in, Figure 5 An exemplary architecture of an electronic device is shown, which may include a processor 510, a video display adapter 511, a disk drive 512, an input / output interface 513, a network interface 514, and a memory 520. The processor 510, video display adapter 511, disk drive 512, input / output interface 513, network interface 514, and memory 520 can communicate with each other via a communication bus 830.
[0110] The processor 510 can be implemented using a general-purpose CPU, microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits to execute relevant programs and implement the technical solution provided in this application.
[0111] The memory 520 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 520 can store the operating system 521 for controlling the operation of the electronic device 500, and the basic input / output system (BIOS) 522 for controlling the low-level operations of the electronic device 500. Additionally, it can store a web browser 523, a data storage management system 524, and a relationship processing device 400 for a social platform, etc. The aforementioned relationship processing device 400 for the social platform can be the application program that specifically implements the aforementioned steps in this embodiment. In summary, when the technical solution provided in this application is implemented through software or firmware, the relevant program code is stored in the memory 520 and is called and executed by the processor 510.
[0112] Input / output interface 513 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touch screens, microphones, various sensors, etc., and output devices may include displays, speakers, vibrators, indicator lights, etc.
[0113] Network interface 514 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).
[0114] Bus 530 includes a pathway for transmitting information between various components of the device, such as processor 510, video display adapter 511, disk drive 512, input / output interface 513, network interface 514, and memory 520.
[0115] It should be noted that although the above-described device only shows the processor 510, video display adapter 511, disk drive 512, input / output interface 513, network interface 514, memory 520, bus 530, etc., in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the solution of this application, and does not necessarily include all the components shown in the figures.
[0116] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer program product. This computer program product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.
[0117] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A method for handling relationships on a social platform, characterized in that, The method includes: In response to triggering a relationship termination operation on the target object, a relationship confirmation interface is displayed; The relationship confirmation interface displays historical interaction data between the user and the target object, allowing the user to reassess whether to continue the relationship termination operation based on the historical interaction data.
2. The method for relationship processing in a social platform according to claim 1, wherein, The historical interaction data includes first interaction data with the target object, and / or second interaction data related to the content published by the target object; The first interaction data includes at least one of the date the user met the target object, the number of interactions, and the number of chat days; the second interaction data includes at least one of the number of likes, comments, and favorites the user has on the content posted by the target object.
3. The method for relationship processing in a social platform of claim 1, wherein, The relationship confirmation interface includes an interactive entry point; the method further includes: In response to the triggering operation of the interactive entry point, the user is redirected to the relationship details page, which displays detailed historical interaction data between the user and the target object. The detailed historical interaction data has more dimensions than the historical interaction data.
4. The method of claim 3, wherein, The detailed historical interaction data between the user and the target object is displayed on the relationship details page, including: Obtain the intimacy value between the user and the target object; When the intimacy value is greater than a preset threshold, key node data from the detailed historical interaction data is displayed; when the intimacy value is not greater than the preset threshold, overall statistical data from the detailed historical interaction data is displayed.
5. The method for relationship processing in a social platform of claim 3, wherein, The detailed historical interaction data between the user and the target object is displayed on the relationship details page, including: The relationship details page displays the detailed historical interaction data in a dynamic and visual manner.
6. The relationship processing method in a social platform according to claim 1, characterized in that, The method further includes: At least one permission adjustment option is displayed on the relationship confirmation interface; In response to a trigger operation on one of the permission adjustment options, the corresponding permission adjustment operation is performed, and the relationship confirmation interface is closed.
7. The relationship processing method in a social platform according to claim 6, characterized in that, The display of at least one permission adjustment option on the relationship confirmation interface includes: Obtain the intimacy value between the user and the target object; When the intimacy value is greater than a preset threshold, the first set of permission adjustment options is displayed; When the intimacy value is not greater than the preset threshold, a second set of permission adjustment options is displayed. The first set of permission adjustment options and the second set of permission adjustment options contain different types or numbers of permission adjustment options.
8. The relationship processing method in a social platform according to claim 6 or 7, characterized in that, The permission adjustment options include at least one of the following: Reduce the content recommendation weight of the target object; To block the display content of the target object; Reduce the content visibility permission of the target object; Disable message notifications from the target object.
9. The relationship processing method in a social platform according to claim 1, characterized in that, The relationship termination operation includes at least one of the following: unfollowing, removing the friend relationship, or leaving the group.
10. A relationship processing device in a social platform, characterized in that, The device includes: The interface display unit is configured to display a relationship confirmation interface in response to triggering a relationship termination operation on the target object; The data display unit is configured to display historical interaction data between the user and the target object on the relationship confirmation interface, so that the user can re-evaluate whether to continue the relationship termination operation based on the historical interaction data.
11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the method according to any one of claims 1 to 9.
12. An electronic device, characterized in that, include: One or more processors; as well as A memory associated with the one or more processors, the memory being used to store program instructions that, when read and executed by the one or more processors, perform the steps of the method according to any one of claims 1 to 9.
13. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 9.