As the first of my interviews from PDC, I noticed that Loic Le Muer was quick to familiarize himself with me as a part of the interview. This fact coupled with his persistent praise for the Seesmic devs who worked on Seesmic for Windows have led me to believe that Seesmic might actually be one of the better small software companies in existence.

Loic demonstrated Seesmic for Windows at PDC 2009 during Tuesday’s keynote. The obvious difference between Seesmic for Windows and Seesmic Desktop (the AIR version) is that the Windows client is native and written on top of the .net CLR. The plus sides to this include far better performance figures, a more Windows-integrated UI, and a lower tendency to leak handles (and fill my ram). The only downside to this is that it’s Windows-only… well, until you realize that moving .net code from a Windows native environment to Silverlight is actually not nearly as bad as writing another app from scratch.

My interview with Loic takes a browse through Seesmic for Windows v. Seesmic Desktop. I also decided to run through Silverlight Seesmic with Loic during our quick block of time, and while the Silverlight version still requires some polish before going live, the Windows preview version is solid enough for everyone to take a look.

Both parts of the interview can be found below the read link. Blame YouTube for forcing me to split a 13 minute video.
My thanks goes to Andrew Lyle from neowin for manning the camera.

For those of you visiting from AeroXperience, you guys are likely well aware of how AeroXperience was started. We began as a set of forums in March of 2004 dedicated to Windows Code Name Longhorn, which later became Windows Vista. We’ve prided ourselves with breaking news about some of the most coveted features in Vista during the Vista development process as well as with breaking the initial reports of the direction of Windows 7. AeroXperience has been one of the most accurate (and most opinionated, in some cases) sources of Windows coverage and news; amongst our bloggers, we’ve had the pleasure of having both Stephen Chapman and Rafael Rivera posting on behalf of AeroXperience during our run, and as I sit here next to them now in the PDC press room, I want to shift the attention to what winJade is and how we plan on rolling this out.

winJade is, in some senses, a new direction for us while allowing us to persist in our current mission of delivering relevant and informative Microsoft coverage. During this initial blog roll-out (planned for PDC), the purpose of the blog will still be to deliver the informative material and solid commentary on the world of Windows which you’ve come to expect. However, the purpose of the forums will shift from merely being a place to discuss Windows to becoming more of a home for novice Windows users, experienced users, and Windows experts to come together and not only talk about Windows and help each other but to also work on individual and group projects. winJade will be a home for people with ideas to implement those ideas, gather feedback, and gain an audience for the next great Windows program, tool, or concept. Stan and I have a few ideas we will be revealing on winJade when the time comes in addition to the innovative ideas which continue to find development time on the forums.

My utmost thanks go to Sam Johnson for implementing my vision for the new winJade blog, to Frank with Contrast Hosting for helping us in this transition, and to the many members on the forums who kept track of our progress and offered the many suggestions we’ve read.

From AeroXperience’s start as a home for discovery in Windows Longhorn to winJade’s mission for information and innovation, we’re looking forward to being your home not only for Microsoft news but for some of the most promising Windows-related projects.

We’ve tried to withhold ourselves from sourcing our news from leaky valves in Microsoft as of late (and you can see where that’s gotten us. ahem), but we don’t just stay away for the sake of keeping ourselves out of that eternally stressful race for content. We tend to stay out of it because behind every leak, someone’s job suffers as a result.

I had a very open interview with someone at the launch event. This person frequently deals with product leaks, and as a result, it’s fair to say that the person knows exactly how said leaks impact work, the lives of everyone connected to the project, the public perception of a product, and so forth. My interview with this particular Microsoft employee was fulfilling in the sense that I’m able to offer an uncensored glimpse into what Microsoft has to deal with whenever someone decides to leak a build, leak a screenshot, break an embargo, and what not.

Check the break to read about how it all went down. Keep in mind that there’s no video or audio and that this is, indeed, a long read apparently not as long as some people have seen in the past. Thanks is due to the anonymous commentators who pointed this out.

Anonymous Softie: So, with regards to leaks

Bryant: Yeah

Anonymous Softie: Leaks can affect the public perception of a product. For instance, there’s a reason why we only release specific builds. You know, because we want to release a certain level of quality that people can take a look at, have faith in, and [say] "okay, this is the product, the product is progressing as planned." Sometimes, interim builds, leaked builds, they often haven’t passed any of our quality checks. They were never meant to be released.

Bryant: Right. They can easily have nasty bugs.

Anonymous Softie: Yeah, exactly, and all of a sudden, you’ve got everyone in the world taking a look at this build; everyone wants to see the leaked build, right? ’cause it’s mysterious. It’s rare. It’s from the inside. So yeah, there could be bugs in it. People [find] bugs in it. They question functionality they find in it. And so when all of that happens, my phone starts ringing [with] people asking for comments. I’m not doing my day job at that point.

Anonymous Softie: And so, one, it’s a huge distraction on all of us. Phones ring off the hook. [People say] "I can’t believe there’s this shitty quality build out there!" It’s like, look, I’m not going to take time to talk to you, first of all, ’cause you, you know, that was an unplanned leak. It’s not representative of what we ultimately want to sanction and release.

Anonymous Softie: So, there’s the distraction, the bugs… if it’s really buggy, people might think that that’s the current state of the product when, in fact, it’s not. Internally, we’re already many many builds beyond the one that’s leaked. We don’t really care about that one. It doesn’t exist.

Bryant: Right.

Anonymous Softie: –for all we care.

Bryant: Right. It never happened.

Anonymous Softie: It never happened! But everyone is quick to jump to an opinion about that particular moment in time. They often draw incorrect conclusions, "oh my gosh, the product is incomplete, it doesn’t have this, it doesn’t have that." So that’s one.

Anonymous Softie: And quite often we have features that come out over time, right? You don’t necessarily have all the features in [Windows 7 Milestone 3], for instance. We didn’t have any [of the new] UI.

Bryant: Right. Well when we posted [the article about Milestone 3], that was it. It was just very bare and everything was hidden by a bunch of switches. I remember when we originally posted the very suggestive "we know what’s coming but we don’t actually… know" article, we got a lot of hits. We really killed your day job with that one.

Anonymous Softie: Yeah. So it’s a big distraction; it causes people to form incorrect opinions which I as a communications professional ultimately have to fix. Right? The world starts thinking "Wow, this is it?" and I go "Wait, wait wait"

Bryant: "Yeah, this was like a few months in the past. We’re much further ahead of this now, and there are different branches [besides the one with the leaked build], etc."

Anonymous Softie: Exactly. It’s a distraction for developers that are… you know, so we have an enormous [Independent Software Vendor] community that tests various milestones. They test their software. They test their drivers. They test their apps.. and for them it’s a distraction too because they’re wondering "wow, what’s going on? Should I look at this? Should I stop what I’m doing and look at this leaked build?" and so it tends to slow everything down.

Anonymous Softie: Those are the biggest issues that we have. And then so many people get sucked into potentially having to respond to all the questions that people are raising about that particular moment in time. We just don’t have time to deal with that, and so, generally, we don’t comment on unreleased builds.

Bryant: There you go.

Bryant:
I guess… how does it affect, I mean, you talked about how it affects you guys, what you guys do, but let’s say… how does it affect the actual development of a product itself? Or, on a similar line, how does it affect the timeline? Let’s say you’ve got a bunch of leaks setting things back.

Anonymous Softie: It generally doesn’t affect the timeline. The developers are always heads down; they’re writing code, they’re fixing bugs, but even they will stop and read the reviews of the leaked build. So there’s loss of progress there, potentially. And so, when you add it all up, it really does no one any good. ’cause even all the people that pause to download it– we also have the problem of viruses. People leak builds. They stuff them with payloads, and everyone wants the leaked build. They get a bunch of viruses, and now I have to deal with that problem. So, in some sense, it’s "dangerous" as well, and we have no control over what’s out there, what the quality is…

Anonymous Softie: but leaks generally don’t affect the schedule, but they affect the communication. They affect the perception They’re a distraction for all of the outside developers in the world that are trying to be focused on the right builds, and they might see something they didn’t expect, but when you catch us in between, all bets are off. We establish a contract with developers. We say "here are the APIs." It’s a contract between Microsoft and the developers. [We tell them] "we’re not going to change these APIs." and interim builds could actually have changes, maybe some things that we’re actually just testing out, prototyping. And so, you get some people on the outside that are, you know, wondering "Gosh. Did Microsoft– Did I not– Did I miss something? Did Microsoft not tell me what’s happened?" And so it’s pure theater.

Bryant: Right.

Anonymous Softie: People like to see it because it’s secret and nobody else can see it, but if you download some rogue binary from some site and you get infected, or you download something that, you know… people accuse that, even, of being Microsoft’s fault, and I’m generally the one that has to deal with… you know, whenever press call, my phone rings. I would rather spend my time preparing for that next big real milestone, making sure people have the most accurate information and keeping everyone on track instead of being distracted by all of these external issues.

Bryant: Now that was with regards to, um, actual build leaks. How about news leaks? Like, um, if somebody leaks a screenshot of something in progress– I figure that would possibly be the same ordeal. You know, news leaks, perception leaks [such as reviews], let’s say an embargo is broken about something. How about those? How does that work?

Anonymous Softie: Both a similar and a whole different set of issues as well. You know, we have a… I have a very professional relationship with all of the professional journalists that I work with. And so, it’s difficult. When I en masse pre-brief journalists and I say "okay, all of the information that I’m telling you under confidence–" professionals embargoed under this certain date. For the most part, people respect that. But then, somebody breaks the embargo, and then all the other journalists look around [and think] "well, they went! I gotta go!" And then it jeopardizes my relationship with other people ’cause suddenly everybody is going. At the end of the day, it often causes a lot of misinformation to be out there because people– I haven’t had a chance to talk to you, Bryant, yet, to let you know what’s our intent, What do we do and what is this about, why are we delivering this thing, who is it for, what’s it capable of doing. And so, if I don’t have that opportunity to kinda frame everything with everybody and put it in context, everybody starts speculating. "Maybe it means this. Maybe it means this. Maybe it means that.” Again, huge distractions. The people that need accurate information don’t have that accurate information any longer, and I spend weeks trying to sorta put things back in order so that everyone has the accurate Microsoft view of things instead of 30 different conspiratorial opinions on what may or may not be true.

Bryant: Yeah, of course. And, well I suppose for now that’s all I’m really looking for.

Anonymous Softie: Cool.

Whether this person’s account of how leaks affect things at Microsoft represents the Microsoft way of thinking is beyond me. I didn’t ask, but it’s safe to infer that this person isn’t the only person who thinks along these lines.

1. The day after 7: perspective… and Brad Brooks (October 23, 2009) (Update: video brightened)
2. The Windows 7 tweet-up in New York City, Winners, etc. (October 24, 2009)
3. The Effects of Leaks: A Candid Interview (October 25, 2009)
4. Unfortunately, the Windows 7 Keynote Interview with  Thorsten Ganz cannot be published due to technical issues.
   

That’s it. Keep an eye on us for PDC!

Thursday evening, I attended and taped the tweet-up which occurred in the Antarctica Bar. Other pressies besides @conhopper (me) who attended include @withinrafael, @thurrott (who organized the event), @tom_warren, @edbott, @maryjofoley, and @inafried. The event can be described in the following concise bullets:

• It was very packed.
• We gave a lot of stuff away. The (almost) complete list of items is in the video.
• A lot of people walked away happy regardless of whether or not they actually won anything.
• Antarctica may have had their best business in a while. You’re welcome, guys!
• A few Microsofties came and contributed to the giving away of items. My thanks in particular goes to Chris Flores, but others were also involved when it came to securing some of the prizes.
• Everyone was generally stunned at how awesome this whole thing was.

In all honesty, this is the first time I’ve seen the power of twitter when it comes to organizing group attendances like this. The enthusiasm here was fantastic, and I met some truly wonderful people as a result (and signed a Kindle. That thing better see some good use).

It didn’t even matter that this was a group of Windows enthusiasts. The discussions ranged anywhere from tech to politics to economics and even to women (I didn’t pay attention to what the women were talking about). One geek even managed to score a girl’s number, and to him I issue a hearty salute for successfully debunking the butt of all jokes in geekdom, at least in his own world.

Anyway, this video here is a tribute to everyone who came even though the people you’ll see here are people who won a giveaway item at the tweet-up. I recorded other video from inside the event, though the question of practicality (do you guys want to see it? What is there to see besides people talking and Ed&Paul giving things away?) still lingers.

The video can be caught after the break.

1. Microsoft is fully shifting focus to Windows 7. Windows Vista, of which the sheer length of the development cycle was inversely related to the level of approval and favor it garnered as time passed, has turned into something of an elephant in the room for Microsoft employees. Using the same metaphor and finding an excuse to quote an anonymous Microsoft employee I overheard yesterday afternoon, Windows 7 is the equivalent of a reputational wrecking ball designed for the sole purpose of “getting that elephant the f*** out”; it was the first Windows consumer OS born almost entirely from what the user wanted (read: what the average user hated about Vista). Now that it’s out and it starts replacing what was a good OS blighted by pre-SP1 bugs with what is a good OS right from the get-go, Microsoft has switched into what’s essentially a massive damage control mode.
2. Adoption rates and momentum are high, at least according to an analysis by Rob Enderle. Based on his analysis of a study done independently from Microsoft by Laura DiDio and Sunbelt Software, he believes that Windows 7 adoption rates are “unmatched since Windows 2000” adoption rates almost a decade ago. Consumer adoption rates are also up there, with PCMag using the line “Windows 7 More Popular Than Harry Potter” to carry their point. Given that Windows 7 beat Harry Potter on Potter’s home turf, I’m going with the notion that PCMag and Amazon UK are right.
3. Apple created more ads specifically for launch day. Yes, that depressing and uninspired ad campaign which Apple has continued for the last 4 years saw three new additions to the lineup. That’s three new ads released on the same day, which makes sense given the massive dearth of negative press against Windows 7. When a competitor simultaneously launches three attack ads specifically for your product launch, it’s a sign of desperation and a good enough reason for you to pull out your grill and refill that propane tank.

Hey, it wasn’t just me. The vast majority of Engadget’s commentators happen to agree.

Despite the recession and the subdued projections stemming as a result, it’s fair to say that all of the excitement is actually making jobs easier. Microsoft’s PR teams have an easier time when products don’t suck, and the press can move on to fuming at something more important, like the name of the next celebrity’s adopted baby.

The benefit to you? Better apps, higher developer morale, a solid OS, a higher willingness to publicly be a fan of Windows 7, and enough free time for a quick and awesome interview with a certain keynoting executive and perhaps the new face of Windows client by the name of Brad Brooks (Brandon LeBlanc would wisely and accurately like to remind me that there is no single face to Windows).

You can catch the video after the break. This interview happened near the end of our day, so the detailed questions were reserved for others who were around the event. You’ll see all (but one) of them over the coming week.

Download links coming in a bit.

In the wonderful world of Zune, all the Zune teamsters, Zune coders, Zune pushers, and Zune lovers are busy celebrating the launch of the Zune HD. That’s not to say there aren’t any snags with which to deal. Case in point: I came across this wonderful screen when I tried to sign into my account under Zune 4.0 for the first time:

“Great, there’s no terms to which I must agree. I’ll just go ahead and click Accept,” (the result of which you can see after the jump)

“Crap.”

I’ll chalk it up to quick thinking on behalf of Michael Gillet (@Gilly2468) for coming up with the bright idea of signing in online and accepting the terms there. If you’re one of the few people who, for whatever reason, aren’t able to sign into the Zune account for which you may have paid, try signing in via Zune.net and accepting the new terms there (you’ll see your account edit screen when you sign in, which is where you’ll do this). Once you’re done, you can sign back in via the Zune software and voila, life is good again.

On Tuesday, some no-good hackers decided to post a vulnerability, complete with a proof-of-concept Python script, that can remotely crash any Windows-based computer that has the SMB 2.0 network protocol enabled, which includes any system running Windows Vista or later. So like anybody with a bunch of free time would do, I cracked open a couple of VM’s and had some BSoD fun with Vista but noticed that 7 didn’t budge whenever I sent the exploit packets, so I suspected that they probably tested the RC version against this exploit

Well my gut feeling was right, and Microsoft released a security advisory later that day stating that it only affected Windows Vista and Server 2008, as well as the Windows 7 RC, but no mention of the 7 RTM (or Server 2008 R2). Plus, the scope was narrowed further when it was revealed that Public network locations were unaffected (they blocked incoming connections anyway). So nothing that bad to get riled over.

Of course, until a hotfix is released, if you’d like to completely protect yourself from the exploit you can follow the directions to either

• Block ports 139 and 445 from inbound connections using a firewall
• Disable the SMB2 driver
• Both (why not? unless you’re actively using file/printer sharing)

For the uninitiated,

FSF = Free Software Foundation

CC = Creative Commons

That out of the way, let’s get to the point: The Free Software Foundation’s latest ridiculous hit piece on Microsoft (after the break) not only uses a license considered a “cardinal sin” (as stated by Matt Asay) amongst free open source software proponents, they actually render their own licensing null and void by blanketing IP which they don’t actually own. Let’s take a look.

The important part, circled in mspaint-esque red, can be found at the bottom of the campaign’s page. Basically, their Creative Commons license requires attribution, denies derivative works (the “cardinal sin”), and, quite ironically, puts no limits on commercial reproduction. I’ve saved a copy of the page to commercially reprint for the sake of covering my PDC bills since they apparently don’t care, but that’s beside the point. The point is that they applied a Creative Commons license to the entire page, which of course spans all of the elements used within the page. This also spans the header image, which violates Microsoft’s trademark by reproducing the new Windows logo with the primary four colors intact, thereby qualifying as a gross breach of Microsoft’s trademark. Because the FSF did not receive permission to use the Windows logo and because they did not exempt the trademark from the license, they’re now left with a license which covers items in violation… which renders the Creative Commons license spanning their entire page (and every other page mentioning that license with that header) null and void. This, of course, also means that my derivative works are perfectly allowed. Score one for defense.

To summarize, not only did the Free Software Foundation violate their own principals, they hypocritically denied the right to create derivative works from the campaign page while creating a derivative work from Microsoft’s logo which is close enough to the original as to give grounds to Microsoft for a lawsuit. In addition, it begs the question of whether the funds they happen to have are truly being used to better the open source cause or if they’re just burning money in a campaign of FUD.

Microsoft, of course, likely won’t sue because giving the Free Software Foundation their own Streisand Effect would be a nightmare scenario.

All of the above is from my primitive understanding of IP law and licenses. I am not a lawyer, but I would love to be corrected by someone who is and hasn’t chosen a side in this mess.

Photopapered derivative of site content ©2009 Bryant Zadegan, all rights reserved. Original site ©2009 Free Software Foundation. No rights were reserved by the FSF, apparently, because they violated the license they were using to cover their stuff.