• Dyskolos@lemmy.zip
    link
    fedilink
    English
    arrow-up
    49
    arrow-down
    8
    ·
    1 day ago

    No thanks. I had like 20 sonos speaker, and then, one day, sonos decided to fuck the app up, making it impossible to use my library anymore. This was the day I sold them all, ranted like a pissed off babuskha and never thought of buying similar products ever but make my own.

    Real open source or go fork yourself in the eye. I’m so done with this corpo-crapshit

    • BeyondRuby@lemmy.world
      link
      fedilink
      English
      arrow-up
      42
      arrow-down
      8
      ·
      1 day ago

      You sound like an extremist brother. If they lie and dont do it (seems like they already have made it open-source) then get mad. But it sounds like you are upset because you got screwed by Sonos and Bose actually are attempting to do the right thing for their customers.

      • Dyskolos@lemmy.zip
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        10 hours ago

        Extremist? Nah, I’m just old enough to have been fooled and fucked way too often by the enshittification, so that I have serious trust issues with corpo promises now.

        I try to stay away from big tech crap as far as I can. If there’s no open source alternative, I make my own (if complexity allows) or just don’t use it at all.

        And I’m not upset at Bose. Great if they really deliver. I just doubt they will. And if they do, it would be the one shiny example that stands out. But it would make Bose a bit more attractive to me then. At least the older ones.

        Besides, other comments say they just release the API, not made it real open source. Dunno what is true and also don’t care. Yet it would be a substantial difference.

      • NovaThePup@piefed.blahaj.zone
        link
        fedilink
        English
        arrow-up
        35
        arrow-down
        1
        ·
        1 day ago

        Thing is they didn’t actually open-source it, as stated in other comments. They just released the api documentation. While, yes, it is a step in the correct direction, it is definitely not open-source. Open source would be releasing the source code for all the software involved, which they haven’t done.

        • AA5B@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          1
          ·
          edit-2
          20 hours ago

          I wasn’t affected by the Sonos App fiasco because I don’t use it. I mostly use the speakers through Spotify, and occasionally through Home Assistant. I only need the app to set my wake schedule but once it was done, I didn’t need to go back.

          Won’t this allow the same? With the API, you should be able to continue using your speakers with local automation, assuming someone wants to implement that.

    • phx@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      20 hours ago

      That kinda sucks, especially since even the older ones work with Home Assistant etc directly now

      • Dyskolos@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 hours ago

        I was on iobroker at that time and HA still wore diapers 😁 So today it Wouldn’t be as bad, but at that time they were just effectively rendered dumb cubes to us.