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

121–130 of 210 posts

Re: Secure Custom Fields by WordPress.org

#121

Post by mthoms »

chx wrote: post #116

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

Good catches. Also note that "ACF" is trademarked by WPEngine and is used throughout the source code and reviews.

Re: Secure Custom Fields by WordPress.org

#122

Post by ankleturtle »

photomatt wrote: post #38
CharlesW wrote: post #20

So WordPress-the-org — which is effectively Matt, as far as I can tell — just Sherlocked a developer's plug-in using the developer's own code, ostensibly as retribution for a security issue that the developer had already fixed. https://www.advancedcustomfields.com/blog/acf-6-3-8-security... What am I missing?

This release fixes a separate security vulnerability from the original update.

You are abusing the community for your own gain. Stop!

Re: Secure Custom Fields by WordPress.org

#123

Post by cyral »

Scaevolus wrote: post #111
unsnap_biceps wrote: post #3

Earlier quoted context omitted.

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.

Yup, removing post revisions which I think is single line change is hacking it up when WP Engine does it, but this is totally okay apparently.

Re: Secure Custom Fields by WordPress.org

#124

Post by ankleturtle »

mirzap wrote: post #112
jnwatson wrote: post #105

Earlier quoted context omitted.

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.

Wow. I will never contribute anything to WordPress again.

Re: Secure Custom Fields by WordPress.org

#125

Post by taikahessu »

photomatt wrote: post #44
joe_hills wrote: post #11

Earlier quoted context omitted.

What a choice, and what poor timing. Companies that make breaking changes on holiday weekends aren’t going to earn much goodwill from developers.

Nothing has broken. Perhaps WP Engine should have consider that before suing us.

Business is war, I get it. But you chose to make innocent bystanders (your users) life difficult and you crossed a line by stealing code with an excuse that everyone sees through. This looks now more and more of a personal vendetta.

Re: Secure Custom Fields by WordPress.org

#126

Post by righthand »

None4U wrote: post #103
righthand wrote: post #12

Earlier quoted context omitted.

> There is separate, but not directly related news that Jason Bahl has left WP Engine to work for Automattic and will be making WPGraphQL a canonical community plugin. We expect others will follow as well. Anything to prop up their position and throw the company they are attacking under the bus. What a jerk.

Which, by the way, previously ended with "We expect others will defect as well." before the post was edited

Not surprised. What scum.

Re: Secure Custom Fields by WordPress.org

#127

Post by mmsnowsniff »

photomatt wrote: post #44
joe_hills wrote: post #11

Earlier quoted context omitted.

What a choice, and what poor timing. Companies that make breaking changes on holiday weekends aren’t going to earn much goodwill from developers.

Nothing has broken. Perhaps WP Engine should have consider that before suing us.

Can't wait for Matt to read this in a deposition. At this point, the dude seems to be intent on running up the highest tab possible.

Re: Secure Custom Fields by WordPress.org

#128

Post by bombcar »

dmvdoug wrote: post #89
batuhanicoz wrote: post #83

Earlier quoted context omitted.

If you point to any lies told by me, I would love to correct them. 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.

What values are those, exactly?

US dollar values deposited into the accounts every paycheck, I assume.

Re: Secure Custom Fields by WordPress.org

#129

Post by bombcar »

photomatt wrote: post #44
joe_hills wrote: post #11

Earlier quoted context omitted.

What a choice, and what poor timing. Companies that make breaking changes on holiday weekends aren’t going to earn much goodwill from developers.

Nothing has broken. Perhaps WP Engine should have consider that before suing us.

These are clearly the actions of someone who is sure they'll win the lawsuit.

(not)

Re: Secure Custom Fields by WordPress.org

#130

Post by getcrunk »

Posted this in the other thread:

A lot of the comments seem to call out Matt (right or wrong). But that’s the easy thing to do.

No one dares address the systemic issue of for profit corporations exploitatively (ab)using open source software.

There is a social contract that people should contribute back, and while it’s largely unenforceable, as it should be, when it’s happening on a systemic level something has to be done. And we are all complicit if we don’t at least say that much and spare some good will towards the guy actively in that fight at least superficially

*Following is a response to some replies on the other thread, that clarifies my points *

Matt being a poor steward of gpl is by definition not a systemic issue … unless ur claim is that many people in positions like him do what he does which is in turn caused by invariant factors?

The systemic issue is companies the world over not giving their fair share back in terms of contributing to foss.

I might agree with most of your points, I’m just trying to get people to realize there’s the local issue of Matt/wp and then there’s this global issue of companies building businesses off foss and not giving back.

Post reply on HN