PF4Public

> have you had problems ever since you started using the patches? Unfortunately I don't have the hardware. I'm aware of only two people, who actually have and use the...

Could it be, that you need to compile Chromium with Ozone and DRM/GBM, like it is done in ChromeOS? [Ozone Overview/#DRM/GBM](https://chromium.googlesource.com/chromium/src.git/+/master/docs/ozone_overview.md#drm_gbm)

Have you tried [Cookie AutoDelete](https://github.com/Cookie-AutoDelete/Cookie-AutoDelete). It does not entirely fulfil your need, but still might be a good solution to your problem.

> I raised this issue as a feature request, rather than a question. This could be a non-trivial feature, which lowers the chances of it being implemented, hence there might...

Those approaches are not that complicated to do oneself without adding any additional; patches into ungoogled-chromium. Each additional patch increases the entropy and hardens the maintenance. One should be very...

By the way, showing this First-run page could be one of the options for #1971

Sorry, I reserved the first message to write more, but didin't have time and inspiration to begin. My intention was to 1. firstly discuss the implementation details and I agree...

I think, we should include some of the most often asked questions into the first-run page in text in order to answer those questions right from the start without needing...

Do I get it right: there is something in Chromium (not Chrome?) that blocks ads, right? Is it somehow disabled by ungoogled-chromium patches?

From the website perspective there is no big difference be it a "built-in native" or "extension" adblocker.