Redact switch

[shiv810]

Config to toggle redacts.

Used for private repos only.¹²

redactPrivateRepoComments: boolean

Default we capture everything.

Maybe we shouldn't redact comments in the near future.³ And instead have a switch for it later when/if partners ever ask. I feel like most people won't care and it will give us more data to work with for research purposes in the near future.

I guess it would be fine to have it as an option in the configuration, because as long as not everybody can access the DB the content of private repositories cannot be read by outsiders.⁴⁵

Originally posted by @gentlementlegen in https://www.github.com/ubiquity-os-marketplace/text-vector-embeddings/pull/20#issuecomment-2382245540

Footnotes

1. ⚠ 81% possible duplicate - File upload fails always ↩

2. ⚠ 80% possible duplicate - Test Issue ↩

3. ⚠ 80% possible duplicate - Bug in User Login Functionality ↩

4. ⚠ 81% possible duplicate - Issue with Account Access ↩

5. ⚠ 80% possible duplicate - Issue with Account Recovery ↩

[test-app-ubo]

Note

The following contributors may be suitable for this task:

gentlementlegen

66% Match ubiquity-os-marketplace/text-conversation-rewards#31
65% Match ubiquity-os-marketplace/text-conversation-rewards#95
65% Match ubiquity-os-marketplace/text-conversation-rewards#110
65% Match ubiquity-os-marketplace/text-conversation-rewards#46

Keyrxng

65% Match ubiquity/devpool-directory-tasks#31

[shiv810]

/ask explain this issue?

[test-app-ubo]

Issue #243 focuses on configuring the redaction of comments within private repositories. The primary objective is to introduce a toggle (redactPrivateRepoComments) that allows administrators to control whether comments in private repositories are redacted. By default, the system captures all comments without redaction. However, there's a consideration to potentially disable redaction in the near future and instead implement a conditional switch based on partner requests. This approach aims to retain more data for research purposes while ensuring that sensitive information remains protected, provided that access to the database is restricted to authorized personnel.

Key Points:

• Configuration Toggle:
  redactPrivateRepoComments: boolean
  Allows toggling the redaction of comments in private repositories.

• Default Behavior:
  All comments are captured without redaction.

• Proposed Change:
  Consider not redacting comments in the near future and instead implementing a switch to control redaction based on specific partner needs.

• Rationale:
  Most users may not require redaction, and retaining unredacted comments can provide valuable data for research. Ensuring that the database is securely accessed prevents unauthorized reading of private repository contents.

• Potential Duplicates:
  Several related issues indicate similar concerns about comment redaction and account access, suggesting that this configuration might overlap with existing discussions.

For more detailed discussions and related concerns, refer to the linked duplicate issues within the issue tree structure.