[d3ad]tags labelled 'rss' e
@barray on Tue Aug 03 22:21:31 UTC 2021 said:
&e@barray on Tue Aug 03 05:47:01 UTC 2021 said:
&e#akregator is now at *1.3GB* of #ram ... For all that RAM use it's not even that fast... Bare in mind that its only real job is to fetch an #xml #rss #feed - it doesn't even recover from #reboot very well either (feeds are forgotten). It's impressive that for what should be a simple program, it actually isn't. I'll keep an eye on it... I legitimately could do a better job than this.
#akregator is now at *1.6GB* - bare in mind this is just an #rss #feed #reader ! Either it is trying to store *all* content in #ram - or there is a #memoryleak ... I really suspect this is what caused my #laptop to #crash just the other day. I'll attempt to contact them on #irc - but not holding my breath.
@barray on Tue Aug 03 05:47:01 UTC 2021 said:
&e@barray on Mon Aug 02 21:57:00 UTC 2021 said:
&eI genuinely believe I could do a better job if I built an #rss #feed #reader myself. Do away with the #webengine - get everything out of #ram - build using the principles of #kiss ... It should be using 64MB of RAM, not over 1GB of RAM. Insanity.
#akregator is now at *1.3GB* of #ram ... For all that RAM use it's not even that fast... Bare in mind that its only real job is to fetch an #xml #rss #feed - it doesn't even recover from #reboot very well either (feeds are forgotten). It's impressive that for what should be a simple program, it actually isn't. I'll keep an eye on it... I legitimately could do a better job than this.
@barray on Mon Aug 02 21:57:00 UTC 2021 said:
&e@barray on Mon Aug 02 21:46:21 UTC 2021 said:
&e#akregator , the #rss #feed #reader I use is currently using 1.1GB of #ram after just a day... I suspect there might be a #memoryleak or some form of inefficiency here... Is it trying to load *all* of the content actively into RAM? According to this article, apparently it is quite crash prone: https://linuxreviews.org/Akregator Half the problem appears to be the use of the #qtwebengine - it essentially has a whole freaking web browser built in.
I genuinely believe I could do a better job if I built an #rss #feed #reader myself. Do away with the #webengine - get everything out of #ram - build using the principles of #kiss ... It should be using 64MB of RAM, not over 1GB of RAM. Insanity.
@barray on Mon Aug 02 21:46:21 UTC 2021 said:
&e#akregator , the #rss #feed #reader I use is currently using 1.1GB of #ram after just a day... I suspect there might be a #memoryleak or some form of inefficiency here... Is it trying to load *all* of the content actively into RAM? According to this article, apparently it is quite crash prone: https://linuxreviews.org/Akregator Half the problem appears to be the use of the #qtwebengine - it essentially has a whole freaking web browser built in.
@barray on Mon Jul 19 03:58:39 UTC 2021 said:
&eSo I have been using #akregator as an #rss #feed #reader for a few weeks now, and generally it is quite good. I do have a few problems with it though. 1. It doesn't support #arrowkeys in the lists, meaning you have to do a *lot* of clicking. 2. If it #crashes or is forced-closed for some reason, it doesn't remember what you have already read. 3. The search feature doesn't allow you to open up an associated feed easily. 4. The import feed should be able to just take a list of #feed #urls - #opml is wonky.
@barray on Wed Jul 14 09:23:44 UTC 2021 said:
&eInteresting, I may have found a way to find #youtube channels that have been #shadowbanned ... I believe that these channels cannot be fetched correctly via #rss if they have been #shadowbanned by #youtube ! Very interesting indeed, I will need to explore more!
@barray on Fri Jul 09 03:00:22 UTC 2021 said:
&eThis is a sad state of affairs, we're back to using #rss feeds to bypass #youtube and #netflix https://streambus.com/ #rss is definitely a viable way to go, but there seems to just be something missing - but it's not entirely clear exactly what that is.
@barray on Sun Jul 04 03:25:16 UTC 2021 said:
&eA half nice article about the benefits of #rss https://ncase.me/rss/ I would only add that the 'tips' section is overly harsh - excerpts can be completely necessary for small servers or servers in high demand. Feeds that update more than once a day can also be manually adjusted with a good reader.
@barray on Sun Jun 27 06:42:15 UTC 2021 said:
&e@barray on Sun Jun 27 06:17:42 UTC 2021 said:
&eFinally finished writing a custom piece of software to abstract the #rss from a corrupted #thunderbird #feed and rebuilding a #opml file that can then be important by another #rssreader - for which I have chosen #akregator for now. What a super pain in the arse that was...
It's really great to have #rss back now, much happier about it. Finally getting news updates again! Fingers crossed #akregator is much better than #thunderbird for #rss ! At least I already exported to #opml file encase I want to go somewhere else, it took an hour or so to rename all of the various #feeds ...
@barray on Sun Jun 27 06:17:42 UTC 2021 said:
&eFinally finished writing a custom piece of software to abstract the #rss from a corrupted #thunderbird #feed and rebuilding a #opml file that can then be important by another #rssreader - for which I have chosen #akregator for now. What a super pain in the arse that was...
@barray on Tue Jun 22 22:46:55 UTC 2021 said:
&e@barray on Tue Jun 22 22:12:26 UTC 2021 said:
&eNot sure why, but the #hackernews #rss feed seems broken for me now? Not getting any new #news articles...
Seems like *none* of my #rss feeds are working at all. No idea what the hell is going on here...
@barray on Tue Jun 22 22:12:26 UTC 2021 said:
&eNot sure why, but the #hackernews #rss feed seems broken for me now? Not getting any new #news articles...