Page MenuHomePureOS Tracker

Purebrowser 68.0.2esr-1pureos3 shows Firefox home page in the home and also in new tabs
Closed, ResolvedPublic


After an update to Purebrowser 68, purebrowser now shows Firefox Home page with quick links to proprietary services (youtube, google, amazon).
And the default selection for now opened tabs now is also Firfox home page.

This is likely related with

Event Timeline

I would mark it as a Freedom Issue.

I don't recognize this as a freedom issue - care to elaborate, @EchedeyLR ?

EchedeyLR added a comment.EditedAug 30 2019, 10:31

Showing that is like recommending these non-free network services by default.

It is true that Freedom Issue here is related with non-free software being attached with a software and/or packages, but I think recommending non-free network services should be included on that.

Maybe its good to investigate deeper which of those Links actually appear to be annoying us.

Sure, proprietary services in general but Youtube, Google and Facebook are sadly still famous websites. I recommend only removing of the two shopping Links: Amazon and Ebay.

We could just replace those two with and

Additional ideas if we really want to remove Google Search and Youtube too: instead of Google Search. We have already consens in DDG is the standard search engine in pureborwser. is the clean search-only page of DDG (without popups appearing on,, instead of Youtube. Its serving YT search results while respecting users privacy. Released under the AGPLv3:

@Badger Thanks for the suggestions. Please, however, file those as separate issues (i.e. wishlist requests).

@EchedeyLR I agree that this issue is an issue for PureOS. It is not a freedom issue however: That tag has a specific definition tied to (if you think the definition should be changed then please discuss that with the GNU project).

@jonas.smedegaard thank you for the clarification.

jonas.smedegaard closed this task as Resolved.Sep 19 2019, 04:16
jonas.smedegaard claimed this task.

PureOS has reverted to PureBrowser based on Firefox 60.x so this bug is fixed (for now...).