Today, my site hit a milestone. Jetpack Protect has blocked 1,000,000 malicious login attempts.
Typically, when using the wrong user name and password on the site, those credentials are sent to the site itself and you’ll see the site’s response that it was a bad password. Since a bunch of bots could try every combination, it could eventually guess your password.
Jetpack Protect monitors who is submitting failed login attempts on every site using Jetpack Protect. When it sees a single actor failing a number of login attempts—on one site or multiple sites—it will block that person from attempting to login on any site using Jetpack Protect.
As of r48048-core, WordPress will polyfill Emoi 13 glyphs on devices that do not support them.
What this means is whether or not your viewer’s device is able to display a 🫀 or not, you can include one on your WordPress site and it’ll display for them.
You have stuff to do — like feed your kids 👨🍼 or tend to a plant 🪴 or making face masks 🪡 — so no need to think about whether or not someone will see an emoji or a blank box on your site.
This will roll out to production as part of the WordPress 5.5, expected to ship in August.
Yesterday marked the 17th anniversary of the first release of WordPress. I didn’t use WordPress back then—I didn’t find my way to it until it was a youthful four years old in 2007.
In the 13 years since, the software has made a major impact of my life, sure, but the community around it has a greater impact. The community is what hooked me into using it and helped me grow as from a shade-tree tinkerer to working as a full-time developer at Automattic.
I didn’t appreciate the nuance of software licenses back then. I hadn’t heard about the four freedoms of software. For me, once I understood the idea, I was hooked. It just made sense.
Thanks WordPress and, more importantly, all the people behind it for 17 years of community and open source.
A long time ago, Jetpack’s Publicize feature—which automatically posts to your social media platforms when you publish a new post—started attaching an image to your tweets to help them catch people’s attention.
At the time, a tweet with a picture would perform better than a tweet with just a link.
This is all fine and good, but a lot has changed since Jetpack started doing that. Twitter cards, if nothing else, not only were developed but were opened up to all (remember when you used to have to opt-in?). When you attach media, that’s the “special” part of your tweet. The Twitter Card, rendered from the meta tags on your post, is not displayed.
Today, effective for all versions of Jetpack and all WordPress.com sites, Publicize will no longer attach a picture to your tweet, instead allowing Twitter to display the Twitter card it renders.
If you want to return to the old way and are on Jetpack 8.5 (released today) or WordPress.com Business, you can add a small code snippet to change it.
This is old news at this point, but I realized I never mentioned it here. A few months back, I shifted from a Happiness Lead to a developer.
I’m excited about the move and especially that I’m able to continue to work on Jetpack. I’ve always worked with the code powering Jetpack, but usually minor things that I discovered through working directly with our customers.
My goal isn’t to create some sweeping new feature, but to make steady, solid improvements to Jetpack. Small fixes that improve what real people are seeing with the project are beautiful things.
Of course, my tinkering is on hold a bit while on paternity leave and being on the sidelines while WordPress 5.0 ships isn’t easy! There is so much to learn, explore, and create in the space with the Block Editor, but I’ll be slinging code again soon!
Note: This post is regarding upcoming WordPress 4.9.8 and this is not applicable to production sites… yet.
In WordPress 4.9.8, among the improvements will be support for the latest Emoji 11 release. WordPress, technically, has already supported it—you’ve been able to add a 🦸 or 🦹 character even since general emoji support was added. One of the pieces of emoji support within WordPress was using the Twemoji library to polyfill emoji that your operating system didn’t support.
In other words, while you can add any Unicode character to your post, it is generally up to your operating system to support it, except for emoji, which WordPress provides a backwards-compatible way for them to display. Emoji 11 went live in early June and WordPress 4.9.7 adds support for the polyfill for these new emoji. Have an old computer? Apple hasn’t released a new version of OS X yet? You’re not on Android P, which is only in development anyhow? No problem, WordPress has your back.
So, no matter if you’re in the heat of summer 🥵 or the dead of winter 🥶, or if you’re 🥺 or 🥳, WordPress is here for you. There are a lot more than just a few smileys or the all-important cupcake 🧁. There are a ton of science-related emoji 🧬 and 🥎 to supplement the existing ⚾️.
If you’re a 🦸 and testing out Gutenberg, the emoji won’t yet render when editing a post. There’s an issue for it—need to find a good way to ensure the emoji aren’t saved as images when they’re rendered via Twemoji.
What is your favorite new emoji coming soon to your WordPress site?