QQ rolls over WeChat bug, how should programmers deal with it?

Huizhimei said that she has been eating melon recently! In addition to the surrogacy incident, the two major products of the goose factory, WeChat and QQ, are also quite interesting.

 

As a software test engineer, I am not curious: If we are IT programmers in the goose factory, how should we deal with it?

 

QQ read browser history

 

process:

● On January 17, there was a forum article saying that "QQ will read the history of web browsers", and the content was then linked to Zhihu to ask questions, which triggered heated discussions among QQ users.

 

● On January 18th, Tencent QQ answered a question on the Zhihu official account and said: QQ security team attaches great importance to it and launched an investigation, and found that PC QQ reads the browser history to determine user login security risks. The data read It is used to judge whether it is malicious login in the local client of PC QQ. All relevant data will not be uploaded to the cloud, will not be stored, and will not be used for any other purpose.

 

 

● Immediately after Tencent claimed to apologize for this incident, internally it is sorting out historical issues and strengthening user data access specifications. At present, the technical logic for detecting malicious and abnormal requests has been replaced to solve the above-mentioned security risk issues, and a new PC QQ version has been released.

 

However, this wave of public relations operations by the Goose Factory did not seem to make the majority of netizens buy it, and even after the official reply, it once again triggered a new wave of rants:

 

 

As for the reason, Huizhimei analyzed the following points:

 

1. The background accesses user data by default without prior notification or authorization, which invisibly violates platform user privacy;

 

2. The goose factory sits on the right to speak, and acts as a monopoly when the laws and regulations are not yet perfect. After the incident, Dongchuang apologized;

 

3. The official explanation is almost perfunctory, and the replacement of the so-called technical logic does not guarantee that it will not infringe on user data privacy again. When the trust of the platform is greatly reduced, this national-level app will inevitably fall into a platform kidnapping situation.

 

WeChat bug incident

 

On the afternoon of January 18th, many netizens continued to report that the messages posted in the WeChat group could not be seen by everyone, and they were suspected to be WeChat bugs. Then the WeChat official responded: I'm very sorry, due to system jitter, some WeChat users encountered a delay in receiving messages at around 14:00 today, and the repair has now been completed.

 

 

Note: System jitter is interpreted as in the request paging storage management, after a page has just been swapped out (Swap Out) from the main memory (DRAM) (swap out to Disk), it will be swapped in (Swap In) immediately upon request. Page, this phenomenon of repeated swapping out and swapping in. The main reason for this phenomenon is improper selection of replacement algorithm.

 

As another major national-level app under the Goose Factory, the emergence of the WeChat bug has caused a mess in the social circle. Everyone has complained about the impact of the WeChat bug, and even bloggers hypothesized that "global internet disconnection" "The impact it will bring, the reply in the comment area is also dumbfounding:

 

 

In fact, social networks have now penetrated into the daily lives of every citizen, and the larger the platform users, the heavier the mission of operation and maintenance security needs to be shouldered.

 

From the perspective of software testing, how to ensure correct product operation and give platform users a smoother experience is not only related to word-of-mouth stickiness, but also the focus of the game against competition.

 

As we all know, other Internet companies other than Goose Factory have tried various social products before. Aiming at the pain points of WeChat user experience, "multi flash" (byte beating Zhang Yiming) "toilet" (Quickcast Wang Xin) "chat" "Bao" (Luo Yonghao) and others were ruthlessly blocked by the goose factory with a strong monopoly position.

 

Although the emergence of the WeChat bug was unexpected by the software testing engineers, it also sounded a wake-up call to the product team of the Goose Factory. It is related to the experience of hundreds of millions of users, and the daily operation and maintenance is extremely sloppy!

 

What would you do if it were you

 

In line with the principle of "not forgetting introspection while eating melons", Huizhimei can't help asking everyone here: In the face of the above product bug incidents, how would you deal with it?

 

You know, as the first echelon of Internet companies, Goose Factory has long been a holy place for countless IT programmers. If interviewers throw similar topics and can win a high-paying offer with a satisfactory answer, this is also what we are. One of the comprehensive IT skills possessed by soft test engineers~

 

 

Huizhimei also shared the regular bug submission process before, but many programmers said that the process of their company is much more complicated than the picture shown. So, the comment area will be handed over to everyone next, and I look forward to the wise you can give the interviewer a unique and wonderful reply!

 

Guess you like

Origin blog.csdn.net/weixin_43802541/article/details/112848860