You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am newer for DRM, and I noticed this repo could support DRM, also I read Readium Architecture, and it seems two difference solutions, for desktop(or mobile), used LCP(Lightweight Content Protection), for web, used Webpub Manifest, because backend server can commutation with other services, so, this is a large challenge to solve web DRM.
Has anyone met this problem? And how do you resolve it?
Everybody is facing this problem of protecting Web Publications against undue copy. But a DRM is based on secret algorithms and nothing is private in a web browser.
Developers involved in Readium (mainly EDRLab and De Marque at this time) are discussing how to implement content protection on web and the NYPL Readme is giving clues about the landscape. But Readium does not currently provide ready-to-use software for that purpose. Either you can spend the time to develop your own solution (several companies already did) or you'll have to wait for an off-the-shelves solution; we cannot give any timeline for this, as Readium is a collaborative open-source effort.
Thank your response, recently, I used Astro to build my website, which supports SSR to render HTML, I guess it perhaps could protect secrets and avoid the public in the browser.
I am newer for DRM, and I noticed this repo could support DRM, also I read Readium Architecture, and it seems two difference solutions, for desktop(or mobile), used LCP(Lightweight Content Protection), for web, used Webpub Manifest, because backend server can commutation with other services, so, this is a large challenge to solve web DRM.
Has anyone met this problem? And how do you resolve it?
refer from Web Origin Explainer: Practical Issues and Possible Solutions
refer from Is it possible to connect to LCP server? #161
The text was updated successfully, but these errors were encountered: