gpodder.net Amarok Integration - Design Issues

[Stefan Derkits]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey,

as Amarok 2.5 Release (and with it hopefully the gpodder.net
Integration) is soon, we need to fix the Service.

As discussed with Stefan Kögl & Thomas Perl, I forward this discussion
also to the gpodder Mailinglist (and hope that maybe some people who
use gpodder want to help a little bit with testing).

Known problems atm:
- -) Episode Actions are sent every 30 seconds always including the last
position (and also not sent for skipped parts)
- -) Episode Actions are not correctly sent if a podcast includes a
"last stop postion" mark but user starts to play from position 0
- -) Annoying popup related to KIO (wrapper around QNetworkAccessManager)

This Popup is related to the isPossibleSpoofingAttack Method in
https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/entry/kioslave/http/http.cpp
& libmygpo-qt setting the data for http basic auth in the url.

@thp: Could you maybe explain how you handle the Episode Actions in
the gpodder App? This could maybe be a good way also for amarok.

@skoegl: Any chance to implement some other Auth Mechanism than basic
auth (I know there is the auth api, but that too needs basic auth) in
gpodder.net really soon?

Stefan

On 10/18/2011 11:30 AM, Stefan Derkits wrote:
> Hello,
> 
>>> we can do this way, but I think it isn't efficient. We only
>>> want to know where we stopped, so there is no need to make more
>>> than one episode action. Unless something like play history is
>>> a to-do for Amarok (Bart should know ^^).
> 
>> It is, we already keep playback position markers automatically to
>>  start playing where amarok stopped before. Full history is not 
>> really required, unless it is used for chaptering of podcast 
>> episodes. This could enhance the podcast listening experience on 
>> Amarok.
> 
> so probably at first we don't want to send Playlist Actions also
> for skips (I will explain in a few Minutes what this could be good
> for).
> 
> Still we need to change the existing implementation. Without
> sending skips and only wanting to know where we stopped, only 1
> EpisodeAction for Play should be uploaded to the Server (and not
> one every Minute or half Minute). This Episode Action should
> probably be sent when the user clicks pause or stop and doesn't
> resume listening in e.g. 1 minute.
> 
> Of course we know the gpodder.net service can be unreliable from
> time to time, but I also think the case where a user stops
> listening a Podcast, shuts down Amarok & his computer (and
> gpodder.net didn't work and the episode action couldn't be sent in
> time) and then wants to continue listening the Podcast on his
> mobile is not soo common.
> 
> Why it makes sense to upload (and it isn't that inefficient,
> keeping some data structures in memory and uploading them as a
> bunch if nothing [related to this episode or podcast in general]
> happened for 1 Minute doesn't "cost" much more then uploading a
> single action) also skips?
> 
> Atm this Data is only used (and visible) internally in gpodder.net
> for Podcast Producers. But Bart made a good point,
> (crowd-sourcing) chaptering of podcast episodes would be a cool
> feature for gpodder.net.
> 
> Stefan _______________________________________________ Amarok-devel
> mailing list Amarok-devel at kde.org 
> https://mail.kde.org/mailman/listinfo/amarok-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk6v+FYACgkQlZvAMV/NgGI7owCfXbSEBA+Wuubl4vAGLh5H7Jwg
Z4AAn1IicNHk/JWcfZmJ3kTkGKT9+MsC
=ne/2
-----END PGP SIGNATURE-----