> requesting the broadcast from your provider This is identical with HTML. I request a page via HTTP, and they send it to me. What I do with that page is up to

> requesting the broadcast from your provider This is identical with HTML. I request a page via HTTP, and they send it to me. What I do with that page is up to me. Just like I can mute a commercial on TV, change the channel, or shut the TV off[1]. > they have some say as to how they package up the data you ask for. Correct. The problem comes when this is extended to include what someone does with that data after it changes hands. We have historically described this situation as the publisher's rights ending at the "1st sale"[2]. Anybody that wants rights to restrict what someone does with the data they are sent should get a contract that describes these requirements. (an EULA, writing at the bottom of a previously-requested page, and the HTTP headers are not contracts) As for paying by CPU usage: I'll run the javascript and load the image or video files only after I receive a payment for electricity usage (CPU time) and compensation for my lost personal time. Hourly rates are available upon request. > The right solution is somewhere in the middle. The right solution respects users instead of trying to move the Overton Window[3]. [1] Max Headroom, Episode 1.6 "The Blanks" Janie Crane: "An off switch?" Metrocop: "She'll get years for that. Off switches are illegal!" [2] https://en.wikipedia.org/wiki/First-sale_doctrine https://en.wikipedia.org/wiki/First-sale_doctrine [3] https://en.wikipedia.org/wiki/Overton_window https://en.wikipedia.org/wiki/Overton_window