Advertisement · 728 × 90
#
Hashtag
#MattBullenweg
Advertisement · 728 × 90
chikorita157 🐰:unverified:
chikorita157 🐰:unverified:
@chikorita157.sakurajima.moe
1 year ago

The full document on the full injection WP Engine filed is now published.

storage.courtlistener.com/recap/gov.uscourts.cand....

#WordPress #SaveWordPress #MattMullenwegResignNow #MattBullenweg

0 0 0 0
chikorita157 🐰:unverified:
chikorita157 🐰:unverified:
@chikorita157.sakurajima.moe
1 year ago
Who killed Hannibal.meme. A man with a gun wearing a suit (Matt Mullenweg) shoots a man on the couch (WordPress) [gunshots] A man with a gun wearing a suit (Matt Mullenweg].while a man on the couch (WordPress) lying dead. Why did WP Engine did this?

Who killed Hannibal.meme. A man with a gun wearing a suit (Matt Mullenweg) shoots a man on the couch (WordPress) [gunshots] A man with a gun wearing a suit (Matt Mullenweg].while a man on the couch (WordPress) lying dead. Why did WP Engine did this?

[WordPress Drama - Meme]

WordPress Drama in a Nutshell.

#WordPress #SaveWordPress #MattMullenwegResignNow #MattBullenweg

0 0 0 0
chikorita157 🐰:unverified:
chikorita157 🐰:unverified:
@chikorita157.sakurajima.moe
1 year ago
Today my WordPress.org account was disabled unexpectedly. I did not request that and I have received no communications with reasoning ahead of time or at the time of that being disabled (like most people who were deactivated on Slack or .org disabled). This puts the @podsframework project at risk on .org since we've used the security best-practice of having release confirmations enabled on the Pods plugins on .org since they added that feature. To confirm a release, you must log into WordPress.org. So this was an attack on not just me but also on the Pods project as it means we can't do releases. I have suspected this could happen since the WE team was locked out of .org so I've already gotten consent from a long time Pods contributor for them to take over the .org listing Now that I have been locked out of org officially, I made a formal request to transfer ownership of the Pods plugins into their control so that we can continue our normal release processes. Nothing is safe here, unsure if his account will be locked or if Pods will be closed. And now my WordPress.org Slack account has been deactivated, assuming that was part of the syncing of .org disabled accounts to deactivating WP Slack accounts. But still, that truly made the cut deeper and more official in my eyes.

Today my WordPress.org account was disabled unexpectedly. I did not request that and I have received no communications with reasoning ahead of time or at the time of that being disabled (like most people who were deactivated on Slack or .org disabled). This puts the @podsframework project at risk on .org since we've used the security best-practice of having release confirmations enabled on the Pods plugins on .org since they added that feature. To confirm a release, you must log into WordPress.org. So this was an attack on not just me but also on the Pods project as it means we can't do releases. I have suspected this could happen since the WE team was locked out of .org so I've already gotten consent from a long time Pods contributor for them to take over the .org listing Now that I have been locked out of org officially, I made a formal request to transfer ownership of the Pods plugins into their control so that we can continue our normal release processes. Nothing is safe here, unsure if his account will be locked or if Pods will be closed. And now my WordPress.org Slack account has been deactivated, assuming that was part of the syncing of .org disabled accounts to deactivating WP Slack accounts. But still, that truly made the cut deeper and more official in my eyes.

Apparently, the pereson who is behind the Pods plugin got banned from WordPress Org for no reason.

Matt Bullenweg is really trying to burn down the WordPress community. WordPress really needs to hard fork, now.

#WordPress #SaveWordPress #MattMullenwegResignNow #MattBullenweg

2 0 2 0