Title photo
frugal technology, simple living and guerrilla large-appliance repair
Tue, 04 Jul 2017

Mozilla convinced me to try Firefox Focus for Android

I'm on Mozilla's mailing list, and they sent me an e-mail about the Firefox Focus browser being available for Android and how it enhances privacy and speeds up browsing by blocking ads.

I'm not one to add browsers to my phone. All of my previous Android phones were storage-challenged, and I could barely keep them running with a bare minimum of apps, so adding browsers just wasn't something I would even consider. And I did add Firefox once, and it took up a LOT of space.

But part of the come-on for Firefox Focus was that it was small and would take up no more than 4 MB of space on the phone.

I have the space for bigger apps on my 16 GB phone. And I know that 32 GB is considered small these days, but I try to pay or less for a phone, and that means 16 GB of internal storage. Maybe a 32 GB phone will cross into my price range during this year's Black Friday. (We try to get a Black Friday phone deal in the sub- every year for the whole family, and I aim to double the phone's internal storage, or I won't do it. We went from 512 MB to 4 GB to 8 to 16 over the past four or five years. The fact that my phones are always storage-challenged has made me reluctant to install apps in general and redundant apps in particular, though with the 16 GB I am loosening up.)

The short version of all this is that I installed Firefox Focus, which has been available for iOS longer and is a recent addition to Android.

It is fast. It is also minimal. No tabs, no bookmarks. It puts up a notification as soon as you use it to forget its history. This all factors into the privacy and the speed. If it keeps me from being tracked in some way, so much the better.

I'm not ready to make it my default browser in Android, but I will continue to use it and follow its development.

Ethical dilemma: My livelihood is supported by websites that sell advertising, and I am somewhat unsettled by major applications that block ads by default. On the other hand, I'm disturbed by the amount of information that is collected, the extent of tracking and the unknowing intrusions into privacy that are all rampant in the service of targeting ads. I'm very, very close to supporting my favored news sources with subscriptions and taking advertising (or at least any guilt over blocking it) out of that portion of my personal media consumption. Plus I'm not blocking ads on any other platforms (principally Google Chrome on Android, Windows and Linux).

But: Am I feeling sorry -- in any way, shape or form -- for Google and Facebook and any revenue they may lose? No. They are doing more than fine as they leverage the hard work of others in order to make billions they don't share, giving "users," be they individuals or companies nothing beyond their "free" service.

Sign of the times: The fact that major applications tout ad-blocking as a key feature says a lot about where the Internet is today, i.e. not in a good place. I fear that the display-ad economy is a false one that will leave many disappointed, crushing labor-intensive news organizations under its fickle, giant-favoring boot.

Tue, 14 Jun 2016

I used Firefox a bunch

I've been using Firefox version 47 for the past couple of days. And it's been working well. This isn't for my day job, where I beat the hell out of the browser, but for "research" (aka looking things up) while learning programming.

Nothing cost $ .

I should probably give it a try for my real work and see how it holds up.

Update: Firefox did better than I thought but not good enough.

Slow rendering in Google Maps was annoying.

It couldn't handle Tweetdeck at all. Nobody would (or should) argue that Tweetdeck is anything but a mess. It is built with unwieldy amounts of JavaScript and delivers messes (or masses) of data. Trying to run Tweetdeck in Firefox was a parade of "unresponsive script" pop-ups that had me bailing out for Chrome within the hour.

I want Firefox to be competitive. I'd rather have fewer eggs in Google's basket. But my web production workflow is just too many windows of pain.

Wed, 13 Jan 2016

Revisiting GNOME's Web (aka Epiphany) browser

The Unix/Linux desktop environment GNOME's many components include a full web browser that used to be called Epiphany and now goes by the very non-Googlable name Web. Yes. it's a Web browser called Web.

Back in the GNOME 2 days, I used it a lot. That wasn't just the GNOME 2 days but the Gecko days, when Epiphany was based on Mozilla's Gecko engine rather than Apple/Google's WebKit.

In the early WebKit days, I think Epiphany/Web went downhill a bit.

Now I use Google Chrome much of the time, though I know in my heart that I shouldn't. I'm usually logged into Google Services for my job, and Google is getting into everything I do.

These days Firefox is just frustrating. Once I get 10 tabs open, it tends to hang when Chrome doesn't.

Maybe a basic browser like Epiphany/Web can help me. Maybe not.

I'll give it a try and let you know how it goes.

Update: Epiphany/Web works very well. I can't say for sure that it's "lighter" than Google Chrome, especially since it uses the same Webkit engine.

What I can say is that for general-purpose web-browsing, it is very fast and stable. And I bet Google is tracking me a whole lot less.

Epiphany is a simple browser. Like Firefox was in its early days.

It's well-integrated as a GTK3 application, so it'll look good either in GNOME 3, or (in my case) among all the other GTK3 apps I'm using in the Xfce desktop environment.

For search, Epiphany defaults to Duck Duck Go which bills itself as "the search engine that doesn't track you," and so far I'm happy with it. It's nice to have an alternative to Google, even in a Web browser using the same engine as a browser that is most definitely tracking you.

I'm not saying I will give up on Google Chrome, especially for my , but when it comes to personal browsing, I can see myself in Epiphany much of that time.

Fri, 30 Oct 2015

Fix for Firefox dark theme issues in GNOME 3

Hey Linux users, are you using GNOME Tweak Tool to choose the "Dark" theme, making your GTK3 applications dark and causing problems with white-on-white text in the Firefox browser?

I have. Even though I almost never use GNOME 3, I do have it installed, and the GNOME Tweak Tool's "dark theme" switch enables me to turn GTK3 applications like Firefox "dark" in their styling. Except that often you can't read text boxes on web sites because the "dark" theme turns the text white while also leaving the background white.

Read the rest of this post

Tue, 05 Aug 2014

How to get Google Chrome to stop crashing while running the AMD Catalyst driver in Linux

If you're having the same problem I am with Google Chrome crashing while running the proprietary AMD Catalyst video driver in Fedora 20 (or any other version of Linux), I have a fix.

My thought was that I could play with command-line switches to "trick" Google Chrome into running.

(Note before we begin: I think different distributions have different commands to run Google Chrome or Chromium in the first place. In Fedora, calling google-chrome runs the browser.)

I found a huge list of command-line switches for Chrome and Chromium from Peter Beverloo's web site and started looking it over and trying a few.

This one worked:

$ google-chrome --disable-gpu

Peter's page describes --disable-gpu this way (and links to this portion of the content-switches code for Chromium):

Disables GPU hardware acceleration. If software renderer is not in place, then the GPU process won't launch.

This means that I'm back in the Google Chrome-running business. I'll have to add this modified command-with-switch to my Xfce panel so I can run Chrome without the terminal.

And now you can, too.

Sat, 19 Jul 2014

Am I the only person who can't run Google Chrome under Linux with the AMD Catalyst driver?

Am I really the only person having trouble with the Google Chrome web browser while running the propretary AMD Catalyst video driver in Linux?

Just checking.

Wed, 25 Jun 2014

Google Chrome fails in Fedora 20 with AMD Catalyst, runs fine with open Radeon driver

I pulled the AMD Catalyst driver from my Fedora 20 system to do some tests. Among the things that started working: The Google Chrome web browser, which in recent weeks kills X while running under the proprietary driver.

It turns out that Google Chrome runs fine with the open Radeon driver.

As always, AMD Catalyst giveth (cooler operation, working suspend/resume) and taketh away (Google Chrome fails, trouble updating when driver doesn't support new kernels, general wonkiness).

Fri, 13 Jun 2014

Google Chrome ran on my Fedora 20 system a couple of days ago but does no longer

A couple days ago, there was a Google Chrome update, and for some reason the browser began working once again on my Fedora 20 system.

Now it's broken again.

It could have been a Mesa update in Fedora. Or something completely different. It could be the dubious AMD Catalyst/fglrx installation I have going, using Fedora 19 packages in Fedora 20.

Whatever it is, Google Chrome is broken again.

I even tried Spot's Chromium repo for Fedora. Chromium crashes X just the same.

Is it just me, or is anybody else having a problem with Chromium/Google Chrome in Fedora?

Wed, 11 Jun 2014

Google Chrome browser is working again on my Fedora 20 system

Google Chrome (using the Google repository because Fedora doesn't package Chromium) is working once again on my Fedora 20 system.

It had been broken for a few weeks. Whenever I started the browser, it would segfault and kill X.

Google pushed a new stable version of the browser today to its Fedora repository. I did the update, started Chrome and am now running it with no crashes and no problems.

Thanks, Google.

Fri, 23 May 2014

The latest Google Chrome browser is segfaulting in Fedora 20

I don't run Google Chrome all that often in Linux, though I run it all the time in Windows.

But I do keep Chrome, via Google's repository, on my Fedora 20 system.

So I try to run it today and it segfaults (I know because it kills X and I see "segfault" in the console messages).

I searched (yes, using Google) and couldn't find anything on this.

I can't remember if I've used this particular version of Google Chrome successfully before my most recent reinstall of AMD Catalyst (via the Fedora 19 packages in RPM Fusion).

Right now I'm unwilling to uninstall Catalyst just to test Chrome, especially because I'm primarily a Firefox user on this machine.