Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intercept URLs for JS libs at public CDNs #674

Open
lidel opened this issue Jan 31, 2019 · 2 comments
Open

Intercept URLs for JS libs at public CDNs #674

lidel opened this issue Jan 31, 2019 · 2 comments

Comments

@lidel
Copy link
Member

@lidel lidel commented Jan 31, 2019

Extracted from #570 (comment)

Summary

Intercept URLs from public CDNs like unpkg.com and load them from IPFS.

Detection

Two ways:

  • Seamless: work with CDN operators to expose assets on IPFS paths /ipfs/<cid>/**/*.min.js
  • Grunt: identify the most popular assets across free CDNs, create a JSON mapping between filename/URL and CID and ship it with ipfs-companion as additional hint for creating redirects.

Additional Resources

@Mikaela

This comment has been minimized.

Copy link
Contributor

@Mikaela Mikaela commented Apr 2, 2019

Will this conflict with Decentraleyes or is the plan to deprecate Decentraleyes? If it is, will there be automagic pinning of the newest versions of the libraries?

(Possibly related #682)

@lidel

This comment has been minimized.

Copy link
Member Author

@lidel lidel commented Apr 2, 2019

Good question. Decentraleyes is limited by the size of assets they can bundle with extension before it gets too big (resources/ directory).

Companion could improve on that by bundling only a small mapping file (but with much better coverage) and fetching the data from IPFS + pin/preload the most popular ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.