batuhanicoz
Joined 15 years ago
Joined 15 years ago
As long as you don't abuse and keep your usage within the parameters of any human, you'll be fine.
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'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).
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 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 [email protected] or just DM me on https://x.com/batuhan
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 [email protected].
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.
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.
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.
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)