tl;dr: Twitter will begin charging for API access, possibly as early as the 9th of February. If your plugin integrates with the API (be it v1.1 or v2), PLEASE make sure you look into the changes and how they might impact you! Yesterday Twitter...
Category - Make Plugins
Looking for your (intentionally) wrong plugins
tl;dr: Do you have demo plugins that are...
Plugin Guideline Update: Community Code of Conduct
tl;dr: All representatives of a plugin are...
Plugins/themes categorization
After State of the Word, you may have noticed a...
Reminder about Final Notices
tl;dr? If you get a final notice from the plugin...
Reminder: We will check your website
tl;dr: If you put a website as the official...
Heroku Free Tier Being Retired
tl;dr: Heroku’s free plan is going away. Please...
Top reasons not to use setlocale() for character encoding conversion
Many WordPress plugins use the setlocale()...
Proposal for a WordPress plugin checker
For a long time, WordPress has had the theme...
X-post: Rollback Feature: Testing Call to Action
X-comment from +make.wordpress.org/core: Comment...
Google Drive is Flagging Plugins as ‘Viruses’
tl;dr Google, who already blocked anyone from...
What’s The Deal with Invalid Reviews?
tl;dr: Don’t make reviews for your own plugin(s)...
Rejoice to sanitize_url()
At least once a day, someone has to explain that...
Featured/Beta Plugins Now Limit Changes
If your plugin is a FEATURED or BETA plugin...
Journal Entry: Removal of the Zamir Plugin
Around 17:30 UTC on March 23, 2022, I was...
Please don’t ‘test’ submitting other people’s plugins.
tl;dr: Never test vulnerabilities on someone...
Reminder: Check Your Accounts’ Emails (and your Committers)
Hi Devs! We’re getting nearer to WordPress 5.9...