| |
In lugnet.off-topic.debate, Tom Stangl writes:
> Right, but once Yahoo has spit out that content, you save it, and modify it
> any way you want to.
Sure, and then when someone clicks "next" or "previous" for that Ring ID,
the Yahoo! server sees that the corresponding JS code for that Ring ID and
Site ID hasn't been fetched recently by that IP address, and it gacks (by
design) and it sends you to some Yahoo! advertising page instead.
And it would *know* that you'd cheated around their JS requirement because
it wouldn't show the next/prev links in the first place unless JS was on.
So if someone requested a next or prev, they'd know that you weren't using
the JS. And they could make the output JS non-caching.
Dunno if this is how it works now, but it *could* work that way later if it
doesn't work that way now. It would be *so* easy for them to enforce the JS
requirement that you have to _actually_ link to their JS code if you want
your ring to work. Just some food for thought.
--Todd
|
|
Message is in Reply To:
48 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
