Support Additional Whisper Services (Focus on OpenAI Whisper API)

[vadanrod14]

Title: Add Support for OpenAI Whisper API Integration

Description:

Currently, the Telegram bot uses AWS Whisper to transcribe voice messages. While this works well, supporting alternative Whisper services could enhance flexibility, performance, and cost-effectiveness, depending on user needs. This issue focuses on integrating the OpenAI Whisper API as an additional transcription backend.

Proposed Solution:

1. Abstraction Layer: Create a modular architecture that allows switching between transcription services easily. This can involve:

   • Defining a common interface for transcription services.
   • Implementing service-specific modules.

2. OpenAI Whisper API Integration:

   • Implement a new module for the OpenAI Whisper API.
   • Include necessary configuration options (e.g., API keys, endpoints).
   • Ensure compatibility with current Telegram bot features.

3. Fallback/Preference Mechanism:

   • Allow users to set a preferred transcription service.
   • Implement fallback logic in case the primary service is unavailable.

Tasks:

• Refactor the existing code to introduce a service abstraction layer.
• Research and document the OpenAI Whisper API (authentication, pricing, limits, etc.).
• Implement and test the OpenAI Whisper API integration.
• Add configuration options for switching between transcription services.
• Update documentation to include instructions for using the OpenAI Whisper API.

Additional Context:

OpenAI Whisper API is known for its accuracy and robustness in handling diverse languages and accents. Including it as an option could provide better transcription quality in some cases compared to AWS Whisper.

Acceptance Criteria:

• The bot can transcribe messages using both AWS Whisper and OpenAI Whisper.
• Users can configure their preferred transcription service.
• Comprehensive documentation and tests are in place.

Feel free to modify or prioritize tasks based on project needs!