Add ipfs-companion chrome extension id to accepted origins for future manifest v3 version #8689
Labels
effort/hours
Estimated to take one or several hours
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
P1
High: Likely tackled by core team if no one steps up
topic/rpc-api
Issues related to Kubo RPC API at /api/v0
Milestone
Manifest v3 removes support for the blocking webRequest api. We are currently using this api to intercept requests and modify the Origin URL to that of the ipfs-webui. With support for this feature gone we need another way for companion to make api requests to ipfs.
I'm proposing that we add the chrome-extension-id (which is generated once on upload to the chrome web store) to the default allowed origins. This way companion can still be useful for users when manifest v2 is deprecated, and they will not have to manually update their configurations.
I have discussed this a bit with @lidel on slack, but wanted to get the ball rolling here so that we can have the ability to get ipfs-companion manifest v3 into the chrome store (if only as a beta channel for power users) by the end of Q1.
For further context: ipfs/ipfs-companion#666 (mv3 tracking issues)
The text was updated successfully, but these errors were encountered: