Now you've found something most curious, haha. These are indeed real events, the issue seems to be that each iteration of the addressable event is appending the unique d-tag with an `@i` iteration interval (`@81`, `@82`, `@83`, etc):
The result is that each event is treated uniquely by the UI, thus rendering the same content ad infinitum (or at least equal to the number of duplicates for the event, currently 80+).
If these are iterations of the same event, then the d-tags should be consistent between those iterations. The current behavior indicates that this is either a test event that has been posted multiple times in isolation, or that these are edits/iterations of a single test event that was posted prior. I'm also only seeing this d-tag behavior on Primal's relay (though this may be a red herring given that the other relays may hide any of these iterative events).
In any case, what you're seeing are multiple 'unique' events in your feed. If you switch to a different relay on your site, the feed should look closer to your expectation.
I tried to review the most recent codebase for Reviewstr, but I was unable to find any explicit logic that would be modifying the d-tag in this manner. To more accurately narrow this down, could you walk through how this test review/event was created, edited, etc.?
