TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Reverse Engineering WhatsApp Web

350 点作者 wjh_大约 7 年前

16 条评论

gustavmarwin大约 7 年前
I&#x27;m very hopeful this reverse engineering effort will enable the creation of a tool to export my conversations (WhatsApp can do email export, which let&#x27;s be real, doesn&#x27;t cut it for most cases).<p>A point to those that support migrating to alternatives such as Signal. Signal is good, but far from great for a single reason: you need a phone number. This is very bad in necsec and reliability terms, my case:<p>Reliability: like more and more people, I travel all the time between countries and live out of Airbnbs. Hence my pre-paid phone numbers changes very regularly. If I lose my phone, I lose the phone number, I also lose my Whatsapp&#x2F;Signal key associated with my phone number.<p>Netsec: A phone number is associated with your physical identity, you might not care, but more and more people do care about this stuff. Yes there are ways around that, but nothing straightforward and actually practical.<p>I&#x27;m patiently, but eagerly, looking forward to status.im .
评论 #16796080 未加载
评论 #16795121 未加载
评论 #16798385 未加载
评论 #16797459 未加载
评论 #16796971 未加载
评论 #16794234 未加载
firefoxd大约 7 年前
I see a lot of &quot;just use X instead.&quot;<p>Unfortunately, unlike the old chat protocols, switching to any other platform means convincing your contacts to use a new platform. They like you and all, but that means they also have to use a special app just to talk with you now.
评论 #16819610 未加载
salqadri大约 7 年前
Wow that&#x27;s impressive. But I would imagine WhatsApp&#x2F;Facebook can just change their protocol at any time since it is easy to redeploy a new version of the WhatsApp Web client, thus breaking any 3p clients built on the original protocol. That would require yet another reverse engineering effort that can take a while. And by the time its reverse engineered again, they can yet again change the protocol. So the only reliable way to create 3p clients would be if WhatsApp itself publicly publishes its protocol.
评论 #16794061 未加载
评论 #16794433 未加载
评论 #16804094 未加载
评论 #16794737 未加载
0x0大约 7 年前
Curious to know why they chose to require python in addition to node, wouldn&#x27;t node with npmjs&#x2F;yarn be sufficient and require less setup? Does python&#x2F;pip provide any benefits here?
评论 #16796791 未加载
评论 #16798037 未加载
ktosobcy大约 7 年前
Wouldn&#x27;t it be better to simply start convincing your friends to use something more open, where you have choice of the client? It feels like solving the problem from the wrong angle…
评论 #16795959 未加载
评论 #16793838 未加载
评论 #16795077 未加载
anonu大约 7 年前
Impressive work.<p>Obviously, WhatsApp&#x2F;Facebook would want to avoid a bunch of third party apps connecting to their service. How long until they make changes to make this more difficult&#x2F;impossible?
评论 #16793816 未加载
评论 #16793711 未加载
alpb大约 7 年前
FWIW Repos like these that reverse engineer a proprietary API that post stuff on GitHub are usually taken down with a DMCA enforcement. The same thing happened multiple times when folks reverse engineered and documented the Snapchat API. <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=6083812" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=6083812</a>
评论 #16796607 未加载
Jaruzel大约 7 年前
From the GitHub readme:<p>&gt; <i>An UI that is not that technical, but rather starts to emulate the actual WhatsApp Web UI.</i><p>No, no, no. This trend of &#x27;Phone UI&#x27; chat interfaces on desktop&#x2F;laptop screens needs to stop. If you are going to all this effort to reverse engineer the protocol, at least make your front end customisable or at the very least IRCish in style.
andjd大约 7 年前
I&#x27;m missing why this needs both a python and a node backend.
评论 #16796800 未加载
评论 #16796885 未加载
mratzloff大约 7 年前
Many of the vendors we partner with (tourism industry) live in countries where the main communication channel is WhatsApp. There&#x27;s a lot of communication we want to automate in the near future—eagerly looking forward to seeing this progress!
mikkelam大约 7 年前
Were you inspired by this repository <a href="https:&#x2F;&#x2F;github.com&#x2F;mukulhase&#x2F;WebWhatsAPI" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mukulhase&#x2F;WebWhatsAPI</a>?<p>Do you need a phone running to use this project?
letslightafire大约 7 年前
I&#x27;m wondering how they actually reverse engineered WhatsApp in the first place. Is there a specific type of software that does this or was it just built from scratch using already available information?
评论 #16796756 未加载
ape4大约 7 年前
A pidgin plugin would be nice. Oh there seems to be one already - <a href="https:&#x2F;&#x2F;github.com&#x2F;davidgfnet&#x2F;whatsapp-purple&#x2F;" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;davidgfnet&#x2F;whatsapp-purple&#x2F;</a>
评论 #16796231 未加载
评论 #16796318 未加载
quantized1大约 7 年前
Let&#x27;s bring some more misery to Zuckerberg
pankajdoharey大约 7 年前
Why did they not write the backend server for Whatsapp web in Erlang, which the original Whatsapp was mostly written in?
评论 #16799203 未加载
Turm大约 7 年前
Noob question: Is traffic going through the websocket-servers properly end-to-end encrypted? That&#x27;s what always held me back about using Whatsapp Web
评论 #16797164 未加载