If your service publishes status/outage info as JSON ...
... but then you 403 when curl or other automated tools are used to harvest what is supposed to be explicitly machine-readable data ...
... then you are bad, and you should feel bad.
If your service publishes status/outage info as JSON ...
... but then you 403 when curl or other automated tools are used to harvest what is supposed to be explicitly machine-readable data ...
... then you are bad, and you should feel bad.
If you have a fediverse account, you can quote this note from your own instance. Search https://infosec.exchange/users/tychotithonus/statuses/116236581182468856 on your instance and quote it. (Note that quoting is not supported in Mastodon.)