Remove dependency on MongoDB

[Zingzy]

To align with Pollinations' vision of complete user privacy, we aim to eliminate the storage of user data in our MongoDB cluster. Currently, the data is primarily used for the redo function. Instead, we will utilize Discord's built-in API and image metadata to enable the redo functionality and other similar features without requiring persistent storage.

This transition will enhance user trust while maintaining the core functionalities of the service.

Tasks

• Analyze Current Data Flow

  • Document how user data is currently stored and accessed in the MongoDB cluster.
  • Identify dependencies on MongoDB for the redo function and similar features.

• Develop a Metadata-Based Solution

  • Explore how Discord's built-in API can be leveraged to fetch necessary information.
  • Investigate image metadata usage for retrieving and replicating requests for redo.
  • Implement a mechanism to dynamically process requests without persistent storage.

• Refactor Codebase

  • Remove MongoDB interactions related to user data storage.
  • Update redo and related functionalities to use the new metadata-based approach.
  • Test the updated functions to ensure parity with the previous implementation.

• Testing and Validation

  • Create unit and integration tests to verify the accuracy of the new implementation.
  • Conduct privacy-focused audits to ensure no user data is stored.

• Deployment and Monitoring

  • Deploy the updated codebase.
  • Monitor logs and user feedback for any issues or improvements needed.

Outcome

This update will align our service with Pollinations' commitment to complete user privacy while maintaining robust and reliable features like redo.