Live data from Hacker News

Wacli – WhatsApp CLI

github.com

151–160 of 168 posts

Re: Wacli – WhatsApp CLI

#151
Ya im totally sure its a good idea to use a tool written by the creator of openclaw with a sensitive account that is closely tied to day to day needs.

What could possibly go wrong with that.

Re: Wacli – WhatsApp CLI

#152
post #107

Earlier quoted context omitted.

Yeah, that's a good workaround. Google Voice can work too. Unfortunately, more and more services are declining to send to VoIP numbers because of seCurItY, so it's a game of cat and mouse. Fortunately SMS is so expensive in parts of Europe and it's not allowable anymore to use SMS by itself for online payment authentication, and both issues combined have slowly been pushing companies to explore alternatives. There un…

If you port a landline number to a VoIP service, services can't really tell that you're using VoIP, as far as I can tell.

In the US, I belive there are three number categories in the NANP porting database (wireline, cellular, and VoIP), and SMS senders can definitely tell, even though it might take a while (presumably there's a lot of caching going on).

If you're lucky, the service you care about only validates at number registration time, not at text sending time, and you can get away with it indefinitely, I suppose.

Re: Wacli – WhatsApp CLI

#153
post #85
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?

It's a bit less automation-friendly because the UX is not great when the bot doesn't have its own phone number (which costs money). I think it has better privacy, though. Matrix server operators can read message metadata.

Re: Wacli – WhatsApp CLI

#154
post #10

I wish it mentioned how safe this is. Some years ago I got banned for just logging in with a third-party client, without sending any messages. Given how critical WhatsApp is for some people, and how permanent the bans are, that's a big risk.

Happened to me on Telegram with their official app. Just because I opened it once when travelling. I got the account back, after 2 years. That's apparently the period to clean banned accounts. Tried to restore it by all means, just to see if that's possible. It wasn't. Though I didn't have anything important, I actually never sent a message. Now I use it for Openclaw :D

Re: Wacli – WhatsApp CLI

#155
post #85

Earlier quoted context omitted.

Even more automation friendly than Matrix?

It's a bit less automation-friendly because the UX is not great when the bot doesn't have its own phone number (which costs money). I think it has better privacy, though. Matrix server operators can read message metadata.

Telegram server operators can read message meta data and messages

Re: Wacli – WhatsApp CLI

#156
post #107

Earlier quoted context omitted.

Yeah, that's a good workaround. Google Voice can work too. Unfortunately, more and more services are declining to send to VoIP numbers because of seCurItY, so it's a game of cat and mouse. Fortunately SMS is so expensive in parts of Europe and it's not allowable anymore to use SMS by itself for online payment authentication, and both issues combined have slowly been pushing companies to explore alternatives. There un…

If you port a landline number to a VoIP service, services can't really tell that you're using VoIP, as far as I can tell.

It's easy and cheap to determine the original carrier (or its sucessor) for a US phone number. It costs money to do a porting lookup to determine the current carrier.

Most of the reason to deny voip users is that many voip services give phone numbers away like candy and then those phone numbers are used to abuse other services, so checking the original carrier tends to be enough for abuse screening.

Some use cases want more though. Banking KYC has some back channel to get subscriber identification or be alerted when ownership changes; those institutions may be willing to pay for current carrier lookups and deny usage of numbers where they don't have a back channel to the current carrier.

Re: Wacli – WhatsApp CLI

#157
post #155

Earlier quoted context omitted.

It's a bit less automation-friendly because the UX is not great when the bot doesn't have its own phone number (which costs money). I think it has better privacy, though. Matrix server operators can read message metadata.

Telegram server operators can read message meta data and messages

You're right, Matrix is a much better option than Telegram. I misread the thread as comparing Signal to Matrix.

Re: Wacli – WhatsApp CLI

#158
post #156

Earlier quoted context omitted.

If you port a landline number to a VoIP service, services can't really tell that you're using VoIP, as far as I can tell.

It's easy and cheap to determine the original carrier (or its sucessor) for a US phone number. It costs money to do a porting lookup to determine the current carrier. Most of the reason to deny voip users is that many voip services give phone numbers away like candy and then those phone numbers are used to abuse other services, so checking the original carrier tends to be enough for abuse screening. Some use cases wa…

This is great info, thanks!

Re: Wacli – WhatsApp CLI

#159

(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

Exactly, "automate your WhatsApp/Signal/..." sounds like "use XMPP for that use case", that's my go-to for bots and notifications, it works as well if not better, and I sleep better at night.
Post reply on HN