Hello, Dreamwidth! I'd like to start this update by wishing my wife sarah a belated happy birthday (putting her on the spot in front of tens of thousands of people) -- her birthday was Saturday, and she had a very good one.

Anyway, we've got a full update this week, so on we go!

Behind the cut:

* Development
* Technical Debt
* Biz Update
* Seed Accounts
* Styles Class
* Invite Codes
* Antispam
* Our Support for LiveJournal
* Our Farewell to Inksome
* Sad News

Development

Since last we spoke, we've had one code tour:

March 17, 2011 - March 31, 2011, done by poulpette

This code tour includes (hopeful) fixes for the problems people were having with their comment import from LiveJournal timing out, an update and overhaul of the Presentation section in the Customize Journal page, and some major, massive, epic work to modernize our JavaScript sitewide. Which brings me to:

Technical Debt

I've seen a few people lamenting the lack of new user-facing features lately, or wondering why it's taking us so long to release features we said we were going to release. This absolutely isn't a sign that DW development is slowing down, or that we're working less hard or accomplishing fewer awesome things. The reason it seems like we haven't had any major feature releases lately is because we've been working hard on things that, if we do them right, you won't ever see -- backend improvements that are critical for us to do before we can do all the new feature work.

Basically, we are working on paying down our technical debt. For those of you who don't know, technical debt is a metaphor used in the software development world for the maintenance and improvements you delay for a future time in order to get code or software shipped now. Because we forked from LiveJournal, we inherited a decade's worth of delayed maintenance that we need to make good on in order to continue forward. We could keep delaying it, but we've reached the point where it's more work to continue working around the problems than it is to fix it.

We've spent the last six months aggressively working on modernizing the code and improving the backend, which is putting us in a much better position to go forward. The project's not completely done yet, but we're getting there! Most of the fixes and improvements are things you guys won't ever see, because there aren't any user-facing changes. But once we're finished, we'll be in a much better position to do feature development much more rapidly.

That's the short explanation -- if you'd like a longer one, I wrote an entry that gets into a lot more detail. You can read that here: Technical debt and the making of payments on it.

Biz Update

So, tax time is upon us, and that means that we've finalized the 2010 books and the results are in. We're cautiously pleased with how things wound up: in 2010, we very nearly broke even for the year, in terms of "money earned vs money spent", and we would have broken even or had a slight profit if it weren't for the three months of being unable to accept payments.

(For those of you who are just tuning in: in January of 2010, PayPal decided that they would no longer do business with us unless we agreed to censor the content our users posted to remove material that did not violate our Terms of Service, but bothered them. We declined, and in the end, we had nearly three months of downtime in which we couldn't accept online payments until we could implement our alternate solution.)

I've posted the 2010 Year End Update in dw_biz, in which I go into some more detail about our expenses, our results, and some of the various factors that meant we didn't actually see all the money we took in this year. If you're interested in the "behind the scenes" aspect of where your payments go and how we handle the business end of things, head on over.

Seed Accounts

We've had multiple people ask us about seed accounts (permanent accounts) lately, and whether or not we ever plan to offer them again. When we started Dreamwidth, the plan was to sell them once -- at the site launch -- and never again unless something major happened; this was to prevent seed account sales from cannibalizing future revenue.

Well, something major happened -- the three months where we were unable to accept payments did eat a lot into our operating fund, and various other factors since then have been nibbling at the reserve. (See the dw_biz post I linked in the previous section for more information there!) In order to replenish that reserve, and make sure that we have the resources to continue to expand through the rest of 2011 instead of just stagnating, we will be putting a limited number of seed accounts on sale next month.

I know that no matter what I say, people are going to worry, but rest assured: we are not in financial trouble. Right now, we are on track to break even or make a modest profit in 2011. (Which is good -- our plan for when we started DW was that we wouldn't actually start seeing a significant profit until 2013 or so!) Rather, this move is to make sure that we have a reasonable reserve in the event of (God forbid) future disaster -- it was that reserve that let us stay on the air last year when we had our payments crisis, and the reserve never quite recovered from that depletion. Having that reserve back in place will let us sleep a lot more soundly at night.

Plans haven't been 100% finalized yet -- stay tuned for more announcements -- but right now, the tentative plan is to place 400 Seed Accounts on sale in four batches over a 24-hour period on April 30 - May 1, our two-year anniversary to launching our open beta. We'll be doing it in batches to make sure that our users in every time zone -- whether geographical or personal -- have at least one opportunity for a sale time that isn't in the middle of their night. Accounts will remain on sale for as long as it takes for the 100 accounts in each batch to sell out, whether it happens immediately or over time, and each new batch will be added to the previous. (So, if there are still 50 accounts left for sale from the first batch when the time for the second batch comes due, the 100 from the second batch will be added to the 50 left from the first batch.)

As with last time, seed accounts will cost $200 (the equivalent of four years of premium paid service). You'll be able to buy them for yourself or for a friend. (We chose that number because it's what we felt was the right balance between replenishing the reserve and not hurting future sales too badly.)

We'll give you more updates on when accounts will go on sale as we get closer to the end of the month.

(Edit: And someone in the comments made me realize I hadn't mentioned: a Seed Account is functionally equivalent to a Premium Paid account, and receives the same benefits. It just won't ever expire. Also, if you have existing paid time when you buy a Seed Account, you can contact us to either transfer the paid time to another account, or have it converted back to Dreamwidth Points.)

Styles Class

Have you been wanting to learn how to customize your style more than the wizard will let you do, but haven't quite gotten around to figuring out how? Or do you have the image of the perfect style in your head and haven't been able to make it a reality?

foxfirefey is starting up a course on the DW style system and how to work it in style_system. You can view the proposed syllabus to see if it's something you might benefit from. It's a low-pressure, no-commitment-necessary way to learn how to play around with making things pretty.

Invite Codes

As many people no doubt noticed, we released another batch of invite codes earlier this week. This time we distributed 1 invite code each to all personal accounts that had been active in the last 30 days. You don't need to save the email you got -- you can always view all your invite codes at the Invite Someone page, linked on all site-skinned pages.

Invite codes don't expire; you can save them for personal use or invite a friend. Or, if all of your friends have already joined you on Dreamwidth, you can share them in dw_codesharing.

Antispam

We've seen a small uptick in the amount of spam being posted to the service, and the "no invite codes" week does seem to have had a small "logged-in spammer" result. (I'm guessing it took time for the result to become apparent, since much spam software will create an account and then let it lie dormant for a bit before posting.)

Our antispam team has been smacking down the spammers as fast as they rise, but this is a good time for yet another reminder! If you receive spam -- whether in comments or in posts to your community -- be sure to pick the "mark as spam" option while you're deleting it. That will put the comment or post into the antispam system, where our antispam team will leap upon it so fast that it's often dealt with within minutes. (No, really. They have an irc bot to alert them to new spam and everything. It's kind of frightening sometimes.)

Our Support for LiveJournal

I'd also like to take a few minutes to publicly offer support to LiveJournal, where the team has been doing an incredible job in responding to and mitigating a Distributed Denial of Service (DDoS) attack. If you haven't been able to reach LJ in the past few days, this is why; the current theory in the press is that the DDoS is a political statement being made against Russian-language bloggers using LJ as their platform. We wish the LJ team luck, perserverence, and a bottle of really good top-shelf liquor in trying to combat the problem.

We've seen increases in the number of people using the content importer to back up their content from LJ over the past few days, and with LiveJournal inaccessible during periods of heavy DDoS traffic, this can cause a problem with imports timing out or not otherwise succeeding. We'd like to ask you to consider holding off on starting a new import for a few days, until the problem can clear up a bit. Our importer is smart enough to retry an import a few times if the process times out before giving up completely, but minimizing the traffic that LJ needs to cope with can only help them out.

Our Farewell to Inksome

This week also will see the closing of Inksome, another site based on the LiveJournal code. Kit and Shell, the owners and operators of Inksome, have been awesome to us throughout, and they've been great to share ideas with over the years. We'll miss you guys, and we wish you luck.

Sad News

It's with regret that I announce the loss of padme_kenobi, a member of the Dreamwidth community. She suffered from Epidermolysis Bullosa, an incredibly rare genetic disorder. Her friends remember her as an incredibly positive force in the world; we are made lesser by her passing.

*

That's it from us for now! As always, if you're having problems with Dreamwidth, Support can help you; for notices of site problems and downtime, check the Twitter status page; if you've got an idea to make the site better, you can make a suggestion.

We'll see you in two weeks for our next update.