Skip to main content

Contributions

What good contributions look like​

  • UI improvements that keep the Instagram-like feel without breaking readability
  • message parsing fixes that preserve archive accuracy
  • export improvements that remove unnecessary runtime weight
  • documentation that helps users host the project more safely

Repository​

Main GitHub profile and project ownership live at:

Code expectations​

  • keep comments focused on non-obvious behavior
  • explain tricky pagination, parsing, and storage logic
  • avoid introducing parallel data paths without a strong reason
  • prefer one clear runtime contract over multiple partial ones

Documentation expectations​

Docs should answer:

  • what exists now
  • what is planned next
  • what is safe to recommend to users
  • what trade-offs still need decisions

Privacy expectations​

Any contribution that increases storage, telemetry, or retained user metadata should be justified carefully and documented clearly.