logoalt Hacker News

recsv-heredoctoday at 7:28 AM4 repliesview on HN

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?


Replies

batuhanicoztoday at 8:02 AM

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: https://github.com/textshq/platform-whatsapp

I would recommend whatsmeow over Baileys just because we are actively involved and incentivized to keep that working perfectly, and have a lot of data points to detect any issues with it at scale.

show 1 reply
3formtoday at 7:34 AM

Don't they ban people using custom clients when discovered? I feel like I've read something on that note.

show 1 reply
dinakars777today at 7:31 AM

WhatsMeow is stable unlike Baileys which faces challenges with maintainability.

TZubiritoday at 8:33 AM

The thing is that their tight control is precisely what makes whatsapp a spam free environment. You can't have a libre federated protocol AND have it be spam free.

As soon as you open up the api floodgate, you'll start to see nigerian prince agents on openclaw speed.