add initial goals documentation #1
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Walros-Dev/ConceptDocs#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "goals"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#2
@ -0,0 +4,4 @@- **Caching & Performance:**- Use cached segments for seamless seeking and fast resume.- If another user starts playback with the same parameters, reuse existing cached data to minimize transcoding and bandwidth usage.- Includes CDN capabilities and P2P federation by Blint.I think CDN deserves it's own section here. I personally have a few ideas for it.
@ -0,0 +16,4 @@- Native Clients: Desktop (Windows, Linux, MacOS), Mobile (Android, iOS), TV (Android TV, Apple TV, WebOS, Roku, Someone could create one for Xbox)- Multiuser Support in clients: You are able to login with multiple users and change between them.- **Offline Access:**- Clients can batch-download content for offline playback, respecting user permissions and device limits.What are device limits exactly?
Just too much copying and pasting. It should not be there.
Removed
@ -0,0 +45,4 @@- **Multi-Format Detection:** Detect multiple versions (e.g., 1080p, 4K, HDR) of the same media and show them in a unified view.- **IPTV / Live TV:** Stream and manage live channels alongside on-demand content.## ArchitectureI would add "Resiliency" as in. "Temporary outage in one service should not affect/disrupt the viewing experience" or something similar along the lines
Added
6009407c99to41fb1e5b55added CDN functionality, @patrik @marcsello please take a look 👀
@ -0,0 +36,4 @@- Multiple CDNs can share content and metadata within a trusted federation network.- The system can automatically balance or replicate popular content across CDNs to optimize bandwidth usage and ensure availability.- **Future Idea - Predictive Caching:**This part should be moved to the later section @blint .
5106ae1a9atobeecae7c09@ -0,0 +30,4 @@- **Peer-to-Peer (P2P) Sharing:**- CDNs and the main server interconnect via **P2P protocols** to simplify file transfer and reduce reliance on centralized infrastructure.- This enables faster, bandwidth-efficient distribution of popular content between geographically distributed CDNs.This is not a goal, this is an explanation.
@ -0,0 +14,4 @@- **Secure Connectivity:**- Each CDN connects to the **main metadata server** using a **pre-shared key** for authentication and trust establishment.- This ensures only authorized CDNs can register and exchange data with the main network.This isn't a goal, that's an explanation.
@ -0,0 +33,4 @@- This enables faster, bandwidth-efficient distribution of popular content between geographically distributed CDNs.- **Federation & Collaboration:**- Multiple CDNs can share content and metadata within a trusted federation network.What does a "trusted federation network" mean in this context?
a connection between the instances via VPN
I think we should write that instead. To me it's more exact and therefore easier to understand.
@ -0,0 +28,4 @@1. **Request content replication:** Copy or prefetch the content from another CDN or the main server.2. **Stream fallback:** Stream the content directly from the main server or the nearest available CDN.- **Peer-to-Peer (P2P) Sharing:**I think this would be better in the "Nice to have/later" part. Sounds a bit complex to be a core feature. (especially if you want to pack all this up to a single binary)
@ -0,0 +4,4 @@- **Caching & Performance:**- Use cached segments for seamless seeking and fast resume.- If another user starts playback with the same parameters, reuse existing cached data to minimize transcoding and bandwidth usage.- **CDN Capabilities and P2P Federation**I think it might worth including that what content does exactly a CDN node deliver? For starters I think serving only "media" would be good.
/lgtm
@patrik wanna take a look?
Lgtm
I can't approve my own PR @blint