Circuit-Forge/snipe
2
0
Fork 0
Code Issues 13 Pull requests Projects Releases Packages Wiki Activity Actions

Scammer database: eBay T&S batch reporting + CF community blocklist #4

New issue
Open
opened 2026-03-26 22:08:36 -07:00 by pyr0ball · 0 comments
pyr0ball commented 2026-03-26 22:08:36 -07:00
Owner
Copy link

Status

Phase 1 (local blocklist) — DONE (migration 006_scammer_blocklist.sql, store methods, API endpoints /api/blocklist, established_bad_actor red flag wired into trust scoring)

Remaining

Phase 2 — eBay Trust & Safety batch reporting

  • Multi-select listings in search results (checkbox UI on cards)
  • "Report sellers" action: generate eBay report deep-links for each selected listing
  • Batch-open in tabs, or generate a summary page the user can work through
  • Track which sellers have been reported (timestamp, reported_by)

Phase 3 — CF Community blocklist (cloud)

  • Cloud-tier: opt-in sync of confirmed bad actors to a shared CF blocklist
  • Privacy-by-architecture: only platform_seller_id + flag reason synced, no PII
  • Consensus threshold before a seller appears in community list (e.g. 3+ independent reports)

Motivation

Users catching scammers should be able to flag them persistently and contribute to protecting the broader community. eBay Trust and Safety reporting is the official channel; the CF blocklist adds a layer that persists across eBay moderation delays.

## Status **Phase 1 (local blocklist) — DONE** (migration `006_scammer_blocklist.sql`, store methods, API endpoints `/api/blocklist`, `established_bad_actor` red flag wired into trust scoring) --- ## Remaining ### Phase 2 — eBay Trust & Safety batch reporting - Multi-select listings in search results (checkbox UI on cards) - "Report sellers" action: generate eBay report deep-links for each selected listing - Batch-open in tabs, or generate a summary page the user can work through - Track which sellers have been reported (timestamp, reported_by) ### Phase 3 — CF Community blocklist (cloud) - Cloud-tier: opt-in sync of confirmed bad actors to a shared CF blocklist - Privacy-by-architecture: only platform_seller_id + flag reason synced, no PII - Consensus threshold before a seller appears in community list (e.g. 3+ independent reports) ## Motivation Users catching scammers should be able to flag them persistently and contribute to protecting the broader community. eBay Trust and Safety reporting is the official channel; the CF blocklist adds a layer that persists across eBay moderation delays.
pyr0ball added this to the Alpha — Pipeline milestone 2026-04-04 16:33:19 -07:00
pyr0ball changed title from Scammer database: community blocklist + batch eBay Trust & Safety reporting to Scammer database: eBay T&S batch reporting + CF community blocklist 2026-04-04 22:48:05 -07:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/affiliate-links
feature/feedback-button
feature/shared-task-scheduler
No results found.
Labels
Clear labels   
backlog
No labels
backlog
Milestone
Clear milestone
No items
No milestone
Alpha — Pipeline
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/snipe#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?