NoMongo: Replace Base64 Storage with MinIO Client in ChatRoom.tsx

[NishantSinghhhhh]

Problem
ChatRoom.tsx currently uses Base64 encoding for storing images and media, leading to high memory consumption and slower performance.

Solution
Implement MinIO client for direct file uploads, storing only the file URLs instead of Base64 strings.

Alternatives Considered

• Keeping Base64 (inefficient for large files).
• Using third-party cloud storage (MinIO offers a self-hosted solution).

Approach

1. Remove Base64 encoding logic.
2. Integrate MinIO file upload for media messages.
3. Store and retrieve file URLs efficiently.

Additional Context
This change will improve chat performance, reduce payload size, and optimize storage usage.

---

NOTE

1. We recently discovered a flaw in the code base where there are some XSS and CORS vulnerabilities. This occurs when the API and Admin servers run on different machines.

2. You will notice this if you configure your Admin app on your local machine to use the API running on https://test.talawa.io/graphql.

3. The errors in your browser will look like this:

   

4. As part of this issue you will need to ensure that the browser only interacts with the API through the Admin server and never with the API directly.

[Nivedita-Chhokar]

@palisadoes Kindly assign it to me

[palisadoes]

PTAL at the XSS and CORS vulnerabilities mentioned above that you will need to address as part of this.

[palisadoes]

Unassigning. 2 weeks of inactivity

[Akshat2gupta]

Hi @NishantSinghhhhh, I’d love to work on this issue! Since optimizing image storage with MinIO is a great improvement for performance and security, I’d be happy to implement the changes.

Could you please assign this issue to me? Thanks!