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.

Sign up for GitHub

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

Jump to bottom

Intercept URLs for JS libs at public CDNs #674

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

Intercept URLs for JS libs at public CDNs #674

lidel opened this issue Jan 31, 2019 · 4 comments
Labels
exp/intermediate Prior experience is likely helpful help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked

Comments

@lidel
Copy link
Member

lidel commented Jan 31, 2019 •
edited
Loading

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
@lidel lidel added kind/enhancement A net-new feature or improvement to an existing feature exp/intermediate Prior experience is likely helpful P3 Low: Not priority right now help wanted Seeking public contribution on this issue labels Jan 31, 2019
@lidel lidel mentioned this issue Jan 31, 2019
Closed
@lidel lidel added the status/ready Ready to be worked label Feb 10, 2019
@autonome autonome mentioned this issue Apr 1, 2019
Open
@Mikaela
Copy link
Contributor

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
Copy link
Member Author

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.

@Mikaela Mikaela mentioned this issue Sep 19, 2019
Closed
@autonome
Copy link

Decentraleyes fork using IPFS:

https://www.reddit.com//r/ipfs/comments/hu7bij/a_fork_of_a_fork_of_the_web_extension/

@Mikaela
Copy link
Contributor

Mikaela commented Jul 21, 2020 •
edited
Loading

GitHub repo link to the Decentraleyes fork: https://github.com/IPFS-Forced-Adoption/IPFS-CDN

I will be following it with interest

@galargh galargh moved this to To do in IPFS-GUI (PL EngRes) Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
exp/intermediate Prior experience is likely helpful help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: Needs Grooming
Milestone
No milestone
Development

No branches or pull requests
3 participants
@autonome @lidel @Mikaela