Gotcha! So this event was only published once for your test? Ultimately, I'm just looking for any clue to identify the mechanism that would cause these duplicate events/reviews to appear in relay traffic.

Reviewstr itself appears to be fine, it is serving content as it is provided from the relay, but the relay is also providing it multiple clones of the same review event, followed by your main reviews (which leads to the effect of it looking like a single review on your feed being repeated).

The first event was posted at 1752892713 (Saturday, July 19, 2025 2:38:33 AM GMT), the last 1752892798 - 86 events in total that appear to have posted sequentially, only within this one window of a minute or so. So this was likely triggered by a single testing action, and hasn't repeated since.

Assuming that this was a one-off occurrence, then to solve this, I would suggest either:

1) Adding a delete button to review listings that the currently logged in user has authored. This will allow you to delete each duplicate event from the UI while logged in as the test user.

2) Hide reviews from the test pubkey - a7bc01ecd959bb68172c047180b3eaa4a1a328cb1165005979f131e9a958da72. I believe Reviewstr operates on a allow/denylist system, so it would likely involve removing this pubkey from the allowed authors list (or adding them to the denied/blocked list if the equivalent exists).

I will investigate more later to see if I can find anything else on what may have triggered this chain of duplicate test reviews to post. In the meanwhile, either of the above options should solve the immediate issue!