-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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.
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
Brave Extension Store #15187
Comments
Regarding the part of it working well to the best of your knowledge, more than a couple of times now I've been forced to remove an extension because a short notice appeared implying the they might have malware, out of fear I thought bugger it I wouldn't be able to tell if something malicious was happening behind the scenes. One of the extension I hadn't used in a while and I think the others were related to tab management, it must have been Great Suspender which reduce memory. Avoiding screws ups like this will be appreciated. It would be good if you took the best parts Mozilla's Firefox Store and Google's Chrome Store in terms of UX and brought it into Brave's Webstore. If this mean we're/you're going to have to communicate with every extension developer about additionally pushing their solutions and future updates into Brave's future store, enticing them with BATs may be a good idea. I always thought Brave should figure out a way to pay extension developers as so many of them don't receive the credit they deserve. Questions -
|
+1 from Community. https://community.brave.com/t/brave-extension-store/271104 @bsclifton, could you take a look at the questions of a Community user below whenever you have the opportunity?
|
If you hosted your own web store, it would make sense to host at least the extension files on IPFS. This could reduce your server load, plus it'd be a great way to promote IPFS after having added support for it to Brave. Even if the main page's html isn't completely hosted on IPFS, at least hosting the extensions themselves and some of the resources used by the page (javascript, images, etc.) on IPFS would be nice. |
The chrome extension store is full with bloat and data harvesting crappy addons while google likes to remove perfectly fine addons like "Youtube auto like" for some stupid reasons. |
Just realize that something like this would take time, effort, and money from the Brave team. They would have to review all the extensions submitted and they wouldn't get much benefit from hosting this - Chrome users will probably keep using the Chrome Web Store. |
I would like to note that, now that the Chrome Store has stopped accepting new Manifest v2 addons, there is no path to publish these addons in Brave either. Installing external addons is theoretically possible but practically not. Thus, either a working Brave Store or an easy way to install external Brave addons seems like an important priority. |
If it's possible, support for the edge extension store would fill the gap. Things like LibRedirect are available there but not on the Chrome Webstore because of Manifest v3. |
Unfortunately, Edge is planning to remove support for v2 extensions on the same timeline Google is. Their store will stop accepting new v2 extensions in July (see). Thus, this would be a temporary patch probably not worth the effort. |
Any update? |
A solution could be to allow users to update their extensions from Github Repo URL with a warning that those extensions are not vetted. Before Chrome M33 it was working well this way and relatively easy to setup: https://developer.chrome.com/docs/apps/autoupdate/#update_url I'm not sure but the restriction since Chrome M33 seem to only aplly to Windows platform and Mac (Not Linux). It could be a special flag to activate with a warning so it would be safe, users that activate flags are "power-users and not casual users. |
In addition it brave ext. store looking forward to have link to specific store from where the ext was installed currently it not have any link every time user need to search by ext id or name in chrome store. |
Why duplicate all the effort that the firefox team make at reviewing the extensions. Surely it would be easier to just add a compatibility layer to allow firefox extensions to run in brave. When i say easier, i know that would not be an easy task, just less effort probably than trying to reproduce everything that mozilla are already doing. I mean Firefox extensions are created using the web extensions API standard, which is based on the chrome extensions API which are very similar as far as i can see. so in theory it shouldnt be all that difficult. |
Mozilla made Firefox partially compatible with the Chrome API by adding a layer on top of their own extension API. Even then, they do not support the same APIs so Chrome devs wanting to port their extension to Firefox have to use Mozilla Compatibility tool. |
Would be nice to see If Brave does create an extension store, I hope it ia fully open source and allows others to self host their own extension store just like how othere can self host their own F-Droid repo. |
Sorry to bother, but I couldn't find an answer anywhere : how to actually create an extension install page ? I suppose it doesn't only consist in serving a CRX file, like a userscript & userstyles store would serve By the way, now that I think about it, I'd say that also offering userscripts and userstyles in a web store could be nice. Thanks |
Since chrome introduce manifest v3 and force developer to use it, I believe brave should came out with its own extension store. Plus chrome webstore is not that great since it still got a lot of spam/fake/scam extension in the store anyway. |
any update on the extension store? we still cannot enable installed extensions directly by turning on developer mode in windows and mac. |
Closing as stale for now - no work planned here at the moment We do have a backup plan for manifest v2 - some additional UI in the browser (no store needed). |
How will developers be able to publish their Manifest V2 extensions then ? |
@2br-2b @KaKi87 see here for more infomation: |
How are the authors of Manifest v2 extensions, other than the four specific ones that are special-cased in that ticket, supposed to publish extensions people can use in Brave? This is obviously not solving the problem of individuals being able to keep publishing extensions. |
Instead of running a whole another store, I will suggest to do what Firefox devs did and allow extensions to be installed from any website that hosts a extension. The current solution only seems to be making a special case for 4 selected extensions, leaving out numerous others in the dust. |
@uBlock-user Is this still a thing? This seems like a massive security issue. |
@Comprehensive-Jason what thing ? and what massive security issue ? |
Letting people install extensions from random websites is indeed a massive security issue. |
@bsclifton So how will developers be able to add and update their extensions to this list ? @deathtrip @Comprehensive-Jason Not really : using an extension store doesn't prevent malware from being published. |
That said, I asked years ago how to create an extension store that the browser would detect (including here), and didn't get any answer. |
What is this backup plan? We're developing an incredible new extension-based product which requires some v2 features. Thanks. |
Description
Currently, Brave is relying on the Chrome Web Store. This is working well and to the best of our knowledge, we have the same policies for loading extensions as Chrome/Chromium (please file an issue if not!).
There are a few reasons we might want to host our own extension store:
Miscellaneous Information:
See #28 for a previous version of this issue. We did some initial investigation work which is linked there 😄
The text was updated successfully, but these errors were encountered: