Streaming Providers

MovieBox-TUI searches and streams media across multiple independent providers.

Available Providers

Switching Providers

• Cycle Provider: Press Ctrl+P on the home screen to switch to the next provider.
• Provider Menu: Click the provider badge in the search bar (or press Enter on it) to open the provider selection menu.
• Enable / Disable Providers: Open /settings → Content Modes → Streaming Sources to toggle providers on or off.

BDIX Network Detection

If you are connected through a Bangladeshi ISP supporting BDIX:

• MovieBox-TUI automatically tests local BDIX mirrors on startup and enables them if reachable.
• You can manually re-test your connection anytime via /settings → Maintenance → Re-check BDIX Network.

Provider Architecture (For Developers)

All providers implement a shared Rust trait in src/providers/:

#![allow(unused)]
fn main() {
pub trait Provider: Send + Sync {
    fn id(&self) -> ProviderKind;
    fn capabilities(&self) -> ProviderCapabilities;
    async fn search(&self, query: &str, page: usize) -> Result<Vec<CatalogItem>, ProviderError>;
    async fn details(&self, id: &str) -> Result<MediaDetails, ProviderError>;
}
}

New providers implement Provider (and optionally ReleaseProvider for multi-mirror streams), then register in src/service.rs. Responses are automatically cached as MessagePack envelopes.

MovieBox CDN Manifest & Failover Resolution

MovieBox CDN stream entries parse signed CloudFront-Policy and Edge-Cache-Cookie tokens to find stream roots. The manifest resolver accepts only /dash/ resources. Unhosted legacy /hls/ cookie targets are dropped to prevent 404 failures during playback or downloads.

When upstream APIs return placeholder deprecation notices, MovieBox-TUI automatically queries the /resource-position/v2 failover endpoint with scoped episode resolution to recover genuine signed MP4 streams, omitting the DASH Referer to prevent CDN HTTP 429 throttling.