Open Dakkaron opened 4 years ago
I think that is a good idea!
I installed all addons in the default list. The only one that doesn't install at all is MYKI Password Manager. That's a lot better than I expected. How many of the other ones actually work is a different thing I didn't get around to test so far.
Yeah, we can pare down that list if things just plain don't install. I threw MYKI off the list.
If we had something on the add on manager screen pointing to docs about how to set up your own collection, and made it easy, we could pare down the list to the ones that really work, and let people set their own list if they want to play with broken ones (or, say, are those add-ons' devs).
Should we rename this to "Please report broken add-ons here" and sticky it? I've seen a few posts in other issues where people reported broken issues.
That would make sense. I didn't know we could sticky issues.
History Block ( https://addons.mozilla.org/en-US/firefox/addon/historyblock/ ) can be installed, the settings screen can be opened, but new domains can't be added and import also does not work, the list of the blocked domains just stays empty.
tabliss is not working.
I've pulled Tabliss because it doesn't seem able to take over the new tab page.
History Block I am going to leave for now; that sounds like a bug the add on devs might be able to fix.
Tabliss will never work if the intention of that add-on is to modify the new tab page. The new tab page is not part of the browser engine but rather a native android screen. A lot of add-ons will not work in Fenix due to this reason. Things like themes, and a lot of about:config settings that affect parts of the browser that is no longer governed by the browser engine will not work. Changes to the new tab screen can only be done by modifying the app, and likewise any potential themes can only be created by adding appropriate resources and modifying the app, for example.
Cookie AutoDelete may cause that app crash after browsing a webpage a few seconds later.
https://github.com/mikecrittenden/shortkeys I'm really dying to use shortkey extension to iceraven https://github.com/mikecrittenden/shortkeys but option page briefly load than disappears anyone has a fix PLEASE?
Could someone add this to the repo and link to it in the README.md
?
.github/ISSUE_TEMPLATE/addons-request.md
---
name: addon-request
about: Use this template to request for add-on support.
title: 'Feature request'
labels: enhancement, add-on
---
Cookie AutoDelete may cause that app crash after browsing a webpage a few seconds later..
@baopaau That can be prevented if Cleanup Notifications are disabled in the add-on settings
Buster: Captcha Solver for Humans doesn't work on v1.4.0. I can't even install it, it says "Failed to install Buster: Captcha Solver for Humans".
@mfymn I can reproduce this. I've taken Buster off the list.
universall bypass doesn't work on v1.6.0
imtranslator can be installed but doesn't work on v1.6.0
cookie quick manager also doesn't work on v1.6.0
SoundCloud Downloader (https://addons.mozilla.org/id/android/addon/soundcloud-dl/) can be installed but doesnt download songs / album. instead, it stuck on full bar and never do anything. tested with v1.7.1
video downloadhelper cannot be downloaded at version 1.7.1
im translator still doesn't work on version 1.7.1
Search by Image the popup windows sometime cannot appear or when trying to search image its just back to current page
IceRaven Version 1.10.0
video downloadhelper cannot be downloaded at version 1.10.1
Multi Container extension(by Mozilla) doesn't work well. almost unusable :(( Also facebook container is unavailable
video downloadhelper cannot be downloaded at version 1.11.1
im translator still doesn't work on version 1.11.1
Webtoepub same to work but after the loading of the packing the download does not start.
Video download helper still doesn't work
Hi guys,for me xbrowsersync is not working. When i'm trying to complete the sync (sync id + password) it always give a generic error such as "Something went wrong,if the problem persists please report the issue"
Multi Container extension(by Mozilla) doesn't work well. almost unusable :(( Also facebook container is unavailable
Multi Container extension(by Mozilla) version 8.0.2 fails to install on iceraven-1.14.0 (Build #2015847283)
Hi guys,for me xbrowsersync is not working. When i'm trying to complete the sync (sync id + password) it always give a generic error such as "Something went wrong,if the problem persists please report the issue"
I have the same issue as well, I have a rough theory that its because the mobile browser needs a switch to manually turn off sync, otherwise it's not going to work
Dear developer, Hello, Video DownloadHelper cannot be installed normally, I hope it can be solved, thank you. Browser version number: iceraven-1.15.0 (Build
LibRedirect (add-on link) is an alternative to Privacy Redirect and is more actively maintained. It also supports a lot more alternative front-ends, like Piped (for Youtube), Proxitok (for TikTok), Rimgo (for Imgur), and Scribe (for Medium). It also has a button for quickly switching instances
Is there any problems with using Popup blocker (Strict) instead? Would rather like to avoid extensions like these.
in the past versions of iceraven/ff this extension worked for me can someone tell if possible to fix install in newer version ? im always getting error ...
And for extension update
This extension replace universal bypass because it got discontinued :)
Knowing that in our day-to-day we need several essential resources that make our life easier in navigation and some of these resources were implemented recently and therefore do not need to be placed on the list, such as: the mode-only-HTTPS, making HTTPS Everywhere obsolete in addition to the uMatrix extension that is outdated and discontinued for everyday use to block ads and because the developer only maintains uBlock Origin, which already does the job and always has a recent update, in addition to being recommended by the Project Arkenfox. That's why I write this message, because they need to be urgently removed, these specific extensions from the current list, because they are outdated and without recent updates and that can do the opposite of what they should do, which is: protect the privacy and security of the user. Here they are separated by categories: before, after Android FF rebuild, discontinued and broken.
•Long time no update of extensions, before FF rebuild for Android
PageZipper →last update 8/25/2016
behavioral-keyboard-privacy →last update 9/22/2016
Expire history by days →last update 6/20/2017
Chrome UA on Google for Firefox Android →last update 7/4/2017
Video Resumer →last update 9/20/2017
IPvFoo →last update 9/26/2017
Fennec Copy Link Text →last update 11/27/2017
External Video Player →last update 24/2/2018
Simple Mouse Gestures →last update 7/3/2018
Taille maximum d'image →last update 4/4/2018
Text Link webext →last update 5/13/2018
Google Docs Viewer →last update 5/18/2018
Pull to Refresh →last update 3/6/2018
Refresh in URL bar for Android →last update 6/15/2018
NoHTTP → last update 8/19/2018
Fennec TextWrap →last update 9/15/2018
Clean YouTube™ - No ADS →last update 11/25/2018
ResultScroller →last update 12/15/2018
Privacy Settings →last update 12/16/2018
Etag Stoppa →last update 12/25/2018
Cookie Quick Manager →last update 11/7/2019
Privacy Possum →last updated 6/22/2019
Image Search Options →last update 6/28/2019
Private Bookmarks →last update 7/15/2019
Bandwidth Hero →last update 8/25/2019
Export Tabs URLs →last update 9/8/2019
Personal Blocklist (not by Google) →last update 11/1/2019
Invidition →last update 11/2/2019
HTTPZ →last update 12/11/2019
Smart Referer →last update 12/18/2019
Header Editor →last update 12/20/2019
Redirector →last update 26/3/2020
Unreddit →last update 5/20/2020
Cookie Cleaner (Cookie Eraser) →last update 2/2/2020
Dark Mode →last update 7/17/2020
Nitter Redirect →last update 7/26/2020
FoxyProxy Basic and FoxyProxy Basic →last update 7/29/2020 and 7/30/2020
Enhance Belfast Telegraph →last update 8/8/2020
CSS Exfil Protection →last update 8/24/2020
•Long time no update after FF rebuild for Android
Nano Defender for Firefox →last update 10/13/2020
I2P Proxy for Android and Other Systems →last update 11/6/2020
Privacy Labrador →last update 12/11/2020
Extensions with no recent update and which could be used as a script
Cookie Cleaner (Cookie Eraser) →last update 2/6/2020
Dark Mode →last update 7/17/2020
Nitter Redirect →last update 7/26/2020
FoxyProxy Basic and FoxyProxy Basic →last update 7/29/2020 and 7/30/2020
Enhance Belfast Telegraph →last update 8/8/2020
CSS Exfil Protection →last update 8/24/2020
Nano Defender for Firefox →last update 10/13/2020
I2P Proxy for Android and Other Systems →last update 11/6/2020
Privacy Labrador →last update 12/11/2020
Temporary Containers →last update 8/2/2021
Mute Tab (WebExtension) →last update 4/18/2021
Don't track me Google →last update 7/7/2021 (there is a script to put in FireMonkey, Greasemonkey, TamperMonkey or ViolentMonkey) FireMonkey uses Mozilla's API to use custom scripts, it's completely safe, constantly updated, and the best of open source.
Block Site →last update 7/12/2021
•Extensions with deprecation announcement by the developer
HTTPS Everywhere (discontinued by developer) →last update 6/14/2021
uMatrix (discontinued by developer) →last update 7/20/2021
•Broken extensions that don't make sense to use in FF for Android
ImTranslator →last update 4/19/2022 (breaking extension settings)
Flagfox →last update 4/29/2022 (breaking extension settings)
At the moment these are the ones I see that really need to be removed.
That's why I write this message, because they need to be urgently removed, these specific extensions from the current list
I respectfully disagree about a lot of these, especially when they have functionality that has not have added to the browser and is not present in quite the same way in any other available extension.
For example:
Expire history by days
Desktop Vivaldi has a built-in option to only retain the last x number of days of history on a rolling basis (i.e. If you select 90 days, on day 91, the original day 1 history disappears. On day 92, the original day 2 history disappears. And so on. So it's always 90 days or however many days the user decides on.).
However, no other desktop or Android browser has that option natively, to my knowledge. That makes access to this extension, which enables the same feature for Iceraven users who add the extension, very important for people who want to maintain a rolling history automatically. If you take that extension away from people, you take that option away from people, and Iceraven generally has been about adding options, not taking them away.
In a perfect world, that feature would be built-in to the browser (or at least part of a regularly updated extension), but Mozilla doesn't make adding those sort of things priorities anymore (If anything, they seem hostile to those type of features), Iceraven's lone developer isn't likely to have time to create and maintain it, no one is likely to volunteer a patch and keep it current so that Iceraven can gain and retain the feature natively, no one has created a new extension that works quite the same way, and so on and so forth.
So, while keeping the extension is not a perfect world ideal solution, it's the least bad solution in the world we have.
If someone wants to code and submit a pull request to make this a native Iceraven feature, or forks/creates a similar extension and provides updates, I'd probably change my stance.
I really don't like seeing extensions removed for which there are no other options to do what they do, though. It's basically the same as eliminating features.
Cookie Cleaner (Cookie Eraser) →last update 2/6/2020
The key feature on this extension that isn't reproduced elsewhere is the ability to automatically delete cookies older than x number of days on a rolling basis (See the previous extension explanation, but this is with cookies instead of history).
There is literally no desktop Chrome extension that does this and no Vivaldi option. It's only available for desktop Firefox and select mobile forks and testing browsers, and only in the form of this particular extension AFAIK.
There are lots of extensions that do the other things this one does, but not that one specific thing. Some people don't see the point, but they are looking at it from a privacy perspective (For which it would not be very effective) instead of from the perspective of people who like it more as an organizational thing, like the type of people who automatically delete emails older than a certain number of days, weeks, months, or years. It's a way of automatically moving on from stuff after a while without losing the advantages of near to mid-term data retention.
HTTPS Everywhere
That one's being maintained by the EFF through the end of 2022.
Its also worth mentioning that every extension that's on the list is on it because someone requested it. The project came out of people looking for Firefox alternatives after they axed thousands of extensions.
People understand that they use extensions at their own risk and that they may not be functional, or may only be partially functional (It's in the readme on the Iceraven GitHub).
Unfortunately, by blocking the use of all but a dozen or so extensions on Firefox stable (Combined with poor market share), Mozilla hasn't given extension developers much of an incentive to keep updating.
Iceraven is I think doing the right thing making these extensions available in a stable browser. People are capable of looking at things like update history, whether an extension has enough functionality left to be useful to them, and so on and so forth so they can make their own choices about which extensions they want to use and feel comfortable with, and which ones they don't.
I really only think extensions that have been shown absolutely not to work for anyone, or that contain known malware, should be removed from the list.
FYI: FireMonkey – Extension for 🦊 Firefox mentioned above was not found in the collection group
That's why I write this message, because they urgently need to be removed, these specific extensions from the current list
I respectfully disagree with many of them, especially when they have functionality that has not been added to the browser and is not present in the same way in any other available extension.
Yes. It is by debating and discussing that we reach a consensus. I understand that there are some extensions with important features that don't currently exist, natively in FF and in any other Android browser, but using extensions that haven't been updated since at least January 2021 is being kind of negligent. , because many of them are from the time when the old Fennec project was used, where it made sense to use them and that they were suitable for mobile, with the current API, which is no longer used in the PC version and that some developers already stated this clearly in their descriptions of their respective extensions, which are difficult to implement in the current FF for Android. What indicates the obvious are difficult and not impossible.
For example:
Expire history for days
Desktop Vivaldi has a built-in option to retain only the last x number of days of history continuously (i.e. if you select 90 days, on day 91, the original history of day 1 disappears. On day 92, the original day 2 history disappears. And so on. So it's always 90 days or however many days the user decides.).
However, no other desktop or Android browser has this option natively, to my knowledge. This makes accessing this extension, which enables the same feature for Iceraven users who add the extension, very important for people who want to keep a scroll history automatically.
A feature like this is interesting and cool, but it would be better to use it with a recently updated extension.
If you take that extension away from people, you take that option away from people, and Iceraven usually adds options, not takes them away.
Extensions that are not being updated regularly with a minimum period of 3 months and a maximum period of 6 months (at least at my discretion) from the last update released, should not be recommended to be used. Iceraven, in this issue is: 'Report broken add-ons here: sensible default add-on list'. This already shows what I mean.
In a perfect world, this feature would be built into the browser, but Mozilla no longer makes adding this sort of thing a priority (if any, they seem hostile to this sort of feature)
Just gather a lot of people and create a discussion in the repository mozilla-mobile/fenix and don't stop charging for action on the part of those responsible for the Fenix project.
the lone developer of Iceraven probably didn't take the time to build and maintain it
It's like the saying goes: "One swallow doesn't make a summer." I don't know how to program, but when I see a person who does what @interfect, proposes to do, it's surprising. He even put a detail that doesn't even have in other FF forks and doesn't even have in FF Nightly, which is the search for the extensions of this list, so you don't have to scroll to the end looking for such an extension, this is already to overcome the other forks and the FF itself.
no one is likely to offer a patch and keep it up to date so Iceraven can get and maintain the feature natively, no one has created a new extension that works the same way, and so on and so forth.
Often, it may be that the developer of the extension itself has not released its source code for others to fork, or does not have developers experienced in this type of subject.
If someone wants to code and submit a pull request to make this a native feature of Iceraven, or fork/create a similar extension and provide updates, I would probably change my stance.
That's the problem, who will put themselves ahead of this enterprise? Even I could change my concept, but I would have to see concrete results in practice.
I really don't like to see extensions removed for which there are no other options to do what they do.
I don't like it either, but seeing extensions of "Fennec" time, it's hard to support such a thing. Options may even have it, just look for it. Otherwise, it's better to go without some specific features than to possibly be invaded by a serious extension flaw that could lead to malware or spyware.
It's basically the same as eliminating resources.
Is it the same as eliminating resources? Not. It is one thing to take an important native resource and delete it where you should never do, another thing is to take an extension that many times may not have been made to the platform it was intended for and can get broken and not work properly. Why has Mozilla not put the web page save in .html and/or .pdf yet? Because of the "Pocket" bought in 2014. Why didn't they put export/import favorites? Because of Firefox Sync. Is it difficult to implement these basic functions? Yes. Is it impossible to implement? Not. They just need to dedicate themselves and really listen to what the user base asks for and not use telemetry because this is not solving anything, it just gets worse with each passing year.
Cookie Cleaner (Cookie Eraser) → last update 06/02/2020
The main feature of this extension that is not reproduced elsewhere is the ability to automatically delete cookies older than x number of days on an ongoing basis (see explanation of the previous extension, but this is with cookies instead of history).
There is literally no desktop Chrome extension that does this, and no Vivaldi option. It is only available for desktop Firefox and some mobile forks and test browsers, and only in the form of this specific AFAIK extension.
Yes, it's an interesting feature, and I saw that this extension is open source which is a great sign, too bad it hasn't been updated in a long time and in the description it says:
"Using this extension, it is possible to clear cookies from three different zones:
Definitions: -> Extensions zone: Extensions and packaged apps that a user has installed -> Protected Websites Zone: Websites that were installed as hosted apps
And how come extensions like 'I don't care about cookies', 'Cookie AutoDelete' and 'Cookies Manager' haven't implemented this feature yet? Are they unaware of such a feature? Could it be that by making a request to each of them, they could not implement it? There are several possible questions.
There are many extensions that do the other things this one does, but not that specific thing. Some people don't see the point but are looking at it from a privacy perspective (which wouldn't be very effective)
Yes, I agree that some extensions don't do what others do. Just because such an extension doesn't have such a feature doesn't mean it can be implemented later.
rather than from the perspective of people who like more of an organization thing, like the kind of people who automatically delete emails older than a certain number of days, weeks, months, or years. It's a way to automatically move forward without losing the benefits of short- and medium-term data retention.
It would be better to use these extensions you described in the form of scripts placed in FireMonkey, Greasemonkey, ViolentMonkey or TamperMonkey.
HTTPS everywhere
This one is being maintained by the EFF until the end of 2022.
Yes. But why keep without updating it, it makes no sense. It's better to get rid of it once and for all and continue with the development of the Privacy Badger, which will soon be another one that will seem to be abandoned.
It's also worth mentioning that all the extensions that are on the list are there because someone requested them.
It's not because they requested that they should be fully placed, it would have to do long tests and see if they really suit Mobile as SingleFile that works very well both on Desktop and on FF Android and is recently updated.
The project arose from people looking for alternatives to Firefox after having eliminated thousands of extensions.
Yes, that's why there are also Fennec F-Droid forks that say "Fennec" but only in the name of the old project and the Mull Browser, it has no conditions to access extensions but also access to about:config with little limitation.
People understand that they use extensions at their own risk and that they may not be functional, or may only be partially functional (it's in the readme on Iceraven GitHub).
Right. Why am I going to install an extension that doesn't work or is partially functional. If it works great, cool. Now, it works broken, with grotesque errors, it has to be discarded yes, like Flagfox and ImTranslator that are broken and that were not even made to support FF Android, let alone forks.
Unfortunately, by blocking the use of nearly a dozen extensions in Firefox stable (combined with a low market share), Mozilla hasn't given extension developers much of an incentive to keep updating.
Yes, unfortunately many extensions have been blocked, I created a discussion 1 year ago and believe that they have not responded so far, and if more people show up, it would be ok to do a vote on which extensions work properly for Mobile, now in relation to low market share is that the Mozilla Corporation, in a short time, lives on revamping the visual aspect of the browser forgetting that it's not just visuals that a browser lives, but resources, chatting, asking, interacting with users as many projects do is simple. But no, they insist on continuing with this telemetry thing, until they declare that they cannot continue with the development of the browser, then we will be left without a competitor to Chrome and then my colleague is just sorry.
Iceraven is I think doing the right thing making these extensions available in a stable browser.
In a way, providing up-to-date extensions: yes, outdated: no. People are able to see things like update history, whether an extension has enough functionality to be useful to them, and so on, to make their own choices about which extensions they want to use and feel comfortable with and which ones. they do not.
I don't agree with this, because from the moment someone requested the inclusion of such an outdated extension, they are wrong with the request they made. Because it has to see in her description if there is compatibility support for the current API used in Android and if this extension has regular updates.
I really just think that extensions that have been shown to absolutely not work for anyone, or that contain known malware, should be removed from the list.
I agree. If they don't work for anyone, there's no need for them to be on the list, especially if you have any that may contain malware or spyware.
A feature like this is interesting and cool, but it would be better to use it with a recently updated extension.
I agree, but to my knowledge no one has created a new extension with that functionality or updated an existing extension to add that functionality.
In the absence of either of those things, the choice is to use the non-updated extension, or to lose the feature completely. By including the extension in the list of available extensions, Iceraven is giving users the option to use it. They also have the option not to use it for security or other reasons.
If someone wants to develop a new extension that does what that one does, and update it regularly, that would be great. I'm sure we could get that swapped in for the one we're using on the default list if it popped into existence. But no one has shown a willingness to do that. It's sometimes very hard to get people to work on open-source projects for free. The Iceraven project iself (Not extensions, the core project) has been looking for volunteers to help interfect out for some time now, and hasn't gotten any takers.
In the absence of a) Mozilla incorporating things like this into it's upstream browser, b) Someone volunteering to code it for Iceraven, c) Creating a new extension/updating an existing one to add the new functionality in a more up to date implementation; there is going to be some reliance on the part of some users on old extensions like this one. Their availability is actually what draws a lot of users to Iceraven.
Extensions that are not being updated regularly with a minimum period of 3 months and a maximum period of 6 months (at least at my discretion) from the last update released, should not be recommended to be used.
I think you're going to have rough sledding getting that sort of standard adopted in a browser that came into being in part to let people use old extensions. Implementing a rule like that would probably cause half the user base to bolt instantly unless of course a vibrant ecosystem of regularly updated extensions could be created to replace the old ones, but people would need to create and update them and no one is stepping up.
Just gather a lot of people and create a discussion in the repository mozilla-mobile/fenix and don't stop charging for action on the part of those responsible for the Fenix project.
I'm, seemingly permanently, banned from that repo (Long story). I would imagine I'm not the only one. If you or someone else wants to go over there and make a bunch of feature requests, that's up to you. It's outside the realm of what they will allow me to do personally.
I think it's also worth noting that even before being banned there, when I would make a simple request, it went something like this:
https://github.com/mozilla-mobile/fenix/issues/12811
Still open, two years later.
Someone submitted a patch to them to add the feature, they rejected it. It was one of the first patches incorporated into Iceraven and works well to this day.
I don't think it's so much that Mozilla hasn't heard these type of ideas as that their target demographic for their browser isn't people who want them. They have a different vision. That's implicitly why a lot of the forks that exist exist, to cater to groups that Mozilla isn't catering to with their main Firefox project, while incorporating the Mozilla code and updates that they need to in order to keep projects viable.
Iceraven, in this issue is: 'Report broken add-ons here: sensible default add-on list'.
Broken, not simply not updated recently.
Why has Mozilla not put the web page save in .html and/or .pdf yet? Because of the "Pocket" bought in 2014. Why didn't they put export/import favorites? Because of Firefox Sync. Is it difficult to implement these basic functions? Yes. Is it impossible to implement? Not. They just need to dedicate themselves and really listen to what the user base asks for and not use telemetry because this is not solving anything, it just gets worse with each passing year.
I agree that it'd be nice if the Mozilla folks implemented those things in Firefox, which eventually we would also get downstream in Iceraven. However, the Mozilla folks aren't implementing them. They've been suggested, the Mozilla folks either don't want to implement them, are divided on whether to implement them or not, or have other priorities.
It'd be cool if Iceraven implemented them itself, but we're down to one developer right now (We used to have three) and he's been pretty clear that he doesn't want to devote the extra time to do expansive stuff like that right now. He's not against adopting features like that, he's just not personally going to do them (Keep in mind he's working for free and has a day job that isn't this.). He'd happy to have a volunteer to do it, though. Go find him one or more people if you can. I've tried and failed to find them.
Video downloadhelper addon is broken for a long time. Please fix it. It's an essential addon for me. #
@bonyjose, the problem with the extension being broken for so long is her own, and it's not Iceraven's in itself. In this case, you would have to contact the developer of the extension and see if it will provide proper support to use it in the FF version for Android.
@bonyjose just use NewPipe app. for downloads. https://github.com/TeamNewPipe/NewPipe#Description
Please await
Sponsorblock not in the list of addons after version 1.13.0. Installed in this version, works fine in version 1.17.0 but doesn't show up in the search list. Just in case, I attached logcat when manipulating the addons list. logcat.log
Hello, Any news on adding LibRedirect ? Thanks
Multi Account Containers is mostly unusable. The sync doesn't work, if it did, I don't really need access to the toolbar menu of the extension. Right now, it's impossible to create/manage containers, except for setting shortcuts.
I suggest to open another seperate thread for new-addon-requests. Would be easier to find IceRaven related issues.
Hello, I got "Failed to install Violentmonkey" on v2.1.0, thanks.
Floccus Bookmark Syncy addon not working. I cant login google or import file
Now that we all can set our own addon collections to experiment (thanks, @abhijitvalluri), it might be a good time to review the default list of addons. Quite a lot of them refuse to install or don't do anything when installed.
I am thinking that all addons that arent installable at all should be removed from the default list. Stuff that installs but doesn't do anything is debatable.
What do you think about that?