-
AuthorPosts
-
-
-
-
-
-
-
Matt has spear headed wordpress in a completely obnoxious direction. He is trying to be this messiah but really wants everything for himself. Remember the High Septon in GOT? WordPress has been steadily taking out everything else from the market and tying it to their own servers. First it was Gutenberg which went against the grain of separating code and design and antagonising Elementor for it. Now this feud with WPEngine.
So now they own woocommerce, the main extension store associated with woocommerce and same with wordpress. Whats to say they will simply stop sharing the extension store tomorrow with any other hosting providers thereby completely monopolising it.
I dont judge him for his actions, but his holier than thou projection is really off the mark. Basically he is afraid a parallel universe might exist which feeds off his baby. I get his emotion.
-
-
-
-
-
-
While WordPress is a community-driven platform, it seems that WP Engine’s commercial interests are overshadowing our collective voice. We should be regarded as ‘WordPress users’ rather than ‘WP Engine customers.’
Additionally, WP Tavern should maintain journalistic objectivity by providing balanced coverage of news, including the recent ‘WP Engine Cease and Desist’ controversy. If the tavern fails to offer a comprehensive perspective, it might be more beneficial for us to seek WordPress-related news from other sources.
-
It was already covered here – https://wptavern.com/automattic-responds-to-wp-engines-cease-and-desist-with-legal-action
-
-
-
-
I understand your concern. But if you go through my articles, you will see that I always try to cover both sides and highlight a range of opinions. And if you feel I’ve overlooked any important points, please don’t hesitate to let me know.
(Till today, Matt has never asked me to cover or omit any news.)
-
Hi Jyolsna! I appreciate your posts. Two days ago, you wrote, “But Automattic is willing to amicably resolve this matter, including through a licensing relationship for use of its trademarks.”
This was days after Matt said WP Engine is a “cancer to WordPress.” I would not characterize the keynote or blog posts on Matt’s personal site as amicable. Thanks for reading.
-
-
-
-
Elon Musk is irrelevant in this conversation and raising him is a distraction. WordPress.org is supposed to be open source and not controlled by one individual. For a leader who promotes the open source ethos to turn around and attack a company and remove its access is a betrayal of the WordPress philosophy. There are other ways to solve these alleged problems than a power move that shows the community-led vision to be a farce. Unless this decision is walked back with a major apology, it’s a new day for WordPress users, and alternatives are suddenly more credible. Today it’s WP Engine, tomorrow, who knows.
-
-
-
-
-
-
It’s disheartening to see the escalating dispute between Automattic and WP Engine reaching a point where clients are caught in the crossfire.
As someone hosting with WP Engine, this situation is becoming increasingly concerning.
The restrictions imposed by WordPress.org not only strain the relationship between these companies but also directly impact the functionality and security of our clients’ websites.
This legal tussle disrupts that synergy, potentially compromising site performance and leaving us vulnerable to security risks.
It’s getting out of hand, and the focus seems to have shifted away from serving the users’ best interests.
Both parties need to prioritize their customers and find a resolution that doesn’t leave us bearing the brunt of their disagreements.
-
-
AutoMATTic should be careful what they do next; they could very suddenly be looking at “just a few thousand” lawsuits from Flywheel + WP Engine WordPress users and developers.
I’ve seen Matt speak several times, and I am actually shocked at what he has said and done in the past few days. And while I am not aware of a timeline prior to WordCamp regarding this, from the outside looking in, it seems like Matt’s actions were taken without warning. And I understand “without warning” may not be entirely correct, but I don’t know. However, for likely 99% of Flywheel+WP Engine customers/users/devs, it was without warning. At the moment, there are workarounds at least for installing or updating plugins. But, if Matt were to take any further steps, watch out.
P.S. I am a Flywheel user/dev with 17 client sites, have been with Fly for 9 years and have only 1 minor-negative issue in that time. And interestingly, I met and spoke with Fly’s founders at the last WordCamp SF at UCSF Mission Bay campus (WordPress’s 10th anniv.) Fun times. Can’t we all just get along, people?
-
Wow. Just now came across this debacle. Or dispute.
On one hand I can see where “WordPress.org” (or rather, Automattic / Matt) is coming from.
On the other, this instantly reminded me of how Matt Mullenweg handled the disagreement about the GPL licence, in the “Thesis theme-creator Chris Pearson vs Matt Mullenweg” . I recall Matt registering/acquiring a domain (thesis.com) only to mock Chris’ Thesis project. And it cost Matt something like 10.000 or 50.000 USD, if I recall correctly (which I probably don’t – but I don’t have time to look it up).
That seemed like a Elon’esque, child-like over-reaction.
And this, “banning” WP Engine, seems to be a response rooted in the same behavior.
It happens at the expense of WP Engine’s users. Who are, after all: WORDPRESS USERS.
It risks alienating other vendors – fragmenting the WordPress community. And it’s not as if we need more fragmenting, after the Gutenberg, block editor, FSE bonanza… 🥹
Cos who wants to be the next “WP Engine” / target of Automattic?
-
Long back, I have worked on wordpress (hosting side). And found these communities and meetups were the most alive and healthier than many of the tech meets.
Wordpress is an FOSS and ayone can customize it and use it. We know nothing is perfect in this world and always have room for improvement. From WP ENGINES point of view, most of their users may not need or can be satisfied with 3 revisions. If so, what’s the problem? We all tweak the things to suit our tastes. From reels, what I know is Only Ferrari doesn’t like tweaks.😀
RHEL, CENTOS, UBUNTU are being used to host PORN and other illegal things. It doesn’t mea n redhat or canonical created these for porn purpose or hosting provider’s sole purpose is it.
Why not the end customer decide, what they need the most? Aren’t we all depending and working for them?(Yes, we are working for Money as well, :P) I feel like WordPress taking away the freedom of users. Know it or not, wpengine itself is a user.
And yes, if automattic was providing some free hosting or /requests/pluginsfor large enterprises, that’s a mistake. Why not monetize it? Especially the bigger fishes who make more requests!Even WP-ENGINE can provide users an option to choose how many revisions to keep during purchase and bill them accordingly.
AFAIK, anything unlimited is going to get misused/overutilized.These are nothing, we have bigger problems in this world. WP or WPE didn’t kill or hurst anyone.
Ending my comments before I fall asleep.
-
-
-
-
Wow, this is a significant move! WP Engine’s ban from using WordPress.org resources really shakes things up. It’s a reminder of the importance of community standards in open-source projects. I’m curious to see how this will affect their services and the overall ecosystem. What are your thoughts on the implications for other hosting providers?”
-
-
Matt has compromised the entire WP ecosystem with this very, very bad decision. My Govt clients who never liked WP now have all the justification in the world to no longer allow WP (they prefer Drupal). Furthermore, it has pushed people who didn’t use or particularly like WPE to side with them. The only winners here will be Wix, Shopify and others as businesses flee from WP to more stable offerings.
-
-
-
-
-
-
AuthorPosts
- You must be logged in to reply to this topic.
