search

wordpressenginetracker / wordpressenginetracker.github.io

A single-page website to publicly track the number of sites migrating away from WP Engine
5 stars 6 forks source link

Track actual sites, not domains #3

Open f3bruary opened 15 hours ago

f3bruary commented 15 hours ago

The summary of this project is:

The purpose of this site is to track how many sites have left WP Engine

Based on the very first entries in the list I found 16 domains all pointing to 1 site. That makes the counter misleading.

Either the summary should be updated so it says domains instead of sites, or the list needs to be filtered down to actual sites, and not all the domains that point to one.

stephcathoh commented 12 hours ago

It's possible some folks have left WordPress as well, so saying sites have left WP Engine doesn't necessarily mean they've gone to another web host that supports WordPress. This is a really tacky endeavor. I am not impressed at all.

DanielRuf commented 11 hours ago

Also the check, if a domain is hosted by WPE, is quite amateurish.

https://github.com/wordpressenginetracker/wordpressenginetracker.github.io/blob/trunk/index.js#L118

I'm not sure what the goal of this website is and what Matt tries to achieve. But the community is getting increasingly annoyed of such unprofessional behavior of Matt and in the security community some also think about dropping 0days for WordPress and related plugins / themes due to this whole situation.

The feedback under the tweet from the official WordPress account and in the reddit community shows, what most of us think.

The whole situation hurts everyone more than needed.

f3bruary commented 2 hours ago

in the security community some also think about dropping 0days for WordPress...

That would punish the users and the theme/plugin authors more than WP/MM. It would be equal to MM blocking WPE's access to the plugin repository.

I don't want to go out of the scope of this ticket, which simply points to the incorrectness of the counter, but if you want to punish the responsible it needs to be a loss of market share. The best thing people can do is stop using WP. Stop developing themes and plugins, and stop offering support and maintenance.

It's the developers that built WP to what it is now and are responsible for its popularity (ignoring the block editor for the sake of the argument and avoid PTSD/trauma/flashbacks/migraines).

The community has the power to destroy it as well by shifting to another platform. Many already have.

In time, WP would become the Yahoo of CMS platforms.

mathieuwa commented 52 minutes ago

More wasted time, more useless action made by Matt. The community being annoyed is an euphemism. Matt told automattic was short staffed and yet it seems some staff have time to waste. Matt is deserving what is coming and I really hope a slap from justice will wake him up.

DanielRuf commented 21 minutes ago

That would punish the users and the theme/plugin authors more than WP/MM.

I think they have the feeling, that Automattic is not a responsible party anymore for a vulnerability reporting process. Especially since Automattic used the reason with a vulnerability to takeover the ACF plugin.