It's hard to envision an outcome of the WordPress nonsense that would leave me able to say "Yes, you should invest in a WordPress solution to your problem." to anyone who wasn't already invested in WordPress in some material way. I'm not even sure how it could get to me doing the work to figure out if I should be saying that. Recommending WordPress for whole huge class of problems went from a no brainer with some security footnotes to a not even worth considering unless nothing else makes sense.
@gl33p Matt stepping down and retiring from tech completely could have been such an outcome.
But also, Wordpress the open source software (which you install on a vps you bought yourself and absolutely don't install the JetPack backdoor onto) is still a very viable thing, and the only "Wordpress" I ever would have recommended to anyone. The dot com was always a non starter.
@gl33p@goblinses That never felt safe to me. If nothing else you were vulnerable to forced updates breaking your site design, workflows, etc. (e.g. the hideous new editor)
@goblinses Yeah I basically do all of the above for various projects and people, but for a long time (15 years or more??) I could just say to folks "OK, just get a domain or subdomain you have control over, map it to WordPress.com, get to work, use good slugs so your urls are not funky & never use a you.wordpress.com URL, and pour your posts into a to-go cup when and if it gets cramped in there, or a rug pull cometh along."
That feels wrong now, with no option as good for nontech folks. @dalias
@dalias@gl33p I’m personally a big fan of ClassicPress but I have not actually used it in ages, for basic blogging stuffs I’ve just been doing the sensible thing and doing a github pages until I can reliably self-host something.