<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>dNeero.com Conversations Blog</title>
    <link>http://www.dneero.com/blog.jsp</link>
    <description>This is the official dNeero Conversations Blog.</description>
    <item>
      <title>Some Degree of Paid Seeding is a Must</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=111</link>
      <description>From &lt;a href="http://www.clickz.com/showPage.html?page=3630488"&gt;ClickZ&lt;/a&gt;: "Face it, even if you become an expert at organic seeding, the competition is tough. Very rarely is a branded viral video going to take off organically. Some degree of paid seeding is a must if you want to rise above the clutter."</description>
      <pubDate>Tue, 12 Aug 2008 23:24:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=111</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-08-12T23:24:00Z</dc:date>
    </item>
    <item>
      <title>Article: Money &amp; Credibility</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=110</link>
      <description>The &lt;a href="http://www.talentzoo.com/news.php?articleID=681"&gt;latest article&lt;/a&gt; was posted a couple days ago and deals with the issues of money and credibility within blog-for-pay models.</description>
      <pubDate>Fri, 25 Jul 2008 20:01:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=110</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-07-25T20:01:00Z</dc:date>
    </item>
    <item>
      <title>Bug Fix to Codes Visibility on Share It Page</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=109</link>
      <description>For those of you who were having trouble seeing embed codes after joining a conversation, we've made a fix and you should be able to see them now.  Apologies for the bug and thanks to everybody who reported it.</description>
      <pubDate>Mon, 21 Jul 2008 16:14:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=109</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-07-21T16:14:00Z</dc:date>
    </item>
    <item>
      <title>No Complaints on dPolice So Far</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=108</link>
      <description>So far so good.  We've flagged about 50 people for putting up obviously junk content.  And nobody's complained.  Which means that we're calling their bluff and they're not contesting it.  If we had flagged people and they had complained then our criteria for flagging could have been wrong.  We're terrified of shutting down legitimate content or censoring anybody... that's not how we roll.  But we will continue, as we have in the past, to increase the quality of the content in the system.  Early indications are that the flagging system is getting people to stop junk postings.  It's not that it was a huge problem.  But the junk postings are what potential customers focus on... as they should... we're asking them to pay for people to engage their brand with their friends.  If people aren't doing that then the model breaks down for everybody.</description>
      <pubDate>Thu, 10 Jul 2008 01:52:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=108</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-07-10T01:52:00Z</dc:date>
    </item>
    <item>
      <title>Change to Impression Scoring Coming Soon: Limit Per Time Period</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=107</link>
      <description>There was a code launch today.  For a few hours clicks on a person's answers acted differently on the front-end than they had in the past. (I've since changed the UI back to, more or less, the way it was before.)  People complained that maybe they'd have to click into profiles to read conversations and that this would be a burden.&lt;br&gt;&lt;br&gt;I do understand.  But potential customers get what's up and they don't like it.  It's clear that they don't want to pay for junk clicks.  A small subset of users aren't reading each other's answers which is what an impression should count for.  Instead, they're trading clicks and in a rapidfire manner are generating impressions for many users' conversations.&lt;br&gt;&lt;br&gt;So I'll soon implement something that makes it so that you can click as much as you want but only one impression is recorded per sixty seconds per web visitor.  When a click doesn't count I'll display a warning on screen to that effect.  Maybe 60 seconds isn't the right time period... maybe it's 2 minutes... maybe it's 20 seconds.  In this way we'll be able to argue that people are actually reading the answers and that clicking purely for impressions isn't happening.  &lt;br&gt;&lt;br&gt;We know that people are actually reading the answers because we email a lot of folks and we check web traffic stats.  But we can't prove it clearly and the quick-clickers are very obvious about their activity on Facebook groups... which is what potential customers find very quickly.   Thanks Search box.&lt;br&gt;&lt;br&gt;Right now we can't prove people aren't quick-clicking and it's hurting our ability to sell.  Companies are saying "well, I don't want to pay cash for people to quickly click and ignore."  As much as we argue that this is a small percentage of users and that the holistic result is great exposure, the risk of junk clicks spooks them.&lt;br&gt;&lt;br&gt;Most people use the system on blogs and in Facebook without trading clicks with their friends.  Clicking-without-reading is hurting most users as they're lumped into a category of people essentially gaming the system.  Clicks alone were never the intention... reading of the conversation and true involvement was.  I thought that clicks was a good proxy but maybe not.&lt;br&gt;&lt;br&gt;In the short term I didn't want to enforce it because the dollar amounts were low and we were young so I decided that it'd be best not to be a hardass about it.  But maybe that was short-sighted.&lt;br&gt;&lt;br&gt;Us getting sales is good for everybody.  We're talking to companies about multi-dollar opportunities and series of conversations.  We can only foot the bill personally for so much longer.  I'm not naive enough to believe that anybody really cares right now whether we go bankrupt, but I do think that people would like to be part of something that grows, takes on new partners and starts to generate some real cash.  Getting there means increasing the quality of the system as a whole... from the way impressions are counted to the ways that people can interact.&lt;br&gt;&lt;br&gt;One big change today, apparently overlooked in the terror exhibited when a small group thought they'd actually have to, you know, read conversations, is that answers are now editable.  Something that's been requested for many months but was herculean to implement.&lt;br&gt;&lt;br&gt;Quality's going up.  Changes to impression scoring coming soon.</description>
      <pubDate>Thu, 10 Jul 2008 01:07:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=107</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-07-10T01:07:00Z</dc:date>
    </item>
    <item>
      <title>Content Flagging and dPolice Launched</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=106</link>
      <description>We've just launched the notion of content flagging.  You won't get flagged for having a particular opinion.  But you will get flagged for junk postings, hate postings (which we haven't seen), etc.  The conversation igniter can flag content but nothing happens until dPolice (dNeero's Content Police) check it out.  In grey areas we'll side with bloggers.  The goal is to increase the quality of the content created in the conversations.  Junk posters can no longer hide!  Let us know what your experience is.</description>
      <pubDate>Tue, 08 Jul 2008 14:13:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=106</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-07-08T14:13:00Z</dc:date>
    </item>
    <item>
      <title>Ability to Edit Answers</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=105</link>
      <description>By popular demand... drum roll please... the ability to edit answers!  When you're reviewing your conversations you now have an Edit button.  You know what to do.  Expect some breakage.  New functionality and all (and it's a pretty big feature, even if on the UI it seems small and obvious.)</description>
      <pubDate>Tue, 08 Jul 2008 14:12:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=105</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-07-08T14:12:00Z</dc:date>
    </item>
    <item>
      <title>Money in Research: Edgar Allen Poe and Game Theory</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=104</link>
      <description>Money's &lt;a href="http://www.sciencenews.org/view/generic/id/33381/title/Math_Trek__The_tell-tale_anecdote"&gt;used in research&lt;/a&gt; all the time.  Most college psychology experiments are paid.  As long as the money doesn't introduce bias then the results remain valid.</description>
      <pubDate>Wed, 25 Jun 2008 18:31:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=104</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-06-25T18:31:00Z</dc:date>
    </item>
    <item>
      <title>Notification: New Release and Balance Lag Time</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=103</link>
      <description>Hi all.  We know, we know.  Some performance issues lately.  Just so many of you joining conversations and posting them to your blogs.  We love it, but to keep up with you we need to do some performance optimization.&lt;br&gt;&lt;br&gt;To that end, we're launching some new optimizations today.  Most is under the covers.  The performance issues were actually caused by background processes that were taking too long to execute.  For example, we calculate your balance and determine whether to pay you overnight.  That's compute-intensive (even though it seems simple).  It starts running around 3am and isn't ending until noon or so.  It used to complete in a couple minutes.&lt;br&gt;&lt;br&gt;So, we're optimizing it and other processes like it.  The tradeoff is that we have to do some of that processing at other times.  We think we've made some good compromises which will give you better site performance.&lt;br&gt;&lt;br&gt;Expect things to look a little wonky for a few days as we work through the changes.&lt;br&gt;&lt;br&gt;Also expect that your balance may not be reflected properly on screen.  Be assured, your balance is in no way affected.  The base tables are all there and your balance is preserved.  What we're doing is storing a calculated/cached balance in a new table for performance.  (We never use the new balance for actual financial calculations, of course... we look to the base tables.)  It'll take a few hours for the system to populate the new tables with your current balance information.  Until that happens you'll see invalid numbers as your balance.&lt;br&gt;&lt;br&gt;Let it ride a couple days.  If it's still wonky please contact us.&lt;br&gt;&lt;br&gt;Apologies for the inconvenience (the performance issues lately and the balance update time period).  We're working hard to keep up with you!&lt;br&gt;&lt;br&gt;We'll probably launch the new code around 11:00am today.&lt;br&gt;&lt;br&gt;Update: The code has been launched and now the balance updates are being calculated.  We appreciate the patience.&lt;br&gt;&lt;br&gt;Update: Joy.  Looks like the new balance stuff triggered some conversations to close for a while.  We'll get 'em going again.&lt;br&gt;&lt;br&gt;Update: Balances should all be back to normal.  Apologies for the inconvenience.  Let us know if you see anything funky.</description>
      <pubDate>Thu, 15 May 2008 10:01:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=103</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-05-15T10:01:00Z</dc:date>
    </item>
    <item>
      <title>Article for Talentzoo.com: N-way Engagement Marketing</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=102</link>
      <description>dNeero CEO Joe Reger, Jr.'s &lt;a href="http://www.talentzoo.com/website/columns/columncontent.aspx?Id=2172"&gt;latest article&lt;/a&gt; for talentzoo.com is up.</description>
      <pubDate>Tue, 13 May 2008 15:30:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=102</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-05-13T15:30:00Z</dc:date>
    </item>
    <item>
      <title>Rankings Capability for Conversation Igniters</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=101</link>
      <description>We recently launched a new capability for those who ignite conversations.  It's called Rankings.&lt;br&gt;&lt;br&gt;What are Rankings?  Rankings allow you to choose certain questions as indicators of a quality that you want to track. For example, you could create an "Environmentally Friendly" Ranking and when people answer the question "Do you care about the environment?" with a "Yes" you assign them 50 points.&lt;br&gt;&lt;br&gt;Identify Users Across Many Conversations: You can use Rankings to measure across many conversations. A conversation here generates a few points... a conversation there a few. In this way you get a sense of how a person responds over time to many different things. You're using your dialog to learn. And you're using the Ranking to quantify.&lt;br&gt;&lt;br&gt;Build Panels with Rankings: As people score points you can skim those in the top 10% of Ranking score and put them into a Panel which allows you to ignite conversations that only they can see and take. In this way you're not only targeting but engaging your audience.</description>
      <pubDate>Sat, 03 May 2008 19:33:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=101</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-05-03T19:33:00Z</dc:date>
    </item>
    <item>
      <title>Surveys are Now Conversations</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=100</link>
      <description>We just launched a big change.  We looked at what we were doing.  We listened to what our users were telling us.  We watched how our users engaged the technology.  We explored the effect that it had on their readers.&lt;br&gt;&lt;br&gt;The result was this.  We weren't surveying.  We were starting conversations.  What we previously called a survey was really a starting point.  The questions of the survey framed what people discussed.  And from there people ran with it.&lt;br&gt;&lt;br&gt;So we went with it.  From here forward we're in the conversation business.&lt;br&gt;&lt;br&gt;To make the switch more complete we've also added a new feature.  You'll notice it the next time you take a survey.  In order to complete the survey you'll need to provide your own question.  Then, anybody who comes to the survey from your blog or social network will need to answer that question in addition to the original ones.&lt;br&gt;&lt;br&gt;In essence, this expands the conversation, helping what we now call our Conversation Igniters find out what's really on your mind.&lt;br&gt;&lt;br&gt;We'll be publishing an article outlining some of the engagement marketing theory that backs this concept.  For now we just wanted to put up a quick note so that you don't get confused by the new terminology.&lt;br&gt;&lt;br&gt;Let us know what you think!</description>
      <pubDate>Sat, 03 May 2008 19:23:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=100</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-05-03T19:23:00Z</dc:date>
    </item>
    <item>
      <title>For Researchers: Filter Results Capability</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=99</link>
      <description>It?s about time we got back to building some cool stuff for dNeero Researchers and Marketers!  Today we launch a filtering capability that allows you to see survey results for a subset of your respondents.   To see it in action, go to one of the surveys you?ve already launched and click on Results from the For Researchers tab? the results section with your private financial info.  If you view Results from the public survey you won?t see the new capability.&lt;br&gt;&lt;br&gt;Click on Filter Results and you?ll be presented with a bunch of demographic fields.  Age, gender, etc.  Choose who you want to see and then click Show Results.  You can add a name to save your filter for future use.  Your filters will work across surveys.&lt;br&gt;&lt;br&gt;How?s this useful?  Let?s say you want to survey anybody in the blogosphere but want to compare results between Males aged 24-29 and Females aged 24-29.  All you need to do is create a filter for each group and compare the results. Using all of the possible combinations in the demographics fields you can really segment your data and see what?s happening.&lt;br&gt;&lt;br&gt;As always, this is a starting point.  We?d like to allow you to compare two (or more?) filter groups on the same page.  And we?d like to add some deeper querying based on survey responses? for example, show me how everybody who answered ?Yes? to this question responded.  We?ll get there.&lt;br&gt;&lt;br&gt;This change touched some fairly core elements of the system.  We?ve tested extensively internally.  That said, please let us know if anything seems goofy over the next few days.</description>
      <pubDate>Wed, 16 Apr 2008 20:14:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=99</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-04-16T20:14:00Z</dc:date>
    </item>
    <item>
      <title>TalentZoo Article Up</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=98</link>
      <description>Got &lt;a href="http://www.talentzoo.com/website/columns/columncontent.aspx?Id=2121"&gt;an article published on TalentZoo.com&lt;/a&gt;.  Many thanks to Colleen, Web Editor at TalentZoo.com.  I'll be doing a column every few weeks... assuming they continue to accept my writings.  They've got a bunch of great content for marketers and according to them: "Each installment of your column will be featured for one month on our homepage receiving more than 200,000 impressions and in our email newsletter to over 80,000 recipients."  Excellent.  I worked dNeero in there where it was relevant but wanted to make sure that I wrote something actually useful to folks.</description>
      <pubDate>Tue, 01 Apr 2008 03:37:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=98</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-04-01T03:37:00Z</dc:date>
    </item>
    <item>
      <title>Please Ignore the Blog Comments</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=97</link>
      <description>Somebody is abusing the social nature of the web.  He or she is posting lude comments to all of the dNeero Blog posts.  Note that they're not affecting any dNeero users' blogs... just our own blog... the blog you're reading now.  We'll likely have to shut down the comment system for a while to let things settle.  And to the person doing this, you should be ashamed.</description>
      <pubDate>Thu, 27 Mar 2008 14:22:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=97</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-03-27T14:22:00Z</dc:date>
    </item>
    <item>
      <title>Referral Money Display</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=96</link>
      <description>Found a bug in the referral system display.  Basically, when you refer people to dNeero your account is tied to theirs and when they get paid dNeero pays you a percentage of what they got paid.  It's important to note that we're not taking anything away from them.&lt;br&gt;&lt;br&gt;This has been going on for a long time but the visibility of those transactions hasn't been clear.  The small payments have been wrapped in to impression payments which are already rather small on many days for most bloggers/facebookers.&lt;br&gt;&lt;br&gt;The net effect is that you didn't have visibility of your referral earnings.  Having identified the issue we believe that you'll have visibility moving forward but please check us on this.  Wait a few daily pay cycles and check your reseller earnings page.  You should also see reseller program entries in your balance screen.  Let us know what looks wonky.  Apologies for the lack of visibility!</description>
      <pubDate>Thu, 27 Mar 2008 13:43:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=96</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-03-27T13:43:00Z</dc:date>
    </item>
    <item>
      <title>More on the Facebook Performance Issue</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=95</link>
      <description>A couple weeks ago we started getting performance issue reports from Facebook users (thanks peeps!).  So we dug in and scratched our heads.  No obvious error messages or memory constraints.&lt;br&gt;&lt;br&gt;A few days ago we installed a performance metric capability with page-level resolution.  We expected that it'd tell us which pages were slow so that we could focus on optimizing them.&lt;br&gt;&lt;br&gt;Bewilderingly, the page that people complain most about was being output by the system at a brisk sub-second clip.  Odd, we thought.  Facebook says that our servers need to respond to theirs in 8 seconds.  Less than one second certainly fulfills their requirements by a long shot.  &lt;br&gt;&lt;br&gt;But the reports continued.&lt;br&gt;&lt;br&gt;Here's what we think is happening.  Facebook has to process pages before passing them on to Facebook users.  This takes them a lot of time on bigger pages.  Pages with a lot of html.&lt;br&gt;&lt;br&gt;Once you understand this the fix is relatively simple.  We took a long list of stuff and added paging capability to break it up into smaller chunks.  Early reports are that it's working and people can get back to that page they were having trouble with.&lt;br&gt;&lt;br&gt;This is part of the fun of writing an app that runs with/on another company's platform.  We're very dependent (i.e. at the mercy of) on Facebook's servers.  I don't believe they've documented the exact page requirements in a way that accurately reflects what our users are experiencing.  I could be wrong.  I'll peruse the app developer message boards a bit.&lt;br&gt;&lt;br&gt;The worst thing we heard is that we lost a couple users over this issue.  We can't blame them.  But hate to hear it.  Sorry peeps!  We'll continue to improve.  Let us know where we're dropping the ball (as you usually do) and we'll keep juggling!</description>
      <pubDate>Thu, 13 Mar 2008 21:12:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=95</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-03-13T21:12:00Z</dc:date>
    </item>
    <item>
      <title>Page Load Times Published</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=94</link>
      <description>Page load times are critical for a web application.  As a site scales you invariably find performance issues.  We've solved many in the past and will solve many in the future.  As you progress along this journey you find that you need increasing levels of resolution when it comes to your performance data.  &lt;br&gt;&lt;br&gt;To that end, we decided to add page-level performance metrics to the system.  These metrics tell us on an hourly basis what the average page load time is for each page on the site.  We've got tons of other metrics in place too, but most are server-based... memory, cpu load, etc.&lt;br&gt;&lt;br&gt;Once we had this thing built we looked at it and said "you know, users may want to see this."  So we made it available!&lt;br&gt;&lt;br&gt;For many months now we've had a number on the bottom right of each page we display.  That number tells you how long it took to load the page you're looking at.  You'll notice that it's now a link.  Click it and you'll be taken to a list of all pages and average page load times.&lt;br&gt;&lt;br&gt;Enjoy.  Clearly we'll be using this to find trouble pages and optimize them.</description>
      <pubDate>Tue, 11 Mar 2008 16:37:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=94</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-03-11T16:37:00Z</dc:date>
    </item>
    <item>
      <title>Marketers Interested in Incorporating Social Media into Campaigns</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=93</link>
      <description>"Social computing/word-of-mouth marketing tops the list with 67 percent interested in incorporating it into their campaigns. The findings resonate across all marketing, not just direct marketing."  More &lt;a href='http://clickz.com/showPage.html?page=3628659'&gt;here&lt;/a&gt;.</description>
      <pubDate>Sat, 08 Mar 2008 21:33:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=93</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-03-08T21:33:00Z</dc:date>
    </item>
    <item>
      <title>Pageload Optimizing and Improvement</title>
      <link>http://www.dneero.com/blogpost.jsp?blogpostid=92</link>
      <description>We continue to get reports of slow Facebook page loads.  Thanks Kymm.  Thanks Paul.  Thanks Ingasol.  You are appreciated and we do apologize for the slowness.&lt;br&gt;&lt;br&gt;As we mentioned in the last blog post, we're experiencing increased load on the servers.  This helps everybody.  With more users we can sooner attract top-tier companies to pay for campaigns.  And with that we can get funding so that we can afford the shiny new servers to keep things zipping along.&lt;br&gt;&lt;br&gt;The main point we'd like to make is that we're just as, if not more, concerned about it as you are.&lt;br&gt;&lt;br&gt;We've been optimizing things behind the scenes for the last few days.  To do this we change some code, launch it and then quantify the improvement.  Doing this has the unhappy side-effect of forcing us to restart the app servers each time we launch new code.  It generally makes for 50sec - 2min of downtime, depending on which server the load balancer sends your browser to.  Some of the slowness you've seen lately has been us trying to make things faster... I know, ironic.&lt;br&gt;&lt;br&gt;Today we stripped out some functionality from the Facebook main page.  There's a lot of stuff that we were doing with your friends and surveys.  Who took what?  Invite friends.  Etc.  Most of you told us that you ignored that stuff.  So we took it out.  Hopefully this will speed up the page loads a bit.&lt;br&gt;&lt;br&gt;We're going to look into other key parts of the system to see what we can remove/optimize.  As always, we'll try to keep you up to speed with the blog here.&lt;br&gt;&lt;br&gt;Thanks for your participation.  We'll get the speed back.</description>
      <pubDate>Fri, 07 Mar 2008 16:13:00 GMT</pubDate>
      <guid>http://www.dneero.com/blogpost.jsp?blogpostid=92</guid>
      <dc:creator>Joe Reger, Jr.</dc:creator>
      <dc:date>2008-03-07T16:13:00Z</dc:date>
    </item>
  </channel>
</rss>

