I'm sorry Dave, I'm afraid I can't do that

I've been a "Linux as my main workstation" person from the Before Times - when you had to go to war to get your sound and/or graphics to work. At my first job, I was given a shiny Macbook and I wanted to change the desktop background to black. I could not. The options were various pastels. I asked the Macbook users on the team to help. They could not. One joked that the restriction was to make sure I didn't pick something tasteless. It's annoying when the tools you are supposed to depend on capriciously dictate what you can do with them.

Recently I needed to build a Country picker widget - a thing I've done a few times. This time I asked Claude to build it. I ran into errors.

API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Output blocked by content filtering policy"}

After some trial and error I concluded that it didn't like a country on the list. Which one? I didn't know. I could build a small country picker with a handful of countries, but the whole thing? Nope. Some internet research found GitHub issues where people think Russia might be the offending country. I considered having Claude do trial and error to figure out which one, but eventually decided to build the widget myself. Didn't want to risk getting an account ban for perceived attempts to violate content filtering.

Got me wondering though, what happens in a world when the tools required to build software police the software you want to build? What if I want to build something tasteless?