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.
Since recently Meta offers this as per European Union mandate (Digital Markets Act, DMA). For both Whatsapp and Facebook messaging. [0]
Now there are a lot of implementation requirements, basically forcing you to have some kind of messaging provider. Therefore difficult to apply for an open source solution. However there is such an interface.
I personally find the almost absence of spam on WhatsApp a big success story for it. Think about how much Spam still hits your email inbox (and nobody knows how much is filtered away before it does).
I totally understand why they try and make it hard for integration to happen. When compared to classic SMS, the fact that you need to start a conversation with a preapproved template means that they have a way to control casual interactions.
I consider marketing use to be spam, and this is what the API is primarily meant for.
I understand that WhatsApp is kinda special in that it effectively replaced SMS in some parts of the world, but IMO this needs to be looked at through the lens of other Meta effort. The same is the case with Facebook/Messenger, and has been since before WhatsApp has been a (Meta) thing - they offer multiple different official ways to support spamming users and tricking them to buy stuff, but may the Lord have mercy on you should you want to create an auto-responder or "save to calendar" script and hook it up to your personal account.
That seems a but pessimistic. A few companies use it for customer service, like ime Adidas Germany [0] (they handled an exchange for me once on there). It is effectively just another customer support line like a chat portal on a website.
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.
I was really pleased to see that - that's the way to introduce premium tiers as your business evolves.
I love Beeper, and have got a couple of colleagues on it. The only feature I'd like - the ability to mute a conversation for a duration rather than forever.
This is an overreaction. It's violence. Trying to justify it by claiming it's part of their culture is not healthy, I think we can have some universal values (don't stab people?) and it is perfectly reasonable to force people to adopt to those values. It's their culture? They can leave the violent parts of culture behind and adopt to the expectations of modern society (not stabbing people).
I'm Turkish. I grew up in Turkey. These things happen, but let's not try to justify them. We should aim to get to a point where people share these "western values" (of not stabbing people).
WordPress.org is not Automattic’s platform (there is a lot of managerial overlap and both are ultimately controlled by the same person).
Our well documented issues with WP Engine does not change the fact Automattic has been one of THE open source companies in tech for the last 2 decades and continues to ship in the open. There is constant push internally to build more in the open.
Bullshit. For all practical purposes, WP.org is Automattic.
> Our well documented issues with WP Engine does not change the fact Automattic has been one of THE open source companies in tech for the last 2 decades
This is debatable but even if I grant this point, I’m saying that the reputation that you’ve built up over the last two decades is completely destroyed, and anyone who actually cares about open source and public stewardship of projects should stay far, far away.
Beeper (Automattic) | Remote | Full-time | Reverse Engineer | $70-$170k and great benefits
Beeper unifies all your chats across networks in one app. We are looking for people to join our incredible team of reverse engineers that build our integrations with chat networks. Like most software at Automattic, all of our bridge work is open source: https://github.com/mautrix (and more of our stack is open source at https://github.com/beeper)
Basically, if you are someone hacks on proprietary software and protocols for fun, we want to hire you. We don't care about your degree or previous work experience. We care about your ability break things to make them work the way you want.
Our bridges are written in Golang, but you don't need to know Golang to apply.
Automattic's products are used by over a billion people each month across WordPress.com, WooCommerce, WordPress VIP, Jetpack, Tumblr, Beeper, Day One, Pocket Casts, and many more. If you love the open web, open source, radical problem ownership, and simple over pure solutions, Automattic is probably the place for you.
The initial release of SCF only applied security fixes, changed the plugin name and removed upsells. I don't think there is any change that might cause the issue you are having.
If you can share the problem you are experiencing on Making WordPress Slack (#secure-custom-fields channel), I'm sure relevant people would love to help out ASAP.
I work at Automattic and I can get you in touch with people from WordPress.org if that's easier. You can email me at batuhan@a8c.com.
If there are any bugs, regressions or any issues with the fork, it's in the interest of everyone to quickly find and resolve them, so I'm sure your help would be appreciated.
So you guys don't get sued any further for essentially hijacking a distribution channel and pushing an unauthorized version?
If I were an employee of A8C I wouldn't be touching this code with a ten foot pole - employees can still be found guilty of criminal wrongdoing even if their employer told them to do something.
It really is strange Automattic's lawyers haven't clamped down on any public comment. Have any of WP Engine's people been as free with commentary as Automattic employees have been?
If I were an employee at a company being sued I wouldn't say anything related to it even without an order from legal because I wouldn't want to have to risk answering for it in the trial. Why dangle yourself out there as a target for the opposition's lawyers?
Lawyers can give advice, but clients make the decisions. One of Automattic's lawyers appeared in an earlier thread and strongly suggested that Matt is ignoring his advice.
I haven't seen any comments from any WP Engine employees. They have an adult CEO, though, so I'm sure she told them not to comment on it.
Matt has actually complained on the official WordPress Twitter account that the WPE CEO hasn't commented on it. It's really bizarre. Honestly, he doesn't sound well. There's no way he can be this reckless and be in his right mind. He's worth a ton of money, so I don't know if anyone can actually get him under control or get him out.
The abbreviation "WP" was initially permitted for use before they retroactively changed it a few days ago.
Saying "We host WordPress" on WPEngine's site constitutes as much trademark violation as a random shoe shop listing Nike shoes in their catalog.
It seems this is more about attempting to undermine a competitor, with trademark issues serving merely as an excuse.
ACF isn’t a premium plugin (linked post only concerns those).
The linked post also might not reflect the current policies. This update was a security update and was done due to the unique circumstances around the original publisher.
The correct information is that your employer created the security problem as part of their shakedown attempt. They then banned the WP Engine developers from Wordpress so that they couldn't update the plugin. Now they've forked the plugin, removed the commercial upgrade, and renamed it.
I'm not sure where values come into it. I'd be ashamed to work there.
"It is difficult to get a man to understand something, when his salary depends upon his not understanding it." -- Upton Sinclair (probably, may be apocryphal)
For sure dude, the guy who came here to defend the values of his own and his megalomaniac employer on a weekend evening is probably much too busy to name one. That tracks.
It still uses trademarks from ACF, those are obviously not "open source", which also has been Matt's & wordpress.org's stance since forever: the _code_ is GPL, but the assets are not.
If you "fork" the assets, you're not covered by GPL.
Obviously it's nonsense to discriminate between the free version of a freemium plugin and a commercial plugin and this is simply a stupid way to lash out.
As long as you don't abuse and keep your usage within the parameters of any human, you'll be fine.
reply