September 29, 2026

[cassidyjames]

Our working group call is today at 1445 UTC.

Potential topics

• Adopter questions, pain points, etc.
• 1.1.0 release
• Decide how to handle "Report Rules" #630

[cassidyjames]

Attendees: @cassidyjames, @selena-lustig, @taobojlen, @juanmrad, @serendipty01, @ThisIsMissEm

Notes

Adopters

• Explicitly label issues filed by adopters #1099 Label issues filed by adopters
  • Should also have a Google Form that’s non-public (share comments/suggestions/issues) “Private feedback” link in issue config; similar to what was done w/HMA in the past
• Increasing Memory Over Time #925 still open, awaiting response from @jess-upscrolled
  • Related: we don’t run Coop in production, so some of these issues are hard for us to track down
  • Could enable memory profiling, let adopters turn that on and provide memory snapshots/flamegraph (privately) for us to investigate further.
• Jobs can not be submitted due to error and get stuck #1097 jobs get stuck (Kyodo)
  • Awaiting response from @ThatKoffe, i.e. Postgres errors/logs
  • @ThisIsMissEm has seen jobs in BullMQ get stuck in other projects
• Notes on items (not just jobs) #1024 clue system/comments: needs design (related: Moderator Notes system #1039 moderator notes/scratch pad, inspired by Everything in Moderation)
  • Moderator Notes system #1039 would be interesting to do some design and prototyping
  • Would be nice to share w/adopters to get feedback!
  • Moderator Notes system #1039 could have split opinions from adopters; some might really want this, some might not want moderators logging things; be an option… but there’s risk of exploding complexity w/combinations of options.

Outstanding actions

• feat: 670 order jobs by num reports #718 - @juanmrad
• Address #1203 Optimizing oldest job by creating a Sorted set for oldest job on queue #1204 - @juanmrad
• [581] Add actions and policy selection on additional content items #1202 - merged!
• @serendipty01 GraphQL issues Missing org id check during routing rule order update #1232, need advisory (@selena-lustig, then add @taobojlen)
• @serendipty01 NCMEC user ID NCMEC escalation silently fails when the content item's type has no creatorId role #1233
  • Might be “expected” but could be better handled w/validation or at least an error
  • Can we require a creatorId on everything? We could enforce this, but it could break things for existing adopters if they don’t have creatorIds—this currently only affects NCMEC reports; the problem is that it should have never been able to be enqueued in the first place

1.1.0 release

• We’ve asked for feedback, but haven’t gotten any at this point
• Pending security advisories dictate that we need to release soon anyway… could include w/1.1.0
• There’s a lot of churn to backport things… is main in a state that it could be 1.1.0 stable?
• Seems like we may be overly-cautious w/release process; considering we’ve not been getting proactive feedback or release-related feedback, we might be better off releasing earlier/more often.
• 1.1.0 didn’t have an explicit milestone list of features to be included, so it’s a bit amorphous
• If we don’t have confidence that main is shippable, that seems like the underlying issue; we don’t have the feedback and testing loop that we need.

Actions

• @cassidyjames look into why @taobojlen can’t create a private PR on advisories
• @juanmrad follow-up on feat: 670 order jobs by num reports #718
• @juanmrad follow-up on Address #1203 Optimizing oldest job by creating a Sorted set for oldest job on queue #1204
• @selena-lustig create advisory for Missing org id check during routing rule order update #1232, then add @taobojlen
• @cassidyjames to comment on NCMEC escalation silently fails when the content item's type has no creatorId role #1233