I've found generally they do not know the answer, but are presumed to know and as a result instead of saying "I don't know" will use the points outlined to seem like they do know.
This assumes you have shell and those tools installed via your Dockerfile. Best practice is to have a multi stage build and just have the working binary, keeping the image as light as possible.
So when do you make a fat image with debug tools and when do you keep it skinny?
For one you can disable the popup ads. Additionally you get paid if you do enable the ads. So it's quite a different system where the user is put first in both cases.
> outside of screwing over the content creator. You're visiting a site for content, and the one really getting paid is Brave
I really wish I had focused on subscription growth instead of ad growth when I was in the content business (I had a few sites over 1m uniques per day). There's just something to delivering something so valuable that readers are willing to pay for it. You end up being much more focused on quality instead of driving ad clicks and directing your readers off site. That said, times have changed a lot, and people now seem much more willing to pay than 10 years ago.
You are getting paid as well. If you want to reward the content creator, you can.
To me that model is a lot better than the status quo. Content creators that I think are producing quality content get rewarded, while those pushing content to attract eye balls lose power.
Not with BAT. But Brave buys the BAT it gives users from the open market using their ad revenue, as far as I know. Which means the creators can sell the BAT for real money, which does pay bills.
The creators that I do support get more from me in BAT than the zero dollars they get from my viewing of their content in Google/Facebook/Twitter/Youtube. This is what matters.
