feed groups auto-deleting working feed urls

  • Resolved Atavisionary

    (@atavisionary)


    6 months ago

    Its not really that page, but that page uses the internal feed list thing feedzy sets up.

    I want to say one thing first, automatically removing feed urls, which are a pain to collect, is an absolutely stupid, annoying and dumb idea. At least create a log file somewhere so they don’t just get lost completely. Its even worse because I have been testing some of the ones that removed for not working and its absolute crap. Those sites are still up. The voxday feed even had a pulled link publicly visible immediately before I updated the list and feedzy automatically removed it! I can’t believe how absolutely terrible this is! In addition, unz blog page feeds are all being removed automatically too.

    SHAME SHAME on you for thinking an occasional non-response or whatever means the feed is completely gone. I don’t need feedzy deciding to remove feeds from my list. Especially when it is provably wrong about it. I will decide that. Remove that bs “feature” immediately please. Or put it in a setting which starts as opt-out.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Atavisionary

    (@atavisionary)

    6 months ago

    We found the following invalid or unreachable by WordPress SimplePie URLs that we have removed from the list: https://voxday.net/feed/http://www.unz.com/xfeed/rss/author/audacious-epigone/http://www.unz.com/xfeed/rss/author/anatoly-karlin/http://www.unz.com/xfeed/rss/author/john-derbyshire/http://www.unz.com/xfeed/rss/author/james-thompson/https://www.unz.com/xfeed/rss/author/steve-sailer/

    that is the error message. I managed to get a save which didn’t remove anything other than the unz review blogs from the feed group, and since most of these haven’t been updated in a while I won’t fuss about getting these back in immediately. But this is really not acceptable WordPress simplePie errors are not a reliable way to determine if a feed is actually gone or broken and should not be used to massively alter a users feed group without even asking them first. And not even saving the feed urls in a log file for the user to go and confirm later. This is an absolutely terrible terrible “feature” and clearly wasn’t tested well before being implemented.

    Thread Starter Atavisionary

    (@atavisionary)

    6 months ago

    I have been looking around the files at my webhost site to try to find the feed group file so I can edit that file without having to go through your absurd auto-remove feeds check and add what I want back in, but it is not immediately obvious what directory you are saving those feed groups in. Can you tell me the directory address so I can manually fix this?

    Plugin Support rodicaelena

    (@rodicaelena)

    6 months ago

    Hi,

    Thank you for reaching out and sharing your detailed feedback. We truly apologize for the frustration this has caused you.

    The feature you’re describing, automatically removing feeds flagged as “invalid or unreachable” is designed to maintain the performance and stability of the entire aggregation system. If the plugin wouldn’t remove these flagged feeds, a large number of broken or non-responsive URLs could:

    1. Massively slow down the overall feed update process.
    2. Cause timeouts or errors when fetching the rest of your feeds.

    While the feature’s intent is performance, your experience proves that there could possibly be some improvements, like a log file from where you could recover the removed feeds.

    I will be sharing your detailed feedback with our development team for review as a potential future improvement.

    Kind regards!

    Thread Starter Atavisionary

    (@atavisionary)

    6 months ago

    If you are going to remove feeds they should actually be down. Some sites go down for a week, but come back up. the feed shouldn’t be removed from the group. Sometimes its just 10 minutes, like with voxday’s site. It wasn’t down, it just couldn’t be fetched that particular moment. It was fine a few minutes later. None of the unz review blogs that are listed are down. They are correct even now. This “feature” doesn’t work correctly and is spitting back 100% false positives for me, and probably for a lot of people.

    I am not sure what the correct solution is here, but at least ask the user if they want those removed before doing so.

    Can you please ask them what the file path is for those group feed files are in cpanel? I could at least sort it out manually for myself if you can get that info. I can probably find it myself eventually, but it would save me time to just give me a file path.

    Plugin Support rodicaelena

    (@rodicaelena)

    4 months, 4 weeks ago

    Hi,

    Thank you for your detailed follow-up. I regret to say that at this time, I do not have a direct solution.

    However, please know that I have shared your feedback, including your specific examples of false positives and the suggestion for a log file or a user confirmation prompt, with our development team as a feature request/improvement for future versions.

    Thank you once again for your patience and for helping us make the plugin better.

    Kind regards,

    Plugin Support rodicaelena

    (@rodicaelena)

    4 months, 4 weeks ago

    Hi,

    You can also check to see if the removed feeds are listed in the current Logs section that we have in Feedzy https://vertis.d.pr/i/IcqlBu

    Kind regards!

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.