To build on @bruno point abt friction, here's the use case I keep thinking about:
Imagine I set up an instance, i don't know, food dot town. It's an instance all about sharing food pics And these food pics? They're Incredible.
Over on bike dot bike, on the other hand, food posting is encouraged, but the norm is using a CW when you post images of food.
Now: Mic@bike.bike wants to share food.town content. What do they do?
If this doesn't make sense, substitute "food" for "surgery" or "porn"
(I keep coming back to "instances should be able to set up a set of C/Ws that boosters can add as they boost" as a potential solution.)
@austin_walker the closest the current infrastructure gets is tech/cues certainly would allow an instance admin to wrap any boosts originating from a (particular) other instance with a (paired) boilerplate C/W _in the webclient_—I would need to look deeper into if it could be wrapped around status regardless of client.
@nightpool I'm not assuming you would dismiss it out of hand, I'm saying the messaging around why QRT-equivalent behaviors are not desirable is compelling—and I'm not a strong enough interaction designer to picture an implementation of this which does not directly lead to the same behaviors.
@nightpool my idea of a "solution" with my limited knowledge of the interface would be an instance admin wrapping statuses boosted from particular instances with boilerplate CW for that instance, and that would be localized action, not a built-in. No shade, just a messy problem (to my thinking)
@austin_walker @bruno I'm coming around to the idea that all images ought to have a cw tag applied by default. Aside from the situation you mentioned, there's also no chance of anyone accidentally forgetting to include a cw when they meant to do so, and it improves accessibility for visually impaired users a little by effectively requiring all images to have some sort of description.
Welcome to content.town, where content rulez!