ramforth/youtube-chat-webhook-v2
2
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Update DEVELOPMENT_PLAN.md with Phase 2 Action 1 findings

Browse Source
This commit is contained in:
Ramforth
2025-10-30 20:14:16 +01:00
parent c4fc7e1680
commit 0d45d295c3
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
DEVELOPMENT_PLAN.md
View File

@@ -76,6 +76,8 @@ Our network analysis revealed that YouTube's web client uses a `POST` request to
* **Objective:** Explore creative, highly optimized uses of the existing REST API that might offer better sustainability, even if not truly event-driven.
* **Actions:**
1. **Live Chat Replay API:** Investigate the `liveChatMessages.list` endpoint when used for *replays*. Does it have different quota characteristics or offer a more complete historical view that could be adapted for near real-time (e.g., fetching a larger batch less frequently)?
* **Findings:** `liveChatMessages.list` costs 5 quota points per request, regardless of whether it's for live or replay chat. Frequent polling (e.g., 1 request/second) will exhaust the 10,000 daily quota in about 33 minutes. The method is not designed for efficiently replaying extensive past chat history. There's no indication of different or more lenient quota characteristics for replay usage. This approach does not offer a sustainable, quota-friendly solution for continuous monitoring.
* **Status:** **COMPLETED.** Conclusion: Not a sustainable solution for continuous monitoring.
2. **Minimal `part` Parameters:** Re-confirm the absolute minimum `part` parameters required for `liveChatMessages.list` to reduce quota cost per call.
3. **Intelligent Polling Refinement:** Explore advanced adaptive polling strategies beyond `pollingIntervalMillis`, potentially incorporating machine learning to predict chat activity and adjust polling frequency.