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

131–140 of 210 posts

Re: Secure Custom Fields by WordPress.org

#131

Post by luckylion »

rasso wrote: post #101
batuhanicoz wrote: post #51

Earlier quoted context omitted.

ACF isn’t a premium plugin (linked post only concerns those). The linked post also might not reflect the current policies. This update was a security update and was done due to the unique circumstances around the original publisher.

Exactly. ACF is free and open source. ACF Pro is not. Secure Custom Fields is based on the free version (ACF, without "Pro").

It still uses trademarks from ACF, those are obviously not "open source", which also has been Matt's & wordpress.org's stance since forever: the _code_ is GPL, but the assets are not.

If you "fork" the assets, you're not covered by GPL.

Obviously it's nonsense to discriminate between the free version of a freemium plugin and a commercial plugin and this is simply a stupid way to lash out.

Re: Secure Custom Fields by WordPress.org

#132

Post by mmsnowsniff »

getcrunk wrote: post #130

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…

I don't know how much goodwill we owe somebody currently being sued for extortion and who lied to a community about ownership of a trademark for over a decade in an attempt to take a whole community hostage when he feels like it's time to cash in. The writing was on the wall when he sold user intellectual property from WordPress.com and Tumblr to OpenAi. Was that fighting for open source?

Re: Secure Custom Fields by WordPress.org

#134

Post by geerlingguy »

getcrunk wrote: post #130

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…

A number of people have dealt with the maker/taker issue, for example Dries, the founder and BDFL of the Drupal project: https://dri.es/solving-the-maker-taker-problem

I think we're pretty far removed from the original issue of WP Engine and WordPress and people are just trying to deal with the fallout from Matt's nuke-the-entire-ecosystem approach he's elected to take.

Re: Secure Custom Fields by WordPress.org

#137

Post by geerlingguy »

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

I feel so bad for all the Wordpress devs and shops right now. This is not the kind of community turmoil I'd want to deal with leading up to holidays/new years!

It makes Drupal 8/Backdrop seem like a pleasant and wonderful experience, in comparison.

Re: Secure Custom Fields by WordPress.org

#138

Post by mnau »

partiallypro wrote: post #10

This is one of the sleaziest things I've ever seen. I fear a hard fork of WordPress is now inevitable and unfortunately, it's possibly going to kill the platform, all over one man's ego. How can I now sell my clients on using WordPress for mission critical things if on a whim the owner of WordPress can break my site or lock out my security updates, just because I chose the "wrong" host or plugin? I don't see how the…

TBF WordPress was also created by two men and one of them was Matt. Of course it only achieved it's success through efforts of countless others, but it's not just some person. Shame, it came to this.

We had hard forks of very popular systems before, e.g. xfree86 turned into x.org, LibreOffice vs OpenOffice.org, Hudson to Jenkins and others and basically everyone switched (nearly) overnight.

Fork will likely have a much better direction structure to avoid precisely this problem, at least it seems to be the pattern.

Re: Secure Custom Fields by WordPress.org

#139

Post by CrimsonRain »

batuhanicoz wrote: post #83
throw16180339 wrote: post #77

Earlier quoted context omitted.

There are a lot of other employers that won't make you lie for them.

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.

You're values are doing open source dirty.

Re: Secure Custom Fields by WordPress.org

#140

Post by chx »

geerlingguy wrote: post #137
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-…

I feel so bad for all the Wordpress devs and shops right now. This is not the kind of community turmoil I'd want to deal with leading up to holidays/new years! It makes Drupal 8/Backdrop seem like a pleasant and wonderful experience, in comparison.

I don't think there was any bad blood between Drupal 8 and Backdrop, was there? It was forked in 2013 and look https://www.drupal.org/u/jenlampton Jen was still doing BADCamps and went to DrupalCons and all that. My memory is fuzzy a little but I do remember we were making huge progress on migrate at BADCamp 2014 and I do not remember a single tense moment with Jen or Nate. Or was that 2013? But even if it was, that was after the fork. Nate also went to DrupalCons look https://www.drupal.org/u/quicksketch

In short, I know I considered Backdrop futile but I don't think there was any significant controversy or is my memory failing me? http://www.drupal4hu.com/node/380 here's my post from the time.

Truth to be told there was significantly more controversy between me and the rest of the Drupal community than Backdrop and Drupal. You can not imagine how much I regret that.

Post reply on HN