Sync stats with last.fm ?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Listen |
New
|
Wishlist
|
Unassigned |
Bug Description
Hello,
I don't know if it is technically feasible, but I realized that it was a shame, as a user point of view, to manage two different stats (esentially song played counters) sources when you use last.fm. I explain : you may lose your local database, because of a bug, hardware crash, etc... Moreover you may use an another music player on an another box, while you still submit songs on last.fm with it. Thus the local stats in listen are finally almost useless, as they are not really up-to-date, and don't really reflect your tastes.
I guess it would be not possible to always rely on the last.fm stats (what to do when you are disconnected, etc...?) So the idea would be to allow to sync the local stats with your last.fm stats, periodically or when the user requests it (may be prefereable as it should be a heavy task). However I'm not sure if last.fm allows to implement that. We can get almost all informations with the "overall tracks chart" page (ex : http://
Well, here is the overall idea. Doing this way, we will never be afraid to lose our stats (one year ago, I lost all my stats (almost 2 years !!) because of a bug with an another music player :(( ), and who knows, you might encourage people to switch to listen as they could keep their previous stats ! ;-)
This ticket was migrated from the old trac: re #707
Originally reported by: vlaaad
tags: | added: last.fm |
Changed in listen: | |
assignee: | Mehdi Abaakouk (sileht) → nobody |
default as a design pattern rather than trying to put it all together. That way you can never create offline or print docs of high quality without again having the devs or current admins maintain the comments and annotations. Hopefully a small Wiki quality team will evolve (i am against ops or admins) to review and summarize the contributions. I hope this gives us more users as contributors than having the docs focused on the devs. Cheers, duns [http:// www.about- china.net. cn/wrought- iron/cat_ 4.html china tour] [http:// www.about- china.net. cn/wrought- iron/cat_ 3.html Apparel] [http:// www.about- china.net. cn/wrought- iron/cat_ 5.html shoes] [http:// www.about- china.net. cn/wrought- iron/cat_ 12.html bags] [http:// www.about- china.net. cn/wrought- iron/cat_ 6.html Kitchen] [http:// www.about- china.net. cn/wrought- iron/cat_ 7.html Food and Wine] [http:// www.about- china.net. cn/wrought- iron/cat_ 8.html Furniture)] [http:// www.about- china.net. cn/wrought- iron/cat_ 9.html Flowers and Gifts] [http:// www.about- china.net. cn/wrought- iron/cat_ 10.html Wall Art] [http:// www.about- china.net. cn/wrought- iron/cat_ 11.html Computer Components] I still prefer a wiki like approach since the php (or mysql) docs are very cluttered when you have to take their comments in account. On the other hand they are professionally maintained imho, since they are *much* better than KDE documentation. KDE is by far larger and has so many different apps, which need screenshots and end user not dev/api docs, that more help is needed as long as the devs prefer to code than to write nice docs. And it is their choice to some degree imo. Technically interested but non-dev end users, which are plenty out there, are the users of and the best contributers to the docs
Originally reported by: add