May 26, 2026

[cassidyjames]

We had our working group call this morning. Here are the notes!

Questions from Adopters

• Can you skip certain item types with partial items #378 (adopter: @ThatKoffe)
  • Example: Adopter only needs updated users/posts, not for other items like chats
  • Partial items API, you send whatever you want to it (pls fact check my notes)
  • FLAG: Coop is throwing errors with partial items API: [Bug] Partial items API not updating objects #585
• Can we escalate the media unification project? Item schema type for media type unification  #418 (adopter: @ThatKoffe)
• IP Address as role Add IP address as a role when creating Items #468 (adopter: @ThatKoffe)

Open issues/PRs

• Make scylla optional: Interface set up for Scylla #190
  • @juanmrad wants to spend some time to figure this out properly; planning to tackle it last for v1 tasks
  • We’re using outdated version of Postgres; also using pgvector instead of upstream/base postgres
  • Analyze how we’re seeing ClickHouse being used in production
  • Theoretically everything could be a single Postgres db; we’d need to handle a lot of migrations which could become unmanageable
• Invalidate reports for a user #404
  • Next on @juanmrad’s list
• Roles/permissions PRs
  • [Permissions] Capability-based authz refactor. gate org secrets, deleteUser, and ReadMe JWT on MANAGE_ORG #528 → [Permissions] Capability-based authz with DB-backed roles + static fallback #560 → [Permissions] Add role editor API and UI #582
  • Todo: review and testing!
• Queues should have custom prioritization in the UI #409
  • It’s a calculation that happens in BullMQ, pulls data back from that based on a score
  • To change the ordering (e.g. influenced by number of reports), we have to recalculate that score of all items in the queue; makes it hard to define in the front-end
  • Bigger scarier question: does this mean we’d want to move away from BullMQ?
  • TODO: Chat w/adopters to see what other ordering they’d like to see
    • Could use weight-based calculation (date, number of reports, user score)
• server: Add end-to-end item submission integration test and harness #488
  • ready for re-review
• Add IP address as a role when creating Items #468
  • Helpful for investigation Support IP address for investigation #591
  • NCMEC reports! Add IP address to NCMEC reports #592

Longer-term questions from @ThisIsMissEm

• Using custom web framework; is that slowing us down?
• Types for Integrations vendors are published under roostorg/types
  • Implies types for all ROOST projects, not just Coop (i.e. should be roostorg/coop-types, maybe!)
  • Breaking change, probably good to tackle pre-v1
• Lead to questions such as:
  • Do we actually need GraphQL?
  • Are we tied to the expressJS framework long-term? If not, what steps can we make to migrate away long-term (dependency injection)
  • How are we keeping track of Coop adopters?
    • Document adopters #54
    • What about:
      • Other self-hosters
      • Vendors with built-in integrations are in the codebase, engaged w/ROOST
      • Other vendors hosting as a product, e.g. Musubi
    • ROOST can keep internal list in addition to public documentation

[cassidyjames]

Actions

• @ThisIsMissEm file an issue re:types package rename
• Swap pgvector to base postgres
• @cassidyjames can make sub-tickets for ip address role
• @cassidyjames review/add issue and PR templates
• @cassidyjames to figure out community team

[ThisIsMissEm]

Types package rename: #598