Is there embedding anymore and where are privacy settings?
JENNIFER JUN 02, 2012 09:00AM PDT
Will the new site allow and embed-code to share playlist on blogs and/or websites since the old-site codes are now useless? And, will you be adding privacy features so that we don't have to share our personal info with the world?
JUN 02, 2012 10:37AM PDT
Starting June 1st, music playback on the embedded (off-site) music widgets may be restricted. It's a tough decision we had to make and we apologize for any inconvenience.
=============================...
It looks like playlist.com completely ditched Flash. That makes it more mobile-friendly, but not very useful for embedded uses -- like a profile page.
Although I generally despise Flash, it was useful in the context of an embedded music player. The old embedded player had no ads and therefore produced no revenue. Even so, I find it hard to believe that their best option was to abandon the market. Generally, when a website exhibits "enhancements" like this, Grim Reaper 404 is just around the corner.
The smart move would have been to craft an HTML5-compatible embedded player with a certain minimum size and include banner ads. What playlist.com did was really dumb. Gotta wonder if there are enough technical people on their payroll to do the job right.
Is there embedding anymore and where are privacy settings?
JENNIFER JUN 02, 2012 09:00AM PDT
Will the new site allow and embed-code to share playlist on blogs and/or websites since the old-site codes are now useless? And, will you be adding privacy features so that we don't have to share our personal info with the world?
JUN 02, 2012 10:37AM PDT
Starting June 1st, music playback on the embedded (off-site) music widgets may be restricted. It's a tough decision we had to make and we apologize for any inconvenience.
=============================...
It looks like playlist.com completely ditched Flash. That makes it more mobile-friendly, but not very useful for embedded uses -- like a profile page.
Although I generally despise Flash, it was useful in the context of an embedded music player. The old embedded player had no ads and therefore produced no revenue. Even so, I find it hard to believe that their best option was to abandon the market. Generally, when a website exhibits "enhancements" like this, Grim Reaper 404 is just around the corner.
The smart move would have been to craft an HTML5-compatible embedded player with a certain minimum size and include banner ads. What playlist.com did was really dumb. Gotta wonder if there are enough technical people on their payroll to do the job right.
there was some question here on sh about it