Stories
Slash Boxes
Comments

SoylentNews is people

Zune Music Service to Close

posted by martyb on Saturday October 31 2015, @10:53AM   Printer-friendly
from the Digital-Restrictions-Management dept.

An Anonymous Coward writes:

Microsoft has announced (non-Javascript version) (emphasis in original) that

As of November 15, 2015, Zune services will be retired. You will no longer be able to stream or download content to your device from the Zune music service. However, Zune devices will still function as music players and any MP3 content that you own on the Zune device will remain there. You'll also be able to transfer music to and from your Zune player.

Note Content that was purchased with DRM may not play if the license can't be renewed.

Existing Zune Music Pass subscriptions will be converted to Groove Music Pass subscriptions.

Analysis:

Original Submission

 
This discussion has been archived. No new comments can be posted.
Zune Music Service to Close | Log In/Create an Account | Top | 28 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 5, Insightful) by BsAtHome on Saturday October 31 2015, @12:01PM

    by BsAtHome (889) on Saturday October 31 2015, @12:01PM (#256862)

    This is only the beginning. There are so many devices and services that limit the access to the stuff you "thought" you bought. All the infrastructure that needs to be kept alive. The same goes for games.

    The outcry will only start once enough junkies feel betrayed by the pusher. That would probably be the best analogy, because the corporations have invested heavily in making all consumers into milking cows. Want your fix, just pay the fee.

    That what looks too easy to be true always is too easy to be true. A critical consumer wouldn't buy into the hype and rather refrained than to become hooked. I just guess that not many are that critical until it is too late.

    Starting Score:    1  point
    Moderation   +3  
       Insightful=2, Interesting=1, Total=3
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  
    Total Score:   5  

  • (Score: 5, Insightful) by stormreaver on Saturday October 31 2015, @12:57PM

    by stormreaver (5101) on Saturday October 31 2015, @12:57PM (#256873)

    I just guess that not many are that critical until it is too late.

    We're eventually going to see this with "Cloud" computing, too.

    • (Score: 5, Informative) by Anonymous Coward on Saturday October 31 2015, @02:34PM

      by Anonymous Coward on Saturday October 31 2015, @02:34PM (#256890)

      "I just guess that not many are that critical until it is too late."

      We're eventually going to see this with "Cloud" computing, too.

      And then when the Cloudpocalypse arrives, I'll sit back with my books on un-DRM'd paper, and my music on un-DRM'd vinyl / CD / mp3 / m4a, and laugh. Or, as happened last Friday night, I won't give a damn because I'm out doing something that doesn't involve "the cloud" at all. I don't really think there's going to be a "cloudpocalypse", but we'll see more and more of these little hitches caused by equipment failures, misconfigured systems, and incompetently executed datacenter buildouts (hell, Microsoft once triggered an outage on Outlook / Hotmail / Skydrive via a firmware update to an air conditioner [wired.com]; how's that for irony?)

      Anyway, we've already had a couple of huge Amazon outages in the past month and a half, particularly the one in September covered by The Register, complete with a picture of demonically laughing Jeff Bezos [theregister.co.uk], as well as the one last week journaled by DatacenterDynamics [datacenterdynamics.com].

      Systems Watch had a nice after last week's outage: [systemswatch.com]

      Typically your organization cannot afford to have 100% capacity redundancy sitting idle all the time, it becomes a money issue. So if you have your resources in two zones with a 50/50 split, and you lose one zone 50% of your resources cannot handle 100% of the load causing degradation of the organizations services. To remedy this whether through automation or manual intervention you spin up the lost 50% of resources in a different unaffected zone to meet your demand.

      This is where the problem often occurs when you can’t manage anything in AWS because their API’s are unavailable, you can’t spin up the lost 50% in an unaffected zone and are in big trouble and helpless. In a perfect world organizations are making so much money they have enough resources in one of the two zones to carry the entire load or better yet in multiple regions with mirrored capacity but most of the time this isn’t the case. This is often because management, not engineering, is willing to take the risk. So organizations feel that degradation is not a full outage and having 50% is better than 0% available resources. To the end user they are angry either way.