• zalgotext@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    17 hours ago

    For the same reasons Lemmy is federated:

    1. Resilience - if one server goes down, only that one artist’s music becomes unavailable
    2. Control - if the artist owns the server, they can control it/moderate it as they see fit

    You can’t really count on either of those things if you’re putting your music up on Spotify, Tidal, etc.

    Edit: there would be nothing stopping several artists from handing together and hosting all their music from a single server/instance, if they wanted to. That’s the point though, there’s choice

    • boonhet@sopuli.xyz
      link
      fedilink
      arrow-up
      1
      ·
      13 hours ago

      Okay, so what I really meant was how federation the way it works here would be of any use. It’d actually make the artist lose all control, as everything gets mirrored.

      If we use the federation as nothing but a discovery mechanism for other nodes, I guess it would accomplish those goals. But then you could do it without the federation too. Have a central discovery server so that any apps immediately know where to connect, instead of the user having to choose (federation is confusing for normies, remember?)

      • zalgotext@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        12 hours ago

        Right, ActivityPub would really just be the discovery mechanism, obviously you wouldn’t want the actual music to be mirrored to other instances.

        If you use a centralized discovery server, you’re right back to where you are with Spotify - at the mercy of whoever controls the discovery server, and shit out of luck if the discovery server goes down. Federation is only confusing for normies because the clients for popular fediverse apps don’t do a good job of making that part clear (or hiding it away).