Re: [Bug-gnuzilla] Icecat 45.2 urgently needed

2016-06-10 Thread Mart Rootamm
The problem with Firefox 44 and greater is, that Mozilla removed the cookie
prompt from core Firefox, namely the "Ask me every time" option for "Keep
[cookies] until:". This affects all browsers that use the Gecko rendering
engine, including Seamonkey.

The relevant bugs are here:
* https://bugzilla.mozilla.org/show_bug.cgi?id=606655 — comments against
removal start after Comment #44. Eventually, comments were restricted, and
discussion moved to the firefox-dev mailing list here:

https://mail.mozilla.org/pipermail/firefox-dev/2016-February/thread.html#3890

Another thread in February 2016:
https://mail.mozilla.org/pipermail/firefox-dev/2016-February/thread.html#3952

Relevant threads for March 2016:
https://mail.mozilla.org/pipermail/firefox-dev/2016-March/thread.html#4004
https://mail.mozilla.org/pipermail/firefox-dev/2016-March/thread.html#4003

* https://bugzilla.mozilla.org/show_bug.cgi?id=1249151 — bug to reintroduce
cookie prompts;
* https://bugzilla.mozilla.org/show_bug.cgi?id=1235199 — for SeaMonkey, but
contains a patch that 'reverts the parts from [bug] 606655 for [Internet]
suite.'

The cookie prompt has been a very important privacy feature in Firefox and
derivatives, because it allows people to choose whether to accept cookies
from a domain or not. People trained on this can also tell apart domains
that are generally ok, and those that are not.

Upgrading to 45 and greater deletes all previously accrued cookie
permissions, thus resulting in data loss and broken sites.

The only recourse has been to use Firefox 38.x ESR, because it has so far
retained the cookie prompt functionality.

-Mart.


2016-06-10 16:24 GMT+03:00 Mark H Weaver :

> On June 7, Mozilla released a batch of security updates on their ESR 45
> branch.  Upstream support for the ESR 38 has apparently been dropped.
> Several of the fixed bugs are labelled "critical" by Mozilla, and some
> are expected to allow arbitrary code execution by a remote attacker.
>
>
> https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox-esr/#firefoxesr45.2
>
> Therefore, GNU Icecat 38.x can no longer be used safely, and we are in
> urgent need of Icecat 45.2.
>
>   Mark
>
> --
> http://gnuzilla.gnu.org
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Suggestion: have a button for disable JavaScript

2016-06-21 Thread Mart Rootamm
Do you use a mobile or desktop browser?

The best extension for you is NoScript, available from
https://noscript.net or the Mozilla app repository, and listed on the
IceCat webpage:
http://directory.fsf.org/wiki/IceCat

NoScript blocks scripts and uses a built-in whitelist, which you can
edit on the fly as you browse the web. Some most-used web services are
included in the whitelist.

You basically won't even need to switch JavaScript on/off with this add-on.

NoScript is also available for Firefox / IceCatMobile as NoScript Anywhere:
https://noscript.net/nsa/

-M.

2016-06-21 18:21 GMT+03:00, Tiberiu-Cezar Tehnoetic :
> Hi again,
>
> I use GNU IceCat with JavaScript disabled and I found it to be difficult
> to temporary enable JavaScript (for webpages not working otherwise) by
> going to Menu -> Preferences -> Content -> Enable JavaScript.
>
> However, there is a GPL-licensed (no-restart) addon Toggle JS which adds
> a toggle JavaScript button to the main window.
>
> https://addons.mozilla.org/en-us/firefox/addon/toggle-js/
>
> I couldn't find this addon in the GNU IceCat addon repository (using
> Trisquel Abrowser repository).
>
> https://trisquel.info/en/browser
>
> Nor here:
>
> https://www.gnu.org/software/gnuzilla/addons.html
> https://directory.fsf.org/wiki/Free_Software_Directory:IceCat_extensions_%28proposed%29
> https://directory.fsf.org/wiki/IceCat
>
> But in all these repositories I found an addon which also includes
> JavaScript toggle button, along with Java, Cookies etc:
>
> https://github.com/ThatOneGuyDotNet/QuickJava
>
> Would it be a good idea to have an addon preinstalled and enabled in GNU
> IceCat for quick JavaScript enable/disable toggle? JavaScript could be
> still left enabled by default...
>
> Also, how can I propose ToggleJS to be addded to the free extensions
> repositories at Free Software Directory (FSD)?
>
> Please let me know. Thanks!
>
> Tiberiu
> --
> https://ceata.org
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] AMO blocks non-Firefox browsers

2016-02-22 Thread Mart Rootamm
Is this in any way related to a.m.o. requiring add-ons to be signed? I
recently tried with version 21 of Debian Iceweasel, and installing
add-ons worked there.

2016-02-23 2:44 GMT+02:00 David Hedlund :
> In fresh IceCat 38.6.0 profile, when I open
> https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/, I get a
> "Download" button (not the typical "Add to Firefox" button). When I click on
> "Download" I get this message:
>
> "The add-on downloaded from addons.mozilla.org could not be installed
> because it appears to be corrupt."
>
>
> --
> http://gnuzilla.gnu.org

--
http://gnuzilla.gnu.org


[Bug-gnuzilla] Cookie confirmation dialog loss in Firefox; affects GNU IceCat

2016-02-17 Thread Mart Rootamm
Hi there.
After Firefox 44.0 was released, it turned out, that it lost the
cookie confirmation dialog, and upgrading to version 44.0 also deleted
all per-site permissions for cookies. It's a reduction of privacy
options, and also introduces some dataloss.

All this was achieved in Mozilla Bug 606655
https://bugzilla.mozilla.org/show_bug.cgi?id=606655

Dataloss reported here:
https://bugzilla.mozilla.org/show_bug.cgi?id=606655#c44

After Firefox 44.0 release, many ferociously complained in Bugzilla,
and the bug was thereafter restricted to any new comments; any
relevant discussion was moved here:

https://mail.mozilla.org/pipermail/firefox-dev/2016-February/thread.html#3890

Note, that SeaMonkey also experienced the same backend/UI loss:
https://bugzilla.mozilla.org/show_bug.cgi?id=1235199

For the time being, people can stay with Firefox 43.0.4 or Firefox 38.6.x ESR.

There is, though, a strong possibility, that Firefox 45 ESR (based on
Firefox 45, planned to be released on March 8) won't have the cookie
confirmation functionality anymore.

I was thinking, that cookie confirmation dialogs should be retained in
IceCat, given that IceCat is much more privacy-conscious.

-M.

--
http://gnuzilla.gnu.org


[Bug-gnuzilla] IceCatMobile: Include NoScript by default?

2016-05-05 Thread Mart Rootamm
Should NoScript Anywhere be included by default in IceCatMobile, given
that it's more a privacy-oriented browser?

If so, then the IceCatMobile first-start/welcome page should contain a
notification about NoScript and some quick instructions, so that
people won't be confused that IceCat breaks their favourite websites.

-M.

--
http://gnuzilla.gnu.org


[Bug-gnuzilla] IceCatMobile and 'More Add-ons'

2016-05-05 Thread Mart Rootamm
The IceCatMobile link to "Get more Firefox Addons" [sic] takes to
https://directory.fsf.org/wiki/IceCat and not to
https://directory.fsf.org/wiki/IceCatMobile .

Suggestion for the target URL to be
https://directory.fsf.org/wiki/IceCatMobile#Related_Projects , as this
will allow the browser to jump to 'more addons'.

-M.

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] thoroughly remove EME

2016-05-05 Thread Mart Rootamm
WebGL is important for very modern websites, such as the Independence Day:
Resurgence site warof1996.com. WebGL should be turned off by default, with
a UI option to turn it on in the desktop version, if a site wants to use it
— the way it currently does with plugins, and if the computer supports it
with all the necessary versions of relevant graphics drivers.

For about:newtab, sponsored ad code should be removed, but the newtab
itself kept, with a doorhanger showing where to switch it off, if need be.

For mobile, I prefer a very clean version, because my phone is rather
underpowered by today's standards. Maybe if WebGL and some other components
could be made optional as installable extensions (like DOM Inspector is in
the desktop version), because some people might want IceCat with WebGL, and
then some others also a variation of Pocket / Hello!/Loop, but not
everything else.

WebGL and many other things can already be turned off with the Privacy
Settings extension.

The feature that I really want to get back, is cookie prompts ("ask for
each cookie"). This feature separated Firefox from most other browsers, but
was removed around Firefox 44 or 45.

-M.

2016-05-05 23:17 GMT+03:00 David Hedlund :

> I submitted this post to https://github.com/amq/firefox-debloat/issues/25
>
> On 2015-06-08 15:39, Orchidaceae Phalaenopsis wrote:
>
>> Dear Rubin,
>>
>> Congratulations! I wish you many happy years to come!
>>
>> I have recently seen firefox adding more and more unnecessary and
>> dangerous things so I have decide to work on a version of firefox
>> which deletes them.
>>
>> Then I discovered Icecat which shares a lot of my goals and I was able
>> to benefit from its source code. Thank you very much!
>>
>> Here are the components I propose for deletion and why:
>>
>> * EME/DRM - [freedom] - This is a sandbox intended to run some kind of
>> nasty binary from adobe used to block users from having full control
>> over videos they watch.
>> * NewTab - [freedom/privacy] - The "newtab" has been getting sponsored
>> adverts being put into it. It is a danger to privacy because when the
>> mouse hovers over them a connection is made to the advertisers page.
>> * HealthReport - [privacy] - Turned this off by default. I do not
>> believe something like this that reports statistics about usage should
>> be on by default.
>> * WebGL - [security] - Turned this off by default. The security
>> dangers of having this on are too high.
>> * Pocket - [freedom] - Pocket seems to be some kind of 3rd party
>> "cloud" service. This is a danger to freedom.
>> * Hello!/Loop - [superfluous] - I think you can technically run your
>> own loop server and all the source code is available so this is not a
>> freedom concern but in any case this is not required to browse the
>> web.
>>
>> To delete EME I did an rm -r on all the relevant directories, added
>> ac_add_options --disable-eme to the mozconf and cleaned up any
>> dangling references to the EME stuff. I think it is important that the
>> code itself not be compiled into the program even if it is not used.
>> "dead" code has been used in security vulnerabilities in the past.
>>
>> For NewTab I blanked out the XML inside content/newtab/newTab.xul and
>> deleted the unneeded files.
>>
>> The patch for HealthReport off-by-default is based on icecat, since
>> icecat already does this!
>>
>> To set WebGL off by default I edited modules/libpref/init/all.js.
>>
>> Pocket and Hello! were removed by rm -r'ing the modules and then
>> cleaning up dangling references:
>>
>> rm -r ./browser/components/pocket/
>>
>> rm -rf ./browser/components/loop/
>> rm ./browser/base/content/browser-loop.js
>>
>> --
>>
>> I am keen on learning about new candidates for removal. I have heard
>> that firefox will soon search users history and provide adverts based
>> on this - I intend to produce a patch/script to remove that too.
>>
>> I have included some patches and scripts here which I hope may be of
>> use or interested to folks.
>>
>> * https://github.com/orchid-hybrid/cozy-cub/tree/master
>>
>> --
>> http://gnuzilla.gnu.org
>>
>
>
> --
> http://gnuzilla.gnu.org
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] GNU IceCat finally on f-droid.org

2016-04-19 Thread Mart Rootamm
I have it. It's noticeably more responsive than Firefox, but much bulkier
in comparison; especially with certain (larger) pages when I try to scroll
them, as other apps will want to quit right then.

One issue is, that IceCatMobile fails to show its own user agent string,
and uses a UA string of non-free software, which skews server statistics. I
had to guesstimate the possible IceCat UA string for myself.

The good thing, though, is that I can have a custom UA string for some
sites that would otherwise display badly.

-M.

2016-04-12 14:09 GMT+03:00 David Hedlund :

> I just started https://directory.fsf.org/wiki/IceCatMobile: "Read the
> IceCat  page for full description;
> This page specifically lists IceCatMobile compatible add-ons. The F-droid
> download page is also provided."
>
> --
> http://gnuzilla.gnu.org
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] GNU IceCat finally on f-droid.org

2016-04-20 Thread Mart Rootamm
> That's intentional, and you're subverting a measure designed to protect
> your privacy by "fixing" this. Using the same user agent string as
> Firefox reduces your fingerprint.

Indeed, but the default IceCatMobile UA string is not even remotely mobile
(Windows 6.1, etc), causing many sites to display a desktop design where
they should not. AFAIK, IceCat does not include the default Firefox UA
string as an optional feature.

On one hand, a person who chooses to use IceCat is already moderately
computer-proficient, but it would be difficult to recommend this browser to
beginners, because "it breaks their site." Truth be told, even a person who
chooses Firefox over Android default or Chrome could also be classed as a
reasonably atypical user.

The site-specific overrides option is useful, though.

btw, is there any progress about Firefox 45+ not having cookie prompts viz
IceCat? I was kinda hoping IceCat would keep them prompts.

-M.

2016-04-20 3:32 GMT+03:00 Julie Marchant <onp...@riseup.net>:

> On 04/19/2016 06:22 PM, Mart Rootamm wrote:
> > One issue is, that IceCatMobile fails to show its own user agent string,
> > and uses a UA string of non-free software, which skews server
> > statistics. I had to guesstimate the possible IceCat UA string for
> myself.
>
> That's intentional, and you're subverting a measure designed to protect
> your privacy by "fixing" this. Using the same user agent string as
> Firefox reduces your fingerprint.
>
> --
> Julie Marchant
> https://onpon4.github.io
>
> Protect your privacy with GnuPG:
> https://emailselfdefense.fsf.org
>
>
> --
> http://gnuzilla.gnu.org
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] GNU IceCat finally on f-droid.org

2016-04-20 Thread Mart Rootamm
> That's why the mobile version of IceCat should copy the user agent
> string of a popular mobile browser, like the mobile version of Firefox.

But it doesn't on install :-\

2016-04-20 14:06 GMT+03:00 Julie Marchant <onp...@riseup.net>:

> On 04/20/2016 05:39 AM, Mart Rootamm wrote:
> > Indeed, but the default IceCatMobile UA string is not even remotely
> > mobile (Windows 6.1, etc), causing many sites to display a desktop
> > design where they should not.
>
> That's why the mobile version of IceCat should copy the user agent
> string of a popular mobile browser, like the mobile version of Firefox.
>
> --
> Julie Marchant
> https://onpon4.github.io
>
> Protect your privacy with GnuPG:
> https://emailselfdefense.fsf.org
>
>
> --
> http://gnuzilla.gnu.org
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] IceCatMobile is recognized as desktop browser

2016-04-21 Thread Mart Rootamm
I think the 'Request Desktop Site' menuitem won't work, because the default
user agent string does not contain the word 'mobile', and by default, it
contains a string for non-free software.

I know, it's supposed to be the most common string to reduce UA
fingerprinting, but eventually, it will be out of date and relatively easy
to distinguish.

-M.

2016-04-20 15:51 GMT+03:00 Narcis Garcia <informat...@actiu.net>:

> To follow thread with right subject:
>
> I see a "Request Desktop Site" option at main menu, but it doesn't seem
> to have effect.
> User Agent may need to only add or remove "Mobile" word when user uses
> "Request Desktop Site" option. And this option could be enabled by default.
>
>
> El 20/04/16 a les 14:44, Mart Rootamm ha escrit:
> > I understand what you mean. I got word from the same list about IceCat
> > not including its own UA string and using the most common UA string as
> > default, that —
> >
> >> That's intentional, and you're subverting a measure designed to protect
> >> your privacy by "fixing" this. Using the same user agent string as
> >> Firefox reduces your fingerprint.
> > [—as written by a seasoned specialist in these things.]
> >
> > Better to only keep the Firefox string, as IceCat is based on Firefox,
> > and Ff market share is very small. To avoid site breakage, most would
> > choose Firefox, while IceCat is for the privacy-conscious.
> >
> > -M.
> >
> >
> > 2016-04-20 5:51 GMT+03:00 Pirate Praveen <prav...@autistici.org
> > <mailto:prav...@autistici.org>>:
> >
> > Its not just about me. Don't you think its important to include by
> > default? Do you want every user to follow these steps so
> > IceCatMobile is recognized as a mobile browser?
> >
> >
> > On 2016, ഏപ്രിൽ 20 4:25:22 AM IST, Mart Rootamm
> > <martroot...@gmail.com <mailto:martroot...@gmail.com>> wrote:
> >
> > In about:config, go to
> >
> > general.useragent.override
> >
> > • There, tap on the setting, then long-tap to copy the parameter
> > name and value, and back these up in a text editor to some text
> > file (for future reference).
> >
> > • I use a UA string similar to this:
> >
> > Mozilla/5.0 (Android 4.4; Mobile; rv:38.0) Gecko/38.0
> > Firefox/38.0 IceCat/38.7.1
> >
> > This is essentially the default Firefox UA string for version
> > 38.0, with IceCat/38.7.1 appended to it.
> >
> > In Android versions below 4.4, Firefox for mobile uses 'Android
> > 4.4' as the general OS identifier; from Android 4.4 and up,
> > Firefox uses the actual Android version number. More here:
> >
> >
> https://developer.mozilla.org/en-US/docs/Web/HTTP/Gecko_user_agent_string_reference
> >
> > -M.
> >
> > 29.03.2016 16:30 kirjutas kuupäeval "Pirate Praveen"
> > <prav...@debian.org <mailto:prav...@debian.org>>:
> >
> > I know IceCat blocks browser based fingerprinting but I
> > think IceCatMobile should identify itself as a mobile
> > browser even if other identifying information are
> > suppressed. gitlab.com <http://gitlab.com> was showing its
> > desktop version making it difficult to use.
> >
> > 38.6.0 from fdroid.
> > --
> > http://gnuzilla.gnu.org
> >
> >
> > --
> > http://gnuzilla.gnu.org
> >
> >
> >
> >
> > --
> > http://gnuzilla.gnu.org
> >
>
> --
> http://gnuzilla.gnu.org
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] GNU IceCat finally on f-droid.org

2016-04-21 Thread Mart Rootamm
[Added a reply here, too]
I think the 'Request Desktop Site' menuitem won't work, because the default
user agent string does not contain the word 'mobile', and by default, it
contains a string for non-free software.

I know, it's supposed to be the most common string to reduce UA
fingerprinting, but eventually, it will be out of date and relatively easy
to distinguish.

2016-04-20 15:50 GMT+03:00 Narcis Garcia <informat...@actiu.net>:

> I see a "Request Desktop Site" option at main menu, but it doesn't seem
> to have effect.
> User Agent may need to only add or remove "Mobile" word when user uses
> "Request Desktop Site" option. And this option could be enabled by default.
>
>
> El 20/04/16 a les 11:39, Mart Rootamm ha escrit:
> >> That's intentional, and you're subverting a measure designed to protect
> >> your privacy by "fixing" this. Using the same user agent string as
> >> Firefox reduces your fingerprint.
> >
> > Indeed, but the default IceCatMobile UA string is not even remotely
> > mobile (Windows 6.1, etc), causing many sites to display a desktop
> > design where they should not. AFAIK, IceCat does not include the default
> > Firefox UA string as an optional feature.
> >
> > On one hand, a person who chooses to use IceCat is already moderately
> > computer-proficient, but it would be difficult to recommend this browser
> > to beginners, because "it breaks their site." Truth be told, even a
> > person who chooses Firefox over Android default or Chrome could also be
> > classed as a reasonably atypical user.
> >
> > The site-specific overrides option is useful, though.
> >
> > btw, is there any progress about Firefox 45+ not having cookie prompts
> > viz IceCat? I was kinda hoping IceCat would keep them prompts.
> >
> > -M.
> >
> > 2016-04-20 3:32 GMT+03:00 Julie Marchant <onp...@riseup.net
> > <mailto:onp...@riseup.net>>:
> >
> > On 04/19/2016 06:22 PM, Mart Rootamm wrote:
> > > One issue is, that IceCatMobile fails to show its own user agent
> string,
> > > and uses a UA string of non-free software, which skews server
> > > statistics. I had to guesstimate the possible IceCat UA string for
> myself.
> >
> > That's intentional, and you're subverting a measure designed to
> protect
> > your privacy by "fixing" this. Using the same user agent string as
> > Firefox reduces your fingerprint.
> >
> > --
> > Julie Marchant
> > https://onpon4.github.io
> >
> > Protect your privacy with GnuPG:
> > https://emailselfdefense.fsf.org
> >
> >
> > --
> > http://gnuzilla.gnu.org
> >
> >
> >
> >
> > --
> > http://gnuzilla.gnu.org
> >
>
> --
> http://gnuzilla.gnu.org
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] 1.: Cannot downgrade to IceCatMobile 38.8.0 with F-Droid / 2.: Bookmark 'star' in the menu is gone

2017-01-15 Thread Mart Rootamm
Hi.
While I thought it possible to get 38.8.0 as a separate APK from the
F-Droid website, then alas. Currently, the earliest is 45.5.1:
https://f-droid.org/repository/browse/?fdfilter=icecat=org.gnu.icecat

Somehow, 38.7.1 and 38.8.0 are still listed, but I don't know if
they're still downloadable via F-Droid, because I don't want to risk
uninstalling the app or messing with app data.

The F-Droid app has a setting to peruse the F-Droid archive. You can try that.

Here's also a list of alternative repositories compatible with F-Droid:
https://f-droid.org/wiki/page/Known_Repositories
The table also shows which of the repositories are trusted / unknown.

Make sure _not_ to uninstall, but to over-install the older version.
Because if you uninstall 45.6.0 first, then you will forever lose all
your user data for that app.

The "Copy profile" Firefox extension allows copying profile data to an
SD card, but doesn't help in migrating profiles. One comment for that
extension suggested using a general Android backup app.
https://addons.mozilla.org/en-US/android/addon/copy-profile/

A note just in case: do make sure, that the build you're downloading,
matches the CPU architecture of your device.

btw, did you come across problems only with 45.6.0, or with earlier
45.x versions on Android?

Which browser extensions do you use in IceCat? What kind of a device
you have, and what version of Android does it run?

-M.


2017-01-15 23:10 GMT+02:00, Philipp Schaefermeier :
> Dear Gnuzilla mailing list,
>
> I'm having some troubles with IceCatMobile 45.6.0 on Android 4. Crashes
> too often.
> I wanted to go back to a pre-40 version, but this is no longer possible
> with F-Droid.
> It gives an error message "unexpected end of stream".
>
> Another thing is the loss of the star-shaped button for bookmarks in the
> ...-menu right to the tabs no.
> Since version 40 it is lost. Tapping the empty space still removes/adds
> bookmarks but the icon is not visible anymore.
> I reported this to Firefox and Orfox, with no reaction, as this seems to
> happen on all FF>40. It's lost in IceCatMobile >40 too, so I report it
> here, too.
>
> Best regards
> Philipp
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] IceCat 45 IMPORTANT consideration: Keep cookie prompt "ask me every time"

2016-09-23 Thread Mart Rootamm
David Hedlund wrote:
> Consider to keep the code for cookies "ask me every time" from Firefox 43
> for IceCat 45.

Concur. This is a must-have feature, and one that should not have been
removed in the first place. If that functionality is kept in IceCat 45,
then there would certainly be more IceCat users.

-M.

2016-09-23 4:12 GMT+03:00 David Hedlund :

> From https://support.mozilla.org/en-US/questions/1118394
>
> hi, the ask anytime option for cookies was removed in firefox 44, which
> was supposed to happen for a long time (bug 606655).
>
> i would recommend the following setup instead: in the custom history
> options choose "keep until i close firefox" as a default option & set
> exceptions for the few sites where you want stay logged-in across sessions.
> this way you'll have less work to do over all and a privacy-minded setup
> after all.
>
> or as an alternative you could also take a look at an extension like
> https://addons.mozilla.org/firefox/addon/self-destructing-cookies/
>
>
> Lots of people complain about this. Consider to keep the code for cookies
> "ask me every time" from Firefox 43 for IceCat 45.
>
>
> --
> http://gnuzilla.gnu.org
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] IceCat v45 beta

2016-08-28 Thread Mart Rootamm
Are there 45 beta binaries available for Windows, too?

For me, there are two important features that I'm not willing to part with:
* The most important lost security function is the cookie confirmation
dialog, which Firefox did away with since Firefox 45;
* The other feature that was removed from Firefox was the tab
collections feature.

If these two things are kept in IceCat — especially the cookie
confirmation dialog — then it could differentiate IceCat from Firefox.

-Mart.

2016-08-29 5:26 GMT+03:00, Rubén Rodríguez :
>
> Hello everybody,
>
> after some radio silence that I apologize for, I recently took some
> vacation that I used to put time into free software projects. Combined
> with some more hours this weekend the output is a beta release of v45
> that is available here: http://jenkins.trisquel.info/icecat/binaries/
>
> The build needs testing, to check all the expected features and also to
> go through all the UI checking for links to Mozilla sites, or anything
> else that is against our policies -including any branding issues-.
>
> With that done we can publish the release, and leave secondary tasks for
> later work. The biggest of those tasks would be to test binary builds
> for windows, macos and android, as well as for distro packagers to make
> any necessary changes.
>
> Please download the sources and binaries and report back with your
> findings!
>
> Cheers,
> Ruben.
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] [VOTE] Tor code base

2016-11-14 Thread Mart Rootamm
Voting against: #2 and No, that is — per arguments by Gary Driggs.

Additional voting is here:
https://savannah.gnu.org/bugs/index.php?49604

The Tor Browser is its own thing, and its code base seems to have diverged,
though most of it is based on upstream Firefox ESR.

If IceCat were based on Tor Browser code, then it would be just a copy of
the same, and that's pointless, when there's really a need for a
general-purpose browser — albeit with greater privacy features than current
Firefox.

-M.

2016-11-15 0:05 GMT+02:00 Gary Driggs :

> I see this project having more in common with the Trisquel browser project
> than TOR browser. I haven't seen anyone list the pros or cons so I'll have
> to vote against if it's just arbitrary.
>
>
> --
> http://gnuzilla.gnu.org
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] concerning voting & further directions

2016-11-14 Thread Mart Rootamm
Concur on most points.

I support informed consensus, insofar as it would succeed in restoring some
previously built-in privacy features.

Simple voting as it's happening here and at Savannah, is not necessarily
democracy, because without any proper discussion, it's often uninformed,
and becomes simply a vote by majority, especially when a bad decision gets
made.

There are also people, who do use IceCat, but who don't vote, and who don't
partake in discussions in this list and elsewhere. The same applies to
users of upstream, but on a scale greater by orders of magnitude. When
something wrong happens to upstream, it's impossible to turn it back, and
users discover fairly late when useful functionality has been removed or
when bloat has been added.

There are things that should be in addons, and then there are things that
should not be. For example, cookie prompt code should be returned, stay
built-in, and be developed further. This would resolve an upstream
regression and increase the user base. If done right, more distros would
then pick IceCat as the defaut browser.

Whilst NoScript is an independently-developed add-on used by other
Gecko-based projects and should therefore stay as is.

wrt future IceCat, then instead of any one adblocker, NoScript should be
bundled, as it has a compatible license, it offers better security, and
most ads are blocked along the way, too. Some distros do that bundling
already. Choosing an adblocker is then up to each user and their preference.

-M.


2016-11-14 21:46 GMT+02:00 Ivan Zaigralin :

> This is just brain-storming, meant for comment only.
>
> I am not convinced voting over a bunch of small initiatives would be very
> effective, at any rate, I will abstain for now.
>
> I think before voting we need to have a consensus on the general direction
> as
> we are moving forward, which is not something we can solve with just
> applying
> the democracy. We've got some technical problems looming for a while now,
> and
> they need some love and care from the few people doing the actual work.
>
> The terrible lag behind the upstream releases was recognized as an issue
> for a
> while now, and it feels to me that part of the problem is that
> modifications
> applied to the upstream are too invasive. May be we can separate this
> project
> into 2 distinct subprojects:
>
> (1)
>
> This one applies the minimal possible changes to the upstream in order to
> make
> it FSDG-compliant. I haven't looked very carefully, but if it's anything
> like
> building FSDG-compliant thunderbird, then may be the following would be
> enough:
>
> (1.1) disable add-on page or replace it with a good page
> (1.2) build without official branding
> (1.3) add icecat branding, or leave it for (2)
>
> (2)
>
> Here we build the icecat proper, with all the extra privacy features.
> icecat
> branding can also be added at this stage, if it wasn't added earlier. I
> have
> nothing against putting the features inside addons, but I must insist the
> way
> it's being done right now is suboptimal. All these feature-imparting addons
> must be made in-house, have their own distinct namespaces, and should not
> replicate functionality provided by upstream addons. In particular, icecat
> signature addons should not prevent the user from installing and using any
> of
> the general-purpose ad-blockers, https enforcers, etc. If we close our
> eyes on
> its philosophical issues and bugs, LibreJS is how we do it right.
> spyblock, on
> the other hand, needs to go. The users should be able to choose whatever
> free
> ad blocker they want.
>
> This two-pronged approach would insure that users and distributions are
> getting the security updates in a timely manner. And may be we can find a
> way
> for the additional features to be packaged separately, and updated
> independently?
>
> --
> http://gnuzilla.gnu.org
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] [VOTE] Cookie prompt

2016-11-14 Thread Mart Rootamm
The cookie prompt vote is now here:
https://savannah.gnu.org/bugs/index.php?49603

-M.

2016-11-14 21:20 GMT+02:00 Mart Rootamm <martroot...@gmail.com>:

> Vote #1 — integrate old cookie prompt into the next ESR, and then develop
> it further. This will bring more users to IceCat.
>
> An add-on is not a good idea, because people not familiar with it would
> have to find it.
>
> The built-in cookie prompt would continue the tradition started by Mozilla
> Application Suite and continued in Firefox until recent years.
>
> -M.
> 14.11.2016 21:04 kirjutas kuupäeval "Daniel Quintiliani" <d...@runbox.com
> >:
>
>> Vote:
>>
>> We should:
>>
>> 1. Wait until we can integrate the old cookie prompt into the new ESR
>> code before a release
>> 2. Allow this feature to be removed and recommend a free addon
>>
>> I vote #2
>>
>> --
>>
>> -Dan Q
>>
>> --
>> http://gnuzilla.gnu.org
>>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Icecat future development

2016-11-15 Thread Mart Rootamm
I don't support..
..using Torbrowser as a base, because it is its own thing now. Since
torbrowser upstreams many of its patches, then it's just as good to
take stuff from upstream, as I see the requirement for a
general-purpose browser that's better, of less bloat, and has slightly
better security than vanilla firefox (aka upstream).

Because if IceCat were advertised as "This is just like Torbrowser",
or "Based on Torbrowser code", then this would give privacy-minded,
but mostly uninformed people a false sense of security.

That us why Torbrowser is separate, and should stay as such.

-M.

2016-11-15 9:05 GMT+02:00, David Hedlund :
> Vote for ng0's proposal on https://savannah.gnu.org/bugs/index.php?49604
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] IceCat website bugs

2016-11-18 Thread Mart Rootamm
Most of these problems
are due to what is called 'browser fingerprinting protection', but
which actually appears to be a simple user agent override. If GNU
IceCat's general override is something akin to only

Android; Mobile;

then many sites just won't accept that, because some actually require
the presence of 'Chrome' or 'Firefox', or even a specific operating
system version (Android 4.4, anyone?).

In my view, one of the ways to remedy this would be with a built-in
tool or add-on to provide a UI both in desktop and mobile that would
facilitate the creation and maintenance of site-specific overrides.
about:config exists already, but it's unwieldy and can scare novice
users.

Some sitees, such as Google and Wikipedia, may require 'Android 4.4'
for some of their functionality to work. Others require the presence
of Desktop Chrome to be able to play video. Yet others may want a
specific Firefox version.

-M.

2016-11-18 7:56 GMT+02:00, David Hedlund :
> For a handful of detailed website incompatibility see
> https://github.com/davidhedlund/Siteboogz/issues
>
> These browsers have been evaluated:
> * Abrowser
> * Firefox ESR
> * GNOME Web (control)
> * GNU IceCat
> * GNU IceCatMobile
> * Tor Browser
>
> Hopefully the link provided can be helpful for the IceCat developers to
> figure out why IceCat on these sites.
>
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Looking for gnuzilla filter lists

2016-11-17 Thread Mart Rootamm
Hi.
There are some backups of this on archive.org:

==blacklist.txt==
Overview:
https://web.archive.org/web/*/http://gnuzilla.gnu.org/filters/blacklist.txt

Latest from the 25 April 2016 snapshot:
https://web.archive.org/web/20160425221243/http://gnuzilla.gnu.org/filters/blacklist.txt
Version: 201604060706 (relatively current)

"Save link as..." should work.

The source of that file was..
"
! Partially based (taking only url based, third-party filters) on:
! https://easylist-downloads.adblockplus.org/easylist.txt
! https://easylist-downloads.adblockplus.org/easyprivacy.txt
! https://easylist-downloads.adblockplus.org/fanboy-social.txt;
"

==third-party.txt==
Only one snapshot of this archived on 21 February 2016:
https://web.archive.org/web/*/http://gnuzilla.gnu.org/filters/third-party.txt
https://web.archive.org/web/20160221135440/http://gnuzilla.gnu.org/filters/third-party.txt
and the version of that is 20140901

Overview of all files:
https://web.archive.org/web/*/http://gnuzilla.gnu.org/filters/*

-Mart.

2016-11-17 3:15 GMT+02:00, Collin M. Barrett :
> I am looking for the filter lists that used to be hosted below. It seems
> like that subdomain is no longer online. Are these lists gone, moved, or is
> this a temporary outage? Thanks!
>
>
> http://gnuzilla.gnu.org/filters/blacklist.txt
> http://gnuzilla.gnu.org/filters/third-party.txt
>
>
>
>
>
>
> ___
> Collin M. Barrett
> [collinmbarrett.com](https://collinmbarrett.com/)

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Icecat clear downloads unexpectedly destructive

2016-11-15 Thread Mart Rootamm
The workaround would be to move all downloads to another folder, and
then clear the list.
In addition, the "clear history" setting at exit shouldn't affect downloads.

-M.

2016-11-15 1:39 GMT+02:00, J.H. :
> Icecat android : no option to.remove items from
> download list only;
> clear downloads actually ERASES THE VERY DOWNLOADS from storage.
> - that doesn't correspond to desktop version behaviour at all
> - you wouldn't expect any than the download history affected by an option
> under the privacy menu
> - no confirmation dialog neither.
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] [VOTE] Cookie prompt

2016-11-14 Thread Mart Rootamm
Vote #1 — integrate old cookie prompt into the next ESR, and then develop
it further. This will bring more users to IceCat.

An add-on is not a good idea, because people not familiar with it would
have to find it.

The built-in cookie prompt would continue the tradition started by Mozilla
Application Suite and continued in Firefox until recent years.

-M.
14.11.2016 21:04 kirjutas kuupäeval "Daniel Quintiliani" :

> Vote:
>
> We should:
>
> 1. Wait until we can integrate the old cookie prompt into the new ESR code
> before a release
> 2. Allow this feature to be removed and recommend a free addon
>
> I vote #2
>
> --
>
> -Dan Q
>
> --
> http://gnuzilla.gnu.org
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] IceCat browser default on Windows 7?

2016-12-12 Thread Mart Rootamm
I agree with Daniel Quintiliani upthread.

In addition,
There are many computers with UEFI and some machines with Windows, that
won't allow installation or running of alternative (aka non-Windows)
operating systems.

Some machines are tablet computers, where changing the default OS is more
difficult, and which internal hardware is specific enough, that drivers for
free operating systems are non-existent.

Suppose the UEFI BIOS is password-protected by the employer, for example,
making it impossible to run an alternative OS from removable media, while
the employee is permitted to run FOSS software on said PC.

Other people who have purchased computers, might not remove the
pre-installed operating system; since a proprietary OS is present, and
that's considered part of the purchase price. A proprietary system is often
required to be present for study—in order to support friends, family, and
potential customers.

For yet others, changing the default operating system is a lot of work.
Repartitioning a main storage to install an alternative operating system
does entail risk; especially for people who are not experienced with that.

Several manufacturers have chosen not to support computers where the main
OS is not Windows.

Yet other people want a Free Software Gecko-based browser for general
browsing, hoping to get funtionality that's not present in Firefox anymore.
Lack of a Windows version thus reduces exposure.

btw, I just discovered in GMail, that if I click on the main field of
e-mail recipients, I can drag and drop recipients from CC and BCC fields to
the To: field. Convenient.

-M.

2016-12-13 3:39 GMT+02:00 Gary Driggs :

> Tails is pretty easy to use; https://tails.boum.org/
>
>
> On Dec 12, 2016, at 2:15 PM, Daniel Quintiliani  wrote:
>
> Seems like a lot of work and reading material for a Windows user who just
> wants to browse the web and not have to worry about corporate and
> government spooks. Plus there's the risk M$ is tampering with the virtual
> machine client, remember you still have UEFI too so it's possible.
>
> --
>
> -Dan Q
>
>
> On Mon, 12 Dec 2016 12:13:49 +0100, Narcis Garcia 
> wrote:
>
> In this needings situation I'd prefer one of following options:
>
> 1) Use directly the computer with GNU/Linux when needing to browse web
>
> 2) Use remotely (eg. vnc) the computer with GNU/Linux to browse web
>
> 3) Run a GNU/Linux virtual machine in Windows host to browse web
>
>
> Running FOSS in Windows, you are exposing this software to
>
> viruses/spammers/trackers customization out of your control.
>
>
> Most of Windows malware is prepared to modify user's aplications behaviour.
>
>
>
> El 11/12/16 a les 19:18, Daniel Quintiliani ha escrit:
>
> You think that people who, through no fault of their own, can only afford
> cheap laptops, or are stuck with Secure Boot and TPM because they lack
> technical expertise to build a computer, should be forced to use unfree
> browsers like Edge and Chrome, or the privacy settings of Firefox? I have
> two computers, one Win10 and one Xubuntu, both of which I built myself. I
> need the Windows computer for a few unfree things, mainly as a substitute
> for a television for my bedroom, and when I'm stuck with this pretty DRM
> machine for whatever reason, I'd rather use a GNU project browser than DRM
> and privacy risks like Edge, Chrome, and Firefox. Wouldn't you?
>
>
> --
>
>
> -Dan Q
>
>
>
> On Sun, 11 Dec 2016 11:55:09 +0100, Narcis Garcia 
> wrote:
>
>
> "IceCat is more needed on unfree OSes than free OSes"
>
> I don't subscribe this sentence. Completely not.
>
>
>
> El 04/12/16 a les 22:29, Daniel Quintiliani ha escrit:
>
> IceCat is more needed on unfree OSes than free OSes. That's why I was a
> little bummed to not see a Windows release of v45, when I have to use
> Windows I'd like a little freedom and privacy even if it isn't much.
>
>
> --
>
>
> -Dan Q
>
>
>
> On Sun, 4 Dec 2016 21:19:32 +0100, mdn 
> wrote:
>
>
> If I am not mistaken,Normally if windows has only one browser he
>
> launches the said browser.
>
>
> Uninstall any other browser (IE included) to uninstall IE go in the
>
> uninstall software section (in the control panel) there is a "add/remove
>
> windows components" button (up left) from where you can remove internet
>
> explorer (has well has others functions)
>
>
>
> Be careful and see to migrate one day to a gnu distribution.
>
> Good luck
>
>
> Le 04/12/2016 02:05, Petr Vláčil a écrit :
>
> Hello,
>
>
> I started using this browser as a main on Windows 7 PRO x64bit, but I
> can't click on set it as a default browser. Is there any chance to set
> IceCat as a default browser?
>
>
> Thank you in advance.
>
>
> Btw. I found this http://www.glump.net/howto/desktop/set-gnu-icecat-as-
> default-browser-in-windows-8-x , but I don't know, whether is this
> functional on Windows 7 PRO x64bit.
>
>
> --
>
> http://gnuzilla.gnu.org

Re: [Bug-gnuzilla] IceCat 45.5.1 for Windows?

2016-12-29 Thread Mart Rootamm
IceCat on Windows would be like wearing warm clothes in the cold in a
bad neighborhood. The bad neighborhood being a proprietary operating
system.

Many people don't have the means or the knowledge to move out of such
a neighborhood, but they'd like to enjoy some warmth, too.

-M.

2016-12-28 21:31 GMT+02:00, Daniel Quintiliani :
> So you wouldn't give a band-aid to someone who has just been raped?
>
> --
>
> -Dan Q
>
> On Wed, 28 Dec 2016 18:18:00 +0100 (CET),  wrote:
>
>> bleh... why would IceCat release on windows? that's like giving someone a
>> bandaid if they need a doctor. the amount of hard work the devs do will be
>> wasted on a release on a system that contradicts the very philosophical
>> values of IceCat. that effort should be spent better making IceCat better
>> where it matters.
>>
>> --
>> Securely sent with Tutanota. Claim your encrypted mailbox today!
>> https://tutanota.com
>>
>> 20. Dec 2016 12:25 by jw...@web.de:
>>
>>
>> > When will IceCat 45.5.1 for Windows be released? Or has Windows support
>> > been dropped? There is no Windows version to download in the repository
>> > > http://ftp.gnu.org/gnu/gnuzilla/45.5.1> .
>> >
>> > --
>> > http://gnuzilla.gnu.org
>> --
>> http://gnuzilla.gnu.org
>
>
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Unable to login to icecat mobile

2017-07-13 Thread Mart Rootamm
I never knew the IceCat browser ever required logging in to use.

-M.

2017-07-10 14:04 GMT+03:00, Pierre Lantin :
> Hello,
>
> Every time i try to login to icecat mobile, i see the dialog during 1/2
> second, then it loads indefinitely. I'm on Android 7.0 and the app
> version is *45.7.0.
>
> *Thanks.
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Icecat 52.x flashplayer plugin location

2017-07-20 Thread Mart Rootamm
I usually put it in $HOME/.mozilla/plugins

This should do:
http://kb.mozillazine.org/Determining_plugin_directory_on_Linux

I don't know, though, how it would work with IceCat, but it should be similar.

-M.

2017-07-19 19:38 GMT+03:00, Habs :
>
>
>
> On Wed, 19 Jul 2017 16:28:19 +0200
> David Hedlund  wrote:
>
>> We are against flash so its not included at all.
>>
>
> thanks for the one-liner - succinct!
>
> I didnt ask if it was included - I asked where I *should* put it (apart
> from the bin if I am to follow your train of thought) and at the same
> time explained where I had put it currently, to get it work.
>
> So once more with feeling, where would be the correct place
> to put it in the Icecat directory structure, or have I got it right
> already ?
>
>
> Cheers
> Habs
>
> PS: it did work in the previous version I had, before this latest one,
> without having to do what I have this time.  I'm guessing the 'we are
> against flash' will have documented somewhere that this was a
> collective decision for this release.and I missed it!
> -
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Firefox cookie prompt patch

2017-07-26 Thread Mart Rootamm
Oh, I forgot the link to the patch:
https://www.savarese.org/patches/firefox.html

-M.

2017-07-27 1:44 GMT+03:00, Mart Rootamm <martroot...@gmail.com>:
> Hi.
> A developer has been maintaining a Firefox cookie prompt patch. If
> this could be reintroduced into IceCat, then it would make IceCat
> awesome.
>
> -M.
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] doesn't show photo in olx.pl site

2017-05-01 Thread Mart Rootamm
Adrian, can you also list any extensions in your installation of
IceCatMobile?

I don't know what the Polish-language menu equivalents are, but the addons
list can be found, when about:addons is entered into the address bar.

I was able to see the images and image previews at the site you specified
without effort in an older IceCat version.

You should also know, that olx.pl includes or accesses content from
accounts.google.com and plus.google.com (the other Google domains "touched"
by olx.pl are www.google.com and www.gstatic.com ). I found all this out
through desktop NoScript. I had to manually deny inclusion of these domains
from olx.pl both in desktop and mobile versions of NoScript.

Application boundaries enforcing (ABE) is more difficult in Android
NoScript because of its more-or-less manual nature, as it requires copying
the specific ABE configuration line (text string) into a separate text
editor (VimTouch, by the way), following its somewhat strict syntax, and
then pasting it back into about:config.

-M.

2017-05-01 21:01 GMT+03:00 Adrian Linke <adrian.l...@poczta.pl>:

> https://www.olx.pl/elektronika/telefony-komorkowe/lodz/
>
>
>
> - Wiadomość oryginalna -
> Od:
> "Mart Rootamm" <martroot...@gmail.com>
>
> Do:
> "GNU IceCat Bugzilla" <bug-gnuzilla@gnu.org>
> Dw:
> "Adrian Linke" <adrian.l...@poczta.pl>
> Wysłano:
> Mon, 1 May 2017 10:01:46 +0300
> Temat:
> Re: [Bug-gnuzilla] doesn't show photo in olx.pl site
>
>
>
> Can you tell exactly the address where the image fails to display?
> Which add-ons do you use in IceCatMobile?
>
> -M.
>
> 2017-04-26 10:37 GMT+03:00 Adrian Linke <adrian.l...@poczta.pl>:
>
>> Hello. I'm use your web browser in android system. icecatmobile version
>> is 45.7.
>> Problem is on the olx.pl site, when we search some product.
>> In olx.pl don't previews/photos products.
>>
>>
>> --
>> http://gnuzilla.gnu.org
>>
>>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] doesn't show photo in olx.pl site

2017-05-01 Thread Mart Rootamm
Can you tell exactly the address where the image fails to display?
Which add-ons do you use in IceCatMobile?

-M.

2017-04-26 10:37 GMT+03:00 Adrian Linke :

> Hello. I'm use your web browser in android system. icecatmobile version is
> 45.7.
> Problem is on the olx.pl site, when we search some product.
> In olx.pl don't previews/photos products.
>
>
> --
> http://gnuzilla.gnu.org
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Adblocker

2017-09-15 Thread Mart Rootamm
What's the version of GNU IceCat, what is the operating system name and version?

-M.

2017-09-15 0:51 GMT+03:00, J. Garry :
> My ublock origin no longer works seemlessly. When I go to tools, add-ons &
> click on them the options are gone for all of them. When I use the right
> side dots, ubo doesn't even show up & it seems like the filters need to be
> updated. Is this some kind of google stunt or what? Please help, thanx.
>
> J. Garry
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] uBlock Origins 1.14.0 incompatible with IceCat 52.1.0

2017-09-02 Thread Mart Rootamm
There is great consternation amonst users and some developers about
the deprecation of XUL in Firefox and some derivatives, because many
useful extensions would be made incompatible.

It would therefore be great, if GNU hosted (or at least linked to)
both the XUL-compatible extensions, and those that support
WebExtensions.

The Firefox-derivative Waterfox browser project has decided to keep
support for XUL ongoing.

-M.

2017-09-02 15:38 GMT+03:00, mdn :
>
> Le 02/09/2017 06:51, David Hedlund a écrit :
>> This was quickly solved after I discussed with the author. I updated
>> https://directory.fsf.org/wiki/UBlock_Origin to version 1.14.4, it
>> should work with IceCat 52.1.0.
> Just to make a small note:
> It also works with the 1.13.7.rc4 beta version of UbO.
> Has for V57 when webextensions will be mandatory UbO works from version
> 1.14.3b1.
> Same thing for umatrix it needs to be upgrade to version 1.0.1rc1.
> With v57 HTTPS everywhere works only with version 2017.8.31.
> Have a good day.
>>
>>
>>
>> On 2017-09-02 00:06, Felix Fröhlich wrote:
>>> Greetings all,
>>>
>>> I recently noticed that uBlock Origins was labelled incompatible with
>>> IceCat 52.1.0. The author published a new version (1.14.0) which drops
>>> the support for any Firefox-based browser that does not support
>>> WebExtensions. It looks like IceCat page saw that version and updated
>>> uBlock Origins without (being capable of?) checking whether that version
>>> could actually be used.
>>>
>>> It was possible to reverse this update by downloading uBlock 1.13.8 from
>>> https://addons.mozilla.org/en-GB/firefox/addon/ublock-origin/versions/1.13.8
>>>
>>> and disabling automatic updates for it (not sure if disabling them was
>>> necessary), but it would be nice if -- until WebExtensions are supported
>>> by IceCat, of course -- IceCat would hold back add-on updates if they
>>> are marked as incompatible with the corresponding Firefox version (in
>>> this case, 52.1.0esr).
>>>
>>> Kind regards.
>>>
>>>
>>>
>>> --
>>> http://gnuzilla.gnu.org
>>
>>
>>
>>
>> --
>> http://gnuzilla.gnu.org
>>
>
> --
> Librement
> BERNARD
>
> ENG: Please be kind enough to use GPG for our future conversations:
> https://emailselfdefense.fsf.org/en/
> If this email isn't PGP signed then it isn't mine.
>
> -If you can't compile it dump it.
>
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] uBlock Origins 1.14.0 incompatible with IceCat 52.1.0

2017-09-02 Thread Mart Rootamm
David, why is Waterfox not fully free?

-M.

2017-09-03 5:11 GMT+03:00, David Hedlund <pub...@beloved.name>:
>
>
> On 2017-09-03 04:05, Mart Rootamm wrote:
>> Hi, Felix
>> I think your input would be welcome, though I'm not an integral part
>> of the GNU community, so I can't speak for GNU people.
>>
>> The Waterfox project is planning to open its own extensions store that
>> supports XUL. I wonder, if it would instead be possible to add UI
>> support for more than just one store.
>
> Waterfox is not fully free like IceCat. And IceCat 57 will support
> WebExtensions.
>
>> -M.
>>
>> 2017-09-02 22:48 GMT+03:00, Felix Fröhlich <felix.froehl...@convey.de>:
>>> On 02/09/17 15:40, David Hedlund wrote:
>>>> On 2017-09-02 15:36, Mart Rootamm wrote:
>>>>> There is great consternation amonst users and some developers about
>>>>> the deprecation of XUL in Firefox and some derivatives, because many
>>>>> useful extensions would be made incompatible.
>>>>>
>>>>> It would therefore be great, if GNU hosted (or at least linked to)
>>>>> both the XUL-compatible extensions, and those that support
>>>>> WebExtensions.
>>>> We have been heavily undermanned for maintaining IceCat add-ons on the
>>>> Free Software Directory. After hundreds of hours I'm not going to
>>>> spend any more time on legacy add-ons except highly relevant add-ons
>>>> like LibreJS.
>>> Is there any way I can help with this?
>>>>> The Firefox-derivative Waterfox browser project has decided to keep
>>>>> support for XUL ongoing.
>>>>>
>>>>> -M.
>>>>>
>>>>> 2017-09-02 15:38 GMT+03:00, mdn <bernardl...@openmailbox.org>:
>>>>>> Le 02/09/2017 06:51, David Hedlund a écrit :
>>>>>>> This was quickly solved after I discussed with the author. I updated
>>>>>>> https://directory.fsf.org/wiki/UBlock_Origin to version 1.14.4, it
>>>>>>> should work with IceCat 52.1.0.
>>>>>> Just to make a small note:
>>>>>> It also works with the 1.13.7.rc4 beta version of UbO.
>>>>>> Has for V57 when webextensions will be mandatory UbO works from
>>>>>> version
>>>>>> 1.14.3b1.
>>>>>> Same thing for umatrix it needs to be upgrade to version 1.0.1rc1.
>>>>>> With v57 HTTPS everywhere works only with version 2017.8.31.
>>>>>> Have a good day.
>>>>>>>
>>>>>>> On 2017-09-02 00:06, Felix Fröhlich wrote:
>>>>>>>> Greetings all,
>>>>>>>>
>>>>>>>> I recently noticed that uBlock Origins was labelled incompatible
>>>>>>>> with
>>>>>>>> IceCat 52.1.0. The author published a new version (1.14.0) which
>>>>>>>> drops
>>>>>>>> the support for any Firefox-based browser that does not support
>>>>>>>> WebExtensions. It looks like IceCat page saw that version and
>>>>>>>> updated
>>>>>>>> uBlock Origins without (being capable of?) checking whether that
>>>>>>>> version
>>>>>>>> could actually be used.
>>>>>>>>
>>>>>>>> It was possible to reverse this update by downloading uBlock
>>>>>>>> 1.13.8 from
>>>>>>>> https://addons.mozilla.org/en-GB/firefox/addon/ublock-origin/versions/1.13.8
>>>>>>>>
>>>>>>>>
>>>>>>>> and disabling automatic updates for it (not sure if disabling them
>>>>>>>> was
>>>>>>>> necessary), but it would be nice if -- until WebExtensions are
>>>>>>>> supported
>>>>>>>> by IceCat, of course -- IceCat would hold back add-on updates if
>>>>>>>> they
>>>>>>>> are marked as incompatible with the corresponding Firefox version
>>>>>>>> (in
>>>>>>>> this case, 52.1.0esr).
>>>>>>>>
>>>>>>>> Kind regards.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> http://gnuzilla.gnu.org
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> http://gnuzilla.gnu.org
>>>>>>>
>>>>>> --
>>>>>> Librement
>>>>>> BERNARD
>>>>>>
>>>>>> ENG: Please be kind enough to use GPG for our future conversations:
>>>>>> https://emailselfdefense.fsf.org/en/
>>>>>> If this email isn't PGP signed then it isn't mine.
>>>>>>
>>>>>> -If you can't compile it dump it.
>>>>>>
>>>>>>
>>>>> --
>>>>> http://gnuzilla.gnu.org
>>>>
>>>> --
>>>> http://gnuzilla.gnu.org
>>>
>>>
>> --
>> http://gnuzilla.gnu.org
>
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Speed problem.

2018-05-16 Thread Mart Rootamm
Γιώργος Κωστόπουλος, can you tell, what versions of each release were you
using? — Not just ESR, but the 52.x version; then also, if you had any
add-ons installed, and when exactly did the speed problems appear?

-M.
17.05.2018 1:59 kirjutas kuupäeval "Γιώργος Κωστόπουλος" <
giorgos...@gmail.com>:

> >
> > Could you try Firefox ESR
> > (https://www.mozilla.org/en-US/firefox/organizations/) and tell us if
> it's
> > faster? IceCat is based on Firefox ESR.
> >
> >
>
> Oh I see! Then we found the source of the problem! :-)
>
> Firefox ESR forcefully installed from repositories on Debian,
> somewhere in the middle of Jessie lifecycle, replacing IceWeasel (the
> now defunct Debian fork of Firefox).
> I tried Firefox ESR at past but I abandoned it, because it was very buggy.
> (First time on repositories after many years, without prior testing).
>
> I think I'll wait and when I'll get my hands to a more up to date
> Linux system, I'll try IceCat again.
> THANKS David for helping identifying the source of the problem!!!
> Bye! :-)
> G.
>
>
> >> IceCat from https://www.gnu.org/software/gnuzilla/
> >> Both official release binaries x64.
> >>
> >>
> >>> On 2018-05-16 19:30, Γιώργος Κωστόπουλος wrote:
> 
>  Hi! :-)
> 
>  I downloaded GNU IceCat x64 binary, before a few days for a test
> drive.
>  (I'm on Debian Jessie (oldstable) x64 KDE).
> 
>  While I'm generally satisfied with it, I have (only) one major
> problem:
>  It's very slow here. It's like having (a better) Firefox, but in slow
>  motion.
>  I tried also in Safe Mode (searching for a troubling addon), but I had
>  no gain in speed.
> 
>  I have no previous experience with IceCat, so I'm just reporting it.
>  Any opinions?
> 
>  TIA! :-)
>  G.
> 
>  --
>  http://gnuzilla.gnu.org
> >>>
> >>>
> >>>
> >>> --
> >>> http://gnuzilla.gnu.org
> >
> >
>
> --
> http://gnuzilla.gnu.org
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Android - cannot configure Add-ons - denied permission WRITE_SETTINGS

2018-06-12 Thread Mart Rootamm
Hi.

The best I can think of, is for you to back up all your information,
root your phone and then install a compatible version of LineageOS or
Replicant.

What is the model of your Xiaomi phone?

Keep in mind, that non-Android certified phones, and devices with
brand headquarters in non-democratic countries might come with malware
preinstalled.

https://techcrunch.com/2018/05/24/some-low-cost-android-phones-shipped-with-malware-built-in/

https://blog.avast.com/android-devices-ship-with-pre-installed-malware

Strictly In terms of nomenclature, that Xiaomi phone runs MIUI 9.5.5.0
based on AOSP 7.1.2, and is not Android-certified.

-M.

2018-06-12 1:21 GMT +03:00, c...@abwesend.de :
> Hello,
>
> In Android 7.1.2 (MIUI 9.5.5.0) I installed Icecat 52.6.0 from F-Droid.org.
>
> I cannot enter "preferences" of e.g. LibreJS addon, and also not of new
> add-ons I install, e.g. uBlock Origin.
>
> Only if I "deactivate" e.g. Gnu LibreJS addon and then "activate" again,
> "preferences" button is visible for a short time. Even if I click it and
> change something, it seems, IceCat cannot keep the settings.
>
> I never managed even betting dsiplayed uBlock Origin settings, or
> preferences/settings button under "addons", though.
>
> Two permissions are shown "denied permissiona" in Android permissions:
> - WRITE_SETTINGS
> - SYSTEM_ALERT_WINDOW
>
> I have tried all I could to grant any permssion. Also with root terminal:
> pm grant org.gnu.icecat android.permission.WRITE_SETTINGS
>
> That results in following error:
> "Operation not allowed: java.lang.SecurityException: Permission
> android.permission.WRITE_SETTINGS is not a changeable permission type."
>
> Is this my problem, Xiaomi MIUI 9.5.50 problem, Android 7.1.2 problem or
> IceCatMobile 52.6.0 problem?
>
> Has anyone noticed the same misfunction or is this a known issue?
>
> Thank you, cotw
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Android - cannot configure Add-ons - denied permission WRITE_SETTINGS

2018-06-14 Thread Mart Rootamm
cotw,

At one point, my running guess is, that even if EMUI and MIUI ARE
based on AOSP, then neither is entirely compatible with AOSP,
Replicant, or LineageOS.

cotw, Brennan

You can try running an earlier version of IceCat (or Firefox), and
test to see, at which version did the addons begin malfunctioning. See
if you can back up your browser-related information first.

If you have any app-related data that you want to maintain, but are
unable to back up, then install any IceCat or Firefox app package over
an existing version from about the same source. — If the initial app
source was F-Droid, then from there; if the app source was an APK
download, then from there again. And installing, do as if you'd be
upgrading, i.e., do not delete the package beforehand; or otherwise
you'll lose user data, if you wanted to retain any.

Another option is to try extensions that are more compatible with your
version of IceCat, including older versions thereof.

Go to about:config, and enter two new settings:

general.useragent.override.mozilla.org
general.useragent.override.mozilla.net

and populate them with the Firefox-only user agent (UA) string that
matches your version of IceCat. Each page for an extension has a link
to versions, where you can see a list of versions should be compatible
with your browser version.

Then at addons.mozilla.org, Mozilla shall show which of the add-ons
are compatible with your version of IceCat, as it would with that
version of Firefox.

Note, that some of the addons are WebExtensions.

-M.

2018-06-14 18:09 GMT +03:00, c...@abwesend.de :
> I guess there is going to be a new IceCat soon, as Fennec's last Extended
> Service Release 60 is out. I guess the sync that somehow, anyway forking a
> project like Firefox one can obviously not release in the same speed, unless
> you have a lot of manpower.
>
> In my old phone I had the same problem of the not showing configs for uBlock
> Origin with IceCat in EMUI (Android 4.4). But there uBlock was functional,
> and the configs accessible by toolbar button. And I don't have other
> add-ons.
>
> As I have a recent Android now, for me it is as good or better, to switch
> back to Firefox. In 4.4. the support for Firefox had been ceased, that's why
> I was attracted to IceCat in the first place. And it served me well for a
> year.
>
> I installed Firefox 60 and uBlock, everything works perfectly.
>
> Also I don't need or even want LibreJS but much less some add-ons, to make
> LibreJS work on some websites that no single human on my whole continent has
> ever heard of. And the Mozilla phoning home has been only mildly reduced in
> IceCat anyway. In IceCat it was necessary to tweak the prefs.js extensively
> all the same. So the added value to Fennec for me is not so big (if Addons
> worked).
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Icecat vs Icecat mobile behavior

2017-12-24 Thread Mart Rootamm
Hi, Brennan.

If and what kind of blocker extension do you use in mobile IceCat? Are
its blocklists updated?

Are there any OS-level blocker apps installed, such as Adblock Plus?

-M.

2017-12-19 23:11 GMT +02:00, Brennan :
> Hi all,
>
> I’ve been using Icecat on desktop for quite some time, and just recently
> began using it on android. I noticed some ads are coming through on mobile,
> but not on desktop. Is there a difference in the block lists being
> implemented in the mobile vs. desktop versions of Icecat? Is there some
> other detail I’m overlooking that would be causing this?
>
> I’m using Icecat mobile downloaded from F-droid, and the desktop version
> built on MacOS Sierra (10.12.6) but following the directions for High
> Sierra.
>
> Thank you for the awesome work you’re doing!
>
> B
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Bugs icecat mobile

2018-01-15 Thread Mart Rootamm
>> 1. In the browser there are no integrated add-ons ("https everythere",
>> for example). See screenshot.
>
> Thanks, I reported this to https://gitlab.com/fdroid/fdroiddata/issues/1088

I'd actually prefer IceCat to be clean of any add-ons, so that
installing any would be up to the discretion of each user. Since
IceCat is used mosty by expert users, then each has their own opinion
about which add-on they want installed, and which they _do not_ want
pre-installed. Pre-installing add-ons would be like distribution
builders forcing them upon users.

-M.

2018-01-15 3:57 GMT +02:00, David Hedlund :
> On 2017-04-03 05:51, Денис Чернов wrote:
>> Hi,
>> I've installed icecat 45.7.0 from f-droid.
>> 1. In the browser there are no integrated add-ons ("https everythere",
>> for example). See screenshot.
>
> Thanks, I reported this to https://gitlab.com/fdroid/fdroiddata/issues/1088
>
>> 2. You cannot install some extensions, for example - "user agen
>> switcher". It is downloaded, but not installed.
>
> The 'Get more Firefox Addons' button opens
> https://directory.fsf.org/wiki/IceCat (not all add-ons in there are
> IceCatMobile compatible) but it should be
> https://directory.fsf.org/wiki/IceCatMobile. I reported this to
> https://gitlab.com/fdroid/fdroiddata/issues/1085
>
> I could install
> https://addons.mozilla.org/firefox/downloads/latest/506646/addon-506646-latest.xpi
>
> from https://directory.fsf.org/wiki/Privacy_Badger
>
>> 3. You can't add search engine "duck duck go"
>
> I could add https://addons.mozilla.org/en-US/firefox/addon/duckduckgo-html/
>
>> 4. On the website www.vgae.ru not working likes - don't react on
>> clicking. See screenshot.
>>
> I don't have time to create an account to evaluate this.
>
>>
>> --
>> http://gnuzilla.gnu.org
>
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] IceCatMobile is recognized as desktop browser

2018-01-15 Thread Mart Rootamm
> How does M.Firefox deal with the "Request Desktop Site" switch?

I recall, that Firefox simply removes the 'Mobile' part of the string
from the referrer when requesting a desktop site. That does not have
an immediate effect when browsing Wikipedia, at which point I'd still
have to request a desktop site from a link on Wikipedia.

-M.

2016-04-21 21:48 GMT +03:00, Narcis Garcia <informat...@actiu.net>:
> How does M.Firefox deal with the "Request Desktop Site" switch?
> If Icecat has 1 UA string hard-coded, could be 2 UA strings prepared for
> each circumstance?
>
>
> El 21/04/16 a les 15:36, Mart Rootamm ha escrit:
>> I think the 'Request Desktop Site' menuitem won't work, because the
>> default user agent string does not contain the word 'mobile', and by
>> default, it contains a string for non-free software.
>>
>> I know, it's supposed to be the most common string to reduce UA
>> fingerprinting, but eventually, it will be out of date and relatively
>> easy to distinguish.
>>
>> -M.
>>
>> 2016-04-20 15:51 GMT+03:00 Narcis Garcia <informat...@actiu.net
>> <mailto:informat...@actiu.net>>:
>>
>> To follow thread with right subject:
>>
>> I see a "Request Desktop Site" option at main menu, but it doesn't
>> seem
>> to have effect.
>> User Agent may need to only add or remove "Mobile" word when user uses
>> "Request Desktop Site" option. And this option could be enabled by
>> default.
>>
>>
>> El 20/04/16 a les 14:44, Mart Rootamm ha escrit:
>> > I understand what you mean. I got word from the same list about
>> IceCat
>> > not including its own UA string and using the most common UA string
>> as
>> > default, that —
>> >
>> >> That's intentional, and you're subverting a measure designed to
>> protect
>> >> your privacy by "fixing" this. Using the same user agent string as
>> >> Firefox reduces your fingerprint.
>> > [—as written by a seasoned specialist in these things.]
>> >
>> > Better to only keep the Firefox string, as IceCat is based on
>> Firefox,
>> > and Ff market share is very small. To avoid site breakage, most
>> would
>> > choose Firefox, while IceCat is for the privacy-conscious.
>> >
>> > -M.
>> >
>> >
>> > 2016-04-20 5:51 GMT+03:00 Pirate Praveen <prav...@autistici.org
>> <mailto:prav...@autistici.org>
>> > <mailto:prav...@autistici.org <mailto:prav...@autistici.org>>>:
>> >
>> > Its not just about me. Don't you think its important to include
>> by
>> > default? Do you want every user to follow these steps so
>> > IceCatMobile is recognized as a mobile browser?
>> >
>> >
>> > On 2016, ഏപ്രിൽ 20 4:25:22 AM IST, Mart Rootamm
>> > <martroot...@gmail.com <mailto:martroot...@gmail.com>
>> <mailto:martroot...@gmail.com <mailto:martroot...@gmail.com>>> wrote:
>> >
>> > In about:config, go to
>> >
>> > general.useragent.override
>> >
>> > • There, tap on the setting, then long-tap to copy the
>> parameter
>> > name and value, and back these up in a text editor to some
>> text
>> > file (for future reference).
>> >
>> > • I use a UA string similar to this:
>> >
>> > Mozilla/5.0 (Android 4.4; Mobile; rv:38.0) Gecko/38.0
>> > Firefox/38.0 IceCat/38.7.1
>> >
>> > This is essentially the default Firefox UA string for
>> version
>> > 38.0, with IceCat/38.7.1 appended to it.
>> >
>> > In Android versions below 4.4, Firefox for mobile uses
>> 'Android
>> > 4.4' as the general OS identifier; from Android 4.4 and up,
>> > Firefox uses the actual Android version number. More here:
>> >
>> >
>> https://developer.mozilla.org/en-US/docs/Web/HTTP/Gecko_user_agent_string_reference
>> >
>> > -M.
>> >
>> > 29.03.2016 16:30 kirjutas kuupäeval "Pirate Praveen"
>> > <prav...@debian.org <mailto:prav...@debian.org>
>> <mailto:prav...@debian.org <mailto:prav...@debian.org>>>:
>> >
>> > I know IceCat blocks browser based fingerprinting but I
>> > think IceCatMobile should identify itself as a mobile
>> > browser even if other identifying information are
>> > suppressed. gitlab.com <http://gitlab.com>
>> <http://gitlab.com> was showing its
>> > desktop version making it difficult to use.
>> >
>> > 38.6.0 from fdroid.
>> > --
>> > http://gnuzilla.gnu.org
>> >
>> >
>> > --
>> > http://gnuzilla.gnu.org
>> >
>> >
>> >
>> >
>> > --
>> > http://gnuzilla.gnu.org
>> >
>>
>> --
>> http://gnuzilla.gnu.org
>>
>>
>>
>>
>> --
>> http://gnuzilla.gnu.org
>>
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] IceCat 38.8.0 bug

2018-01-15 Thread Mart Rootamm
Alex,

If you click on an anchor in IceCat 38.8, then the URL in the address bar
does change; so, if you activate the address bar (w/ blinking cursor) and
presss the return key on the keyboard, the browser will make the jump.
Thereafter, jumping to anchors from links should works on that page.

It has happened, that pressing the off-screen Back key does not jump the
view to the start of the document or to where the anchor link is located.

If I browse to a new page using an URL with a pre-existing anchor, then the
jump does happen:

https://en.wikipedia.org/wiki/Samsung_Galaxy_Ace_2#Samsung_Galaxy_Ace_2_x_/_Trend

Even with
https://en.m.wikipedia.org/wiki/Samsung_Galaxy_Ace_2#Samsung_Galaxy_Ace_2_x_/_Trend
— though the section won't open on its own.

Any particular reason you are still using IceCat 38.8?

-M.
On Jan 15, 2018 2:49 AM, "David Hedlund"  wrote:

> On 2016-05-14 05:43, Alex Schekoldin wrote:
>
> Bug: IceCat don't scroll to html anchor until you refresh the page.
> Version: IceCat 38.8.0 for android, f-droid build
>
>
> --http://gnuzilla.gnu.org
>
> I cannot reproduce this bug in the IceCatMobile version 52.4.1 (F-Droid
> build).
>
>
> --
> http://gnuzilla.gnu.org
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Browse all addons doesn't work properly on Android

2018-01-16 Thread Mart Rootamm
Hi.
The list of add-ons it at
https://directory.fsf.org/wiki/IceCatMobile#Related_Projects

It's possible, that you saw that same page, but the list of add-ons is
further down the page.

-M.
On Jan 13, 2018 5:03 PM, <9jdvrf+5a29ajoqkt...@guerrillamail.com> wrote:

> Hi,
>
> I want to install an addon and press "Browse all IceCat Add-ons". This
> action doesn't open addon directory but instead opens some wiki page.
>
> Using IceCat 45.7.0 (I cannot test any newer version because this is the
> last working on Android 4).
>
>
>
>
>
> 
> Sent using Guerrillamail.com
> Block or report abuse: https://www.guerrillamail.com//abuse/?a=
> Q1RzSAoOVq4chAK10HkRZ1rIX80%3D
>
>
>
> --
> http://gnuzilla.gnu.org
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] LibreJS: even when whitelisted, tv.nrk.no does not play

2018-01-28 Thread Mart Rootamm
Marco,

with NoScript, I found out the following domains that tv.nrk.no uses:

static.nrk.no
innlogging.nrk.no
psapi-ne.nrk.no
dc.services.visualstudio.com

With these unblocked, the Flash player launched, and a trailer for a
new tv show played. Though I don't use LibreJS.

With Network Inspector, I got a few more:

az416426.vo.msecnd.net — a Microsoft Azure domain. The important part
is vo.msecnd.net
nrk-od-08.akamaized.net — video stream

-M.


2018-01-28 17:00 GMT +02:00, Marco van Hulten :
> Bill—
>
> Thank you for your response.  I think I can roughly interpret it as
> that it would be best to wait until the FFv57+ equivalent of IceCat has
> arrived to GuixSD and/or Parabola before using LibreJS again on those
> systems.
>
> Je 28 jan 07:20 skribis bill-auger:
>> this is probably not related to icecat but a bug in librejs itself -
>> unless you can show that the same behavior is not present using a
>> different browser such as firefox or iceweasel, then this is actually an
>> issue for the librejs mailing list -
>
> On my Debian 9.3 (stretch) laptop with Firefox 52.6.0 with LibreJS
> 6.0.13, videos on https://tv.nrk.no/ do play when I add tv.nrk.no to
> the whitelist.
>
> The same version of LibreJS with IceCat 52.3.0 (on both GuixSD and
> Parabola) does not work when tv.nrk.no is added to the exception list.
> However, I now found out that it does when I add *.nrk.no to that list.
>
> In short, there appears to be difference between the system with
> Firefox and the systems with IceCat, but it may be too minor or unclear
> to report on this at another place.
>
>> although there is little point in
>> reporting it now as the version of librejs in the current version of
>> icecat has been obsoleted by mozilla starting with v57; so that librejs
>> development is now entirely focussed on the new FFv57+ compatible
>> version - what this means unfortunately for now is that it is highly
>> doubtful that the version of librejs in icecat will ever be upgraded or
>> have any bugs fixed - so whatever problems you have today with librejs
>> will remain until the next release of icecat; which should be compatible
>> with the new version of librejs
>
> On my Ubuntu 16.04 laptop I run Firefox 58.0.  There I could not
> install LibreJS 6.0.13.  On the Mozilla Add-ons site there is a newer
> version of LibreJS 7.11 available.  It is where the GNU website links
> to, so it should be an official version, but this is puzzling [1]:
>
>> The LibreJS source files can be found via HTTPS:
>> librejs-6.0.13.tar.gz (462K). Or FTP: ftp://ftp.gnu.org/gnu/librejs/.
>> It can also be found on the GNU mirrors. This link will automatically
>> select a mirror for you. LibreJS is also available at the Mozilla
>> Add-ons site. Due to Mozilla's review process, the version of LibreJS
>> available at the Add-ons site is often outdated. This isn't in our
>> control.
>
> [1]: https://www.gnu.org/software/librejs/
>
> It appears that it is outdated on the official website, or at least
> that GNU only offers the pre-FFv57 version of LibreJS.
>
> With LibreJS 7.11 the issue was more or less the same as for LibreJS
> 6.0.13 (on other systems): the video did not play (whereas it does
> when the extension is disabled).  But now, after removing and
> installing the extension again from Mozilla, it does work, even without
> adding domains to the whitelist.  Furthermore, the LibreJS button is
> an empty icon; I found it by hovering over an apparently empty space at
> the top-right of the window (next to Adblock Plus and so on).  When I
> click on it, nothing happens.  All seems fine and thus according to
> LibreJS 7.11 on this Ubuntu system at this point in time does not use
> any non-free JavaScript.
>
> I realise that all this information can be confusion.  I was not sure
> what was important to mention, so I decided to report all my findings
> here.
>
> —Marco
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Icecat Mobile

2018-09-11 Thread Mart Rootamm
Jennifer,
can you update your tablet to at least Android 4.1 Jelly Bean?

What make and model is your tablet?

-M.
11.09.2018 0:20 kirjutas kuupäeval "Jennifer Brice" :

>
> Since the new version of Firefox ESR is based on Quantum and since Firefox
> Quantum mobile no longer works with Ice Cream Sandwich version of Android,
> will the next version of Icecat Mobile drop support for ICS too?
>
> Yes, I use an ICS tablet, and would like to continue using the latest Ice
> Cat Mobile. So if there was no good reason for Firefox to drop support for
> these tablets, could you continue support.
>
> --
> http://gnuzilla.gnu.org
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Emoji in IceCat

2018-04-20 Thread Mart Rootamm
Felix,
There are additional font size settings in about:config, if you search
there just with 'font'.

The about:config solution is one, though in some operating systems,
browsers typically default to the closest possible match, if they rely
on the OS to match missing characters, thus precluding the trip to
about:config.

wrt font size, can you send a screenshot of what the Noto emoji look
like for you with text?
For example, both in a plain Wikipedia article, and in a textarea
(editing an article).

wrt to replies, then I originally sent a reply both to bug-gnuzilla,
and a carbon copy to you. On assumption, that you've subscribed
anyway, then I won't :cc you.

-M.

2018-04-20 0:52 GMT +03:00, Felix Fröhlich :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Whoops. Apparently that email didn't include the previous reply I sent
> to Mart. Here you go:
>
> Hi Mart,
>
> Great! Thanks for the advice.
>
> I added the Noto Color Emoji font to the following about:config
> settings:
>
>  * font.name.monospace.x-unicode
>  * font.name.sans-serif.x-unicode
>  * font.name.serif.x-unicode
>
> Now the Emoji actually do show up. They're way too big, though ^^
>
> I'll play around with the font settings and see if I can manage
> this; Maybe I'll have to use a different font.
>
> - --
> Felix Fröhlich
> GnuPG: AC26CC3F517BA1794743512E32E7A8DAB442426F
>
> On Thu, 2018-04-19 at 23:33 +0200, Felix Fröhlich wrote:
>> Hi all,
>>
>> So, erm, that was... not optimal. I wrote the mail to Mart and bug-
>> gnuz
>> i...@lists.gnu.org because for some reason I believed that was the
>> correct email address... Please don't ask me why.
>>
>> Anyhow, with Mart's help I figured out how to display the emoji (see
>> below).
>>
>> I also found out that -- for some reason I don't know -- the Noto
>> Color
>> Emoji font on my system appears to be corrupted, as the font shows up
>> as what looks like a rounded square in gnome-font-viewer (see
>> attachment). Not sure what causes this, but I fell back to the
>> uncoloured version of that font, namely Noto Emoji. It's no big deal,
>> really.
>>
>> Now all emoji that I wanted to display show up just fine.
>>
>> Thanks again for your help, Mart!
>>
>> --
>> http://gnuzilla.gnu.org
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEErCbMP1F7oXlHQ1EuMueo2rRCQm8FAlrZD7QACgkQMueo2rRC
> Qm8zvw/9Hstj1r/u5kb7+8R+PTr32FjujwvDzZg1J5Nb598evLHhDUZ8KeQdW3aD
> TTbi31ICOOnrHCzG0/5tKW3sbY0J8tKFV7oEuj+gWdAmTCRSaLKQxBho7iHSIsaL
> vdhQZt8wtMwN9XGeOaGZm5Ifq6Ykz9rTS24IWfzb5mZ5/9ojXsDy7x2C92g/evQW
> YOR+Qp2xukY9sjVDYqjrHP4visJIDR8wyXsezNKUA1wbsUnOmHb7oygtMMV0iEMZ
> A87SP/kah3Nscue7f/c/3J1E61XoB0rPwsI7vp3ZrKjz6nC/nBqI4D3l3t06So38
> pC2cQKvOZ5jEykvnSiGQdSVGLZfAjL8k/6kXuLyLDeY6ppQqZ4GGKAeopqNgH+SP
> ZF2rc5U+r02QH83o597fVMOIS+o0yftH8O9e9FCIBD4ttxBEjPjyNqr/KlPw7378
> Oit3sWi46dWC8bv95gvidROCPvEuTcXWBuVlVO89BsQRj7uuIt8cmcxJkr7SmjLY
> tlIetL03muTkMZ1+uBHeIgl35t5hp+NsZgcK4aAvn82RmRAXPQzDQZSff4NmUdX0
> qLuET207xRUZh8l3ZOnhyZiwGN6b97DSYbpUPRw0Pr6vs9gsLyjJwPetEJiaTp+/
> jrJ3l+yDy9/+kwAn0Jsn4h8ksGUdcn2JYCFFt350d8VNVjowQj0=
> =1nZe
> -END PGP SIGNATURE-
>
>
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Emoji in IceCat

2018-04-20 Thread Mart Rootamm
David,

> Mart, is this "Emoji in IceCat" issue a bug or not?

Felix's initial issue is resolved. He did complain about the too big
font size for his emoji font, so now I'm waiting for a screenshot from
him.

-M.

2018-04-20 22:19 GMT +03:00, David Hedlund <pub...@beloved.name>:
> Mart, is this "Emoji in IceCat" issue a bug or not?
>
>
> On 2018-04-20 19:51, Mart Rootamm wrote:
>> Felix,
>> There are additional font size settings in about:config, if you search
>> there just with 'font'.
>>
>> The about:config solution is one, though in some operating systems,
>> browsers typically default to the closest possible match, if they rely
>> on the OS to match missing characters, thus precluding the trip to
>> about:config.
>>
>> wrt font size, can you send a screenshot of what the Noto emoji look
>> like for you with text?
>> For example, both in a plain Wikipedia article, and in a textarea
>> (editing an article).
>>
>> wrt to replies, then I originally sent a reply both to bug-gnuzilla,
>> and a carbon copy to you. On assumption, that you've subscribed
>> anyway, then I won't :cc you.
>>
>> -M.
>>
>> 2018-04-20 0:52 GMT +03:00, Felix Fröhlich <felix.froehl...@convey.de>:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA512
>>>
>>> Whoops. Apparently that email didn't include the previous reply I sent
>>> to Mart. Here you go:
>>>
>>>  Hi Mart,
>>>
>>>  Great! Thanks for the advice.
>>>
>>>  I added the Noto Color Emoji font to the following about:config
>>>  settings:
>>>
>>>   * font.name.monospace.x-unicode
>>>   * font.name.sans-serif.x-unicode
>>>   * font.name.serif.x-unicode
>>>
>>>  Now the Emoji actually do show up. They're way too big, though ^^
>>>
>>>  I'll play around with the font settings and see if I can manage
>>>  this; Maybe I'll have to use a different font.
>>>
>>> - --
>>> Felix Fröhlich
>>> GnuPG: AC26CC3F517BA1794743512E32E7A8DAB442426F
>>>
>>> On Thu, 2018-04-19 at 23:33 +0200, Felix Fröhlich wrote:
>>>> Hi all,
>>>>
>>>> So, erm, that was... not optimal. I wrote the mail to Mart and bug-
>>>> gnuz
>>>> i...@lists.gnu.org because for some reason I believed that was the
>>>> correct email address... Please don't ask me why.
>>>>
>>>> Anyhow, with Mart's help I figured out how to display the emoji (see
>>>> below).
>>>>
>>>> I also found out that -- for some reason I don't know -- the Noto
>>>> Color
>>>> Emoji font on my system appears to be corrupted, as the font shows up
>>>> as what looks like a rounded square in gnome-font-viewer (see
>>>> attachment). Not sure what causes this, but I fell back to the
>>>> uncoloured version of that font, namely Noto Emoji. It's no big deal,
>>>> really.
>>>>
>>>> Now all emoji that I wanted to display show up just fine.
>>>>
>>>> Thanks again for your help, Mart!
>>>>
>>>> --
>>>> http://gnuzilla.gnu.org
>>> -BEGIN PGP SIGNATURE-
>>>
>>> iQIzBAEBCgAdFiEErCbMP1F7oXlHQ1EuMueo2rRCQm8FAlrZD7QACgkQMueo2rRC
>>> Qm8zvw/9Hstj1r/u5kb7+8R+PTr32FjujwvDzZg1J5Nb598evLHhDUZ8KeQdW3aD
>>> TTbi31ICOOnrHCzG0/5tKW3sbY0J8tKFV7oEuj+gWdAmTCRSaLKQxBho7iHSIsaL
>>> vdhQZt8wtMwN9XGeOaGZm5Ifq6Ykz9rTS24IWfzb5mZ5/9ojXsDy7x2C92g/evQW
>>> YOR+Qp2xukY9sjVDYqjrHP4visJIDR8wyXsezNKUA1wbsUnOmHb7oygtMMV0iEMZ
>>> A87SP/kah3Nscue7f/c/3J1E61XoB0rPwsI7vp3ZrKjz6nC/nBqI4D3l3t06So38
>>> pC2cQKvOZ5jEykvnSiGQdSVGLZfAjL8k/6kXuLyLDeY6ppQqZ4GGKAeopqNgH+SP
>>> ZF2rc5U+r02QH83o597fVMOIS+o0yftH8O9e9FCIBD4ttxBEjPjyNqr/KlPw7378
>>> Oit3sWi46dWC8bv95gvidROCPvEuTcXWBuVlVO89BsQRj7uuIt8cmcxJkr7SmjLY
>>> tlIetL03muTkMZ1+uBHeIgl35t5hp+NsZgcK4aAvn82RmRAXPQzDQZSff4NmUdX0
>>> qLuET207xRUZh8l3ZOnhyZiwGN6b97DSYbpUPRw0Pr6vs9gsLyjJwPetEJiaTp+/
>>> jrJ3l+yDy9/+kwAn0Jsn4h8ksGUdcn2JYCFFt350d8VNVjowQj0=
>>> =1nZe
>>> -END PGP SIGNATURE-
>>>
>>>
>>>
>>> --
>>> http://gnuzilla.gnu.org
>>>
>> --
>> http://gnuzilla.gnu.org
>
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Emoji in IceCat

2018-04-21 Thread Mart Rootamm
The color emoji are too large.

When using Android, the color emoji are typically much bigger than the
rest of the text, which I have always thought to be a feature in order
to increase the visibility of any (color) emoji, and not a bug.

In computers that still have Windows xp, I've installed Symbola as the
go-to font for emoji. There, Firefox did not require about:config
tweaks, but the old SeaMonkey 1.1 did.

License change issue with Symbola and other fonts by George Douros.

Symbola and many other fonts are available at below link:
http://users.teilar.gr/~g1951d/

But I've just discovered, that George Douros has changed the license
of the fonts between 29 January 2018, and 7 March 2018.

The Internet Archive snapshot on 29 January 2018 says:
"In lieu of a licence; fonts and documents in this site are free for any use;"
This includes Symbola 10.23 and many other fonts by Douros.
Source:
https://web.archive.org/web/20180129230141/http://users.teilar.gr/~g1951d/

The next snapshot from 7 March 2018 says this:
"Free use of the software on this site is strictly limited to
personal, non-commercial use;"
Involves Symbola 10.24 and many other fonts.
Source:
https://web.archive.org/web/20180307012615/http://users.teilar.gr/~g1951d/

It should be possible to narrow down the date span of the change with
other web archive services.

Word should be spread, that fonts by George Douros are no longer free
in the spirit of GNU.

-Mart.

2018-04-21 3:22 GMT +03:00, Felix Fröhlich <felix.froehl...@convey.de>:
> Hi Matt,
>
> As for the Noto Emoji font, everything's a-okay. They show up in the
> size of the surrounding text, and even though they're not coloured
> (because they're not coloured in the font, either), they work just as
> you'd expect emoji to work.
>
> When using the Noto Color Emoji font, however, it produces results as
> shown in the pictures attached. As you may notice, they are WAY
> oversized for the area they're supposed to be displayed in. The first
> attachment (emoji-regular.png) shows the emoji as they show up on
> https://en.wikipedia.org/wiki/Template:Emoji_(Unicode_block). The
> second one (emoji-textarea.png) shows the emoji when used in a text
> area. The emoji was pasted in line 7 as last character on the line.
>
> As I said, though, I am pretty sure the oversized display is due to my
> installation of the font (or the font in general?) being corrupted or
> unusable, not a bug in IceCat.
>
> With regard to the replies: Yes, I am subscribed to the list, so
> there's no need to CC me :)
>
> --
> Felix Fröhlich
> GnuPG: AC26CC3F517BA1794743512E32E7A8DAB442426F
>
> On Fri, 2018-04-20 at 20:51 +0300, Mart Rootamm wrote:
>> Felix,
>> There are additional font size settings in about:config, if you
>> search
>> there just with 'font'.
>>
>> The about:config solution is one, though in some operating systems,
>> browsers typically default to the closest possible match, if they
>> rely
>> on the OS to match missing characters, thus precluding the trip to
>> about:config.
>>
>> wrt font size, can you send a screenshot of what the Noto emoji look
>> like for you with text?
>> For example, both in a plain Wikipedia article, and in a textarea
>> (editing an article).
>>
>> wrt to replies, then I originally sent a reply both to bug-gnuzilla,
>> and a carbon copy to you. On assumption, that you've subscribed
>> anyway, then I won't :cc you.
>>
>> -M.
>>
>> 2018-04-20 0:52 GMT +03:00, Felix Fröhlich <felix.froehl...@convey.de
>> >:
>> > -BEGIN PGP SIGNED MESSAGE-
>> > Hash: SHA512
>> >
>> > Whoops. Apparently that email didn't include the previous reply I
>> > sent
>> > to Mart. Here you go:
>> >
>> > Hi Mart,
>> >
>> > Great! Thanks for the advice.
>> >
>> > I added the Noto Color Emoji font to the following about:config
>> > settings:
>> >
>> >  * font.name.monospace.x-unicode
>> >  * font.name.sans-serif.x-unicode
>> >  * font.name.serif.x-unicode
>> >
>> > Now the Emoji actually do show up. They're way too big, though
>> > ^^
>> >
>> > I'll play around with the font settings and see if I can manage
>> > this; Maybe I'll have to use a different font.
>> >
>> > - --
>> > Felix Fröhlich
>> > GnuPG: AC26CC3F517BA1794743512E32E7A8DAB442426F
>> >
>> > On Thu, 2018-04-19 at 23:33 +0200, Felix Fröhlich wrote:
>> > > Hi all,
>> > >
>> > > So, erm, that was... not optimal. I wrote the mail to Mart and
>> > > bu

Re: [Bug-gnuzilla] Emoji in IceCat

2018-04-19 Thread Mart Rootamm
Hi, Felix.
To test again, if things work with less resource usage, use this Wikipedia
template:
https://en.wikipedia.org/wiki/Template:Emoji_(Unicode_block)

To the best of my knowledge, the address bar and the textarea employ
different fonts.

The textarea should be easy:

You'll have to add the color emoji font name to the comma-separated list of
font substitutes in about:config, including at the end of the list in
font.name.monospace.x-unicode
.

The address bar could be dependent on OS-level settings.

-M.
18.04.2018 21:54 kirjutas kuupäeval "Felix Fröhlich" <
felix.froehl...@convey.de>:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi everyone,
>
> I've been trying to work out how to get emoji and other symbols working
> in IceCat 52.6.0 on Debian 9 but failed (mostly, see below).
>
> What I tried is the following:
>
>  * Because I installed IceCat via GNU Guix, I installed some fonts that
>are capable of displaying Emoji. In my case, that was the Guix
>package font-google-noto. It shows up when running fc-list.
>  * To test if that sufficed to display Emoji, I went to the [Full Emoji
>List][1] by the Unicode Consortium (WARNING: opening may cause long
>loading times!) and noticed that a good number of the emoji listed
>in the "Browser" column were actually displayed. Inspecting those
>emoji via right mouse click → "Inspect Element" → "Fonts" in the
>pane on the right revealed that they were, indeed, using the font
>Noto Color Emoji (system). So far, so good.
>  * Then I tried copying some of them (namely U+1F465 , U+1F3F7  and
>U+1F6E0 ) to the [searx instance I'm using][2], the address bar of
>IceCat and the post area on the [diaspora* pod I'm using][3]. In all
>three of these locations, the emoji show up as blank space. Also, in
>contrast to the Unicode page above, Noto Color Emoji does not show
>up as used font.
>  * Modifying the fonts for Latin in about:preferences#content to Noto
>and prohibiting pages from choosing their own fonts didn't help,
>either.
>
> I have some extensions installed that may interfere with fonts:
>
>  * uBlock Origins: Remote fonts are enabled on all affected sites.
>  * uMatrix: CSS is enabled everywhere.
>  * NoScript: @font-face is allowed everywhere.
>  * IceCatHome: Enabling/disabling the "Use system fonts" option doesn't
>  change IceCat's ability to display Emoji, even after restarting.
>
> Do you know of anything that I have missed and could check to see why
> IceCat doesn't display Emoji unless on unicode.org?
>
> Thanks in advance for any help you can provide!
>
>  [1]: https://unicode.org/emoji/charts/full-emoji-list.html
>  [2]: https://searx.ch/
>  [3]: https://diasporing.ch/
>
> - --
> Felix Fröhlich
> GnuPG: AC26CC3F517BA1794743512E32E7A8DAB442426F
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEErCbMP1F7oXlHQ1EuMueo2rRCQm8FAlrXj10ACgkQMueo2rRC
> Qm+iMg/9FoQQQIYqFFR7aNnsuTxFkuYO92SJlhJswTsdw+Fn3bJiyQLExeP3UbZL
> PenliatG6MaRyqydSaAl/FSjAjAeFFD7NCzKP2axDDrY2CdQJXiGBIhZ8FlEkGtx
> apYhh6RV7lstqnF0yTqo1U5+KkDf2i3SAe7YbadErxsRoxZdtCGm+2QGB1G4AGHp
> A+y07gMmUoO0BJ52kLUli5zBRQWXySP6X+e+gnIFwB+nilxLwrxLoK0y7IiR0H3d
> 41SurpTPnF/GvwEyhvqfS3I31uaG86uE5m5lnH1sYxGMoSyK2tN2T2Lj9BuBfHhM
> b45xkiymOCmHWgozAEjAwa319AZnx44SW+niOEUBzf4zN7v+tdsJPqi5bbxI+QOV
> AzCiRBCAvsPjXUeA8s+83oU8tNkSE3WD32XdzY53HGO+/vZtc6EpnTCeAFjh5Jek
> t7x/DaeE0BK+DD9SytNUB+fYZDo6JHlgqiCPD65cSyypNFrRSnkTDA3QsZV9ZLES
> lj7oOFWBzJk3rM5Rx6nFbFMRktsroG0EP01AHqbwog5aGXuhsMaTr1wy8/19dUG8
> ivR0HUKZj4JJNXFNEQPYVNZORHyzjnbOzAvM8gTNm3K9qxX728yMkgFRXm/hbc95
> 8pnIGvoA6O4yAMoHr+Wyw0VBUDZzL0KWrsYHdTehHp8xxXXNpHU=
> =J1kG
> -END PGP SIGNATURE-
>
>
>
> --
> http://gnuzilla.gnu.org
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] IceCat oddities with minified resources in 60.2.0

2018-09-27 Thread Mart Rootamm
That's quite an interesting observation, because I have occasionally had a
very similar problem with pre-webextension Gecko-based browsers, whereby
the browser would encounter certain minified CSS, and would then hang with
100% CPU, and RAM usage getting higher and higher, for which reason I've
had to force-stop the browser processes.

Often, it's been some font file, or some JavaScript that's been the culprit
instead, but not always.

The only remedy was to find the offending file by blocking all types of
SCRIPT,FONT,CSS in classic NoScript's Application Boundaries Enforcer
(ABE), and to test which type of file, and then which particular file has
been acting up so much. After that, the hang-inducing file could be blocked
individually; best even with a partial pattern match, or a regular
expression in NoScript's ABE rules to prevent newer versions of the same
file from being blocked.

Alas, I have not seen the ABE configuration UI in webextension NoScript,
nor any other complex, or granular and detailed ways of configuring the
new-type NoScript.

-M.
27.09.2018 3:15 kirjutas kuupäeval "Mike Gerwitz" :

> On Wed, Sep 26, 2018 at 01:14:05 +, f133y9+7xq0rlfpyo0is@
> sharklasers.com wrote:
> > I am using GuixSD and its IceCat version was recently upgraded to
> 60.2.0. I
> > found, then, that a lot of websites were broken and did not behave like
> they
> > did before the update
>
> Mark Weaver made a couple of important fixes yesterday for the Guix
> package.  Please give it another try.
>
> --
> Mike Gerwitz
>
> --
> http://gnuzilla.gnu.org
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Icecat Mobile

2018-09-18 Thread Mart Rootamm
Indeed, Jennifer,
Acer did not give enough love for their A100 and A500 models.
https://androidcommunity.com/acer-iconia-tab-a100-a200-and-a500-wont-receive-jelly-bean-20121003/
The A100 is a decent device, and with 1 Gb of RAM, a dual-core CPU, and the
nVidia Tegra 2 GPU, it should have been possible for Acer to upgrade.
Unless there was a particular roadblock, such as insufficient storage.

My best suggestion is to keep the latest version of IceCat that would still
run on it, and then use at least an adblocker to prevent web sites from
hogging system resources and battery life.

Another option is to use the NoScript Anywhere extension. It uses
user-buildable whitelists. Fine-grained, subdomain-level whitelisting and
domain blocking requires use of about:config, and good knowledge of the
very advanced Vim text editor (Vim Touch for Android).

Yet another option is the uMatrix extension.

There is no system-level adblocker I know of that would block ads on the
mobile Internet for ICS. Ad-Away requires at least Android 4.1; DNS66 at
least Android 5.0.

A system-level adblocker that works on Wi-Fi, is the legacy Adblock Plus
app, available via F-Droid.

-M.
17.09.2018 8:25 kirjutas kuupäeval "Jennifer Brice" :

> It is an Acer Iconia A100, and there is no official upgrade to jellybean
> for it.  There is on unofficial version of xda called Jellytime Sosei that
> I tried, and it was very crashy and rebooted alot so I reset the device.
>
>   On Tue, 11 Sep 2018 01:56:50 -0500 Mart Rootamm <
> martroot...@gmail.com> wrote 
>  > Jennifer,
>  >  can you update your tablet to at least Android 4.1 Jelly Bean?
>  >  What make and model is your tablet?
>  >  -M.
>  >  11.09.2018 0:20 kirjutas kuupäeval "Jennifer Brice" <
> jenniferbr...@zoho.com>:
>  >  --
>  > http://gnuzilla.gnu.org
>  >
>  >  Since the new version of Firefox ESR is based on Quantum and since
> Firefox Quantum mobile no longer works with Ice Cream Sandwich version of
> Android, will the next version of Icecat Mobile drop support for ICS too?
>  >  Yes, I use an ICS tablet, and would like to continue using the latest
> Ice Cat Mobile. So if there was no good reason for Firefox to drop support
> for these tablets, could you continue support.
>  >
>  > --
>  >  http://gnuzilla.gnu.org
>  >
>  >
>
>
>
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Can't install IceCatMobile on Android

2019-02-02 Thread Mart Rootamm
Hi, secmail user.

MSM8916 is a 64-bit chip:

https://en.wikipedia.org/wiki/List_of_Qualcomm_Snapdragon_systems-on-chip#Snapdragon_410.2C_412_and_415_.282014.2F15.29

That could be the reason why the install error message is

"INSTALL_FAILED_NO_MATCHING_ABIS" (ABI - Application Binary Interface)

— as you might have been trying to install a package incompatible with
the CPU architecture of your device.

Can you tell me more about your device, such as make/model, and how
much RAM memory it has?

F-Droid 0.102.3 is the last version with a more practical user
interface that shows detailed package information for each available
app, including the supported architecture of each package (APK).

To install that version of F-Droid from the contemporary F-Droid app,
you'll have to ensure, that the F-Droid Archive repository in the list
of available repositories in app settings is active, and that the
package list is thereonafter updated.

Install the F-Droid 0.102.3 package compatible with your device, and
update the package once more.

As you search for and tap on IceCatMobile, then F-Droid 0.102.3 should
show all the available APKs of IceCat, their versions, and the
supported architecture of each.

The packages incompatible with your device are grayed out or not
displayed, depending on app settings in F-Droid.

At this time, the only CPU architectures shown for IceCatMobile are
armeabi-v7a (ARMv7) and x86. The processor architecture of your device
is most likely arm64-v8a.

Firefox Klar is Firefox Focus rebranded, so as to avoid confusion with
Focus Magazin in German-speaking countries.

Firefox Klar uses the built-in WebKit/Blink rendering engine, and not
the dedicated renderer of Firefox (Gecko).
https://en.wikipedia.org/wiki/Firefox_Focus

-M.

2019-02-01 9:31 GMT +02:00, ice...@secmail.pro :
> Processor: MSM8916 (Qualcomm)
> Android: 5.1 series
>
> I've download IceCat from this webpage[1]
> and when I tried to install it, it shows "Application not installed".
>
> And when I tried installing it via ADB,
>>adb install xxx\org.gnu.icecat_600410.apk
> pkg: /xxx.apk
> Failure [INSTALL_FAILED_NO_MATCHING_ABIS]
>
>
> Can anyone please provide a working APK for my phone?
> I was able to install these on this phone:
> 1. "Fennec FDroid version 60"
> 2. "Firefox Klar" on F-Droid
>
>
>
> Somehow I was blocked by posting(because I had to use Tor to bypass
> my restrictive ISP) to FDroid forum.
>
> [1] https://f-droid.org/en/packages/org.gnu.icecat/
>
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Impossible to install IceCat

2019-04-11 Thread Mart Rootamm
xfs,
what version of IceCat were you trying to install? Did it match the
architecture of your CPU?

What is your device make and model?

What's your device CPU architecture and clock speed, and how much RAM
memory does it have? Also, is there enough storage space to install
stuff?

Why do you still have Android 4.1.2?

I have Android 4.1.2, too, so I can relate.

I've only installed IceCatMobile 52.6.0, but that install included
about a dozen add-ons that I'd never have any use for, and which
almost prevented me from using IceCat, because all those add-ons were
active by default, were chugging precious amounts of RAM (updating?),
and were nearly impossible to deactivate.

I cannot say, if these add-ons were included by upstream, or by the
package maintainer at F-Droid.

If you're worried about strange JavaScript, then you can install
NoScript. It blocks most JavaScript by default, and has a tiny
whitelist that you can clean up later on.

If you have a pre-57 version of a Firefox derivative — including
IceCat — then you can install NoScript Anywhere from

https://noscript.net/nsa/

But it's quite difficult to modify that whitelist on a subdomain
level: you need to know your way around about:config, and you'll need
good knowledge of Vim (VimTouch for Android), which was once available
at F-Droid, too.

IceCat 60.x and newer require the WebExtension edition of NoScript.
It's less functional than classic desktop NoScript, but with a more
functional user interface than NoScript Anywhere. You can get that
from

https://noscript.net

So, anyway, in the WebExtension NoScript, you can set NoScript to
display full domains, you can clean up the built-in whitelist, you can
temporarily allow certain Google domains (if need be), and then not
worry about JavaScript at all for sites that you won't want to track
your device.

NoScript is the least-resource-intensive blocking tool.

If your device has 1 Gb or more RAM, you can also add uBlock Origin
for adblocking and for more fine-grained permissions, but it has a
steeper learning curve, and uBlock Origin does not default to blocking
everything.

For pre-Quantum Firefox and IceCat, I can recommend the following extensions:

* Console (1.1.1.1)
* Cookie whitelist for Fennec (0.9.5.1)
* Copy Profile (1.1.1)
* PageInfo Viewer (1.0.0.1)
* Privacy Settings (0.2.4)
* Proxy Mobile (0.0.10) — you can use apps that present a proxy in your device
* Stylish (2.1.1)
* View Source Mobile (0.1.1.1)

* AddCertificate (1.0.10.01.1)

All of the above extensions are not resource-hungry.

But these are pre-Quantum versions of extensions, and
addons.mozilla.org no longer hosts them. If you feel adventurous, then
you can search for them on the Interwebs, if you've decided on a
pre-Quantum version of IceCat.

Also, to prevent automatic updates to WebExtension versions, then in
about:config, set

extensions.update.enabled

to false.

Do keep in mind, that pre-Quantum versions of IceCat are less secure,
and do not have as good support for newer web standards. Many sites
may hang your browser pre-Quantum IceCat on what I see as malformed
CSS, fonts, and terrible JavaScript.

Sites that use these fonts, or which increasingly rely on CSS
variables (such as the new Skype for Web), will make pre-Quantum
IceCat Very Slow.

And if you want a device without Android, then see, if you can install
Sailfish OS.

For secure Android-based stuff, I could have at one time suggested
CopperheadOS, but its original developer was kicked out of the project
amidst deep acrimony.

Devices with non-Google Android are rare. The Nokia X family — from
before the Nokia mobile division was sold to Microsoft — is the only
such series of Android devices, but they separately promoted Nokia and
Microsoft products. Nokia X devices are now rare, and might even be
considered collector's items.

-M.

2019-04-01 23:45 GMT +03:00, x...@riseup.net :
> Hello,
>
> I cannot install IceCat using F-Droid on Android 4.1.2.
>
> The app gets downloaded and when it comes to
> installation, the required permissions are shown and I
> have to choose between "Install" and "Cancel". I tap
> "Install" (again and again to infinity) but the button
> simply doesn't respond. So I have to tap "Cancel". I
> have tried many times and it is always the same. Of
> course I have allowed installation of apps from
> external sources, that's not the issue. I have been
> able to install other apps using F-Droid.
>
> I tried to contact t...@f-droid.org several times but
> each time their mail server fails to deliver the
> message with a 550 5.7.1 error.
>
> Can you help?
>
> --
> http://gnuzilla.gnu.org
>

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] IceCat and security updates

2019-05-05 Thread Mart Rootamm
As and when Mozilla releases 60.6.2 or 60.7.0, there quickly needs to
be a new build because of an upstream brouhaha involving the expiry of
an intermediate signing certificate that disabled all extensions.

To mitigate the issue, existing users can set

xpinstall.signatures.required

to false

in about:config.

-M.

2019-05-04 5:29 GMT +03:00, Mike Gerwitz :
> On Fri, May 03, 2019 at 15:48:34 -0400, Mark H Weaver wrote:
>>> Is there any reason why IceCat is skipping updates?
>>
>> It's due to lack of developer resources.
>
> I talked to Rubén (the current maintainer) at LibrePlanet and he doesn't
> have the time, and would appreciate any help that anyone can
> provide.  If anyone is interested, get in touch with us at
> maintain...@gnu.org.
>
> --
> Mike Gerwitz
> Free Software Hacker+Activist | GNU Maintainer & Volunteer
> GPG: D6E9 B930 028A 6C38 F43B  2388 FEF6 3574 5E6F 6D05
> https://mikegerwitz.com
>

--
http://gnuzilla.gnu.org


bug#47276: Stuck at Cloudflare 'browser checks'

2021-05-11 Thread Mart Rootamm
It appears, that Cloudflare might have been designed to detect a
mismatch between what the string reports itself as, and what the oscpu
and platform strings say.

> whitelisting the host in "Manage Permissions" under
> "Cookies and Site Data"

This whitelisting works via View Page Info, too, where Allow under
Cookies is selected.

-M.

2021-05-11 3:07 GMT +03:00, bill-auger :
> i may have found a solution for this
>
> there has been a long-standing debate in parabola, as to whether
> spoofing the user-agent is a good anti-fingerprinting measure -
> people tend to agree that it probably does more harm than good
>
> for example, 'IceCat' in the user-agent string, actually presents
> significantly more identifiable information than the generic
> 'Firefox' would
>
> in addition to the user-agent string, there are javascript
> properties, which identify the browser and host - these are
> supposedly deprecated now; but they are available - icecat
> reports: 'Windows NT 6.1', where i believe this would be
> 'Windows NT 10.0' on most current windows systems
>
> related to this ticket, i have removed the user-agent
> over-rides in parabola's iceweasel, for the reasons above -
> the user-agent is now the same as archlinux and most other
> distros (the defaults) - in doing so, the problem with login
> to gitlab.com was resolved - i discovered that it is the
> 'general.platform.override' property, which is responsible for
> the gitlab/cloudflare rejecting the browser - presumably,
> because it conflicts with the user-agent information - setting
> it to 'Linux x86_64' (manually) satisfied the browser check;
> so this appears to be the general solution
>
> at least, the 'oscpu' and 'platform' properties should be updated
> to match the most common windows hosts - 'appVersion' also appears
> to be wrong - the default value is '5.0 (X11)' (not the browser
> version) - however, changing those properties to agree with the
> user-agent string, is effectively removing the overrides (which
> again, are deprecated)
>
> here is a test page:
>   
>   document.write("codeName="   + navigator.appCodeName + "
"); > document.write("appName="+ navigator.appName + "
"); > document.write("appVersion=" + navigator.appVersion + "
"); > document.write("oscpu=" + navigator.oscpu + "
"); > document.write("platform=" + navigator.platform+ "
"); > document.write("product="+ navigator.product + "
"); > document.write("buildID="+ navigator.buildID + "
"); > document.write("userAgent=" + navigator.userAgent + "
"); > > > icecat: > codeName=Mozilla > appName=Netscape > appVersion=78.0 > oscpu=Windows NT 6.1 > platform=Win32 > product=Gecko > buildID=Gecko/20100101 > userAgent=Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 > IceCat/78.0 > > arch (default values): > appCodeName=Mozilla > appName=Netscape > appVersion=5.0 (X11) > oscpu=Linux x86_64 > platform=Linux x86_64 > product=Gecko > buildID=Gecko/20100101 > userAgent=Mozilla/5.0 (X11; Linux x86_64; rv:88.0) Gecko/20100101 > Firefox/88.0 > > > >

bug#48720: GNU IceCat Updates???

2021-05-28 Thread Mart Rootamm
I've seen binaries of IceCat for Android on the F-Droid app and store, too.

-M.

2021-05-29 2:38 GMT +03:00, bill-auger :
> its not over-looked; but there have not been any recent binary
> releases - the current versions are in source code form only
>
> http://git.savannah.gnu.org/cgit/gnuzilla.git
>
> there are community packages though - fedora, guix, and parabola
> have icecat binaries packaged, and there is a debian package on
> the OBS, and a PKBUILD on the AUR - those would be the easiest
> way to use the current versions
>
> https://software.opensuse.org//download.html?project=home%3Alosuler%3Aicecat=icecat
>
>
>
>





bug#47276: Stuck at Cloudflare 'browser checks'

2021-03-24 Thread Mart Rootamm
Right-click the GitLab page, click on View Page Info, go to
Permissions tab, scroll to the Cookie section, uncheck the default,
and make sure Allow (radio button) is checked.

In some cases, there's a Tools > Page Info menu option to access the
same page properties window.

Allowing cookies like that has usually worked for most things that
have Cloudflare or other like protection from automated.

Mozilla removed cookie prompting from Firefox 44.0. This worked by
prompting to set cookies before any cookie was saved, and a user could
allow a domain, allow it for session, or block it, and then set the
permission as permanent. This also applied for third-party domains.

A developer named Savarese has continually created patches to
reinclude this functionality:
https://www.savarese.org/patches/firefox.html

If this very important privacy-enhancing functionality were
reintroduced in GNU IceCat (including in older verisons, such as 68.x
for Android), I'd make this browser my daily driver everywhere.

-Mart.

2021-03-20 20:09 GMT +02:00, bill-auger :
> i dont have a solution for this; but it turned up on the
> parabola bug tracker some months ago, conflated with other
> similar issues, which affected icecat and parabola's iceweasel,
> probably since v81 - i dont believe that the problem existed
> when iceweasel was v78, so it is probably not the browser
> configuration that changed; but something gitlab.com changed
> recently
>
> there seems to be multiple reasons why some websites dont work -
> one of them is the "enhanced tracking protection", another is
> geo-location - relaxing those settings, did not make gitlab.com
> work though
>
> there are multiple tickets on the gitlab bug tracker, which seem
> to be the same problem - several suggest that it is related to
> cookie expiration; but nothing indicated a solution
>
> i discovered that i could make gitlab,com work with iceweasel,
> by deleting the profile under ~/.mozilla/; but that trick did
> not work for icecat - i still dont know why that website rejects
> icecat - other instances of the gitlab software work as expected
> - changing the user-agent does not help either
>
>
>
>





bug#55454: Icecat not updated on F-Droid

2022-06-18 Thread Mart Rootamm
Cloudflare's browser checks may require accepting/whitelisting a
site's JavaScript, if an extension such as NoScript or uBlock Origin
blocks it, and then, sometimes, manually accepting a cookie from that
domain in the Permissions section of the Page Info window (via
Ctrl+i).

Mozilla removed cookie prompting from Firefox 44.0, and D.F. Savarese
has been maintaining a personal cookie prompter patch ever since:

https://www.savarese.org/patches/firefox.html

In mobile Firefox, cookie prompting was never implemented, though the
backend was still there, and Makoto Kato developed a cookie prompt
extension:

https://github.com/makotokato/cookieprompter

The extension was not a WebExtension, and so it no longer available at
Mozilla Addons.

An archived version of the original addon page, and an archived xpi
file do exist, though:

https://web.archive.org/web/20171010095515/https://addons.mozilla.org/en-US/android/addon/cookieprompter/

XPI, Firefox / IceCat / Fennec F-Droid up to and including v. 43.0 —

https://web.archive.org/web/20170917182220/https://addons.cdn.mozilla.net/user-media/addons/406692/cookie_prompter_add_on-0.1-fn-android.xpi?filehash=sha256%3A40a75f9039f735dde03bee5e04360ef23d63c109cce092aa9145a83349785a8c

The filehash URL parameter is important, btw.

-M.


2022-06-18 15:46 GMT +03:00, bill-auger :
> gnuzilla does not publish to f-droid - upstream projects
> generally do not publish prepared packages of that sort - if you
> find a problem with any pre-packaged binary icecat, or youd like
> the package upgraded in that repo, you would need to contact the
> person who publishes the package
>
> i dont know about the f-droid repo specifically; but normally,
> the package itself would tell you who the packager was, with
> contact information and how file bug reports
>
> but WRT gitlab.com specifically, it is not likely that upgrading
> icecat would change the behavior - the reason why you can not log
> in is documented in BR #47276 "Stuck at Cloudflare 'browser
> checks'" - that includes patches to make it work (and other
> websites guarded by cloudflare); but the patches have not yet
> been accepted into icecat
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47276
>
>
>
>





bug#60668: IceCatMobile: Dark mode?

2023-02-14 Thread Mart Rootamm
Hi, Mr. T.

I couldn't find the perfect theme extension for IceCat Mobile from
Mozilla Addons, but there is only one that does work for me, though it
only paints the address bar gray, but not the menus or settings pages:

Dark Theme for Android & PC
https://addons.mozilla.org/en-US/android/addon/dark-theme-android-pc/

Version 68.4.2 of IceCatMobile is old, and its rendering engine is
much slower than that of the latest version of Firefox, and some sites
no longer support it: For example, the "more extensions by user"
section at Mozilla Addons won't load information, and the placeholder
spans continue to animate; GitHub always supports the very latest
version of Firefox, and relies on the latest functionality; the
desktop version of YouTube has a somewhat mangled design, which loads
slowly anyway.

The saving grace of IceCat Mobile 68.x is the support of a greater
number of WebExtensions, the presence of about:config, and maybe a few
other things.

With regard to the possibility of enabling dark mode on sites by
default and in the browser UI, I've added the following settings in
about:config —

Integers:

ui.systemUsesDarkTheme;1
widget.non-native-theme.scrollbar.style;4

Booleans:

userChrome.theme.fully_dark;true
userContent.page.dark_mode;true
widget.content.allow-gtk-dark-theme;true
widget.disable-dark-scrollbar;false
widget.gtk.alt-theme.dark;true
widget.non-native-theme.scrollbar.active-always-themed;true
widget.non-native-theme.scrollbar.dark-themed;true

The above settings for UI in about:config don't seem to work, as they
are far too new for IceCat Mobile 68.4.

Neither is there any guarantee, that IceCat 68 will be able to make
these site-oriented settings work, or that sites that use conditional
dark mode in CSS, would be able to detect browser-based dark mode
settings in this version of IceCat. I've kept the settings anyway.

Other dark extensions do not work in this browser version: the "Native
Dark" extension, and some themes, such as Dark Theme for Firefox, Arc
Dark Theme, and a number of others.

Interestingly enough, "Dark Mysterious Forest" works in Fennec F-Droid
68.12.0esr.

Most other "dark theme" extensions paint individual websites.

Global Dark Style paints all sites dark, and one can disable certain
domains. There is also Dark Reader. I haven't tried those out.

Some individual extensions, such as NoScript and uBlock Origin, have
dark theme support for themselves.

Here's a list of extensions that I use:

NoScript
Stylus
uBlock Origin

I've added links for all the other WebExtensions, because Mozilla's
own search facility does not display them.

Custom UserAgent String (clunky UI, but works)
https://addons.mozilla.org/en-US/android/addon/custom-user-agent-revived/

MobiDevTools (vaguely similar to FireBug, and to Firefox developer tools)
https://addons.mozilla.org/en-US/android/addon/mobidevtools/

Privacy Settings
https://addons.mozilla.org/en-US/android/addon/privacy-settings/

Work with URLs (urls paths opener obfuscate decode) [sic]
https://addons.mozilla.org/en-US/firefox/addon/workwithurls/

Video Background Play Fix — this is important when playing YouTube and
switching to other apps, or when the lock screen appears.
https://addons.mozilla.org/en-US/firefox/addon/video-background-play-fix/

View Page Source Mobile
https://addons.mozilla.org/en-US/firefox/addon/view-page-source-mobile/

I can also suggest CleanLinks, which cleans up URLs of tracking codes
when copying them, but I haven't tried it out.

Return YouTube Dislike — While this extension will install in mobile
IceCat 68.x, and while it may have worked there at one time or
another, then it no longer seems to work in that version of IceCat,
either with mobile YouTube, or with the desktop version of YouTube.
This extension works only in desktop Firefox or derivatives.
https://addons.mozilla.org/en-US/firefox/addon/return-youtube-dislikes/

A note about Fennec F-Droid 68.12.0esr and IceCatMobile 68.4: Besides
version differences, Fennec F-Droid, while newer, uses an animated
progress bar, which slows down rendering in really old smartphones,
while I haven't noticed progress bar animations in IceCat Mobile.

-M.

2023-01-08 23:31 GMT +02:00, Mr. T :
> Hi,
>
> thanks a lot, finally a mobile browser that allows all addons like the
> old firefox versions and not just a hand full of selected add-ons that
> are not quite enough.
>
>
> I hate mozilla for always trashing good stuff like rss support, ftp
> support and now mobile addon support, thankfully there are people who
> care about real free software ;)
>
>
> but there is one thing i miss on the installed icecat mobile version
> 68.4.2 (is this really the latest version, fdroid dosnt provide a later
> one but release date 2020 seams a bit old)
>
> and that is dark mode, there is no way to set it and its also not
> enabled when enabled system wide, i like to browse in the evening before
> sleeping in while lying in bed so its a must have for me to have a dark
> as possible