https://bugs.gpodder.org/show_bug.cgi?id=747
Thomas Perl <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|[email protected] |[email protected] --- Comment #10 from Thomas Perl <[email protected]> 2010-01-11 11:26:35 GMT --- (In reply to comment #9) > (In reply to comment #6) > > Added to the Wiki page. Implementation still missing. > > Are current versions of gPodder prepared to receive different (sanitized) URLs > when accessing /getlist next time? Do we need an exception when accessing URLs > through the Legacy API? As discussed on private IM, as soon as the next version of gPodder is released (+ some weeks to allow packages to flow into distributions), we will set the legacy API to report "@GOTOMYGPODDER" so that users of legacy clients are informed about this fact. > What about the Simple API? If the client application uses this API, it has to deal with this situations (ideally, the client app will display "added" and "removed" items, and the user can "match" the URLs - but that's really up to the application developer). -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
