https://bugs.kde.org/show_bug.cgi?id=344027
Harshit Garg <hg1...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hg1...@gmail.com
--- Comment #8 from Harshit Garg <hg1...@gmail.com> ---
(In reply to acidrums4 from comment #7)
> (In reply to jerryzh0524 from comment #6)
> > Is there any update on this feature?
>
> Alas as with all of this features on the wishlist, this won't be implemented
> until someone interested and with enough skills and knowledge can step up
> and take a look at it. But it's been 6+ years since it was reported, so...
>
> And this will be a complicated one, because it will mean not only dealing
> with the Feedly API and KDEPIM/Akonadi thingies, but setting the path so
> Akregator can have synchronization with other third-party services, and I
> guess it would mean a huge deal in how Akregator code is structured right
> now.
>
> In top of all of that, there's the fact that RSS popularity has decayed. One
> can hope that the incoming feature on Chrome about 'reviving' RSS can give
> it a second chance, but also it seems KDEPIM devs are focused on KMail, the
> new Kalendar thing and that stuff - maybe someone at some GSoC could take
> this one, or we can keep it upvoting this bug report and making noise about
> it so there's more chance of it to be discovered by someone who can do this.
I'd love to take this up (as a student, GSoC or not), if the current
architecture of Akregator makes it possible. I'm quite comfortable working in
C/C++, I love RSS and I love KDE; it's a shame I can't use an RSS reader with a
K in it (my rss server is miniflux).
I will fiddle around the code when I get the free time, although it'd
definitely help more if a developer could point me in the right direction
regarding this.
And I do believe that adding support for Google Reader API / Fever API would be
a better first step than specific services like feedly, because many
clients/servers implement Google Reader API.
--
You are receiving this mail because:
You are watching all bug changes.
