While most clients seem to automatically set "sensitive" to true if a content warning is used, some clients don't. This leads to situations where some folks can set a content warning, assume that media will be marked sensitive, and then accidentally create posts with a content warning, but unblurred media, leading to embarrassing situations like posting bare-ass nudes on the timeline immediately visible. We should probably just set the "sensitive" flag to "true" on the server side if a client doesn't do it.
While most clients seem to automatically set "sensitive" to true if a content warning is used, some clients don't. This leads to situations where some folks can set a content warning, assume that media will be marked sensitive, and then accidentally create posts with a content warning, but unblurred media, leading to embarrassing situations like posting bare-ass nudes on the timeline immediately visible. We should probably just set the "sensitive" flag to "true" on the server side if a client doesn't do it.