Thanks for tracking that down. It makes finding the issue and fixing it a lot easier. rimu will likely see this thread before I get a chance to sit down and work on it, but should have a fix soon probably. Sorry for the extraneous reports!
Let me see if I understand this issue correctly…
You are a lemmy instance admin. If a user from your instance is moderating a community, then any report in that community that is made by a piefed user is also forwarded to you. This happens even if the user being reported is not local to your instance.
You might not know the answer to this since it happens rarely, but does this happen for reports just in local communities, or also in remote communities that your user is a moderator for? So, if modA@slrpnk.net is a mod for commA@notslrpnk.net, do you still see the report if a piefed user makes a report in commA?
I have both a piefed and a lemmy instance I run for testing things, I can try to mess around with the different permutations for this one.
There’s no winning against Blaze.
As far as I know, this is the community where it happens so to speak. There is also !piefed_announcements@peertube.wtf where @rimu@piefed.social will post videos showcasing new features. However, not all features have need of a video.
because > doesn’t seem to work in selectors
I learned this the other day when I was trying to troubleshoot some css. It gets html-encoded so it doesn’t work anymore in the selector.
Interesting. It shows up, but just as the shortcode:
@rimu@piefed.social - not sure what the json looks like coming from mitra, but at least in the short term it might make sense to just have piefed interpret emoji it doesn’t understand as an upvote (like it had been doing up to now) so that it doesn’t break the UI like this.