mirror of
https://github.com/gorhill/uBlock.git
synced 2026-03-11 09:04:36 +00:00
01e36db23a
Related issue: https://github.com/uBlockOrigin/uBOL-home/issues/326 uBOL now asks broad host permissions by default. Users can still choose narrow host permissions by using their browser's controls for this. For instance in Chromium, those host permissions controls are found in the "Site access" section in the detailed view of an extension. One can set "Site access" to "On click" to revoke broad host permissions, and grant host permissions to only specific site. In such mode, uBOL will still block through the DNR API, but no cosmetic or scriptlet filtering will occurs, as these requires permission to "read and change data" on websites for which higher filtering mode is desired. Some browsers do not automatically grant broad host permissions even when an extension asks for broad permissions at install time, and going forward all browsers will likely adopt this approach, and thus it no longer made sense for uBOL to default to no broad hosts permissions at install time, especially given this leads to issues with no solution -- issues solved with the new approach (e.g. like the ability to deploy uBOL in Optimal mode by default).
12 lines
854 B
Text
12 lines
854 B
Text
uBO Lite (uBOL) is an MV3-based content blocker.
|
||
|
||
기본 규칙 목록은 uBlock Origin의 기본 필터 목록과 대응됩니다.
|
||
|
||
- uBlock Origin 내장 필터 목록
|
||
- EasyList
|
||
- EasyPrivacy
|
||
- Peter Lowe’s Ad and tracking server list
|
||
|
||
설정 페이지에서 규칙 목록을 더 활성화할 수 있습니다. 팝업 창의 _Cogs_ 아이콘을 누르세요.
|
||
|
||
uBOL은 완전히 선언적이라 필터링 중 영구적으로 실행되는 uBOL 프로세스를 필요로 하지 않으며, CSS/JS 주입 기반 콘텐츠 필터링이 확장 프로그램이 아닌 브라우저 자체에서 더욱 안정적으로 동작합니다. 즉 uBOL 자체는 콘텐츠 차단을 하는 동안 CPU/메모리 리소스를 소비하지 않습니다. uBOL 서비스워커 프로세스는 사용자가 팝업 창이나 설정을 열었을 _때에만_ 동작합니다.
|