←back to thread

Secure Custom Fields by WordPress.org

(wordpress.org)
172 points ValentineC | 1 comments | 12 Oct 24 18:38 UTC | HN request time: 0s | source
Show context
mirzap ◴[12 Oct 24 19:32 UTC] No.41821754[source]▶
Pathetic. Matt banned one of the most popular WordPress plugins. Then, he forked the code and hosted it on WP.org, which is against the Terms of Service. He also hosted it in the plugin directory on the same path as ACF, stealing its SEO traffic. Wow!

Matt's state of mind is clearly not good. If I were an investor in WordPress, I would start thinking about cutting my losses. WordPress will not recover from this self-inflicted destruction

*Update* Oh, it's worse than that. He just renamed the ACF to SCF and claimed all the installations and reviews from ACF. I still can't believe this happened. This can't be legal!

replies(1): >>41822198 #
photomatt ◴[12 Oct 24 20:21 UTC] No.41822198[source]▶
Have you read the GPL?
replies(8): >>41822224 #>>41822230 #>>41822245 #>>41822270 #>>41822711 #>>41823254 #>>41823381 #>>41827030 #
DonnieBurger ◴[12 Oct 24 20:24 UTC] No.41822230[source]▶
Parent does not mention GPL, nor is this a GPL issue. It's about the takeover of an existing plugin and it's reviews/installs.
replies(1): >>41823410 #
1. ankleturtle ◴[12 Oct 24 22:49 UTC] No.41823410{3}[source]▶
I am not a lawyer, but I am really curious if this would amount to tortious interference.