nev@abolisyonista the platforms themselves are fine, but the WordPress founder/CEO* recently went *completely* mad with power. See e.g. https://www.theregister.com/Tag/WordPress/
* It's complicated, and I'm probably not getting it totally right, but: WordPress the software project (headquartered at wordpress.org**, but we'll get back to that later) is open source and, on paper, run by a nonprofit foundation with a small board. The board consists of the founder and a couple cronies of his who are pretty much inactive and are uninvolved in development. The founder's for-profit company, Automattic, runs WordPress.com (managed WordPress hosting), owns/develops the closely integrated plugin family Jetpack, and in recent years bought Tumblr. It also funds/controls much core WordPress development.
The founder recently tried to take down a rival managed WordPress hosting company, WP Engine (which also owns/develops several major plugins), on extremely shaky grounds and in a very unprofessional manner—basically, threatening to sue for trademark infringement unless they forked over a ton of money, ostensibly to fund WordPress development. This involved claiming he personally owns WordPress.org, the open-source project site. Purportedly for "security", he then *replaced the free version of WPE's main plugin* in the WP.org plugin repo—not actually forking it, but literally removing WPE's access to the repo, taking it over, and replacing the plugin with an Automattic-controlled one with the serial numbers filed off (but still retaining the download stats, reviews, etc.), so on the next plugin update people with the free version installed would find it had been replaced. This is just Never Done and was a very unwelcome surprise to everyone, including core WP.org devs and contributors, who assumed WP.org was community-run.
He then basically demanded WP.org contributors and Automattic employees proclaim loyalty or else be removed from the open source project/quit and take a severance package, respectively. Objectors found themselves unceremoniously banned from the WP development Slack and WP.org.
He has continued to Post Through It, and on top of that, like many techbros recently has been tripping over himself to ingratiate himself with the new US President.
Anyway, the upshot is that the long-term future doesn't look great, *even for self-hosted WordPress.* While I don't think people with long-running WordPress sites should necessarily jump ship right away (I haven't), I would *definitely* steer people away from starting a WP site (either managed or self-hosted) or a Tumblr.
All GNU social JP content and data are available under the