Bug 158763 - Akregator should be able to handle periodic podcasts
Summary: Akregator should be able to handle periodic podcasts
Status: REPORTED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-04 15:29 UTC by Christoph Bartoschek
Modified: 2023-08-27 16:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Bartoschek 2008-03-04 15:29:07 UTC 
Version:            (using KDE 3.5.9)
Installed from:    SuSE RPMs

Akregator is good at helping the user to retrieve periodical asynchronous text content. Lots of podcasts are also asynchronous and periodical, but they are not text. However they fit into the general use case of akregator: consuming periodical asynchronous content. 

Therefore I would like to see podcast support in akregator. In my opinion podcasts fit better into akregator than into amarok.
Comment 1 Per Ångström 2008-08-19 20:56:47 UTC 
Hear hear!
Comment 2 Arne Babenhauserheide 2009-06-22 10:10:55 UTC 
Couldn't both be integrated? Maybe Amarok could retrieve the list of podcasts from akregator. And Akregator could use an Amarok plasmoid for playing podcasts.
Comment 3 Justin Zobel 2021-03-09 04:11:32 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 4 luna 2023-08-27 16:13:29 UTC 
(In reply to Justin Zobel from comment #3)
> Thank you for the bug report.
> 
> As this report hasn't seen any changes in 5 years or more, we ask if you can
> please confirm that the issue still persists.
> 
> If this bug is no longer persisting or relevant please change the status to
> resolved.

This is still relevant.