ipfs / in-web-browsers

Tracking the endeavor towards getting web browsers to natively support IPFS and content-addressing
https://docs.ipfs.tech/how-to/address-ipfs-on-web/
MIT License
349 stars 29 forks source link

Provide a list of things that we want/need changed in the Web Extension Spec #56

Closed flyingzumwalt closed 5 years ago

flyingzumwalt commented 7 years ago

related to #35

Given our experience building these web extensions, provide a list of things we want or need changed in the Web Extension spec in order to support IPFS in web browsers more cleanly. We will pass this list to the team who are working on the spec.

Example: Allow Web Extensions to provide protocol handlers.

lidel commented 7 years ago

Things identified during development of firefox add-on rewrite to WebExtension:

flyingzumwalt commented 7 years ago

need web workers to support webrtc

dignifiedquire commented 7 years ago

need fast, optimized webrtc data channels

daviddias commented 7 years ago
daviddias commented 7 years ago

@lgierth @flyingzumwalt what's the follow up to this thread? Shall we schedule a call?

ghost commented 7 years ago

We should make this into a comprehensive, prioritized list that we can point browser people too. Ideally with a brief description which features each of the items unlocks. There are things which are absolute dealbreakers (e.g. proper protocol handlers), and things which are important but not essential. The list should convey this importance and priorities.

ghost commented 7 years ago

We can then also use this list to track the outreach and progress for each of the items.

lidel commented 6 years ago

FYSA discussion moved to: