Humm.. because it is spam, it will not be cached locally. So, if you are going back to one of the hashtag views, it will keep asking for it. I will check when I get back home  

 Ty kind sir 

 @Vitor Pamplona you need to make a cache of spam event IDs so it doesn't request them again also perhaps? 

 Nice catch 

 Can the client mark it In a spam list and prevent Download the next time? 

 of course amethyst should look at why it's happening on their side but if your relay is authing you can maybe come up with a rate limiter to cut back on how often it actually sends the same event within a short time period to limit this