Common CDN assets (JS / CSS)

[Jonas Z]

In a decentralized web, nobody wants to rely on (not truly decentraliced) CDNs for their common JS and CSS assets. Why don't we mirror the most commen assets into a dat archive like this: dat://common-assets-jfowl.hashbase.io (most stuff taken from the Decentraleyes extension), so that everyone can use them and they don't end up re-dat-ed for each side where they are used?

Is hashbase enough for re-seeding these assets?
They take up ~ 20 MB, and I think many of us would be able to hypercored this on their own servers.

[Paul Frazee]

I see no reason not to do it, especially as we start using ES modules.

--
You received this message because you are subscribed to the Google Groups "Beaker Browser" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beaker-browser+unsubscribe@googlegroups.com.
To post to this group, send email to beaker-browser@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beaker-browser/5d907853-3594-4112-be6e-322405d8773d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.