As WordPress Incorporated fizzled, Matt pitched a WordPress-based blogging network to his employers at CNET. Many major internet companies had blogging networks including Google, Blogger, Yahoo 360, and Microsoft Spaces. CNET also owned several domains, like online.com, that seemed perfect for a blogging network.<\/p>\n
CNET decided against it, but the idea didn\u2019t disappear. Matt decided to build a blogging network himself. [footnote]CNET went on to be one of the first investors in Automattic.[\/footnote]<\/p>\n
First, he needed the WordPress.com domain name. At the time, it was owned by Open Domain<\/a>, an organization that registered domains and gave projects permission to use them in return for acknowledgement. It was unclear whether Open Domain was squatting on domains, or genuinely trying to help free software communities<\/a>. (They’d also registered Drupal.com, then donated it to Drupal without incident<\/a>). The WordPress community was understandably perturbed by the idea of someone squatting on WordPress.com. Owning the domain was key; there was little security in a blogging network without control of its own name.<\/p>\n After months of wrangling, Matt acquired the WordPress.com domain and work began. Donncha, as the developer of WPMU, was a perfect candidate — and fortuitously, was looking for new work opportunities. When Matt emailed the WordPress security mailing list to see if anyone was interested, Donncha got in touch.<\/p>\n The new WordPress.com ran WPMU trunk. Development was fast. Donncha worked on two servers and live-edited code. Without users to worry about, he moved quickly. He improved user-focused functionality and built network administration tools. The WPMU community helped, submitting patches to clean up admin screens. Features like domain mapping and tags, which didn\u2019t sit well in WPMU, went into plugins.<\/p>\n Andy Skelton (skeltoac<\/a>) was WordPress.com’s second employee — and first acquisition. Andy had developed Blogs of the Day, a self-hosted stats plugin that produced a list of each day’s most popular blogs. After meeting him in Seattle, Matt brought Andy on board to create a stats plugin for WordPress.com based on Blogs of the Day which, for a number of years, was featured on WordPress.com’s home page.<\/p>\n WordPress.com opened to signups in August 2005, by invitation only<\/a>, to control user growth on untested servers. Many who were involved with the WordPress project got WordPress.com blogs, including Lorelle VanFossen<\/a> and Mark Riley<\/a>. Every new WordPress.com member also got one invite to share.<\/p>\n People could also join by downloading the Flock browser, a browser with built-in social networking tools. \u201cI thought Flock was the future,\u201d says Matt<\/a>. \u201cFirst we did invites, and then we thought well, we\u2019ll allow you to bypass an invite if you\u2019re using Flock because then we\u2019ll know that you\u2019re kind of a social, in-the-know person.\u201d Flock integrated with WordPress.com, and users could use it to post straight to their blogs.<\/p>\n Both of these measures — invites and Flock — allowed WordPress.com to grow in a steady and sustainable way. Putting in sign-up barriers controlled the flow of people and helped ensure scalability. Nevertheless, demand quickly outstripped supply; one invite even landed on eBay<\/a>.<\/p>\n The influx of new bloggers also brought demands for support. Without a clear distinction between WordPress.com and WordPress.org, many bloggers made their way to the WordPress.org forums looking for help. This caused some discontent among WordPress.org forum volunteers, who felt that they were doing free work for a service that would eventually become commercial.<\/p>\n