Re:MusicKit JS
by kitsunesoba on Saturday February 22, 2020 @03:51PM
(#22393242)
Props to Apple for releasing this. The way Spotify has handled the deprecation of libspotify without a proper replacement and removing streaming/playback from their other SDKs has been extremely disappointing.
libspotify and the old iOS Spotify SDK used to provide the ability to stream and play songs in your app, without having to play through a Spotify device or backgrounded Spotify app. This was particularly great in the case of libspotify because it was written in C, making it easy to bind to whichever language you preferred. It was complete enough to write an entire alternative client with.
It looks like this web playback SDK works by creating a local Spotify Connect device to play to, which I guess would technically work, but it’d be much nicer if it just directly played songs as libspotify did and now MusicKit JS does.
Re:MusicKit JS
by DelightOne on Sunday February 23, 2020 @11:17AM
(#22397594)
Hmm that sounds indeed much better! Sadly not C, but cross-platform JavaScript is still nice to have.
Is it possible to embed this in native apps with an embedded browser? Hmm sounds complicated, or is there a different way to integrate this (using the apis the library uses).
Embedding just the web player in native apps would be a pain due to communication between the native and web layer. If you just did the whole thing in JS (electron, etc) you’re barely any better off than the official client in terms of resource consumption, defeating much of the point of building an alternative client.
There are reverse engineered libraries available (mainly librespot[1]) but they come with the caveat of violating the EULA and risking the accounts used with it. AFAIK Spotify hasn’t banned anybody for using it yet, but it’s always a possibility.
Re:MusicKit JS
by jamsinclair on Saturday February 22, 2020 @07:25PM
(#22394273)
A 99 USD commercial web API. This one, and their other endpoints, require being part of paid Apple Developer program. I understand, but it's frustrating if you're wanting to play around or use in free open source.
Re:MusicKit JS
by cptskippy on Saturday February 22, 2020 @11:00PM
(#22395039)
Once upon a time businesses had to submit paper work verifying their business to a registrar to get an SSL cert. It wasn't just about encryption but also identity.
I remember as late as 2004 trying to scrounge up copies of our business license to fax or mail into our registrar.
Today the SSL cert has lost it's identity aspect and is just a sign of secure communication, not trusted.
Re:MusicKit JS
by duskwuff on Sunday February 23, 2020 @12:01AM
(#22395240)
> Once upon a time businesses had to submit paper work verifying their business to a registrar to get an SSL cert. It wasn't just about encryption but also identity.
And those policies made it impossible for personal and hobbyist sites to use secure communications, while doing very little to actually prevent abuse. (Most of the apparent "success" of these policies was simply because the motivations for abuse were lower at the time.)
Re:MusicKit JS
by cptskippy on Sunday February 23, 2020 @05:12PM
(#22399906)
Originally SSL required identity verification and financial costs were very high.
Fraudulent SSL certs weren't a thing because the barrier to entry way so high and the rewards for spoofing a site were low since e-commerce was insignificant.
Re:MusicKit JS
by duskwuff on Saturday February 22, 2020 @10:43PM
(#22394969)
One real-world use case is on Genius.com, where it can be used to play songs (or previews, for users without Apple Music) while reading an analysis of their lyrics.
Re:MusicKit JS
by parhamn on Saturday February 22, 2020 @05:15PM
(#22393696)
I've always wondered why Netflix and all don't have clip widgets that you can link/embed on other sites. It is essentially free mass embedded paywalls.
Re:MusicKit JS
by GuiA on Saturday February 22, 2020 @05:44PM
(#22393848)
I can see the short term benefit, but inevitably some big content distributor would want to opt out on condition of providing their content to Netflix due to some disadvantage they perceive with it. From there more and more content providers would want to opt out (“Disney does it, we should do it too because it makes us more like Disney”) and then the feature becomes useless and people who use it get mad.
Re:MusicKit JS
by crooked-v on Saturday February 22, 2020 @06:28PM
(#22394051)
If you have "Sync Library" turned on (the feature's gone through several renames by now), it will also let you play local mp3s that have been uploaded.
Re:MusicKit JS
by dawnerd on Saturday February 22, 2020 @03:29PM
(#22393139)
About time. Rdio has such an amazing embed api (I built the JS api for it at the time and a site that was really heavily used). Total shame when Apple bought and shut them down. Maybe I can bring that old site out from the dead. Hmm
https://developer.spotify.com/documentation/web-playback-sdk...
It looks like this web playback SDK works by creating a local Spotify Connect device to play to, which I guess would technically work, but it’d be much nicer if it just directly played songs as libspotify did and now MusicKit JS does.
Is it possible to embed this in native apps with an embedded browser? Hmm sounds complicated, or is there a different way to integrate this (using the apis the library uses).
There are reverse engineered libraries available (mainly librespot[1]) but they come with the caveat of violating the EULA and risking the accounts used with it. AFAIK Spotify hasn’t banned anybody for using it yet, but it’s always a possibility.
[1] https://github.com/librespot-org/librespot
Thanks for the tip!
But agreed, the documentation looks like it was written in 2014/2015.
https://developer.apple.com/documentation/musickitjs#3004817
It deincentivizes abuse not unlike how SSL originally worked before it became a farming operation.
I remember as late as 2004 trying to scrounge up copies of our business license to fax or mail into our registrar.
Today the SSL cert has lost it's identity aspect and is just a sign of secure communication, not trusted.
And those policies made it impossible for personal and hobbyist sites to use secure communications, while doing very little to actually prevent abuse. (Most of the apparent "success" of these policies was simply because the motivations for abuse were lower at the time.)
Ease of SSL certs provides significantly better protection from threats between you and legitimate sites than potential illigitimate sites.
Fraudulent SSL certs weren't a thing because the barrier to entry way so high and the rewards for spoofing a site were low since e-commerce was insignificant.
What's the use for this? ( in a mainstream product way, not in some cool personal private project way)
But still, I miss rdio.
https://www.cultofmac.com/211126/the-inside-story-of-how-app...