batuhanicoz

Neither of them require a browser. We run whatsmeow inside iOS and Android apps, with no browser whatsoever.

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.

Peter is also the creator of PSPDFKit, and people have considered him an incredible engineer way before transformers were even invented.

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.

For any user that was with us before today, it's free!

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.

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.

You can apply or find out more about the role at https://join.a8c.com/rehn

If you have any questions or hesitations, let's chat! You can reach me at batuhan@a8c.com or just DM me on https://x.com/batuhan

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.

Our attempts at resolving trademark issues with WPE predate our discovery of the attribution removal.

If you point to any lies told by me, I would love to correct them.

No one has told me to come here and defend anyone. I work at a part of Automattic that is isolated from anything WordPress — I don’t have to be here.

I am defending values I believe in. I am trying to make sure correct information is out there.

You are free to not believe that of course.

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.

As I understand it, WordPress Foundation's board can revoke the license if Automattic is no longer a good custodian of the brand.

It makes sure even if Automattic is no longer in good hands, the Foundation can protect the WordPress brand from Automattic.

(I work at Automattic but did not specifically checked the details of the trademark agreement)

> If wp.org is part of the foundation

It is not.

> a8c is intentionally obfuscating their ownership of wp.org

Automattic (my employer) does not own WordPress.org

There is no obligation on WordPress.org's part to provide free services to WP Engine. WP Engine uses trademarks in misleading ways while WordPress.org has a license from WPF to use the trademark.

Thank you for bringing this to our attention. I asked people who are helping with the infra of WordPress.org and they are not sure why Singlehop is showing "The Wordpress Foundation" for those IPs. They belong to the hosting provider W.ORG is using and this is just mislabelling on their part. Relevant people will get in touch and ask them to correct it.

And, quick side note, no one from Automattic or WordPress Foundation would ever misspell WordPress!

Publicly, perhaps but we've been trying to resolve these issues with WP Engine for at least 18 months now.

Most of my other comments I was speaking in first person, in others I did not initially realize it wasn't as clear in some of them.

I also updated my bio here to reflect the product I am working for belongs to Automattic. Previously, it only mentioned the product which not everyone has to know belongs to Automattic.

I am an employee of Automattic, that's correct and public.

The problem is not the "WP" in their name but their specific usage of "WordPress" and "WooCommerce" on their website and marketing. You don't have to literally use the trademarked in your brand name for infringement. Legal threshold, AFAIK, is around 15% of the people thinking you are officially related to the owner or the licensees of the trademark.

https://automattic.com/2024/09/25/open-source-trademarks-wp-...

If WP Engine wanted to dedicate resources to build on the code they are using, they would've contributed more to the core itself.

Instead of forking, they could channel their resources to give back and that would be a good step to resolve this.

Disclaimer: I work at Automattic.

Using WordPress the software is totally free, in both senses of the word.

Using the WordPress and WooCommerce trademarks outside of fair use is not.

Disclaimer: I work at Automattic.

WordPress.com started out as a WordPressµ (WordPress Multi User) provider. Just a place for people to quickly start their own blogs, mainly hosted on a WordPress.com subdomain. To learn more about WordPress MU: https://codex.wordpress.org/WordPress_MU

"WordPress hosting" is a relatively new option on WordPress.com. Pressable is a more advanced WordPress hosting provider, built by Automattic.

Disclaimer: I work at Automattic.

Projects page of the Foundation (https://wordpressfoundation.org/projects/) does not say those projects belong to the Foundation. It states:

> Matt Mullenweg, the director of the WordPress Foundation, has been directly involved in the creation of, or coordination of volunteers around, a number of WordPress projects that espouse the core philosophy

I'll admit this might sound confusing. Foundation came years after some of these projects were already established.

As long as competitors of Automattic does not infringe on the trademarks owned (in the case of WooCommerce) or licensed (WordPress) by Automattic, I don't see any reason for us taking any action.

I would personally ask everyone to at least try to contribute back to the open source projects they rely on though.

I work at Automattic, owner of WordPress.com.

I asked how WordPress.org is funded and will get details on that but I can tell you WordPress.org is not part of the foundation.

Open source project and the WordPress trademark are owned the WordPress Foundation. WordPress.org has a license to use the name from the Foundation, as does Automattic.

> are all of those services provided by WordPress.org without funding from WordPress foundation?

As far as I am aware, this is correct.

WordPress.org is operated by Matt Mullenweg as a free service that hosts plugins, themes, docs and more. It does not take donations, or as far I am aware, make any profits.

Instead, people are encouraged to donate to the Foundation, which helps with the development of WordPress the software and organizes things like WordCamps.

Infra, services and trademarks. They are not part of the GPL license. Everyone is welcomed to use any GPL code as they see fit, as long as they are within their limits as outlined in the license.

But this does not mean W.ORG has to keep providing these free services to you and your customers, and it does not mean you are free to use trademarks in a misleading way.

Disclaimer: I work at Automattic.

WordPress has been around for a long time, and there is no change to how open it is. It is GPL code, Automattic is not forking it and selling access to the fork.

We are just asking WP Engine to contribute back to the project that they are basing their entire business on.

This is primarily a trademark infringement issue, we asked them to give back to be able to use the trademark we have the license for.

Hiding the widgets isn't the main issue. If you infringe the WordPress trademark in commercial use, and ignore any attempt to make it right, and pursue legal action, W.ORG does not have to provide those free services to you.

I'm guessing you are not size of WP Engine and Silver Lake, honest question, if you were, would you want to contribute back to WordPress?

We made many attempts to communicate and solve these issues long before it was made public.

They were asked to contribute back, either in cash or in people hours and they refused.