RussPA wrote:At some point after about 10 or so feed refills, it stops and I get about 40 of these in the console: Failed to load resource: the server responded with a status of 429 () /Descartes/app/Feed/Issues/UPDATE_REQUEST/8720282:1

Or this: DELETE https://www.waze.com/Descartes/app/Feed ... ST/8719096 429 app-75b9047afacbd6b7b171.js:1
If I click Clear Feed, it continues. Once I got 999 cleared, clicked the button again and got 161 cleared, the got 253 cleared. Feed seems to refill as fast as it empties.

It's being rate limited, the server doesn't like so many requests being sent so quickly. I've never had that many entries in my feed so I can't really test that.

Script is updated with a timer that should hopefully resolve this, but since I have no real way of testing I can't know for sure. If people could report back and let me know I would greatly appreciate it!

RussPA wrote:If it's no big deal, then sure that would be fine. Thanks!

Just updated, the success message at the end will now display the total number of cleared items. Let me know if that works for you.

RussPA wrote:Yea, I was just curious. For people who have a large area, like an entire state or country it might be interesting to see how many feed items they have, like is it in the hundreds or thousands, but not worth any trouble.

It would be trivial for me to add that, but it could only display after you clear the feed. Would you like that?

RussPA wrote:Just curious, is there a way to know how many items are in the feed?

Just checked, the API doesn't send the total number of issues back, so there's no way to know in advance how many there are. I could keep track of how many are cleared and display that if that's what you're asking.

Just updated it for the latest WME. I will look into doing some of the other suggestions that were offered in the replies years ago, but no promises at this point.

Olestas wrote:So what does it do actually?

I just updated the OP to explain. It clears what's currently on the screen, then reloads, clears again, reloads, etc. until everything is clear. No better way to do it that I could find, unfortunately.

I'd only recently thought about adding this sort of functionality to the feed filter in URO+, so there's definitely a demand for it (even if that demand is only from me ).

The one main difference in the version I was planning to add is that mine would only clear feed entries that were still visible on screen after the feed filter settings had been applied, so that I could quickly remove entries that I really wasn't interested in (e.g. all of the ones generated by my testing AM area in Mexico) without also removing ones I wanted to deal with by hand.

Any chance you could look at modifying your script to clear only the visible feed entries, either as an option or as the default mode of operation - the only time this would kick in is if someone was using the feed filter, so to turn off the option in your script they'd just need to turn off their filter settings in mine...

One other option I'd like to see is to make the feed reload optional, and have it clear only the currently visible entries on each click.


Finally, although removing feed entries doesn't affect the map data or the user editing profile, it should still be considered a destructive act which, once initiated, cannot be undone. So I'd also recommend almost to the point of insisting on it, that you include an "are you REALLY sure you want to nuke your feed entries?" confirmation prompt just in case someone clicks the link by accident.