(#fml2g4a) @prologic this is going on for multiple pages on your pod, viewing in guest/logged out mode, so someone is following that feed I guess. I guess this leads into the question, do we need a way to automatically limit content that might be considered spam? 🤔 As in totally duplicate yarns like that one.

(#fml2g4a) It's at this point that I _believe_ it might be time to implement and add support for pod-level "blacklist"(s). Basically I'm not even sure how this feed hits my pod's cache, like at all. Noone on my pod seems to follow it? 🤔

(#fml2g4a)

(#fml2g4a) @eldersnake Yeah I emailed the "administrator" / "maintainer" and this is the response I got: 🤷‍♂️ I _honestly_ don't know how to help if the help is just flat out refused 😢 😔

Man, that Port70 feed... 😂

(#fml2g4a) Oh well good news, we're having a dialogue, so we'll see where this goes. The problem as I've stated is I have no idea where or how this is landing n my pod's cache at all 😢 It's a right royal #mystery 🤔

(#fml2g4a) @eldersnake > I guess this leads into the question, do we need a way to automatically limit content that might be considered spam? 🤔 As in totally duplicate yarns like that one. Well yes and no, the thing is; The Feed Cachee's `MaxCacheTTL` and `MaxCacheItems` already limit this kind of thing to a degree. The so-called "spam" will come and go as quickly as it came just be sheer fact of other activity.