Browser of the Year

JWJones · 03-02-2019, 07:25 AM

As I have now migrated my Linux usage to Fedora and Gnome 3, I decided to give Gnome Web (a.k.a. Epiphany) a fair shakedown (I'm typing on it now).

To my surprise, it's a really decent browser. It has ad blocking by default, and also has the option to use Firefox Sync, so I was able to bring in all of my FF bookmarks, etc. Additionally, it has Reader View (like FF) by default, which I use a lot to cut out all the BS on a website, so I can just read the text. All wrapped up in a simple, minimal interface. I must say, I'm impressed. I will keep this on my machines and continue to use it, along with Firefox. Surprised that it got zero votes. I would definitely use it over anything from Google-land.

ondoho · 03-02-2019, 11:52 AM

^ anything that doesn't have an option to selectively disable javascript is out for me.
it's sad, because there's a few otherwise fairly decent browsers like that - falkon, midori, maybe also epiphany...

JWJones · 03-02-2019, 02:52 PM

Quote:

Originally Posted by ondoho

^ anything that doesn't have an option to selectively disable javascript is out for me.
it's sad, because there's a few otherwise fairly decent browsers like that - falkon, midori, maybe also epiphany...

I'll have to look into the javascript disabling options and report back. Yeah, falkon is another one that caught my attention. I found it to be quite nice, too, for the little bit I have used it so far.

teckk · 03-03-2019, 11:40 AM

I looked this thread over before posting. I don't see a few
things mentioned. Can I take this thread in a little different
direction?

Have not run Firefox for years. I see that a lot of members like it.
I looked to see what it and its depends were on this arch box now.

Accoding to pacman -Si Its major ones are:

Code:

firefox     41.87 MiB
libxt       534.39 KiB
dbus-glib   119.12 KiB
libpulse    358.58 KiB
libvpx      1.28 MiB
gtk3        10.55 MiB
ffmpeg      8.54 MiB
icu         8.64 MiB
nss         1.35 MiB
sqlite      1.35 MiB

That's 75 MB+ every update.

And the installed size is: 320 MB+

Code:

Firefox     161.98 MiB
libxt       2.06 MiB
dbus-glib   769.00 KiB
libpulse    1.40 MiB
libvpx      4.98 MiB
gtk3        71.08 MiB
ffmpeg      29.13 MiB
icu         35.81 MiB
nss         5.12 MiB
sqlite      8.50 MiB

Optional Deps:

Code:

networkmanager: Location detection via available WiFi networks
libnotify: Notification integration
pulseaudio: Audio support
speech-dispatcher: Text-to-Speech
hunspell-en_US: Spell checking, American English

Is that a web browser or small operating system?

Chrome/Chromium:

Download:

Code:

Chromium    49.06 MiB
gtk3        10.55 MiB
libgcrypt   485.69 KiB
nss         1.35 MiB
icu         8.64 MiB
ffmpeg      8.54 MiB
etc...

Installed:

Code:

Chromium    171.21 MiB
gtk3        71.08 MiB
libgcrypt   1.39 MiB
nss         5.12 MiB
icu         35.81 MiB
ffmpeg      29.13 MiB
etc...

Optional Deps:

Code:

pepper-flash: support for Flash content
kdialog: needed for file dialogs in KDE
gnome-keyring: for storing passwords in GNOME keyring
kwallet: for storing passwords in KWallet

That's the reason that I don't have those huge bloated things installed.
Not because they don't work. That's a factor for me but must not be
a factor for many members.

And then all of the Chrome type browsers, Chrome, Chromium, Inox,
Iridium sit there and send data to Google, Amazon, Akamai all of
the time. Start tcpdump then open one of them and watch.
So does Qupzilla/Falcon. How about Midori, SeaMonkey, Brave, Vivaldi,
etc.

Looking at the pole at the top of this page. Dillo does not phone home,
either does lynx, w3m, PaleMoon(not installed, untared into a directory),
Firefox phones home, the only webengine browser I have are my python
scripts, and they don't. I quit using webkit, a while back.

Since this is a browser thread, talk about those things in relation
to browsers or your favorite browser. Do you care one way or the other
just as long as the browser does what you wish? Or does phoning home turn
you off to any of them.

Does the size of them, and the bandwidth it takes to update them influence
which browser that you use?

How about the way/speed at which your browsers engine handle/render
javascript content as compared to others. And the ease or pain of turning
scripts/images on/off in your favorite browser. This was talked about
a little bit.

How about the plugins that are/aren't available for them. Or the ability
to write your own scripts for them.

Reziac · 03-03-2019, 12:15 PM

Mozilla and Chrome were both originally meant to become functionally operating systems, which is to say, host systems for everything else you do. Size and efficiency were never a concern. It continually croggles me that a modern web browser can take 1.5GB of memory to display 30k worth of text. (I'm reminded that on the one hand we have massive office suites, and on the other we have Atlantis, which can do nearly all the same document formatting with a mere 2MB binary.)

Being able to toggle various browser functions without dumpster-diving in Preferences is critical for me. The toggles I can't live without:

Site colors (for when your colors hurt my eyes)
Javascript (for all the usual reasons)
Site fonts (what's with all the microthin fonts?)
CSS (for when the text is lost in the junk)
UserAgent (to force Mobile layout on overbearing sites)

To this end I require a browser that supports PrefBar and NoScript, or an exact equivalent.

I also want real menus and the ability to access everything from it, not that crippled 'hamburger' menu with the loathesome cellphone way of hiding everything.

I'm less concerned about their data snooping; I'll just block the mothership in HOSTS.

So that's why I use SeaMonkey as primary, PaleMoon or Borealis as secondaries, and Chrome as a last resort. I haven't installed Firefox in about 10 years, and since then have only looked at it when it arrives preinstalled on some distro -- and last time it annoyed me to the point that it hit my Never Again circuit.

ondoho · 03-04-2019, 11:42 PM

Quote:

Originally Posted by teckk

Firefox phones home

can you clarify this please? how did you find out? where to?

ondoho · 03-04-2019, 11:45 PM

Quote:

Originally Posted by Reziac

The toggles I can't live without:

Site colors (for when your colors hurt my eyes)
Javascript (for all the usual reasons)
Site fonts (what's with all the microthin fonts?)
CSS (for when the text is lost in the junk)
UserAgent (to force Mobile layout on overbearing sites)

So that's why I use SeaMonkey as primary

may i ask how you toggle all this with seamonkey?
I know that noscript works, CSS can be switched on/off from the menu, but the rest?

Reziac · 03-05-2019, 12:07 AM

Quote:

Originally Posted by ondoho

may i ask how you toggle all this with seamonkey?
I know that noscript works, CSS can be switched on/off from the menu, but the rest?

One line down:
To this end I require a browser that supports PrefBar and NoScript, or an exact equivalent.

http://prefbar.tuxfamily.org

SeaMonkey 2.49.4 still supports the archive version.

However, I will not be upgrading...
https://unofficialseamonkeynews.wordpress.com/tag/2-52/

teckk · 03-06-2019, 09:14 AM

@ondoho
Be glad to answer you.

I hadn't had firefox installed for a long time. I haven't updated for a month either.
There are 2 version of arch, up to date and not up to date. If you haven't updated
for 15 min, then you are out of date.

Ok, here we go...

Code:

sudo pacman -S firefox
resolving dependencies...
looking for conflicting packages...

Packages (3) mailcap-2.1.48+14+g5811758-1  mozilla-common-1.4-5  firefox-65.0-1

Total Download Size:    38.67 MiB
Total Installed Size:  162.08 MiB

:: Proceed with installation? [Y/n]y

Let firefox and depends install...

I then took the ethernet interface down

Code:

sudo netctl stop mynetworkname

So I could launch firefox without it connecting to the internet and downloading
it's home page or anything else. (I want it's cache empty so nothing has touched it.)

Ok, launch firefox...

First thing I see is a message in the info panel at the bottom of firefox.
"Firefox automatically sends some data to Mozilla so that we can improve your experience."

Ok, at least they are honest. I then looked around and found the preferences page, and
unclicked auto update anything I could find,
unclicked search suggestions,
unclicked Allow Firefox to send technical and interaction data to Mozilla,
set home page to blank page,
new tabs to blank page,
unlicked Snippets, Updates from Mozilla and Firefox,
I looked until I couldn't find anything else that gave firefox permissions to send data anywhere.

I closed firefox.

I opened up a xterm and issued

Code:

sudo tcpdump -qtni any

Then brought the ethernet interface up

Code:

sudo netctl start mynetworkname

And watched what was happening on the LAN...nothing but some arp requests, and the routers heatbeat that it does.

I then launched firefox to a blank page... I'm going to abbreviate this, because it's very long.

Code:

IP 192.168.0.3.36612 > 4.2.2.1.53: UDP, length 42
IP 192.168.0.3.37772 > 125.56.201.115.80
...30 lines of packets
IP 192.168.0.3.52770 > 34.252.164.43.443
IP 34.252.164.43.443 > 192.168.0.3.52770
...20 lines of packets
IP 192.168.0.3.39634 > 54.187.176.55.443
IP 54.187.176.55.443 > 192.168.0.3.39634
...20 lines of packets
IP 192.168.0.3.43904 > 72.21.91.29.80
IP 72.21.91.29.80 > 192.168.0.3.43904
...20 lines of packets
IP 192.168.0.3.60708 > 13.249.87.121.443
IP 13.249.87.121.443 > 192.168.0.3.60708
...450 lines of packets
IP 192.168.0.3.47264 > 23.44.170.8.443
IP 23.44.170.8.443 > 192.168.0.3.47264
...20 lines of packets
IP 192.168.0.3.43916 > 72.21.91.29.80
IP 72.21.91.29.80 > 192.168.0.3.43914
...
IP 192.168.0.3.43056 > 35.166.112.39.443
...
IP 192.168.0.3.47264 > 23.44.170.8.443
I Ctrl+s and froze the shell here after about 10 seconds

I then killed firefox and used whois

4.2.2.1 is a DNS server
125.56.201.115 is Akamai
34.252.164.43 is Amazon
54.187.176.55 is Amazon
72.21.91.29 is MCI Communications
13.249.87.121 is Amazon
23.44.170.8 is Akamai

So, before I have loaded a single web page, streamed a single video/audio,
before I have downloaded a single ad from amazon, firefox is talking.
Why? I haven't asked for anything.

Now, this may be setting up things in the background so that the user gets the best experience possible
when they do steam a video or get and ad from amazon. I don't like it, Chrome/Chromium does the same.

Code:

sudo pacman -Rns firefox

hydrurga · 03-06-2019, 10:11 AM

teckk, as you already have a good clean setup to test this, do you fancy re-installing Firefox anew, ensuring that any personal config files from your previous installation have been deleted, and switch off all the config settings mentioned on the following page before testing again.

https://support.mozilla.org/en-US/kb...ic-connections

I know it's a faff, but I for one am interested in whether or not those automatic connections you noticed can actually be switched off.

Apologies in advance for the work that this will entail.

teckk · 03-06-2019, 01:57 PM

Ok, I'll do that.

Find it, nuke it.

Code:

find ~ -type d -name '*mozilla'
rm ~/.cache/mozilla/*
rmdir ~/.cache/mozilla
rm ~/.mozilla/*
rmdir ~/.mozilla

Get a local copy of the directions

Code:

lynx -dump https://support.mozilla.org/en-US/kb/how-stop-firefox-making-automatic-connections > Firefox_config.txt

Disconnect

Code:

sudo netctl stop mynetworkname

Re-install Firefox 65.0 from pacman cache

Code:

sudo pacman -U /var/cache/pacman/pkg/firefox-65.0-1-x86_64.pkg.tar.xz

Launch firefox, read directions, configure according to directions.
Took a few minutes to complete. This version of firefox has options in different
location/tab from the directions. I disabled everything.

Ok, lets play again.

Code:

sudo tcpdump -lqtni any | tee firecap.txt

Code:

sudo netctl start mynetworkname

Launch firefox, let sit for a 30 sec. while I capture packets and the stdout to file.

Ok, close firefox, lets see what we have. That's just a text file so lets parse it.

Code:

sort -u < firecap.txt
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 0
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 0 
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 1096
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 112
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 144
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 1448
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 15928
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 2407
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 258
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 2896
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 352
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 4344
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 481
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 482
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 483
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 484
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 485
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 532
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 556
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 566
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 616
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 651
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 7725
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 80
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 882
IP 13.249.87.60.443 > 192.168.0.3.36172: tcp 970
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 0
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 0 
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 126
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 31
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 423
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 424
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 425
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 428
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 429
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 430
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 431
IP 192.168.0.3.36172 > 13.249.87.60.443: tcp 517
IP 192.168.0.3.36783 > 4.2.2.1.53: UDP, length 43
IP 192.168.0.3.37518 > 52.88.150.81.443: tcp 0
IP 192.168.0.3.37518 > 52.88.150.81.443: tcp 0 
IP 192.168.0.3.37518 > 52.88.150.81.443: tcp 126
IP 192.168.0.3.37518 > 52.88.150.81.443: tcp 31
IP 192.168.0.3.37518 > 52.88.150.81.443: tcp 361
IP 192.168.0.3.37518 > 52.88.150.81.443: tcp 517
IP 192.168.0.3.39637 > 4.2.2.1.53: UDP, length 47
IP 192.168.0.3.40467 > 4.2.2.1.53: UDP, length 45
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 0
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 0  
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 126
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 137
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 140
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 156
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 177
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 269
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 31
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 38
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 46
IP 192.168.0.3.47800 > 23.44.170.8.443: tcp 517
IP 192.168.0.3.47802 > 23.44.170.8.443: tcp 0
IP 192.168.0.3.47802 > 23.44.170.8.443: tcp 126
IP 192.168.0.3.47802 > 23.44.170.8.443: tcp 194
IP 192.168.0.3.47802 > 23.44.170.8.443: tcp 31
IP 192.168.0.3.47802 > 23.44.170.8.443: tcp 517
IP 192.168.0.3.49782 > 54.200.76.177.443: tcp 0
IP 192.168.0.3.49782 > 54.200.76.177.443: tcp 126
IP 192.168.0.3.49782 > 54.200.76.177.443: tcp 31
IP 192.168.0.3.49782 > 54.200.76.177.443: tcp 517
IP 192.168.0.3.49782 > 54.200.76.177.443: tcp 730
IP 192.168.0.3.51232 > 34.251.59.153.443: tcp 0
IP 192.168.0.3.51232 > 34.251.59.153.443: tcp 126
IP 192.168.0.3.51232 > 34.251.59.153.443: tcp 31
IP 192.168.0.3.51232 > 34.251.59.153.443: tcp 377
IP 192.168.0.3.51232 > 34.251.59.153.443: tcp 517 
IP 192.168.0.3.53374 > 52.84.65.87.443: tcp 0
IP 192.168.0.3.53374 > 52.84.65.87.443: tcp 126
IP 192.168.0.3.53374 > 52.84.65.87.443: tcp 31
IP 192.168.0.3.53374 > 52.84.65.87.443: tcp 335
IP 192.168.0.3.53374 > 52.84.65.87.443: tcp 422
IP 192.168.0.3.53374 > 52.84.65.87.443: tcp 517
IP 192.168.0.3.54131 > 4.2.2.1.53: UDP, length 45
IP 192.168.0.3.55568 > 4.2.2.1.53: UDP, length 42
IP 192.168.0.3.57955 > 4.2.2.1.53: UDP, length 53
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 0
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 1053
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 1447
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 1448
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 258
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 2896
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 31
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 46
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 521
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 77
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 88
IP 23.44.170.8.443 > 192.168.0.3.47800: tcp 912
IP 23.44.170.8.443 > 192.168.0.3.47802: tcp 0
IP 23.44.170.8.443 > 192.168.0.3.47802: tcp 1448
IP 23.44.170.8.443 > 192.168.0.3.47802: tcp 258
IP 23.44.170.8.443 > 192.168.0.3.47802: tcp 31
IP 23.44.170.8.443 > 192.168.0.3.47802: tcp 77
IP 23.44.170.8.443 > 192.168.0.3.47802: tcp 88
IP 34.251.59.153.443 > 192.168.0.3.51232: tcp 0
IP 34.251.59.153.443 > 192.168.0.3.51232: tcp 1448
IP 34.251.59.153.443 > 192.168.0.3.51232: tcp 31
IP 34.251.59.153.443 > 192.168.0.3.51232: tcp 311
IP 34.251.59.153.443 > 192.168.0.3.51232: tcp 374
IP 34.251.59.153.443 > 192.168.0.3.51232: tcp 51
IP 4.2.2.1.53 > 192.168.0.3.36783: UDP, length 183
IP 4.2.2.1.53 > 192.168.0.3.36783: UDP, length 223
IP 4.2.2.1.53 > 192.168.0.3.39637: UDP, length 147
IP 4.2.2.1.53 > 192.168.0.3.39637: UDP, length 181
IP 4.2.2.1.53 > 192.168.0.3.40467: UDP, length 120
IP 4.2.2.1.53 > 192.168.0.3.40467: UDP, length 154
IP 4.2.2.1.53 > 192.168.0.3.54131: UDP, length 163
IP 4.2.2.1.53 > 192.168.0.3.54131: UDP, length 177
IP 4.2.2.1.53 > 192.168.0.3.55568: UDP, length 162
IP 4.2.2.1.53 > 192.168.0.3.55568: UDP, length 97
IP 4.2.2.1.53 > 192.168.0.3.57955: UDP, length 157
IP 4.2.2.1.53 > 192.168.0.3.57955: UDP, length 174
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 0
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 1032
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 11584
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 1448
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 1951
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 242
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 2896
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 416
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 485
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 58
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 638
IP 52.84.65.87.443 > 192.168.0.3.53374: tcp 810
IP 52.88.150.81.443 > 192.168.0.3.37518: tcp 0
IP 52.88.150.81.443 > 192.168.0.3.37518: tcp 118
IP 52.88.150.81.443 > 192.168.0.3.37518: tcp 1448
IP 52.88.150.81.443 > 192.168.0.3.37518: tcp 31
IP 52.88.150.81.443 > 192.168.0.3.37518: tcp 348
IP 52.88.150.81.443 > 192.168.0.3.37518: tcp 51
IP 54.200.76.177.443 > 192.168.0.3.49782: tcp 0
IP 54.200.76.177.443 > 192.168.0.3.49782: tcp 0 
IP 54.200.76.177.443 > 192.168.0.3.49782: tcp 1164
IP 54.200.76.177.443 > 192.168.0.3.49782: tcp 1448
IP 54.200.76.177.443 > 192.168.0.3.49782: tcp 31
IP 54.200.76.177.443 > 192.168.0.3.49782: tcp 470
IP 54.200.76.177.443 > 192.168.0.3.49782: tcp 51

Firefox and amazon are friends. That doesn't surprise me. Even the hardware
that the ISP's give you to use (AT&T)(Comcast) sit there and talk to amazon if you
don't block it in your firewall. So that you can be targeted for advertising.
You can block all of that with a no script or images off, but it's still telling
on you.

hydrurga · 03-06-2019, 02:14 PM

Ok, cheers teckk. I appreciate the time you took to look at this.

There's a possibility that these are calls to Amazon Web Services or other CDN services.

http://forums.mozillazine.org/viewto...f=38&t=2929835

https://groups.google.com/forum/#!to...ox/6lmodAJe7MA

I'll need to look at this further.

teckk · 03-06-2019, 02:46 PM

You may understand that better than me. And why that is necessary.

I've been using Palemoon(Firefox fork), so it has stuff in it's cache. But anyway...

Code:

sudo tcpdump -qtni any

Opened Palemoon, left it open for 1 min, never got a single packet out of it.

And it'll do anything that Firefox will.

Or maybe there are browser features that I just don't use. Very possible since I
use dillo for 95% of web browsing. And just because a browser doesn't send packets
to anyone other that the server whose page you are requesting...don't know if
that means anything either.

Newer members to linux and LQ can get an idea from this thread on how to check
their browsers to see what they are doing. Which is why I posted to start with.

Reziac · 03-06-2019, 02:52 PM

Guessing these connections are mostly prefetch for FF's default homepage, with all its myriad news and advertising feeds. Would be interesting to know if its behavior differs if you set Home to about:blank before ever letting it see a network connection. Or if it matters if you disable cache.

teckk · 03-06-2019, 02:57 PM

I did that. That what post 99 was for. Brand new install, Disconnect, launch firefox first time with no network connection, change all settings first like home about:blank. Then launch it and see who it talks to.