Feature: Implement Web Scraper, Discord, Telegram and/or Diariazation endpoints

[teslashibe]

Problem Statement

Currently, our system only has functional endpoints for Twitter data. Discord and Telegram endpoints are stubbed but not yet implemented. We need to expand our data sources to include these platforms to provide a more comprehensive service.

Acceptance Criteria

• [ ] Implement functional Discord endpoints
• [ ] Implement functional Telegram endpoints
• [ ] Ensure new endpoints follow the same data contract structure as the Twitter endpoint
• [ ] Test new endpoints
• [ ] Update relevant documentation to include information about the new endpoints

Additional Context

• This feature is part of the natural expansion of our data sources
• Discord endpoints were specifically mentioned as having issues over the weekend
• The implementation should follow the pattern established with the Twitter endpoint

Proposed Solution

1. Review the existing Twitter endpoint implementation
2. Design and implement similar structures for Discord and Telegram
3. Ensure proper error handling and rate limiting for the new endpoints
4. Integrate the new endpoints with the existing validator infrastructure

Next Steps

1. Analyze the specific requirements for Discord and Telegram APIs
2. Design the data structure for the new endpoints
3. Implement the new endpoints
4. Create unit and integration tests
5. Update the documentation to include the new endpoints

This feature will enhance our platform's capabilities and provide more diverse data sources for our users. Please discuss any questions or concerns about this feature in the comments.

[Luka-Loncar]

Blocked by spikes from the week of 9th September.