Skip to content

Add negative examples that should retain ordinary prose #180

Closed

Description

@ashrafee-dev

PRI-05 · Privacy filtering

Difficulty: beginner · Status: ready

This is a focused contribution against current main. No unmerged feature PR is required.

Why this is useful

Over-redaction can hide useful scam context

Start here

Source audit: 9d8ac3e01df1. Read these files on current main too, because paths may change after the audit:

Scope and intended output

Add the focused test file tests/roadmap/privacy/test_safe_prose.py. Change runtime code only if the acceptance criteria explicitly request a behavior fix; otherwise report newly discovered behavior separately.

Acceptance criteria

  • Use benign synthetic sentences without identifiers
  • Assert exact preservation
  • Keep disputes about numeric sequences as separate design cases

Verification

uv run pytest tests/roadmap/privacy/test_safe_prose.py -q
uv run pylint app tests

Create the named focused test file before running its command. Tests must be deterministic, mock external services, and avoid paid calls. Run bash scripts/check.sh before submitting a Python change.

Dependencies

None. Keep the PR based on current upstream main.

Out of scope

  • Unrelated refactors, broad formatting, endpoint renames, or extra dependencies without agreement.
  • Live cloud provisioning, paid model calls, real private messages, or credentials in fixtures/logs.
  • Implementing neighboring roadmap issues in the same PR.

Getting help and submitting

Comment with your intended approach and ask when expected behavior is unclear. Check for an existing PR before starting; there is no deadline for a volunteer contribution. A useful reproduction or partial finding is welcome.

Use the issue's criteria as the review checklist. Include the commands actually run and any limitations. Link the issue; use Fixes only when its entire agreed scope is complete. If CONTRIBUTING.md is not yet on main, the contributor-roadmap PR provides the onboarding guide.

Activity

  1. added
    help wantedExtra attention is needed
    contributor-roadmapRoadmap item with a scoped contributor brief
    status:readyScoped work against main; no unmerged prerequisite
    difficulty:beginnerSmall locally verifiable contribution with clear guidance
    on Sep 28, 2026
  2. sivaadithya25 commented on Sep 28, 2026

    @sivaadithya25
    Contributor

    Hi, I'd like to work on this issue. Could you assign it to me?

  3. sivaadithya25 commented on Sep 28, 2026

    @sivaadithya25
    Contributor

    am is still assigned to this! I saw there it shows assigned and unassigned

  4. sivaadithya25 commented on Sep 28, 2026

    @sivaadithya25
    Contributor

    if you didn't have problem please assign me back it will grate for me to work with you

  5. ashrafee-dev commented on Sep 28, 2026

    @ashrafee-dev
    OwnerAuthor

    @sivaadithya25 You are still assigned for this issue. Really appreciate all the contributions you are making.

  6. sivaadithya25 commented on Sep 28, 2026

    @sivaadithya25
    Contributor

    Thank you for confirming ill be working on it now!

  7. sivaadithya25 commented on Sep 29, 2026

    @sivaadithya25
    Contributor

    Hi @ashrafee-dev, just a small reminder — PR #372 for this issue has been merged successfully. When you get a chance, could you please close Issue #180? Thank you! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:privacyPrivacy filteringcontributor-roadmapRoadmap item with a scoped contributor briefdifficulty:beginnerSmall locally verifiable contribution with clear guidancegood first issueGood for newcomershelp wantedExtra attention is neededstatus:readyScoped work against main; no unmerged prerequisite

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions