Aside Archives

Two cool new WordPresses launched on VIP: Nate Silver’s new FiveThirtyEight site, and the Facebook Newsroom, which I believe is the first WP-powered Facebook site. (Hopefully the first of many!) Also congrats to 10up and Beyond respectively for working on each of these sites.

Very honored to be on Time’s 30 under 30 list alongside some amazing folks across a number of fields. I only have about another month of being under 30, so good to be on these lists while I still can. 🙂

Comscore, whose accuracy is generally between a Lotto Quick Pick and a drunken dart throw, says Google Maps usage has fallen since Apple Maps came on the scene. The Guardian has a good overview: How Google lost when everyone thought it had won.

We shouldn’t be surprised that in the absence of choice, people take the path of least resistance. What’s missing in these discussions is how it’s criminal Apple gets away with not allowing alternative defaults for maps, browsers, calendars, and any number of other areas, which means every time you click a link or address in the OS it opens Safari or Apple Maps, in my opinion inferior apps. Some developers get away with this by having settings to set Chrome or Google Maps as your default, like Tripit just added, but this is implemented in a hacky, per-application way, and every app puts their setting in a different place if they support it at all.

If Microsoft did this a decade ago we’d call for the DoJ to reopen their investigation. Apple has the best phone, best tablet, and in many ways the best operating system — we should not give them a pass for this blatantly self-interested and user-hostile stance. Defaults matter.

Today Akismet blocked its 100 billionth spam. 100,000,000,000. Billion with a B. We had to tweak the counter on the homepage to handle more numbers.

I’m really excited about the launch of WordPress.com Connect. Yes Facebook et al offer similar APIs and have more users, but there are two key differences. First is Automattic is not an advertising-driven company, so our priorities around users are different than ones who are. Second is that these APIs are the basis for interacting with any element of an entire website hosted on WP.com or not, meaning themes, widgets, posts, content, CSS… any company that does something that ultimately ends up on a website should be looking at the APIs on developer.wordpress.com and pushing us where there isn’t one yet.

Dave Winer tweeted this on Saturday:

One of the things I love and admire about him is that many, many years after he doesn’t have to anymore he’s still learning, hacking, and taking free time on a weeknd to make something new.

Almost 3 years ago we released a version of WordPress (3.0) that allowed you to pick a custom username on installation, which largely ended people using “admin” as their default username. Right now there’s a botnet going around all of the WordPresses it can find trying to login with the “admin” username and a bunch of common passwords, and it has turned into a news story (especially from companies that sell “solutions” to the problem).

Here’s what I would recommend: If you still use “admin” as a username on your blog, change it, use a strong password, if you’re on WP.com turn on two-factor authentication, and of course make sure you’re up-to-date on the latest version of WordPress. Do this and you’ll be ahead of 99% of sites out there and probably never have a problem. Most other advice isn’t great — supposedly this botnet has over 90,000 IP addresses, so an IP limiting or login throttling plugin isn’t going to be great (they could try from a different IP a second for 24 hours).