I can't count every web site that has an API, but examples include Amazon, eBay, and Twitter.

One can only hope that things will get better.

I did scraping before (and note that we aren't talking about screenscraping here, but rather website scraping) - I once wrote a scraper that presented an entire online forum as a newsgroup. Based on my experience with that, and on the layout of the RCW website, scraping this particular thing is absolutely trivial.

I agree that we shouldn't have to do that. I'm just saying that I find it doubtful that they do it to extract money from people, because I just don't see that working well when it's so easily scraped. If someone were to hire me to do that, it'd probably take me something like a few hours, and I wouldn't ask more than $200 for such a job.

If it's not "I/O gapped" - that is, if state changes aren't completely undetectable outside of the "secure environment" - then for all practical purposes it's not what we used to mean when we said something was "air-gapped."

In today's standards, it needs to be in an EMF-shielded room with an independent power supply (probably batteries), and it needs to be powered down completely when the shielded room's doors are open.

The way the laws are laid out on that website, it would be trivial to scrape them into a single document. Even the URLs there are very predictable, making it particularly easy. For $615/year, I'm sure someone would do it.

All I can say is that I regularly look up RCWs pertaining to different things where I have doubts or am just curious about it, and so far I haven't found any trouble finding the relevant bits.

From a lawyer's perspective, perhaps this all is still missing crucial bits. If providing, say, a single-page HTML download would be immensely useful, then sure, they should do it (especially as they already likely have some kind of script along these lines, as you do have a single-HTML option for individual chapters).

So far, all the people responding to my example have overlooked one crucial word in it: "force". Does Finland merely provide incentive for people to maintain a healthy lifestyle? Or do they actively force people into such a lifestyle. That's the main distinction here.

Using "some sort of server-side code" would require re-sending the entire web page if one small part of it has changed. This is slow and expensive on cellular or satellite connections. It also requires a hosting plan that allows use of "some sort of server-side code", unlike ad-supported shared hosting providers that have historically supported only static HTML files.

As for "web page", AJAX apps do exactly this. As for "native app", good luck getting a Mac-only native app to run on your Windows PC.

Then let me reiterate the question I linked above: How should I, as a server administrator or as the developer of an application that will be installed on servers by third parties, go about determining at any moment in time what "the top several" OpenID Connect identity providers are?

This when one user instructs another on how to use the site:
"...and look in the right column."
"What right column?"

Also, how do you avoid loading the HTML that goes into the hidden columns so that mobile viewers don't have to pay data overages for things they'll never see?

In theory, that's the point. In practice, the web browser included with Windows (Internet Explorer), OS X (Safari), and iOS (Safari) has tended to lack support for key web standards. For example, the latest version of Internet Explorer for the oldest supported version of Windows didn't support most HTML5 features until April 2014, when support for Windows XP was ended, and it won't support WebGL until April 2017, when Microsoft plans to end support for Windows Vista. Safari for iOS didn't support photo and video uploads through the browser prior to iOS 6 nor WebGL prior to iOS 8. A lot of browsers still lack support for, say, plugged-in USB joysticks. For anything that the user's browser doesn't support and which cannot be polyfilled efficiently if at all, the user will need to install a native app.

Please don't start a sentence in the subject and finish it in the comment. It makes it harder to quote your post for context.

I can think of three kinds of interstitials, each with a different set of who pays and who earns. For ad interstitials, the advertiser pays, and the ad network and the "publisher" (site on which ads are placed) earn. For stickiness interstitials, such as follow us via e-mail or Twitter or download our app, the same happens except much later when the user visits again later and views more ads. For subscription interstitials, the user has to pay to make the box disappear.

I've seen this with "1 weird trick" clickbait ads that lead to a 20-minute video infomercial with no progress meter. Click the back button or close box, and they will replace the video with a transcript and put up an "are you sure" to let the viewer choose to finish the ad in case the viewer prefers text to video.

FPGA can also have backdoors.

Thank you for illustrating my point so eloquently. It's precisely because of people like you that this line of reasoning is so fraught with peril.