Which was actually my point. I don't see anyone willingly adding a feature to actually restrict functionality the way a currency detection engine would/does. At

Which was actually my point. I don't see anyone willingly adding a feature to actually restrict functionality the way a currency detection engine would/does. At least, in an open source project, I think there would be enough resistance from contributors to keep such components from becoming standard features. This I consider a good thing about the GIMP, Krita, and any/every other FOSS graphics package out there. That said, it does present a pretty little puzzle for the FOSS community. Given governments' recent roles in expanding the reach of FOSS software, I don't think we can ignore the question of what happens when and where the interests of the state conflict with those of the FOSS community. Here, specifically, we have a case where a government may desire a "feature" anathema to the community, but likely can't force the community to accept such a requirement. What they might be able to do is outlaw any version of the package which does not incorporate the restriction. How effectively can could they enforce it? Not much, perhaps, right now, but we'd be fooling ourselves to think they never could. It's all but certain they're going to keep trying, even if it proves utterly impossible. Thank you for responding, A1kmm. This is what I was really hoping to see: some actual discussion of the point. In any case, I apologize for offending whoever downmodded me. I'll try not to be quite so snarky in future.