Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Handhelds Microsoft News

Microsoft Ousts IE Mobile Manager For Revealing Nokia Phone Details 158

suraj.sun writes with an article in CNet concerning the axing of a Microsoft employee for revealing a few too many details about the upcoming Nokia Windows Phone. From the article: "...Joe Marini, who worked as a Seattle-based principal program manager on the Windows Phone team, tweeted: 'I just got a chance to try out one of the slickest looking #Nokia phones I have ever seen. Soon, you will too!' The tweet contained a Windows Phone 7 hashtag, #WP7. Marini sent subsequent tweets about the device, including one that rated it an '8' and another that said 'the camera was good, but I didn't have optimal lighting.' ... Marini stepped down after being informed that he would be let go for violating Microsoft's social-media and blogging policy (PDF). "
This discussion has been archived. No new comments can be posted.

Microsoft Ousts IE Mobile Manager For Revealing Nokia Phone Details

Comments Filter:
  • by Trepidity ( 597 ) <> on Wednesday September 21, 2011 @09:44AM (#37467522)

    It's not even particularly new for companies to be super paranoid about "leaks", and to interpret what constitutes a leak very broadly. Apple is probably more paranoid, for example, and Apple employees tend to just avoid Tweeting anything Apple-related for that reason.

    I do agree that this was stupid, unless there's something more to the story; it doesn't appear that he actually leaked anything that could plausibly be considered secret, and certainly not any interesting secrets.

    I also like the now-self-referential part of the policy that recommends employees think, before they take an action online:

    How would it look on Slashdot or on the front page of the New York Times?

  • Re:Shame (Score:2, Informative)

    by Anonymous Coward on Wednesday September 21, 2011 @09:50AM (#37467636)

    Unfortunately CyanogenMod is all but dead since Samsung bought out the primary developer. Yeah I know all about the "state of cyanogen" blog post but the fact is, the ROM has had very little progress in months and these types of situations rarely get better.

    It's dead unless someone forks it and takes over.

10.0 times 0.1 is hardly ever 1.0.