There are some very good (and some funny), recent Twitter threads here full of people sharing their “WordPress stories.” Thanks to John James Jacoby for asking! 😄
We’ve seen forced updates become increasingly common and less controversial over time. But who decides, and how is that decision made? Are there unofficial channels and processes, like a decision tree, for escalating to a forced update?
John James Jacoby has created Publishiza, which is a plugin that allows one to, “compose and publish a Tweetstorm” in WordPress. I personally tried this (David Bisset speaking!) and it does work like a charm. If it stops me from Tweetstorming exclusively on Twitter remains to be seen. Brian’s additional and very important note: I…
This is an important topic that came out of a Post Status Slack #security discussion involving Robert Rowley and John James Jacoby: WordPress Terminology Meta. It continued over at the WPwatercooler.
Tom Willmot on the Challenges and Opportunities Facing Enterprise WordPress • Tom Lach on the costs of rapid growth — It’s not for everyone • The Future of GiveWP and the Block Editor • Evolving Edupack — and Sunsetting It • and more…
John James Jacoby has released WP Spider Cache, and it looks really great. Specifically, he’s done some work to cater it for use with Jetpack, WooCommerce, EDD, BuddyPress, bbPress, and in networks. Definitely check it out.
John James Jacoby has created a utility called Persistent Dismissible. Here’s how he describes it, in his words: “How many times have you written some WordPress code to help you with storing the state of whether-or-not a logged-in user clicked “dismiss” on an admin-area notice, promo, or banner? Yeah. Us too.”