131–140 of 303 posts
Earlier quoted context omitted.
Presumably the worry is that the big ad companies would get approximately every website in the world to use this technique, which is already the only reason web advertising is such a big problem.
Thankfully, the biggest ad company - Google - would hate it because it would dramatically reduce page performance. And webpage performance apparently has a big impact on ad clickthrough rates.
Why do people love JavaScript and want everything written in it?
Earlier quoted context omitted.
> Deliver your site only to the "inner browser" (that the user has no control over because it's heavily obfuscated and tricked-out with anti-debugging code) and you eliminate all ad blockers. Throw some DNS-over-HTTPS w/ certificate pinning in for good measure and you kill DNS-based ad blockers too. I'm confused how the "inner browser" meaningfully helps you accomplish this. How is this any easier or more effective t…
Well the idea is stupid and makes no sense but > How is this any easier or more effective than just having a website that hosts its own advertising assets advertisers REALLY don't want you to do that because it's far too easy to cheat.
Earlier quoted context omitted.
At that point I'm just going to have my ad blocker block the entire "inner browser." No website that would employ such a lovecraftian horror is worth visiting anyway.
Presumably the worry is that the big ad companies would get approximately every website in the world to use this technique, which is already the only reason web advertising is such a big problem.
Earlier quoted context omitted.
Presumably the worry is that the big ad companies would get approximately every website in the world to use this technique, which is already the only reason web advertising is such a big problem.
Thankfully, the biggest ad company - Google - would hate it because it would dramatically reduce page performance. And webpage performance apparently has a big impact on ad clickthrough rates.
There's a product here that's been waiting to happen for awhile. I've been anticipating somebody cross-compiling another browser engine to WASM but this works, too. Deliver your site only to the "inner browser" (that the user has no control over because it's heavily obfuscated and tricked-out with anti-debugging code) and you eliminate all ad blockers. Throw some DNS-over-HTTPS w/ certificate pinning in for good meas…
I think this evokes the static vs dynamic linking argument again though. If you consider your browser client code as your "source code" and the browser as a "dynamically linked library", then there are substantial pros and cons. Your proposal, while feasible, turns this into a static linking affair. This comes with many risks, like becoming complacent and not updating the "inner browser" due to browser incompatibilit…
user doesn't want to download an app, since that has a lot of friction. Going to a url and waiting (even if the download time is the same) feels like there's less friction, and so this idea of shipping a blackbox is more desirable.
The only problem really is the jankiness of any non-browser controls. The user expects a good right-click context menu, keyboard navigation, scrolling, etc, which all would have to be implemented if you're compiling a native app into WASM. But if the app itself is just HTML+javascript, then shipping a WASM browser, then using that browser as the app layer solves all of those UX jankiness (since the user should not really be able to tell it's a WASM browser).
The idea is insidiouly bad for user freedom, but great for businesses like google (who wants to control the user space completely).
Earlier quoted context omitted.
Presumably the worry is that the big ad companies would get approximately every website in the world to use this technique, which is already the only reason web advertising is such a big problem.
> ad companies would get approximately every website in the world to use this technique I really doubt it, but if that did happen then I could simplify my filter list to just a single wildcard. Silver lining.
I think it's an inevitable future tbh. The users have lost - they just dont know it yet. Google's WEI [1] is their first foray into this, and i dont doubt there will be future iterations they try to push through. The browser-in-browser is but one alternative idea.