> With the new WhatsApp interface mandated by the DMA, any BirdyChat user in the EEA will be able to start a chat with any WhatsApp user in the region simply by knowing their phone number.
Unfortunately, as it's been implemented as opt-in on WhatsApp's side, this isn't really true. Honestly that decision alone means it's kinda dead in the water.
Just opened my Whatsapp settings and "Third-party chat requests" is on by default (From the Netherlands). Although to actually receive messages you do have to activate this feature.
Exciting news! Can't wait for iMessage to open up too. Any idea if this (or other future messengers) will work outside of Europe too or does WhatsApp use some kind of geofencing, like Apple, to prevent non-EU citizens from enjoying the same rights too?
I must protest that this kind of announcement belies the stupidity of proprietary chat protocols.
Remember when IRC was king, and basically, anyone could write an IRC client? Anyone could write a MUD client, or even a Telnet client. Those are open protocols.
When Pidgin came out, it was like a breath of fresh air for me. In the early 90s I had multiple IM accounts (starting with ICQ!) and unifying them, especially under a Linux client, was a dream come true.
But of course, AIM purported to use Oscar at the time, but they really hated F/OSS and 3rd-party clients, and so did the other proprietary guys, so it became cat-and-mouse to keep the client compatible while the servers always tried to break their functionality.
Now this dumb announcement comes out that a 3rd party has (apparently legally) established interop with a Meta property with (I am guessing) a completely proprietary, undocumented, secret protocol underneath.
I am not impressed. I am McKayla Maroney unimpressed.
I want open protocols and I want client devs who are free to produce clients in freeform, as long as they can follow the protocol specs. Now we have email clients who speak SMTP, IMAP, and POP3, including the "secured, encrypted" versions of those protocols. We should ask for nothing less when it comes to other communications.
This is pretty amazing, but I wish they picked a better name for it. I have a feeling that a good amount of people will dismiss it just because of the name.
Even the first announcement about this included BirdyChat and Haiket. Two completely unknown and yet unreleased closed source chat apps with a waitlist.
Can't help but think they are maintained by people close to Meta dev teams and were hand-picked for a malicious compliance, where they can just point to them as examples, and they make onboarding as complicated and expensive as possible for others.
As a European, I would like to know in _which_ European country you're based. I think I know all of them, people from abroad might not. Saying "Made in Europe" is too general for my European liking. ;)
Warning! Badly broken user interface, I wouldn't trust these programmers to get the end-to-end encryption right.
On the second screen of the app there is already an infuriating bug: they ask to give your work email because than you go hire in priority on their invite-only waiting list. So you type in your email again and again and again, alternating between all your emails, but you keep returning to the form asking for your work email. You check those emails to see if they send you something to activate your account but nothing. Exasperated you try the only other button, sign up with private email instead. Guess that works, because you leave the infinite loop. But than zilch, nada, nothing.
I was a big fan of pidgin, but this premise makes me feel iffy.
Why would I ever want my work to intrude on my personal messaging? My private time is my own.
Slack/Teams is perfect because I can mute it on a schedule when I stop for the day.
Anything that is urgent can be managed via Pagerduty or similar on a controlled fashion
> this premise makes me feel iffy. Why would I ever want my work to intrude on my personal messaging?
I think the pitch here is exactly the opposite of that? Many businesses in the EU already use WhatsApp for customer contact - this lets you separate your business communications from the app you use for personal messaging
When a smaller network tries to be interoperable with a larger network, the larger network almost always eats up the smaller one. This is how XMPP was killed by Gtalk, if any of you are old enough to remember.
Want to elaborate a little? I think I got only one spammy WhatsApp message in the last who knows how many years it was made available (I remember the time when I had to pay to use it on the iPhone). I get more SMS spam nowadays.
Newly registered Accounts from India/Pakistan were spamming me (pig butchering scam ) .
Around 90% got picked up by the spam filter,but when they use hundreds/thousands accounts even 10% is a lot.
While not a commercial offering, which is what this is saying in reality - closed source, commercial alternative with (limited) interoperability, I've been running my own chat server for a while now with (limited) interoperability with both Whatsapp and Messenger.
I suspect a good number of people here don't care for any of this - FOSS, chat, voice, and video is where it's at. Interoperability for those last two don't exist yet AFAIK, and they're truly game-changers. Will that change? Does the DMA mention anything other than chat? Perhaps someone could enlighten me.
Yes but element/matrix aren't going to work with WhatsApp on offering compatibility. They have reasons for that, most of them good ones but I doubt that video is coming.
This is really amazing. I hope some regulation like DMA comes to India as well.
Does WhatsApp charge money for this? If not, why would a business use their API? They could simply create an app to directly talk to their customers, or am I missing something?
72 comments
[ 3.4 ms ] story [ 79.9 ms ] threadUnfortunately, as it's been implemented as opt-in on WhatsApp's side, this isn't really true. Honestly that decision alone means it's kinda dead in the water.
FAIL
Chatting with anyone has always been opt in from the point of the receiver, so I don't get your point?
And how many of these are there? Anyone?
Remember when IRC was king, and basically, anyone could write an IRC client? Anyone could write a MUD client, or even a Telnet client. Those are open protocols.
When Pidgin came out, it was like a breath of fresh air for me. In the early 90s I had multiple IM accounts (starting with ICQ!) and unifying them, especially under a Linux client, was a dream come true.
But of course, AIM purported to use Oscar at the time, but they really hated F/OSS and 3rd-party clients, and so did the other proprietary guys, so it became cat-and-mouse to keep the client compatible while the servers always tried to break their functionality.
Now this dumb announcement comes out that a 3rd party has (apparently legally) established interop with a Meta property with (I am guessing) a completely proprietary, undocumented, secret protocol underneath.
I am not impressed. I am McKayla Maroney unimpressed.
I want open protocols and I want client devs who are free to produce clients in freeform, as long as they can follow the protocol specs. Now we have email clients who speak SMTP, IMAP, and POP3, including the "secured, encrypted" versions of those protocols. We should ask for nothing less when it comes to other communications.
Can't help but think they are maintained by people close to Meta dev teams and were hand-picked for a malicious compliance, where they can just point to them as examples, and they make onboarding as complicated and expensive as possible for others.
On the second screen of the app there is already an infuriating bug: they ask to give your work email because than you go hire in priority on their invite-only waiting list. So you type in your email again and again and again, alternating between all your emails, but you keep returning to the form asking for your work email. You check those emails to see if they send you something to activate your account but nothing. Exasperated you try the only other button, sign up with private email instead. Guess that works, because you leave the infinite loop. But than zilch, nada, nothing.
Don't these script-kiddies use their own app?
Why would I ever want my work to intrude on my personal messaging? My private time is my own. Slack/Teams is perfect because I can mute it on a schedule when I stop for the day.
Anything that is urgent can be managed via Pagerduty or similar on a controlled fashion
I think the pitch here is exactly the opposite of that? Many businesses in the EU already use WhatsApp for customer contact - this lets you separate your business communications from the app you use for personal messaging
People need signal. It's not perfect, but it's the best available.
No source code, wait list, special compatibility with a for-profit ad based company. No thanks.
Want to elaborate a little? I think I got only one spammy WhatsApp message in the last who knows how many years it was made available (I remember the time when I had to pay to use it on the iPhone). I get more SMS spam nowadays.
https://news.ycombinator.com/item?id=44736050
I suspect a good number of people here don't care for any of this - FOSS, chat, voice, and video is where it's at. Interoperability for those last two don't exist yet AFAIK, and they're truly game-changers. Will that change? Does the DMA mention anything other than chat? Perhaps someone could enlighten me.
Does WhatsApp charge money for this? If not, why would a business use their API? They could simply create an app to directly talk to their customers, or am I missing something?