Anonymous
9/3/2025, 5:47:22 AM
No.106469683
>>106469686
>>106469728
>>106470646
>>106470664
>>106470886
>>106471068
>>106471096
>>106471164
>>106471276
>>106471428
>>106471601
>>106472373
>>106472469
>>106472889
>>106474509
>>106474696
>>106475168
>>106475513
Compiling UBlock Origin
Google has decided to play hardball with Ublock Origin. I need adfree gooning or I'm going to get blueballs. Should I just compile it from the source and load it in developer mode? I have already messed with the flags, but it seems like Google is messing with that option too. I realized that in the time I have been searching for config options I could have just compiled it. What work around are you using Anon? I'm using Chrome.
Google Chrome 140.0.7339.80 (Official Build) (64-bit)
Revision 670b6f192f4668d2ac2c06bd77ec3e4eeda7d648-refs/branch-heads/7339_41@{#3}
OS Linux
JavaScript V8 14.0.365.4
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36
Command Line /usr/bin/google-chrome-stable --flag-switches-begin --enable-features=UnexpireFlagsM138,UnexpireFlagsM139 --flag-switches-end --ozone-platform=wayland --render-node-override=/dev/dri/renderD128
Executable Path /opt/google/chrome/google-chrome
Profile Path /home/user/.config/google-chrome/Default
Google Chrome 140.0.7339.80 (Official Build) (64-bit)
Revision 670b6f192f4668d2ac2c06bd77ec3e4eeda7d648-refs/branch-heads/7339_41@{#3}
OS Linux
JavaScript V8 14.0.365.4
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36
Command Line /usr/bin/google-chrome-stable --flag-switches-begin --enable-features=UnexpireFlagsM138,UnexpireFlagsM139 --flag-switches-end --ozone-platform=wayland --render-node-override=/dev/dri/renderD128
Executable Path /opt/google/chrome/google-chrome
Profile Path /home/user/.config/google-chrome/Default