Publish IPFS companion on the Microsoft Edge Addons store

[ghost]

It is now possible to submit and publish chromium extensions for the new Microsoft Edge. https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/publish-extension

Starting January 15th the new browser will replace the existing Microsoft Edge through a windows update (not a feature update). They also plan on making the browser available on Linux in the future, and have comitted to releasing apps on linux as seen with the release of microsoft teams on linux.

[DavidBurela]

Would be great to see this included in the Microsoft store.
Metamask & ipfs comanion are the 2 extensions left I have from the Chrome store.

EFF just added their Privacy Badger extension to the store :-) EFForg/privacybadger#1290 (comment)

IPFS companion extension most likely will be able to be submitted without any modifications.
https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension

Also, access to your extension submissions dashboard, info, etc. can be found at
https://developer.microsoft.com/en-us/microsoft-edge/extensions/

Disclaimer: Software Engineer at Microsoft. But have no relation with the Edge team.

[lidel]

@DavidBurela iiuc publishing at Microsoft store requires a paid account:

• https://docs.microsoft.com/en-us/windows/uwp/publish/account-types-locations-and-fees:
  • Individual account: $19 USD
  • Company account: $99 USD

Is this the same for open source projects such as IPFS? Should we get "Company account"?

Docs are unclear how sharing publishing rights between multiple users work. All I was able to find is a mention of Azure Active Directory:

In order to add and manage account users, you must first associate your Partner Center account with your organization's Azure Active Directory.

Not a Windows person, so would appreciate guidance here :-)

[lidel]

Continued in #1005

[DavidBurela]

@lidel can you check the issue number, that one gives a 404

[lidel]

Indeed, for some reason it got removed(?)
Let's reopen this one then.

[Mikaela]

It looks like #1005 is back