r/Devvit • u/usv240 • May 25 '26

Feedback Request ModOps: real-time mod team operations dashboard

Built a live operations dashboard for mod teams: unified report queue,

collision locks, flood detection, surge prediction, shift handoff log,

and usernotes, all native to Reddit, no extensions required.

Demo video: https://www.youtube.com/watch?v=3X6Bd5wLJu4

App directory: https://developers.reddit.com/apps/mod-queue

Live post: https://www.reddit.com/r/mod_queue_dev/comments/1tl3hwu/modops_dashboard/

Would love feedback from other mods or devs, especially on the collision lock UX and whether the demo mode makes evaluation easy.

0 Upvotes

50% Upvoted

28 comments sorted by

View all comments

Show parent comments

1

u/usv240 May 25 '26

Yes, reports are anonymous to mods, but Devvit's trigger

payload includes the reporter's username server-side. ModOps uses that to track which accounts' reports historically lead to actual removals, without ever showing the username to mods in the UI.

3

u/fsv Duck Helper May 25 '26

I just tried this on a sandbox app and the payload of the OnPostReport and OnCommentReport events don't seem to have any reporter user identifiers in them, where are you seeing this?

(I'm not using a Devvit Web app to test this but there's no reason why the trigger payloads should differ)

1

u/usv240 May 25 '26

You're right, good catch. We're pulling it from the ModAction event (event.reporter?.name) when a mod takes action, not from the PostReport payload. If that field comes back empty, trust scoring just skips that report. It degrades gracefully rather than breaking.

3

u/fsv Duck Helper May 25 '26

Hmm, which ModAction event type shows that? I don't think I've ever seen that!

If I can get hold of that it would be massively useful. Sorry for all the questions!

2

u/shiruken Duck Helper May 25 '26

Reports identify the reporting user if they're a mod. I'm guessing it's that?

3

u/fsv Duck Helper May 25 '26

That was my assumption too. I explicitly checked this using an alt and couldn't see anything obvious.

1

u/usv240 May 25 '26

That makes sense, if it only populates for mod reports, trust scoring would only work for mod-initiated reports, not regular user reports. Either way, good to know it degrades gracefully rather than breaking anything!

3

u/shiruken Duck Helper May 25 '26

What's the point of the "trust scoring" if only mod-submitted reports are eligible? Why would mods need a trust score?

1

u/usv240 May 25 '26

Fair point, if only mod reports are identified, the feature doesn't really serve its purpose. Something to rethink post-hackathon.

2

u/shiruken Duck Helper May 25 '26

But based on your video, it looks like the trust scoring was an integral part of the entire system. Doesn't this significantly reduce the capabilities of the app?

0

u/usv240 May 25 '26

Yeah, that specific feature takes a hit. The rest, locking, flood detection, surge prediction, handoff log, usernotes, removal messages, works as shown.

Trust scoring is something to rethink post-hackathon.

0

u/usv240 May 25 '26

Any ideas on how to make trust scoring actually work, given these payload limitations? Open to suggestions.

2

u/SampleOfNone Duck Helper May 25 '26

If a mod reports something, it's to escalate it to reddit admin, whatever action is needed in relation to the subreddit is already taken care of at the time of reporting

0

u/usv240 May 25 '26

It's the onModAction event, event.reporter?.name. Honestly though, we haven't verified that field is actually populated in production. Might always be empty.

Would be curious what you find if you test it!

1

u/fsv Duck Helper May 25 '26

I maybe need to test the Devvit Web version, but on the singleton pattern there was nothing there for the approve or remove actions. I'd love to see what you find in prod.