3 ms·
Unfortunately the first two options aren't really viable if you're an ad supported website. HTTPS will kill your ad revenue since most ad scripts don't work pro
by r1ch 11y ago
Unfortunately the first two options aren't really viable if you're an ad supported website. HTTPS will kill your ad revenue since most ad scripts don't work properly over HTTPS.
- dogma1138 11y agoThat's a problem for site operators not users if more people force sites to switch to HTTP's more AdNetworks will start serving content via HTTPS. The good thing is that at least most browsers these days are good at blocking mixed content so you won't have HTTP adds growing tumors due to injections anyhow. What i don't understand is why AT&T has to do injection in the 1st place they can easily setup their own AdNetwork and partner with the large AdNetworks to route through AT&T's own internal servers.
- rsanders 11y agoWithout injection, their own ad network is irrelevant. Nobody (more or less) is getting on Free AT&T Wi-Fi to visit AT&T's websites. Without injection, any ad revenue goes to the actual site operators.
- dogma1138 11y agoWell that was a given in my statement... hence partner with the large AdNetworks, use the already existing scripts which are integrated much better into the existing sites, AT&T can simply server all requests to www.big.ad.network/ads.js from it's own servers in it's own internal network serving ads from their internal campaigns sharing revenue.... Heck considering that the ads AT&T can serve can be much more relevant to a specific location such as a mall, a large venue, or an airport heck even stores within say half a mile of the hotspot they might actually be "useful". Adnetworks are saving bandwidth, AT&T doesn't have to fight with HTML injection which can break on many sites, AdNetworks get better targeted advertisement win for everyone...
- bpicolo 11y agoAds are fine over https. Choose your ad networks wisely.