“The Weather Service’s proposed remedy is to limit users to 60 connections per minute on a large number of its websites that provide weather observations, forecasts, warnings, computer model data, air quality information, aviation weather support and ocean conditions.”

Well that sounds incredibly reasonable in general, but it completely depends upon what type of interface they’re providing. Do you have to query all of those things separately for every locality you serve?

Honestly, this is why so many big companies still prefer things that HN would call “stupid” like an FTP drop of a file 5 times per day/hour/etc.

Every FTP implementation I’ve ever seen has included either checking the timestamp, timestamping the filename and filtering on that, or moving to an “archive” folder after processing. Most of the API implementations I see ignore the fact that HEAD requests exist, cache headers can and should be used, etc.