Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wacli – WhatsApp CLI

github.com

Post reply on HN
Print view View original

51–60 of 168 posts

Re: Wacli – WhatsApp CLI

#51

Post by NoahZuniga »

sigmoid10 wrote: post #49
batuhanicoz wrote: post #34

Earlier quoted context omitted.

The way I would put it as someone who works at Beeper is: only use messaging automations for personal use, and don't use it to spam anyone or do anything you wouldn't do yourself within the app. As long as you don't abuse and keep your usage within the parameters of any human, you'll be fine.

...until Meta decides they want to offer this kind of thing themselves and ban everyone else. Building your SaaS on top of someone else's SaaS is always a gamble, especially if said product is directly sold to users already and not a pure b2b intermediate.

Meta already has a whatsapp api product

Re: Wacli – WhatsApp CLI

#52

Post by taminka »

tazjin wrote: post #22
taminka wrote: post #18

Earlier quoted context omitted.

it's really unfortunate that telegram doesn't do e2ee, bc it's hands down the best messenger otherwise :(

It does, but only for chats between two specific devices. Multi-device support is one of its best features that you lose with E2E. Key distribution is just too hard. I think we won't get a messenger for non-tech people that works well with multi-device and E2E basically ever.

whatsapp, facebook messenger, imessage all support multi-device and it's pretty convenient, in fairness to telegram they launched a bit before double ratched was invented, but still, they've had over a decade to switch to it...

Re: Wacli – WhatsApp CLI

#53

Post by joshwarwick15 »

sigmoid10 wrote: post #49
batuhanicoz wrote: post #34

Earlier quoted context omitted.

The way I would put it as someone who works at Beeper is: only use messaging automations for personal use, and don't use it to spam anyone or do anything you wouldn't do yourself within the app. As long as you don't abuse and keep your usage within the parameters of any human, you'll be fine.

...until Meta decides they want to offer this kind of thing themselves and ban everyone else. Building your SaaS on top of someone else's SaaS is always a gamble, especially if said product is directly sold to users already and not a pure b2b intermediate.

They're already outright banning many OpenClaw usecases via their official API: https://techcrunch.com/2025/10/18/whatssapp-changes-its-term...

Re: Wacli – WhatsApp CLI

#54

Post by taminka »

ymolodtsov wrote: post #27
tazjin wrote: post #22

Earlier quoted context omitted.

It does, but only for chats between two specific devices. Multi-device support is one of its best features that you lose with E2E. Key distribution is just too hard. I think we won't get a messenger for non-tech people that works well with multi-device and E2E basically ever.

It's called iMessage. It's possible, Telegram just doesn't care. All their differentiating features (large groups, channels, device sync) is directly enabled by the lack of encryption.

they do have encryption, just not e2ee, and in fairness to them, it doesn't make sense to have e2ee on a channel or a group with 100k ppl in it, also device sync is possible with e2ee, it's just a slower

Re: Wacli – WhatsApp CLI

#55

Post by ButlerianJihad »

miroljub wrote: post #21
watermelon0 wrote: post #13

Earlier quoted context omitted.

You should use a separate WhatsApp account for bot purposes. Recently, I used a separate WhatsApp account to interact with a group chat that I have with my friends. After about a week, they disabled the account, with no way to re-enable it.

Since WhatsApp accounts are bound to phone numbers, getting a new phone number is a significant hurdle in many legislations. An easier solution is to just not use WhatsApp at all and look for the alternatives for bot purposes. Telegram explicitly encourages bot usage with no risk of bans.

> in many legislations

Do you mean “jurisdictions”?

Re: Wacli – WhatsApp CLI

#56

Post by adaptit »

zarzavat wrote: post #11

Beware that if this does not use a real web browser then it's likely to get your whatsapp account suspended. Don't use it with any account you care about, you will lose all your data. Hell, I got my whatsapp account suspended (appealed and reversed) just for using the official web client too soon after creating a new account.

[dead]

Re: Wacli – WhatsApp CLI

#58

Post by oulipo2 »

batuhanicoz wrote: post #19
recsv-heredoc wrote: post #3

This is such a sorely needed point of integration. Cool to see Peter still shipping tools. It’s such a pity meta refuses to play ball like Telegram. Either they’ll double-down and make this even harder -or- hopefully realise that WhatsApp is likely to be a really common control plane for AI systems in the next few years. Let’s hope the Llama energy strikes and it’s the latter. How does WhatsMeow compare with Baileys?

whatsmeow is built and maintained by Beeper's bridge architect, Tulir Asokan, and is used by many Beeper users every day with no issues. It's at the core of our WhatsApp bridge: https://github.com/mautrix/whatsapp Baileys is also a great library with a big community and one of the primary maintainers of that is also helping us with the bridge/whatsmeow. WhatsApp integration in our old app, Texts, was built with it: h…

So whatsmeow requires a browser, and Baileys not right? So it's a bit more lightweight in terms of RAM?

Re: Wacli – WhatsApp CLI

#59

Post by batuhanicoz »

oulipo2 wrote: post #58
batuhanicoz wrote: post #19

Earlier quoted context omitted.

whatsmeow is built and maintained by Beeper's bridge architect, Tulir Asokan, and is used by many Beeper users every day with no issues. It's at the core of our WhatsApp bridge: https://github.com/mautrix/whatsapp Baileys is also a great library with a big community and one of the primary maintainers of that is also helping us with the bridge/whatsmeow. WhatsApp integration in our old app, Texts, was built with it: h…

So whatsmeow requires a browser, and Baileys not right? So it's a bit more lightweight in terms of RAM?

Neither of them require a browser. We run whatsmeow inside iOS and Android apps, with no browser whatsoever.

Re: Wacli – WhatsApp CLI

#60

Post by stavros »

taminka wrote: post #52
tazjin wrote: post #22

Earlier quoted context omitted.

It does, but only for chats between two specific devices. Multi-device support is one of its best features that you lose with E2E. Key distribution is just too hard. I think we won't get a messenger for non-tech people that works well with multi-device and E2E basically ever.

whatsapp, facebook messenger, imessage all support multi-device and it's pretty convenient, in fairness to telegram they launched a bit before double ratched was invented, but still, they've had over a decade to switch to it...

WhatsApp doesn't support multi-device. You can't have it installed on two phones at once.
Post reply on HN