Woo & Automattic

Automattic

For years, we’ve been working on democratizing publishing, and today more people have independent sites built on open source software than ever before in the history of the web. Now, we want to make it easy for anyone to sell online independently, without being locked into closed, centralized services — to enable freedom of livelihood along with freedom of expression.

It’s not a new idea: at a WordCamp a few years ago, someone stood up and asked me when we were going to make it as easy to create an online store as we’d made it to create a blog. Everyone applauded; there’s long been demand for better ecommerce functionality, but it’s been outside the scope of what Automattic could do well.

That changes today — drum roll — as WooCommerce joins the Automattic team to make it easier for people to sell online. Along with Woo’s announcement, here’s a short video explaining more:

In the past few years, WooCommerce really distinguished itself in its field. Just like WordPress as a whole, it developed a robust community around its software, and its products meet the needs of hundreds of thousands of people around the world.

Woo is also a team after Automattic’s own distributed heart: WooCommerce is created and supported by 55 people in 16 countries. Added to Automattic’s 325 people in 37 countries, that’s a combined 380-person company across 42 countries — the sun never sets.* I can’t wait to meet all my new colleagues.

Just like us, the vast majority of WooCommerce’s work is also open source and 100% GPL. And just like WordPress, you’ll find WooCommerce meetups popping up everywhere, from Los Angeles to London, and its global and community-focused work together to make the users’ experiences the best they can be.

ecomm-trends The stats are impressive: the WooCommerce plugin has over 7.5 million downloads and a million+ active installs; BuiltWith’s survey of ecommerce platforms shows Woo passing up Magento in the top million, with about triple the number of total sites. Even a conservative estimate that WooCommerce powers 650,000 storefronts means they’re enabling a huge number of independent sellers. They’ve added a tremendous amount to the WordPress ecosystem (alongside everyone else working in this area).

WordPress currently powers about 23% of the web. As we work our way toward 51%, WooCommerce joining Automattic is a big step opening WordPress up to an entirely new audience. I can’t wait to see how much more we can build together.

Automattic turns ten next month: another amazing milestone I couldn’t have imagined a decade ago. Today’s news is just the first of a number of announcements we have planned for the remainder of the year, so please stay tuned! There’s still so much work to do.

* Want to work with us? We’re hiring. Bonus points if you live in Antarctica, the only continent we don’t have covered.

As I said in the video, please drop any questions you might have in the comments and I’ll answer them as soon as I can. Also check out the posts from Mark and Magnus.

Read more: Mashable, Recode, Techcrunch, Venturebeat.

How P2 Changed Automattic

Automattic, Essays

If you haven’t heard of P2 yet, check out this quick video:

https://videopress.com/v/YYNW9iSj

Almost everyone at Automattic is a blogger, but for the first couple of years of the company we didn’t blog much internally. Everything happened over IRC, Skype, and email. (In that order.) Eventually we started a blog that worked like a traditional blog did with long posts and comments, but everyone forgot to visit it until I wrote a quick script on cron job that would email everybody summaries of new posts and comments.

There was a disconnect we couldn’t reconcile: even though our internal blogs didn’t work out most of the company was active on Twitter every day. (WordPress users are some of the most passionate adopters of micro-blogging.)

We found a solution in Prologue which added a posting box to the home page and gave it a Twitter-like feel. Now Automattic had a pulse, a place where the incredible amount of activity was chronicled and captured. It was low-friction and hassle-free, we all started using it more.

But there was still a problem, Prologue was great for status updates but terribly awkward for conversation. P2 solves all this by moving the conversation inline on the homepage. Conversations can be fully threaded using 2.7’s new comment features. Finally the blog started to get so busy we made it real time so you can just leave the page open and new stuff will come in. (It’s hard to describe, so watch the video above.) Seemingly simple changes have increased engagement many-fold: our main P2 now has over 4,700 posts in it with 1,100 of those in the past 60 days.

It completely transformed how Automattic works internally and I think is one of the most valuable things we’ve adopted in the past year. I’m on the road a lot, and sometimes my only connection is checking the mobile-optimized P2 on my iPhone.

I’m excited about P2 partly because blogs provide an incredibly robust infrastructure on which to build more advanced apps and this is a good example of that. I’d love to see more themes that transform what WordPress can do top-to-bottom.

You can get P2 for your WordPress.org blog here, and it’s available for all of WordPress.com too.

The Redhat of Drupal

Asides

I got this email today:

Hi Matt,

I apologize for the cold email. I was researching Automattic , Inc. and wanted to ask you if there was any gaps/pains within your CMS and website. I work for the “Redhat of Drupal”, (Acquia) and we have seen an explosion of Drupal use in the Media, News, and Entertainment Industry.

Some companies using Drupal/Acquia include Warner Music, Maxim, NBC Universal, and NPR.
If you are evaluating your current system or are looking into new web projects, I would love to connect and discuss Drupal as an option.

Would it make sense to connect on this? If there is someone better at Automattic , Inc. to speak with, perhaps you could point me in the right direction?

Cheers,

—
Dillon J. ********
Enterprise Drupal Solutions
Direct: (781) 238-****

http://www.acquia.com
Acquia, 25 Corporate Drive Fourth Floor
Burlington, MA 01803

Acquia ranked #1 Software Vendor on the 2012 Inc 500

Hmmm, maybe I’ve been doing it wrong all these years… Dillon, I’ll be in touch!

New Blog Design

Design, Meta

It is now official get out of your RSS reader day. Take a few minutes to check out the new photomatt.net and browse around a bit. This is, I believe, the fifth major iteration of the design here but it’s the first one since 2003. When I last freshened the paint around here it got a link from Zeldman saying “lucky in redesign” and I figured I would never be able to top that, so I left the design the same for years. The only major change was the introduction of Asides in 2004.

Well I couldn’t top the last design, but Nicolò Volpato had no trouble creating something beautiful I started coding up earlier this weekend. Nicolò is still working on mocking up a few of the pages, and in the meantime I’ve been working on a little additional functionality around the site, particularly with photos.

Here are a few things you might notice so far: related posts on entry pages, recent entries shown in the sidebar on entries older than 2 weeks, when a blog is from the same day as a photo album random photos from that day are shown at the bottom, and likewise a photo will show when there’s a post that day.

The main goals of the photo integration were to enable a little more serendipity. There are a lot of other little Easter eggs, but those will remain an exercise for the reader.

6 Steps to Kill Your Community

Essays

There have been a number of new platforms popping up recently that claim to increase your user engagement, get you more comments, increase your traffic, and more, through means that I consider short-sighted and harmful. Since people seem not to mind, I thought I’d write a guide for how to increase the number of comments you get by 400-1,000% and ruin whatever shred of community you had on your site.

  1. Don’t Moderate. Allow anybody to post anything regardless of whether it contributes to the conversation or not. Stupidity, libel, hate, curse words are all okay because in the comments you have plausible deniability. Make sure people know that whatever they post will live forever, and anything goes. The few smart people you did have in your comments will enjoy responding to these folks. Advertisers love being next to a good fight, too.
  2. Allow Spam Through. I don’t mean the obvious viagra mortgage stuff, but the human-written and surface-thoughtful comment that “Florida Real Estate” or “Poll Widgets” decided to leave on your entry. Or the guy who comments on every post and has a 3-link signature. Or the lame startup that mentions itself at every possible opportunity, however tangentially related it is. Once spammers catch a sniff of this stuff getting through, they’ll descend on your site like locusts and instantly double or treble your “community.”
  3. Force Signup. You’re not a blog, you’re a social network cum media empire and even to leave the smallest comment you should make me fill out a profile, preferably with demographic information you can use in advertiser pitches later. (*cough* CNET) Please ignore useful services like Gravatar and try to get me to upload yet another profile picture because you think that makes your site more “sticky.” (In a sense of the word, it does.)
  4. Don’t Participate in Comments. Make it clear that your post itself is for annointed authors who don’t mix with the hoi polloi in the comments ghetto. Don’t link or highlight anything good from the comment section; those people silly enough to contribute content to your site for free should feel ignored. If an author does happen to drop in and make a comment, make sure it doesn’t stand out from the rest so it’s lost amid the sea of…
  5. Random Crap from Around the Web. Make sure any comments you have are buried by every random piece of “conversation” from around the web, especially retweets, Delicious links, Digg and Slashdot comments, pretty much anything will work here. Bonus points for unmoderated pingbacks, so every scraper spam blog copying the content of the post gets a free link in the comments.
  6. Design Like NASCAR. The more buttons, widgets, stickers, and visual clutter the better. I want to see every possible login system including but not limited to Facebook, Twitter, OpenID, Google Friend Connect, and that Myspace thing. Because of their respective crappy terms of service, use the giant buttons they insist on. Also include a megabyte of “share this” icons for every obscure service in every language. People love options! Complexity is for closers.

As a bonus, here are a few extra that don’t make any sense to me, but seem to be popular:

  1. Abandon Search Engines. Make sure your comment system is externally hosted on a separate domain and injects comments in via JavaScript, so everything is completely invisible to search engines. For bonus points, even if you have an existing database, say WordPress, with all of your comments, make sure the external service doesn’t synchronize any of the new stuff back into it, so you’re at the mercy of the external provider forever and ever.
  2. Be Famous! You’ll get thousands of comments on almost everything you post and make sure only to let through the most sycophantic and saccharine, don’t tolerate real conversation or debate. To spice it up every now and then opine on a known controversial subject like abortion and let your audience loose on each other like gladiators while you watch from the stands.
  3. Put the Comment Form at Top. This ensures everyone making a comment hasn’t read any of the discussion so they’ll leave a comment anyway even if the exact same thing has been said already or a question has already been answered.
  4. No Subscriptions. Don’t allow me to get email notifications of new stuff, make me visit your site and reload the page constantly to see if there’s anything new.
  5. Make People Click Click Click. Ideally do 1-comment-per-page CNET-style and your pageviews will go through the roof, but if you can’t stomach that just make comments-per-page setting low or have some sort of complicated nesting scheme.
  6. Treat Everyone the Same. If I’ve left hundreds of great comments over many years on your site, please make me wait in the moderation queue like some random stranger off Digg. Don’t let anyone know I’m a regular, or talk to me, or invite me to test out beta stuff, or pretty much anything that acknowledges my existence or shows any degree of trust.
  7. Don’t Ask Anything of Your Audience. No polls, surveys, or open-ended blog entries. What do those plebes know anyway?

Shameless: IntenseDebate does all of the software stuff right, or will shortly. Core WordPress threading, moderation, and whitelists are already built in but also check out Subscribe to Comments and of course Akismet.

What are your pet peeves and rules?

Twenty-six

Personal

Today is my birthday! It is also, if you write it the right way, a palindrome: 01-11-10. (Hat tip: Mike Adams.)

Twenty-five was a very good year. I started out with a lot of goals and actually made progress or accomplished most of them, as well as some things I didn’t anticipate. Of my 14 resolutions last year 10 of them are solid or at least had significant improvement, while the things I never do I still didn’t do: Spanish, cooking, exercise. (I might post a more detailed review later.) The thing I’m most happy with this year has been quantity of reading — I’ve read more in the last year than the past several years combined, and have also started keeping up with periodicals (New Yorker, Economist, Atlantic, Wired) pretty much every issue which has helped me feel much better informed about the world. The most significant device to me in 2009 wasn’t the iPhone, it was the Kindle.

In some ways I’ve nested a lot in the past year, including the oh-my-goodness scary commitment of buying my first place, but at the same time I’m still addicted to movement. I saw the excellent movie Up in the Air recently and related to it more than I was comfortable.

I’d like for twenty-six to be an infrastructure year, laying down the groundwork for things to come. No open source resolution like last year, but here’s what I’d like to focus on in 2010:

  • Minimize and simplify, try to de-cruft and streamline as much as possible, particularly with regards to physical possessions.
  • Move, which hopefully is a good opportunity for the above.
  • Eat, hopefully not too richly, and stop when I’m full. (I have so much trouble with that, I love food and I’m a completionist.)
  • Watch Farscape from start to finish, since my sister gave it to me for Christmas.
  • Bike and walk, more than drive.
  • Learn more about captology.
  • Showcase my photography, in print, somewhere.
  • Redesign, this site, because it’s fun. 🙂
  • Talk more, with the people I love.
  • Eliminate “sort of” and “kind of” from my speech.
  • Launch, launch, launch. (Code for me: JQ, OT, NA, MT, BB, UL, MA, VP, NT, 5L, 20, 70.)

This is the eighth year I’ve blogged my birthday: 19, 20, 21, 22 (this one is funny), and 23, 24, and 25. Whew. Here’s to the second quarter century of life.

All birthday posts: 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40.

Twenty-four

Asides

Every year my birthday sneaks up on me, and this was no exception. After the lull of the holidays and the whirlwind first few days of the year, I am now officially 24. This is the sixth year I’ve celebrated with you guys on this blog, 19, 20, 21, 22, and 23. This year should be interesting because many of the things I started 2–5 years ago are just now starting to come to fruition. I’m also hoping there will be some big changes on photomatt.net, including possibly a change in domain name. I’ll post more on that as it develops though. I hope everyone has a wonderful weekend!

All birthday posts: 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40.

Wither Dreamweaver

rant, , ,

I’ve done my coding in Dreamweaver for 5+ years now. I think I’m the only one who does so at Automattic, but it’s a good fit for me with the network/SFTP integration, decent PHP highlight, regex search/replace, and good project support. It was a natural transition for me from Homesite. I know there are a thousand other editors that I could use, and I know I shouldn’t be on Windows most of the time, but that’s not what this post is about. I’m utterly appalled by how bad Dreamweaver CS3 is. I paid hundreds of dollars to upgrade to something that consistently crashes when I edit certain parts of PHP files and CTRL + F no longer opens a search box unless I have a document open.

Dear Dreamweaver team, I’ve been putting up with these bugs for close to a year now. I will come down to San Jose and show you the bugs personally. Just please do something, or feign the appearance of movement. For now, I’m switching from CS3 to version 8, which is just sad.

Dance to Calypso

Automattic, WordPress

One of the hardest things to do in technology is disrupt yourself.

But we’re trying our darndest, and have some cool news to introduce today. When I took on the responsibility of CEO of Automattic January of last year, we faced two huge problems: our growth was constrained by lack of capital, and the technological foundations of the past decade weren’t strong enough for the demands of next one.

The first has a relatively straightforward answer. We found some fantastic partners, agreed on a fair price, issued new equity in the company to raise $160M, and started investing in areas we felt were high potential, like this year’s WooCommerce acquisition. This “war chest” gives us a huge array of options, especially given our fairly flat burn rate — we don’t need to raise money again to keep the company going, and any capital we raise in the future will be purely discretionary. (Since last May when the round happened we’ve only spent $3M of the investment on opex.)

The second is much harder to address. The WordPress codebase is actually incredible in many ways — the result of many thousands of people collaborating over 13 years — but some of WordPress’ greatest strengths were also holding it back.

The WordPress codebase contains a sea of institutional knowledge and countless bug fixes. It handles hundreds of edge cases. Integrates constant security improvements. Is coded to scale. Development moves at a fast clip, with six major releases over the past two years and more around the corner. Its power and flexibility is undeniable: WordPress just passed a huge milestone, and now powers 25% of the web. You can run it on a $5-a-month web host, or scale it up to serve billions of pageviews on one of the largest sites on the web, WordPress.com.

The interface, however, has been a struggle. Many of us attempted to give it a reboot with the MP6 project and the version 3.8 release, but what that release made clear to me is that an incremental approach wouldn’t give us the improvements we needed, and that two of the things that helped make WordPress the strong, stable, powerful tool it is — backward compatibility and working without JavaScript — were actually holding it back.

The basic paradigms of wp-admin are largely the same as they were five years ago. Working within them had become limiting. The time seemed ripe for something new, something big… but if you’re going to break back compat, it needs to be for a really good reason. A 20x improvement, not a 2x. Most open source projects fade away rather than make evolutionary jumps.

So we asked ourselves a big question. What would we build if we were starting from scratch today, knowing all we’ve learned over the past 13 years of building WordPress? At the beginning of last year, we decided to start experimenting and see.

Today we’re announcing something brand new, a new approach to WordPress, and open sourcing the code behind it. The project, codenamed Calypso, is the culmination of more than 20 months of work by dozens of the most talented engineers and designers I’ve had the pleasure of working with (127 contributors with over 26,000 commits!).

gm-2015-final

Calypso is…

  • Incredibly fast. It’ll charm you.
  • Written purely in JavaScript, leveraging libraries like Node and React.
  • 100% API-powered. Those APIs are open, and now available to every developer in the world.
  • A great place to read, allowing you to follow sites across the web (even if they’re not using WordPress).
  • Social, with stats, likes, and notifications baked in.
  • Fully responsive. Make it small and put it in your sidebar, or go full-screen.
  • Really fun to write in, especially the drag-and-drop image uploads.
  • Fully multi-site for advanced users, so you can manage hundreds of WordPresses from one place.
  • Able to manage plugins and themes on Jetpack sites, including auto-upgrading them!
  • 100% open source, with all future development happening in the open.
  • Available for anyone to adapt to make their own, including building custom interfaces, distributions, or working with web services besides WordPress.com.

A lot of people thought we should keep this proprietary, but throughout my life I’ve learned that the more you give away, the more you get back. We still have a ton to figure out around plugins, extensibility, contributions, Windows and Linux releases, API speed, localization, and harmonizing the WordPress.com API and WP-API so it can work with core WordPress. Thousands more PHP developers will need to become fluent with JavaScript to recreate their admin interfaces in this fashion. I’m also really excited to revisit and redesign many more screens now that we have this first version out the door.

This is a beginning, not an ending. (1.0 is the loneliest.) Better things are yet to come, as all of you dig in. Check out these links to read more about Calypso from different perpsectives:

This was a huge bet, incredibly risky, and difficult to execute, but it paid off. Like any disruption it is uncomfortable, and I’m sure will be controversial in some circles. What the team has accomplished in such a short time is amazing, and I’m incredibly proud of everyone who has contributed and will contribute in the future. This is the most exciting project I’ve been involved with in my career.

With core WordPress on the server and Calypso as a client I think we have a good chance to bring another 25% of the web onto open source, making the web a more open place, and people’s lives more free.

If you’re curious more about the before and after, what’s changed, here’s a chart:

Whats-New-WPcom@2x

 

WP.com Marketplace Idea

wordpress.com, ,

At WordCamp Argentina yesterday I talked about an upcoming feature for WordPress.com, a theme marketplace, and while the feedback has been universally positive amoung everyone I talked to some folks who weren’t there and don’t speak Spanish seem to be criticizing third-hand, Google-translated information, which is a little sad to watch, so here’s some details. 🙂

Right now WordPress.com is a little bit like a clothing store with only XXL men’s pink ponchos available — not a lot of selection. We’d like to offer more products, hence the idea of a theme marketplace.

Imagine you’re a theme designer and if you do a custom one-off theme for a site like this you may get $500. (Keeping the numbers simple for the sake of argument.) Making a good theme is really hard, and you may only be able to do one a week. Now imagine you made a theme and uploaded it to our theme marketplace, then set a price of $50. You’re now an option on the dashboard of 1,736,206 blogs, if we split the price evenly and 20 of those 1,736,206 blogs purchase the theme, you just made as much as you would doing a one-off design. You can plug in different numbers and assumptions there and it’s pretty easy to see how this could be big for designers.

There are some obvious things that need to be in place, and probably a few we haven’t thought of yet. There need to be some theme guidelines (and good taste) enforced, an easy, safe interface for uploading and updating of themes, a system for previewing a theme live on your blog. Beyond the obvious guidelines of browser compatibility and general not-sucking, we’ll require submissions be original, link-free, not published before, and GPL-licensed. (That also means that all themes in the marketplace will be available FREE to wordpress.org users. That may force some to switch from .com to .org, but that’s fine. :)) Will .com users want to buy premium themes? I think so, but the only people really taking that risk are launch partners, and worst-case scenario you’ve got a cool WP theme on your hands. (By the way if you have an amazing theme and you want to be in this program at launch, which should give it a nice boost, drop me an email m@mullenweg.com with “killer theme” in the subject.)

At the end of the day, it’s just a market. I’m sure styles, pricing strategies, and more will develop over time.

Turkey Update

Censorship,

The folks responsible for blocking WordPress.com in Turkey have issued a press release, here’s some snippets.

As it is known by public, the entry of the publications to Turkey of the blog service named “woldpress.com” that gives the opportunity of opening free site to internet users is interrupted with the judgement. This judgement is applied on 17.8.2007 and thus the entery of worldpress.com service and the publications of all sub-sites which takes service from this service to Turkey is interrupted.

aI wish they had blocked worldpress.com instead. They seem proud that they blocked all the sites instead of just the ones that they consider illegal under Turkish law.

The reason of this suspention, is that the limitlessly enable to illegal publications of the mentioned blog service, not taking to notice about the suspention of the applications and ignoring the judgements that are given by the Turkish courts related to the suspention of known sub-sites. The free and uncontrolled opportunities provided by the mentioned service are directed baleful people to this service and in a short time wordpress.com is returned to the voice and publication center of separatist-disastrous ideologies, private hostilities, illegal targets.

As far as I know, we never received any notice from Turkish courts about anything, only barely coherent threats and bully-attempts written much like the above.

Thus before ABOUT 17 TÄ°MES we have appealed to the mentioned site administration for the suspention of the unlawful publications , but the site administration did not take any caution about these publications.(one of our applications is published in their sites) Thereon about our applications RELATED WITH THE SUB SITES THAT ABUSE OUR CLIENT’S PERSONAL RIGHTS the Turkish courts have given numerous judgements for the closing of the illegal sub-sites which are broadcasting under WordPress. These judgements are delivered to the center of the mentioned firm in USA and to the agency in Turkey, this time the suspention of the illegal publications according to the judgements of the Turkish courts is asked. BUT, IN SPITE OF THE ALL WRITTEN AND ORAL APPLICATIONS, THE MENTIONED FIRM AND ITS AGENCIES ARE NOT AFFILIATE OUR REQUIREMENTS AND THE JUDGEMENTS OF THE TURKISH COURTS AND THEY INSISTED ON APPLYING.

Just to clarify when they said they contacted us 17 times, that means that they would blast the same email to multiple address and when they didn’t get the reply they wanted they sent the same message over and over again.

In addition to some blogs they complained about, their main request was that we block the name of their client being used by any blog hosted by our site, much like you can’t write “democracy” on blogs hosted by MSN Spaces in China. I’m going to skip some bits to the threat at the end:

There is a lesson which all blog services and internet service providers should take from this judgement. Blog services, especially the ones that give free service, should be careful about the sites that are illegally active through their firms. These services should not remain insensitive to the complints that they receive and especially to the judgements. It is certain that the services which behave opppositely will meet with the same enforcement that WordPress met.

So if you don’t disallow certain words being used on your blogs, you’ll be punitively punished through our state-controlled ISP. Today those words are “Adnan Oktar.” Who knows what they’ll be tomorrow.

Meaningful Overnight Relationship

press

One thing I’ve noticed about talking to certain types of press, particularly mainstream, is that they have a pattern in mind before they write about something, and the better you conform to the pattern the more coverage you get.

I think what they really want is an unusually young founder, possibly with a partner, who stumbled on an idea in an epiphany moment, implemented it in days, and then enjoyed overnight success, preferably capped with some sort of financial hook such as a huge VC funding or selling out to a large company for millions of dollars.

It’s not uncommon to get leading questions trying to hit a point in the above patterns… Yes, WordPress really is four years old. I was 19. No, I didn’t create it alone, if I did you would have never heard of it. Actually, it entered a rather crowded field, not even close to being first. No, not planning to sell it, there isn’t really anything to sell, it’s more of a movement. No, I didn’t make 60 million dollars in 18 months.

What’s worst is I think these stories sell a false promise and hope to people outside of the industry — it attracts the wrong type of entrepreneurs — and inside of the industry it distracts us from what really matters.

Someday I think there will be a realization that the real story is more exciting than the cookie-cutter founder myth the media tries frame everything in. It’s not just one or two guys hacking on something alone, it’s dozens of people from across the world coming together because of a shared passion. It’s not about selling out to a single company, it’s dozens of companies independently adopting and backing an open source platform for no reason other than its quality. I’m not a millionaire, and may never be, but there are now hundreds of people making their living using WordPress, and I expect that number to grow to tens of thousands. That’s what gets me out of bed in the morning, not the prospect of becoming a feature on an internet behemoth’s checklist.

Finally it’s not Web 2.0, or another bandwagon me-too content management system with AJAX, it’s a mature project that has been around and grown up over four years of hard work, and it has many, many more years of hard work ahead of it. I smile these days when I see WordPress referred to as an “overnight success,” if only they knew how long an overnight success takes.

Update, see also:

The Wix Mobile App, a WordPress Joint

Open Source

Anyone who knows me knows that I like to try new things — phones, gadgets, apps. Last week I downloaded the new Wix (closed, proprietary, non-open-sourced, non-GPL) mobile app. I’m always interested to see how others tackle the challenge of building and editing websites from a mobile device.

I started playing around with the editor, and felt… déjà vu. It was familiar. Like I had used it before.

Turns out I had. Because it’s WordPress.

If I were being charitable, I’d say, “The app’s editor is based on the WordPress mobile app’s editor.” If I were being honest, I’d say that Wix copied WordPress without attribution, credit, or following the license. The custom icons, the class names, even the bugs. You can see the forked repositories on GitHub complete with original commits from Alex and Maxime, two developers on Automattic’s mobile team. Wix has always borrowed liberally from WordPress — including their company name, which used to be Wixpress Ltd. — but this blatant rip-off and code theft is beyond anything I’ve seen before from a competitor.

Dear Wix,

This explicitly contravenes the GPL, which requires attribution and a corresponding GPL license on whatever you release publicly built on top of GPL code. The GPL is what has allowed WordPress to flourish, and that let us create this code. Your app’s editor is built with stolen code, so your whole app is now in violation of the license.

I suppose we’ll take this as a compliment — I’m sure the hundreds of people who have contributed to WordPress Core and our mobile apps are flattered that you chose to build one of your company’s core features using our code. We’re also excited to see what great things you create with all the time you saved not having to write your own mobile editor.

You know what’d be even more exciting? To see you abide by the GPL and release your source code back to the community that gave you that jump start.

I’ve always said that the GPL isn’t about limits, it’s about possibilities. In open source software, you trade some of your control as a developer to better serve the developer community and the people using your sites and products. I don’t think that’s a limit, I think it’s a way to make sure we encourage innovation and momentum. If you want to close the door on innovation, Wix, that’s your decision to make — just write your own code. If you’re going to join the open source community, play by the open source rules.

Release your app under the GPL, and put the source code for your app up on GitHub so that we can all build on it, improve it, and learn from it.

Love,
Matt and the open source community

An Update

The CEO of Wix has posted a response on their blog. I’ll also try to post my response it to the comments there. Miriam Schwab also has a very good response.

We were all very surprised by your post, as you have so many claims against us.

Wow, dude I did not even know we were fighting.

It’s not a fight: the claim is that the Wix mobile apps distribute GPL code and aren’t themselves GPL, so they violate the license.

First, you say we have been taking from the open source community without giving back, well, of course, that isn’t true. Here is a list of 224 projects on our public GitHub page, and as you can see they are all dated before your post. We have not checked if WordPress is using them, but you are more than welcome to do so, some of them are pretty good.

Very glad your company has projects on GitHub! Thank you for the offer to use them; if we do, we’ll make sure to follow the license you’ve put on the code very carefully.

Releasing other open source projects doesn’t mean that you can violate the license of the editor code you distributed in your mobile apps. To repeat my earlier points: since you distributed GPL code with your apps, the entire apps need to be released at GPL, not just your modifications to that one library.

As this Hacker News comment put it, “Open source is not a swap meet; you can’t violate a license if you voluntarily release some other code to make up for it.”

We always shared and admired your commitment to give back, which is exactly why we have those 224 open source projects, and thousands more bugs/improvements available to the open source community and we will release the app you saw as well.

If you were to release the entire source code of the apps under GPL that would bring you back into compliance with the license you violated. I think you’re saying you will do that here, but can you clarify? When should we look for the app code to be released, and where? That would resolve this issue completely.

Next, you talk about the Wix App being stolen from WordPress. There are more than 3 million lines of code in the Wix application, notably the hotels/blogs/chat/eCommerce/scheduling/booking is all our code.

I said the app includes stolen code. It doesn’t matter if it’s 30 lines or 30 million lines: because it includes GPL code and you distributed the app, the entire thing needs to be GPL. If you release the entire app’s code, as I think you said you would, then that resolves the license violation.

Yes, we did use the WordPress open source library for a minor part of the application (that is the concept of open source right?), and everything we improved there or modified, we submitted back as open source, see here in this link – you should check it out, pretty cool way of using it on mobile native. I really think you guys can use it with your app (and it is open source, so you are welcome to use it for free). And, by the way, the part that we used was in fact developed by another and modified by you.

Thank you for admitting you used the code and not trying to hide it. The issue isn’t the changes you made, it’s that including the editor means you need to submit the entire app as open source, which you have not yet — it’s completely proprietary.

If you want to read the account from Tal Kol, one of the leading engineers on this project, here it is. He was really happy to share his side of the story.

I have seen it, and it already has a number of good comments on it, including this one: “Can you address this point made in Matt’s post: ‘This explicitly contravenes the GPL, which requires attribution and a corresponding GPL license on whatever you release publicly built on top of GPL code’.” It appears you and Tal might share a misunderstanding of how the GPL works — software licensing can be tricky and many people make honest mistakes. (If you want to get into serious detail, this comment lays the licensing requirements out clearly.) It is easy to rectify this one: release your apps as open source under the GPL.

Now, what is this thing about us stealing your branding? Our product was always called Wix and our website Wix.com, we never borrowed from your marketing or brand.

Sorry for including this distraction; I was referring specifically to the fact that Wix used to go by “Wixpress.” You can see this in your Form F-1, and there used to be a support page about this on your site:

Although that is still in Google, the page it links to now mysteriously returns a 404 error, which you may want to look into.

In fact, if I remember correctly, until recently the Automattic home page was all about blogs and only recently it has become “websites.” Also, your business model changed to almost exactly the one we had for years. Can it be that you guys are borrowing from us? If so, again, you are welcome to it.

The Automattic home page has been a series of haiku about our products since 2009, pretty much unchanged — I think you mean the WordPress.com home page here. WordPress has been used for creating websites, not just blogs, since our 1.5 release in 2005 added themes and pages. In my 2014 State of the Word address I talked about how 87% of WordPress sites use it as a CMS. We regularly test dozens of variations of the WP.com homepage and some of them definitely emphasize website creation. I will say we look to Wix, Weebly, and Squarespace as innovators in the space with products that reach many small businesses, and Wix especially should be commended for its success and growth as a public company.

If you believe that we need to give you credit, that you deserve credit, I must say, absolutely yes. You guys deserve a lot of credit, but not because of a few lines of source code, you deserve credit because you guys have been making the internet dramatically better, and for that we at Wix are big fans. We love what you have been trying to do, and are working very hard to add our own contribution to make the internet better.

Thank you very much, that is kind. I do think there are a lot of values we share in common and would love to see this one issue resolved.

If you need source code that we have, and we have not yet released, then, most likely we will be happy to share, you only need to ask. We share your belief that making the internet better, is best for everyone.

That’s what my post was asking, for you to release the code. To quote my original letter: “Release your app under the GPL, and put the source code for your app up on GitHub so that we can all build on it, improve it, and learn from it.”

Finally, during the last couple of years, I reached out a couple of times trying to meet with you. Could I do that again here? I believe in friendly competition, and as much fun as it is to chat over the blogosphere, maybe we can also do it over a cup of coffee?

Once this is resolved I’d be happy to meet up. I believe when we exchanged emails in 2014 there was trouble finding overlap in our travel schedules.

I hope the above clarifies where we think Wix made a mistake, and how to fix it.

Don’t Check Your Valuables

Karma

Another lesson learned the hard way — on the flight from Philadelphia to San Francisco on US Airways my baggage was delayed, and then when it arrived the following morning all my camera equipment was missing. Since I had just been to Italy I was carrying more than usual. The toll ended up being:

  • Nikon D3
  • Nikkor 85mm f/1.4D IF
  • Nikkor 24-70mm f/2.8G ED
  • Leica M8
  • Leica 50mm f/1.0 Noctilux
  • Cards, cases, etc.

I’ve traveled so many times with things in my suitcase I just don’t think about it anymore, literally over a hundred trips over the last 4-5 years. This has shaken me a lot more than the incident a few weeks ago and I’m probably not going to check any electronics anymore. Jon Udell had something similar happen and found a story about packing a starter pistol to get your baggage treated differently. (Hat tip: Lloyd.)

Since relating this story a few other people have told me they’ve had things stolen when leaving Philadelphia specifically, it sounds like there might be a serious problem there, one that warrants investigation. US Airways is just sending me through the “lost luggage” form, so I doubt anything will change or happen. Be extra careful if you travel through there.

Intense Debate Goes Automattic

Automattic, , ,

Some cool news today — Automattic is acquiring Intense Debate. You can read more on Jon’s blog on Intense Debate, or on Toni’s blog, or on VC Mike’s blog.

For those of you who aren’t familiar with the product, Intense Debate supercharges the comment section of WordPress blogs and other sites with cool features like threading, reply by email, voting, reputation, and global profiles. There are a few companies tackling this space right now, but I was impressed with how much ID (Intense Debate) has been able to do with a small team, and happy to find that their common platform (PHP and MySQL) would make integration a lot easier.

Going forward, the plan is to keep Intense Debate available as a platform-agnostic independent service, much like Akismet. We’ll start to integrate its features into WordPress core, WordPress.com, and Gravatar as appropriate. For example, comment threading is going to be in WordPress 2.7, but reply by email is a lot easier to implement on a hosted service like WordPress.com. We’re also going to be able to lend our expertise in scaling to the ID team to make sure their users enjoy the same hassle-free speed and bulletproof availability as users of other Automattic services.

Long-term, I think that comments are the most crucial interaction point for blogs, and an area that deserves a lot of investment and innovation. Comments really haven’t changed in a decade, and it’s time to spice things up a little.

We were early in the space with investing in Akismet to solve the spam problem, but now I think the real growth opportunities are in the user interaction and social features across comments. There is a huge opportunity to increase the traffic and engagement of blogs significantly. WordPress.com alone already gets about three legitimate comments every second — more than a quarter of a million every day. I’m excited to see what the Intense Debate team can do to make things more interesting.

The Blogging Software Dilemma

Asides

This site is beginning to grow and grow, and forward compatibility has lately been in my mind more. Several days ago this site passed twenty thousand unique visitors, and more than seventy thousand hits, since late August. I recently converted everything (except the photolog) to XHTML 1.1, which was nice, but it’s not the markup I’m worried about. My logging software hasn’t been updated for months, and the main developer has disappeared, and I can only hope that he’s okay.

What to do? Well, Textpattern looks like everything I could ever want, but it doesn’t look like it’s going to be licensed under something politically I could agree with. Fortunately, b2/cafelog is GPL, which means that I could use the existing codebase to create a fork, integrating all the cool stuff that Michel would be working on right now if only he was around. The work would never be lost, as if I fell of the face of the planet a year from now, whatever code I made would be free to the world, and if someone else wanted to pick it up they could. I’ve decided that this the course of action I’d like to go in, now all I need is a name. What should it do? Well, it would be nice to have the flexibility of MovableType, the parsing of TextPattern, the hackability of b2, and the ease of setup of Blogger. Someday, right?

Update, 2003-12-26: This became WordPress.

On the Dvorak Keyboard Layout

Uncategorized

It’s a relatively well-known fact that I am a Dvorak typist, and have been for about four or five years now. Just an introduction for the uninitiated, the Dvorak keyboard layout is just a different arrangements of letters purposively chosen because it is more efficient for typing the English language. For example, instead of my left hand resting on the letters ASDF it rests on the letters AOEU. There have been studies both ways saying it is or is not faster than QWERTY, and frankly I think most of them are useless. Logically you can see that if the letters you use most are right under your fingers, ultimately you’re going to work less while typing.

Why did I switch? If I remember correctly, I was surfing around the website of columnist John Dvorak and on some page he mentioned the Dvorak keyboard layout and linked to a site about it. Several web searches later, I had read all about the layout I could find on the web and I was ready to switch. Some of my motivation was that I wanted to be as fast as humanly possible, but it was mostly that I spend a tremendous amount of time typing and I often got pains in my hands and wrists. Switching did not seem like a big obstacle simply because it seemed very similar to learning to play a new instrument, something that as a musician I could relate to and didn’t seem too challenging.

I know now that some of my reasons for switching may have been hype on the part of the websites I read, I can offer what I have found in my personal experience to be true.

Switching is not as hard as people make it out to be. Even if you are already quite proficient at QWERTY, it’s not too hard to switch. You don’t need to buy a new keyboard, in every operating system there is a mechanism for switching what’s called the “keymap” or the mapping between the physical keys on your keyboard and what the operating system prints out. So if you switch your keymap to dvorak you can immediately begin typing dvorak in all your applications. However it can be confusing to press the button labeled T and get a Y, so it is generally better, at least while learning, to give yourself some visual aids. What I did was print out letters on a piece of paper and then stick them to the keys using double-sided tape. Of course I was 14 or 15 and had a lot more time on my hands. For some people it might be enough just to have a printout of the layout by their monitor or keyboard, but there is something to be said for being able to look at the key and seeing what you’re going to type. What I do now, if I want to physically switch a keyboard over, is actually pop off the keys and put them back in the Dvorak positions.

This is much easier than it sounds, and probably takes about ten minutes. Of course be careful because sometimes the keys literally pop right off and might jump behind a desk or something, speaking from personal experience. The main disadvantage to doing this in that your home keys no longer have ridges on them and because of the bizarre way that keyboards are manufactured, on every keyboard I’ve done this two the hook on back of the guide keys (usually F and J on your keyboard) is sideways to every other hook for every other key which means that to put those keys someplace else you’d have to put them sideways, and whatever key you put in that position will also have to be sideways. This isn’t as bad as it sounds because it actually serves as a new guide mechanism, but it looks a little funky. I can’t think of a way to do this with a natural keyboard. You can buy keyboards designed for Dvorak, but for me it has never been worth the bother. I don’t want to have to special-order my keyboard, I just want to pick up whatever is the coolest at the computer store.

My writing speed did not increase significantly. Although I could type faster than ever, the limiting factor in my writing speed is and was the way I formulate sentences in my mind, often thinking of several different ways to say something. However in situations where I can type without thinking too much, for example taking notes in class or at a conference, it has been a huge benefit and often I can keep up almost in real time with what’s being said. Of course if I stop to consider something or participate in class discussion I get behind but I think the advantage of actively participating in the class or conference outweighs whatever benefits I would get from having a transcription of it.

The big thing for me is comfort. I can now type for long periods of time with no fatigue at all, and that isn’t even an issue I think of anymore. I can’t point to anything scientific that says for every person Dvorak will be more comfortable, I just know it’s been a major improvement for me.

One advantage I don’t think I have seen mentioned before is the security aspect. On my laptop in particular there is now a device with all of my personal information on it that might be in the hands of anyone. Lets say that you knew my password, if you picked up my laptop you still would have trouble getting in simply because you wouldn’t know how to type the password in Dvorak. In the grander scheme of things this might only be a minor deterrent, but it’s enough. In situations where I want other people to use my laptop I can configure a keyboard shortcut to switch between the two layouts transparently, but more often I don’t even have the QWERTY keymap installed, simply because I don’t want to switch back and forth accidentally.

It would be overly biased of me not to mention some of the disadvantages though. Nearly every problem I’ve run into isn’t so much a problem with the layout itself, but rather being a Dvorak user in a QWERTY world. Non-configurable keyboard shortcuts are often designed to be convenient on QWERTY and so when you’re under Dvorak they can be awkward. The most notable is X, C, and V, which in most applications becomes cut, copy, and paste when used with CTRL, are no longer right next to each other and are instead all over the keyboard. I’ve found it to be not that big a deal. Though I am still alright with typing QWERTY, I am often self-conscious while at other people’s computers, because as someone who is supposed to be computer savvy it must look bad to have to hunt and peck. Of course I may just be blowing it out of proportion. If I use QWERTY for anything more than a minute or two it comes back to me and I can at least partially touch-type again, but usually my exposure to it is much shorter than that. There might be something else that has slipped my mind, but those are the only two drawbacks I can think of.

I suppose it might be significant that I am the only person I know that uses Dvorak. At some point or another, I know that many of my friends and family have given Dvorak a try, but none have stuck with it. There are hundreds of possible reasons why, but I suspect with most is they didn’t feel like investing the time. For my it was a no-brainer because I knew that however long it took me to learn it would be incrementally paid for by the increased productivity and comfort in the future. Part of it may have been incentive though, and to make things interesting I’m willing to spring for a prize.

I will buy a Logitech Elite Keyboard for the first person who switches from QWERTY to Dvorak (and sticks with it!) as a result of this post.

The judging is completely subjective, but using Dvorak exclusively for more than a couple of weeks is good enough for me.

Funnily enough, this whole thing started out as a simple link/commentary post that was supposed to be about twenty words. Getting to that, there’s an article at Kuro5shin called An Argument for Dvorak that makes some good points. The comments, on par, are mostly useless or misinformed so I wouldn’t weigh them too seriously.