@mntmn @aral @david That's cool, Epiphany will happily run without the whole of GNOME. I do use it myself as daily browser, most of the time on Sway or Budgie because running GNOME Shell is not an option: the Shell takes so much RAM that there is not enough memory left to link debug builds of WebKit :thounking:

Taking into account that the last days I've been also chasing gremlins in the build bots, which took time, and that I did have social life during this weekend, it's solid progress :blobpats:

More on the content extensions saga for the GTK+ and WPE ports: today I landed some cleanups for the SharedMemory factory functions (used indirectly), rebased the rest of the code on top of that, moved the new WebKitContentFilterError into a more appropriate location (WebKitErrors.{h,cpp}), and made sure that the documentation for the new API bits gets built. Still pending to enable the layout tests and rephrasing the docstrings a bit here and there.

I'm looking for a kitten to adopt but people won't respond to my messages

It feels good to start a branch of GNOME's web browser where the first commit is a big removal that kills the old, memory-hog ad blocker. Next up: add the new ad blocker, using 's built-in content extensions support.

The new code only needs to care about downloading the filtering rules and using the new API to compile and make WebKit use them.

For testing I have EasyList (what Ephy uses now) converted to the JSON format, and using @aral's Better ruleset is the final target 🧐

Well, after an intense afternoon and evening of debugging, the fix turned out to be a one-liner. Now I need to finish the busywork (enabling layout tests, making sure to not break the build for other ports, fixing the style checker, and so on) but I am getting quite confident that the content extensions support will be a new feature in and 2.24.x

"JavaScript growth and third parties" by Steve Souders speedcurve.com/blog/javascript

"JavaScript is the main cause for making websites slow. [Compared to 7 years ago, ] 1st-party JS doubled from 53 KB to 106 KB. 3rd-party JS octupled (!) from 32 KB to 258 KB."

What's most remarkable is that this happened even with the rise of bundlers, which effectively make 3rd-party JS "look" like 1st-party. In other words, that 1st-party growth is probably node_modules; the 3rd-party growth is ads/trackers/???.

Quick update on content extensions in and : landed a couple of patches upstream in preparation for the actual big patch. The new API bits are looking solid and the MiniBrowser now had a CLI option to load a JSON filter rule set.

Pending: enabling the layout tests and solving another assertion — the one from last week is solved and now I kind of understand the disk format of compiled extensions as a side effect. It looks like next I'll need to dive in the bytecode compiler itself

Also, realizing this, if it is true in reality (so far it's a theory floating in my head), kind of helps explain the demise of Firefox OS — it may have even been doomed from the start!

Also, while possible, restricting what native apps can effectively collect or do requires system modifications: a custom ROM, or some kind of non-stock modifications (for example Xposed on Android). On the other hand, even my dad knows how to install a Firefox extension: getting a Web engine tweaked is much more approachable.

Surveillance capitalism prefers native apps, so they make their websites suck on mobile, even when we had the technology to build good mobile webapps for many years 🧐

It just dawned on me that one reason why webapps have not been doing great compared to native mobile apps is that running on a more sandboxed environment (a Web engine) kind of makes collection of user data and presenting ads kind of more difficult. Many users know that adblockers (and to some extent tracking prevention tools) exist for browsing the Web so they would expect the same or similar for Web apps. Native apps? Users have no previous expectation, and it is more difficult to limit them.

@aral That made me remember that my website also uses the Google fonts service, I should just serve the web fonts from my own server and convert the header text logo to SVG, which is the only tricky part ad it uses the automagic font subset feature. Having a SVG in 2018 is just fine, now that I think of it any reasonably decent web rendering engine supports it nowadays :thaenkin:

Seriously considering a series of blog posts about reducing the disk and memory footprint of .

Recently I have been working on an device which has a 256 MiB memory budget for the embedded Web engine, which is used for the user interface. I have also gotten some report about running WPE on 128 MiB, which is very tight, but definitely doable depending on which Web content one throws at it... I would not recommend 128 MiB for browsing random Internet pages, though! (Tons of JS, anyone?)

It looks as if I might be getting a slight flu, which is something I definitely wasn't looking forward to. Let's see how it goes tomorrow after a good night's rest :blobpats:

On the Edge team, we had a *whole team* dedicated to finding compat bugs, reducing them, and reaching out to site owners with fixes. Sometimes we would reach out to a site owner and they'd say, "Sorry, you don't have enough market share for us to bother fixing this bug."

This is where we get -webkit prefixed CSS in the standard, as well as de-facto standards and "works best in Chrome." This is why both Opera and Edge switched to Chromium.

If you really want to help Firefox succeed, file a bug on webcompat.com/ when you find a broken website. Don't just switch back to Chrome; let Mozilla know there's a problem so they can try to fix it.

When browsers lose market share, they fall into the "compatibility death spiral." Sites don't bother to test, they break, and users flee to the browser that "just works." Mozilla is fighting this battle every day, and it just got harder.

my company (MNT) is looking for office/production space in berlin, around 50sqm. preferably kreuzberg or mitte. we’ll be working on open (libre) hardware and software with a team of three. if you hear sth, please write to lukas@mntmn.com. 🙏

Show more

Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!