Extension ideas - what's worth building?

[SashankBhamidi]

Milestone A is done. Before diving into B (CLI) and C (web service), wanted to list some extension ideas that came up. Some might fit into second round work, others could be standalone features.

Technical stuff

• Pluggable hash algorithms - SHA-256/SHA-512/Argon2 choice (ties into Code quality improvements from PR #51 review #52's Strategy pattern)
• Anonymization profiles - Preset preservation sets: "debug-friendly", "minimal", "strict"
• Anonymization report - Summary of what got anonymized
• Reverse mapping file - Encrypted file to de-anonymize (for original submitter only)
• Validation mode - Detect if calendar already anonymized or has sensitive data

Integrations

• GitHub Action - Auto-anonymize calendars in issues/PRs
• Pre-commit hook - Block committing non-anonymized calendars
• Browser extension - Right-click anonymize .ics
• Thunderbird/Outlook plugin - Direct export anonymized
• Bulk API endpoint - Process multiple calendars

Quality improvements

• Diff mode - Side-by-side original vs anonymized
• Selective anonymization - Interactive CLI to pick events/properties
• Pattern-based preservation - Regex matching for properties
• Smart detection - Auto-detect/preserve non-sensitive data (public holidays)

Ecosystem

• CalDAV integration - Test harness with anonymized calendars
• Upstream contribution - Add .anonymize() to icalendar library
• Academic paper - Document the privacy approach

Which of these are worth pursuing? What else should be on this list?

[tobixen]

For the CalDAV integration, I can see two usage patterns, one is to take events from one calendar, anonymize them and save it to another calendar. The other calendar may be owned by another user or even be on another server. The other usage pattern is to anonymize events inline on the same calendar. It's probably most important to support the first.

Source objects should probably be picked out through a search.

I suppose a good interface would be a method taking a list of events/tasks as input (typically some results from a search - calendar.search() gives all the objects), a target calendar and options for the anonymizing.