Show HN: Tired of the non-portability of my playlists, I wrote my own format
universalplaylist.stavros.io
Show HN: Tired of the non-portability of my playlists, I wrote my own format
1–10 of 104 posts
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#2My own format = https://xkcd.com/927/
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#3I'd love something like this, but I don't see any upside for iTunes or Spotify to support it. Anything that makes it easier for a customer to switch to a competitor is something they're going to resist.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#4This looks interesting. Do you have any plans to create converters to convert to UPL from other formats?
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#5why does the example have md5 and sha1?
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#6I'd love something like this, but I don't see any upside for iTunes or Spotify to support it. Anything that makes it easier for a customer to switch to a competitor is something they're going to resist.
Ha that reminds me to cancel my Spotify, thank you!
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#7What's wrong with xspf? Couldn't you just extend that with more attributes (which legacy apps could ignore)?
https://en.m.wikipedia.org/wiki/XML_Shareable_Playlist_Forma...
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#8My own format = https://xkcd.com/927/
oh man... 10 minutes late!
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#9Are relative paths supported?
Probably in this day and age it would have better chance at adoption if it would be a JSON file. It's just network effects.
Re: Show HN: Tired of the non-portability of my playlists, I wrote my own format
#10What's wrong with xspf? Couldn't you just extend that with more attributes (which legacy apps could ignore)? https://en.m.wikipedia.org/wiki/XML_Shareable_Playlist_Forma...
Nothing's wrong per se (and it has roughly the same goals as mine), it's just that it's pretty much the XML equivalent of M3U, and doesn't have any provisions for stronger identification (it relies on titles), at least as far as I know.
I would really like the MBID to be the main way of identifying songs throughout the industry, and possibly the AcoustID fingerprint, as that's more specific. I think it would be fantastic if each song had its own UUID that computers could refer to, and this spec tries to incorporate that.
Since I don't really gain anything from reusing its format (most players won't support the strong IDs), I thought I might as well create a new format that was better suited to this task.