In T821#15452, @jeremiah.foster wrote:

The plan is actually to deprecate PureBrowser as Mozilla doesn't share the same goals we put forward and that makes it a lot of work to ensure that our user's privacy is protected.

@jeremiah.foster That's a good plan but it's not yet ready, is it? This hiatus is not acceptable. I suggest fixing PureBrowser and overtime you can replace it by GNOME Web (I'm sure it will not look splendid in Plasma though). Anyways, when can we expect GNOME Web to be up to the job?
Lol!

@todd If we can't deal with this issue in-house, maybe we should out-source it to people who specialize in browsers. What do you think?

WebKit is in fact the same browser engine that Apple's Safari uses. https://webkitgtk.org/

The changes in PureBrowser come from changes done upstream by Mozilla. It is resource intensive to continue to use their browser when we're investing in GNOME Web (which runs WebKit.)

I've just checked GNOME Web and it is not ready for real-world usage. It is very basic and has absolutely no tracking protection whatsoever. Currently the only browser that is usable is Chromium. With Ublock from Google :-)

Until you've got something that is good enough to replace PureBrowser, you should absolutely fix PureBrowser. I've been thinking that Falkon is underdeveloped. Well, with all due respect, GNOME Web is even more underdeveloped. Are you even using it at all? Can we please think deeply and rationally for a second? Can we please not give in to our emotions and think from a technical perspective? Please have PureBrowser fixed! Close it down if it makes you happy but I suggest you leave it on the board. Thank you.

T814

Neither KDE nor Gnome can make browsers because neither of the 2 communities are in the browser business. Deny it! So it makes perfect sense to re-use the code base of either Firefox or Chromium with some adjustments. That's what all sane projects are doing. If you don't want to deal with Firefox anymore, then may I suggest making ungoogled-chromium the successor PureBrowser? I'm kindly submitting to your attention the following link and all the links within the link: https://chromium.woolyss.com/ Thank you.

Until recently T814 we didn't know whether it was a PureBrowser issue or a Ublock issue. I think it is fair to assume that as soon as Ublock gets re-packaged in Amber, we can close this down. Some relevant aspects have been touched upon, although not strictly related to the task. A task should never diverge from its intended purpose or duplicate another task. It is indeed easier to merge than to split although enforcing separation is not always easy or even possible.

@jonas.smedegaard Provided that my style or the lack thereof has irritated you, I'm sorry for that.

Either this is a needless duplicate of T814 or it is a call to leadership about special-treating T814. In either case my participation is irrelevant.

@Squid Please respect my unsubscribing from this issue. Please don't subscribe me again.

Please respect my unsubscribing from this issue. Please don't subscribe me again.

Deal.

An error occurred during a connection to error.woolyss.com.
This problem can sometimes be caused by disabling or refusing to accept cookies.

{F333687}Hmm. I only know that I had been previously able to access it without issues on Chromium with uBlock Origin and HTTPS Everywhere from Google As a side note, uBlock Origin from Google was significantly more tolerant to trackers. Needless to say that I don't intend to re-install Chromium or ever again get any add-ons from Google.

@Squid this issue is a clearly a duplicate of issue T814 were the cause of the problem with uBlock Origin has already been identified. And a temporary solution until the issue can be permanently resolved.

So maybe this ticket can be closed and just track this issue from T814?