WhatsApp 网页版又重又慢？
ZapFast 是 Rust 原生客户端，Linux 下 1 秒内打开、待机约 200MB，多号一窗切换，扫码以伴侣设备接入。
适合多号、嫌网页版重的人，非官方客户端有封号风险，先拿备用号试。
你 WhatsApp 几个号，一个还是多个？
#WhatsApp #Rust @grok
crmne/zapfast
3 likes · 186 views
@WindowsLatest Whatsapp made with rust, test this app please.
crmne/zapfast
2 likes · 26 views
@notdarkhead @WindowsLatest Whatsapp client made with rust.
crmne/zapfast
2 likes · 15 views
Po Zap em Rust crmne/zapfast
Nice @paolino. I'm going to try it right now!
4 likes · 239 views
WhatsApp’s latest Mac update is a disaster for UI/UX and performance.
I tried Zapfast, and I’m loving it. Great work @paolino
crmne/zapfast
5 likes · 1 repost · 227 views
ZapFast GitHub Explained: Native WhatsApp Client Tradeoffs and Account Risk
zapfast by crmne: crmne/zapfast
ZapFast website: zapfast.rocks
ZapFast is a native desktop WhatsApp companion built in Rust with an immediate-mode egui interface. This overview explains the central tradeoff: avoiding a browser wrapper can reduce the narrated idle-memory comparison from more than 1.13 GB to about 150–200 MB, with a launch time under one second. The efficiency comes with a phone-dependent companion protocol: QR authorization, recent-message sync, an encrypted local SQLCipher archive, and limited access to older history. Keyboard navigation and multi-account support improve the local workflow, while group-call creation and automatic downloads for videos over 64 MB remain constrained. The biggest caveat is platform risk: the narration says this unofficial interface violates WhatsApp's terms and may lead to account restriction or suspension.
TimeStamps:
0:00 Why web-wrapped chat apps are memory-heavy
0:41 Rust and egui cut the desktop footprint
1:12 Companion-device pairing without its own servers
1:38 QR authorization and the local encrypted archive
2:15 Why older chat history depends on the phone
2:52 Keyboard navigation and multi-account support
3:17 Protocol limits: group calls and large media
3:44 Fast local UI, network walls, and account risk
4:24 Engineering proof of concept, not a mass-market recommendation
4:52 The memory-versus-account-risk tradeoff
🧠 Native Rust and egui architecture target a leaner desktop footprint.
🔗 QR pairing makes the phone the authority for sync and history.
⌨️ Keyboard navigation and multi-account support improve local workflow.
⚠️ Protocol limits and WhatsApp account risk define the tradeoff.
ZapFast is best understood as an engineering case study in native desktop messaging: lean local rendering and useful keyboard workflows traded against phone-dependent history, protocol gaps, and platform enforcement risk. Developers can inspect the repository and weigh the memory savings against those limits before considering any personal or production use.
#ZapFast #Rust #WhatsApp
[de-DE] YNAS ynp_dd4613ff6ead1bac Cinematic
Privater automatisierter Staging-Upload. Paketidentität: ynp_dd4613ff6ead1bac; Ausgabe: cinematic.
[es-US] YNAS ynp_dd4613ff6ead1bac cinemático
Carga de entorno de prueba de automatización privada. Identidad del paquete: ynp_dd4613ff6ead1bac; salida: cinemática.
[fr-FR] YNAS ynp_dd4613ff6ead1bac cinématique
Téléchargement de l'environnement de test d'automatisation privé. Identifiant du package : ynp_dd4613ff6ead1bac ; sortie : cinématique.
[hi] YNAS ynp_dd4613ff6ead1bac सिनेमैटिक
निजी स्वचालन स्टेजिंग अपलोड। पैकेज पहचान: ynp_dd4613ff6ead1bac; आउटपुट: सिनेमाई।
[id] Sinematik YNAS ynp_dd4613ff6ead1bac
Unggahan staging otomatisasi pribadi. Identitas paket: ynp_dd4613ff6ead1bac; output: cinematic.
[it] YNAS ynp_dd4613ff6ead1bac cinematic
Caricamento di automazione privata. Identità del pacchetto: ynp_dd4613ff6ead1bac; output: cinematico.
[pt-BR] YNAS ynp_dd4613ff6ead1bac cinematográfico
Upload de teste de automação privada. Identificação do pacote: ynp_dd4613ff6ead1bac; saída: cinemática.
4 likes · 787 views
WhatsApp Client
I have been using CachyOS for 70 days now, and I am really impressed.
I use WhatsApp a lot, but have hated using the web client because a separate window is so much easier to monitor. I have used the dedicated client Whatsie and it has been great, but it really eats through RAM. I had a Whatsie session running at 4GB of RAM, when my Firefox session with 8 tabs only needed 3.5GB. I decided to try something else...
Zapfast does mostly the same as Whatsie but is only using 200mb of RAM. I had to compile it for CachyOS, but the time spent was well worth it. Would recommend.
crmne/zapfast
**Edit**
No spell check! This is probably going to be a deal breaker for me.
Looking at some advice from people below I am trying PWA for Firefox. So far, so good.
addons.mozilla.org
But no calling, and needing to use Profiles messed up everything else.
Going back to Zapfast and learning to spell...
65 points · 47 comments
ZapTide: a native GTK4/libadwaita WhatsApp client for GNOME, written in Rust
Image illustration of ZapTide a native GTK4\/Libadwaita WhatsApp client for Linux
I've been building ZapTide, a WhatsApp client for Linux with a native GTK4 and libadwaita interface. It uses Relm4 and has no browser engine or Electron underneath. Uses between 150 MiB ~ 350 MiB of RAM.
It pairs with your phone as a linked device through whatsapp-rust. Messages are stored locally in an archive encrypted with a key from your OS keyring.
You can chat, search, and send text, replies, reactions, polls, voice notes, stickers and attachments. Photos sent together show up as one album, and you can drop files anywhere in a conversation to attach them. Contact cards come with copy, add-to-contacts and message actions. Notifications, typing and delivery status work, and read state, mutes and chat locks stay in sync with your phone. There are light, dark and custom themes, keyboard shortcuts and screen-reader labels, though accessibility is still incomplete.
Calls, status posts, communities and group administration aren't supported, and newsletter channels are read-only.
It comes as a Flatpak bundle or AppImage for x86_64 and aarch64 on the releases page.
It's unofficial and not affiliated with WhatsApp or Meta. Using an unofficial client may violate their terms and put your account at risk, so link it at your own discretion.
ZapTide is a fork of ZapFast. I replaced the egui interface with a native GTK one; the protocol and archive layers still come from upstream. It's still 0.x, so expect rough edges.
Source, releases and bug reports: luminusOS/zaptide
Regarding the use of LLMs, I use Open Code with Zed IDE as my main coding tool. It helps mostly with finding APIs and integrations that would otherwise take a lot of digging through docs. The ideas, code review and final testing are my own.
I'd like feedback on the UI and on how well it follows the GNOME HIG.
56 points · 18 comments
Mentions
WhatsApp 网页版又重又慢？ ZapFast 是 Rust 原生客户端，Linux 下 1 秒内打开、待机约 200MB，多号一窗切换，扫码以伴侣设备接入。 适合多号、嫌网页版重的人，非官方客户端有封号风险，先拿备用号试。 你 WhatsApp 几个号，一个还是多个？ #WhatsApp #Rust @grok crmne/zapfast
@WindowsLatest Whatsapp made with rust, test this app please. crmne/zapfast
@notdarkhead @WindowsLatest Whatsapp client made with rust. crmne/zapfast
Po Zap em Rust crmne/zapfast Nice @paolino. I'm going to try it right now!
WhatsApp’s latest Mac update is a disaster for UI/UX and performance. I tried Zapfast, and I’m loving it. Great work @paolino crmne/zapfast
ZapFast GitHub Explained: Native WhatsApp Client Tradeoffs and Account Risk zapfast by crmne: crmne/zapfast ZapFast website: zapfast.rocks ZapFast is a native desktop WhatsApp companion built in Rust with an immediate-mode egui interface. This overview explains the central tradeoff: avoiding a browser wrapper can reduce the narrated idle-memory comparison from more than 1.13 GB to about 150–200 MB, with a launch time under one second. The efficiency comes with a phone-dependent companion protocol: QR authorization, recent-message sync, an encrypted local SQLCipher archive, and limited access to older history. Keyboard navigation and multi-account support improve the local workflow, while group-call creation and automatic downloads for videos over 64 MB remain constrained. The biggest caveat is platform risk: the narration says this unofficial interface violates WhatsApp's terms and may lead to account restriction or suspension. TimeStamps: 0:00 Why web-wrapped chat apps are memory-heavy 0:41 Rust and egui cut the desktop footprint 1:12 Companion-device pairing without its own servers 1:38 QR authorization and the local encrypted archive 2:15 Why older chat history depends on the phone 2:52 Keyboard navigation and multi-account support 3:17 Protocol limits: group calls and large media 3:44 Fast local UI, network walls, and account risk 4:24 Engineering proof of concept, not a mass-market recommendation 4:52 The memory-versus-account-risk tradeoff 🧠 Native Rust and egui architecture target a leaner desktop footprint. 🔗 QR pairing makes the phone the authority for sync and history. ⌨️ Keyboard navigation and multi-account support improve local workflow. ⚠️ Protocol limits and WhatsApp account risk define the tradeoff. ZapFast is best understood as an engineering case study in native desktop messaging: lean local rendering and useful keyboard workflows traded against phone-dependent history, protocol gaps, and platform enforcement risk. Developers can inspect the repository and weigh the memory savings against those limits before considering any personal or production use. #ZapFast #Rust #WhatsApp [de-DE] YNAS ynp_dd4613ff6ead1bac Cinematic Privater automatisierter Staging-Upload. Paketidentität: ynp_dd4613ff6ead1bac; Ausgabe: cinematic. [es-US] YNAS ynp_dd4613ff6ead1bac cinemático Carga de entorno de prueba de automatización privada. Identidad del paquete: ynp_dd4613ff6ead1bac; salida: cinemática. [fr-FR] YNAS ynp_dd4613ff6ead1bac cinématique Téléchargement de l'environnement de test d'automatisation privé. Identifiant du package : ynp_dd4613ff6ead1bac ; sortie : cinématique. [hi] YNAS ynp_dd4613ff6ead1bac सिनेमैटिक निजी स्वचालन स्टेजिंग अपलोड। पैकेज पहचान: ynp_dd4613ff6ead1bac; आउटपुट: सिनेमाई। [id] Sinematik YNAS ynp_dd4613ff6ead1bac Unggahan staging otomatisasi pribadi. Identitas paket: ynp_dd4613ff6ead1bac; output: cinematic. [it] YNAS ynp_dd4613ff6ead1bac cinematic Caricamento di automazione privata. Identità del pacchetto: ynp_dd4613ff6ead1bac; output: cinematico. [pt-BR] YNAS ynp_dd4613ff6ead1bac cinematográfico Upload de teste de automação privada. Identificação do pacote: ynp_dd4613ff6ead1bac; saída: cinemática.
WhatsApp Client I have been using CachyOS for 70 days now, and I am really impressed. I use WhatsApp a lot, but have hated using the web client because a separate window is so much easier to monitor. I have used the dedicated client Whatsie and it has been great, but it really eats through RAM. I had a Whatsie session running at 4GB of RAM, when my Firefox session with 8 tabs only needed 3.5GB. I decided to try something else... Zapfast does mostly the same as Whatsie but is only using 200mb of RAM. I had to compile it for CachyOS, but the time spent was well worth it. Would recommend. crmne/zapfast **Edit** No spell check! This is probably going to be a deal breaker for me. Looking at some advice from people below I am trying PWA for Firefox. So far, so good. addons.mozilla.org But no calling, and needing to use Profiles messed up everything else. Going back to Zapfast and learning to spell...
ZapTide: a native GTK4/libadwaita WhatsApp client for GNOME, written in Rust Image illustration of ZapTide a native GTK4\/Libadwaita WhatsApp client for Linux I've been building ZapTide, a WhatsApp client for Linux with a native GTK4 and libadwaita interface. It uses Relm4 and has no browser engine or Electron underneath. Uses between 150 MiB ~ 350 MiB of RAM. It pairs with your phone as a linked device through whatsapp-rust. Messages are stored locally in an archive encrypted with a key from your OS keyring. You can chat, search, and send text, replies, reactions, polls, voice notes, stickers and attachments. Photos sent together show up as one album, and you can drop files anywhere in a conversation to attach them. Contact cards come with copy, add-to-contacts and message actions. Notifications, typing and delivery status work, and read state, mutes and chat locks stay in sync with your phone. There are light, dark and custom themes, keyboard shortcuts and screen-reader labels, though accessibility is still incomplete. Calls, status posts, communities and group administration aren't supported, and newsletter channels are read-only. It comes as a Flatpak bundle or AppImage for x86_64 and aarch64 on the releases page. It's unofficial and not affiliated with WhatsApp or Meta. Using an unofficial client may violate their terms and put your account at risk, so link it at your own discretion. ZapTide is a fork of ZapFast. I replaced the egui interface with a native GTK one; the protocol and archive layers still come from upstream. It's still 0.x, so expect rough edges. Source, releases and bug reports: luminusOS/zaptide Regarding the use of LLMs, I use Open Code with Zed IDE as my main coding tool. It helps mostly with finding APIs and integrations that would otherwise take a lot of digging through docs. The ideas, code review and final testing are my own. I'd like feedback on the UI and on how well it follows the GNOME HIG.