Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Secure Custom Fields by WordPress.org

wordpress.org

Post reply on HN
Print view View original

111–120 of 210 posts

Re: Secure Custom Fields by WordPress.org

#111

Post by Scaevolus »

unsnap_biceps wrote: post #3
stefanos82 wrote: post #2

The URL though says "advanced-custom-fields"; Matt...I can't find the words to comment; I just shake my head -_-

If you look at the reviews, they took over the advanced-custom-fields plugin and modified the owner to be Wordpress.org and renamed it to Secure Custom Fields. What a terrible look They also modified it by ripping out the pro features, so if people update their ACF Plugin and they had pro features enabled, it'll just break their install https://plugins.trac.wordpress.org/changeset/3167679/advance...

So they forked some open source software and "hacked it up" to remove notices from the original creators? Fascinating.

Re: Secure Custom Fields by WordPress.org

#112

Post by mirzap »

jnwatson wrote: post #105
mirzap wrote: post #74

Earlier quoted context omitted.

It doesn't matter. Matt didn't have the right to hijack ACF.

I'm not on Matt's side, but anyone has the right to fork a GPL project and call it something else.

This is not a fork. He stole the original project plugin space, its reviews, download statistics, SEO traffic, etc. It has nothing to do with GPL.

Re: Secure Custom Fields by WordPress.org

#114

Post by kristofferR »

shermantanktop wrote: post #108
kristofferR wrote: post #32

Earlier quoted context omitted.

Wow, I hadn't heard about the nosebleed incident. Absurd, even if he ain't snorting coke, it's deeply weird to continue an interview while profusely bleeding as if nothing is happening.

I have no stake in any of this but some people have nosebleeds without anything nefarious or bad going on. This guy doesn’t need any help looking bad, suggesting that his nosebleed is important is stupid.

It's not the nosebleed in itself, it's the ignoration of the blood streaming down the face during a video interview that is the most curious. And it wouldn't be as relevant if the subject hadn't acted increasingly erratic and self-destructive at the same time period.

It's not "important", it's just deeply weird, because it tracks.

Re: Secure Custom Fields by WordPress.org

#115

Post by jrflowers »

This whole saga is surreal because I thought myself to be constitutionally incapable of rooting for a private equity firm to win a fight, but this is like watching a guy violently strain to shit his pants while yelling “Look what they made me do!”

Also the guy is in a hot tub with all of his friends and employees

Re: Secure Custom Fields by WordPress.org

#116

Post by chx »

According to https://make.wordpress.org/plugins/2021/02/16/reminder-forke... this is piracy.

Let's look at newer documentation:

https://developer.wordpress.org/plugins/wordpress-org/detail...

> The use of trademarks or other projects as the sole or initial term of a plugin slug is prohibited unless proof of legal ownership/representation can be confirmed

The plugin is at https://wordpress.org/plugins/advanced-custom-fields and advanced custom fields filed for trademark last December https://trademarks.justia.com/983/21/advanced-custom-9832116...

Also

https://developer.wordpress.org/plugins/wordpress-org/plugin...

> We also don’t accept 100% copies of other people’s work

There's a clause which looks applicable https://developer.wordpress.org/plugins/wordpress-org/plugin...

> What happens to a plugin if the plugin owner gets blocked?

however the page says "Last Updated: 12 October 2024" and https://github.com/WordPress/developer-plugins-handbook/blob... (permalink at the time of writing this) doesn't have this section. So it really looks someone manually edited the page on wordpress.org without editing the source. Now, who has such permissions and has the motive to do this?

Re: Secure Custom Fields by WordPress.org

#117

Post by Scaevolus »

mattbee wrote: post #28

I can't even follow what's going on here, and I used to be an expert in software licensing drama. All I see is a bunch of unilateral actions driven by Matt Mullenweg that breaks so many implicit promises of how a free software steward should behave. Wordpress sites quite often seen to be a hodge-podge of plugins, each with their own UI and conventions, and (as a host) I'm never an expert in anye one of them. Has one…

Theoretically WPE might be a bad actor-- perhaps even more than any commercial competitor naturally is-- but they're smart enough to not smear it around with absurd moves like this that radiate a lack of professionalism or ability to predict reactions.

Re: Secure Custom Fields by WordPress.org

#118

Post by mthoms »

akira2501 wrote: post #23

> This update is as minimal as possible to fix the security issue. > This is a rare and unusual situation brought on by WP Engine’s legal attacks, we do not anticipate this happening for other plugins. So.. is this fixing a security issue.. or is this because of WP Engine? > and are forking Advanced Custom Fields (ACF) into a new plugin And stealing their place in the plugin store. A fork generally implies that you a…

Not just "stealing their place in the plugin store" but also blatantly committing trademark violations. https://imgur.com/a/D7YHn4e

Pot... Kettle... Something, something.

Re: Secure Custom Fields by WordPress.org

#119

Post by mthoms »

photomatt wrote: post #41
ivanmontillam wrote: post #24

Earlier quoted context omitted.

This is excellent! Is there a repo of this website? It would be good to have for preservation purposes.

It actually is an excellent website, and the repo is here: https://github.com/bullenweg/bullenweg.github.io

People are concerned about you, my dude. Very concerned. From one human being to another - please consider taking a step back to get some perspective.

Re: Secure Custom Fields by WordPress.org

#120

Post by kristofferR »

photomatt wrote: post #87
mirzap wrote: post #25

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-…

Have you read the GPL?

What kind of response is that? Does that mean you approve of sites like GPLDL then?
Post reply on HN