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

131–140 of 168 posts

Re: Wacli – WhatsApp CLI

#131

Post by boxingdog »

batuhanicoz wrote: post #34
joshwarwick15 wrote: post #25

(Caveat I’m the founder of https://wassist.app - The WhatsApp Agent Platform) Please be very careful using this tool to automate your WhatsApp - if you send too many messages, too quickly, you are going to get banned. This is NOT an officially supported api by WhatsApp and the risk of ban is relatively high

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.

[dead]

Re: Wacli – WhatsApp CLI

#132

Post by mediaman »

alex-nikitin wrote: post #122

There's a whole cottage industry around WhatsApp that exists to provide tools and services to commodity brokers and traders, primarily for compliance and bulk messaging existing customers. Meta has nerfed bulk forwarding on their desktop app, and the industry moved to third party tools to work around this. The reality is, no-one is spamming, everyone is consenting to this, everyone understands the risks, but a lot of…

Meta could turn Whatsapp into the next Slack. I know a lot of businesses (especially international ones) that use it for team communication. It's so much better than Teams.

I guess they think it's a small market, or maybe you can't really monetize enterprise with ads and it's all they know how to do.

Re: Wacli – WhatsApp CLI

#133

Post by Mordisquitos »

righthand wrote: post #129
hikarudo wrote: post #116

Earlier quoted context omitted.

WhatsApp is end-to-end encrypted. No one at Meta can read your messages.

If I can log into whatsapp on a new device and old messages aren’t encrypted then they have a copy of your key and it is not true e2e encryption.

Try logging in on a new device and putting your main device into aeroplane mode as soon as the login succeeds. Loading of old messages on the new device will stop.

Re: Wacli – WhatsApp CLI

#134

Post by neya »

tcfhgj wrote: post #85
neya wrote: post #39

Earlier quoted context omitted.

Second this. Their API is such a breeze and it is so much more automation friendly than any other messenger platform. It has a good adoption % too, otherwise Signal is the real winner if we account for privacy.

Even more automation friendly than Matrix?

Unfortunately, I haven't used Matrix personally enough to comment, sorry. But, I've heard only good things about it so far.

Re: Wacli – WhatsApp CLI

#135

Post by [deleted] »

mediaman wrote: post #132
alex-nikitin wrote: post #122

There's a whole cottage industry around WhatsApp that exists to provide tools and services to commodity brokers and traders, primarily for compliance and bulk messaging existing customers. Meta has nerfed bulk forwarding on their desktop app, and the industry moved to third party tools to work around this. The reality is, no-one is spamming, everyone is consenting to this, everyone understands the risks, but a lot of…

Meta could turn Whatsapp into the next Slack. I know a lot of businesses (especially international ones) that use it for team communication. It's so much better than Teams. I guess they think it's a small market, or maybe you can't really monetize enterprise with ads and it's all they know how to do.

[deleted]

Re: Wacli – WhatsApp CLI

#136

Post by lukebennett »

righthand wrote: post #129
hikarudo wrote: post #116

Earlier quoted context omitted.

WhatsApp is end-to-end encrypted. No one at Meta can read your messages.

If I can log into whatsapp on a new device and old messages aren’t encrypted then they have a copy of your key and it is not true e2e encryption.

You can't unless you've chosen to back up your WhatsApp messages to iCloud/Google in which case it's Apple/Google responsible for preserving the messages and subject to their encryption standards, nothing to do with Meta.

Re: Wacli – WhatsApp CLI

#137

Post by BeetleB »

faangguyindia wrote: post #5

I just use telegram. Just yesterday I setup a bot which is easy via botfather And also, setup an app (claude built it but I had to fiddle with it, it works like pagerduty) but uses cloudflate worker to push downtime/errors (via fcm) in production (from graphana) via webhooks to "full screen, by pass dnd, alerts, with loud music, this one: https://www.youtube.com/watch?v=H0IQBWWabuU ) I named the app "Siren". It's not…

I'll second the "Telegram is great for bots". It's the reason OpenClaw users use it.

I stopped using OpenClaw a while ago, but I did vibe code the very basic automations I had used OpenClaw for. Getting it to work with Telegram was trivial.

I don't use Telegram for chatting. In fact, I try not to use any IM tools with humans. ;-)

Re: Wacli – WhatsApp CLI

#138

Post by theoryaway »

batuhanicoz wrote: post #34
joshwarwick15 wrote: post #25

(Caveat I’m the founder of https://wassist.app - The WhatsApp Agent Platform) Please be very careful using this tool to automate your WhatsApp - if you send too many messages, too quickly, you are going to get banned. This is NOT an officially supported api by WhatsApp and the risk of ban is relatively high

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.

Someone who previously helped a project Barista/instagrabber, you should be wary of it.

https://web.archive.org/web/20240527132615/https://austinhua...

Post reply on HN