Hello, this is Lisa here (lead product designer at Forem).
I think this is a fantastic idea, and we see this commonly on other platforms that may show a content warning before someone continues to watch/view a photo, video, or text.
Given the immediate priorities of Forem, this is not something we're going to focus on anytime soon, but that doesn't mean we can be observant of people's workarounds for this. We can observe how people accomplish this with our features to help us understand how we might develop new features improving this in the future.
For example, what if people marketing "[WARNING]" in their post title? Or tagged their content with #warning? We want to observe these workarounds that people are using in their communities before we invest in productizing this so that we can truly validate the need for this when that time comes.
Another thing I want to note is that abuse comes in many forms, but one of the most visceral ways it shows up is through visual content (photos, videos). Because the Home feed showcases primarily text-based content, this already acts as a filter before people come in. We want to enable communities to eventually enable different feed types (for example, feeds that prioritize showing photos in a grid), and in that time, this is where looking deeper into these content warnings will be more critical. I hope this is helpful context.
Hey, thanks for the comment!
I don't think, that simply adding [WARNING] to the title of a post or as a tag is sufficient. What might be a trigger for one person might not be for another, it tells you nothing about the content you're about to encounter. Another solution might be a disclaimer over the actual blog post content that would warn of potential triggers that the author could display.
And of course, the feed as it currently is is a filter against triggers contained in video and photo formats, but that does nothing for the contents that might be mentioned within the blog post itself in text form, which can be just as harmful for a person.
Having a mechanism that prevents people from seeing such content or even just warning them of it might help a lot with that I think.
You know, what I was calling a "label" below is probably much better described as a "disclaimer" like you're mentioning here.
For instance, if you look at our terms you'll see the phrase:
If a post contains affiliate links, that fact must be clearly disclosed. For instance, with language such as: “This post includes affiliate links; I may receive compensation if you purchase products or services from the different links provided in this article.”
I was thinking of this when mentioning the affiliate label, but this is totally more of a disclaimer than label.
Just wanted to clear that up as we're thinking about something quite similar.
For further actions, you may consider blocking this person and/or reporting abuse
@abenettt
Hello, this is Lisa here (lead product designer at Forem).
I think this is a fantastic idea, and we see this commonly on other platforms that may show a content warning before someone continues to watch/view a photo, video, or text.
Given the immediate priorities of Forem, this is not something we're going to focus on anytime soon, but that doesn't mean we can be observant of people's workarounds for this. We can observe how people accomplish this with our features to help us understand how we might develop new features improving this in the future.
For example, what if people marketing "[WARNING]" in their post title? Or tagged their content with #warning? We want to observe these workarounds that people are using in their communities before we invest in productizing this so that we can truly validate the need for this when that time comes.
Another thing I want to note is that abuse comes in many forms, but one of the most visceral ways it shows up is through visual content (photos, videos). Because the Home feed showcases primarily text-based content, this already acts as a filter before people come in. We want to enable communities to eventually enable different feed types (for example, feeds that prioritize showing photos in a grid), and in that time, this is where looking deeper into these content warnings will be more critical. I hope this is helpful context.
Cheers. 🌱
Hey, thanks for the comment!
I don't think, that simply adding [WARNING] to the title of a post or as a tag is sufficient. What might be a trigger for one person might not be for another, it tells you nothing about the content you're about to encounter. Another solution might be a disclaimer over the actual blog post content that would warn of potential triggers that the author could display.
And of course, the feed as it currently is is a filter against triggers contained in video and photo formats, but that does nothing for the contents that might be mentioned within the blog post itself in text form, which can be just as harmful for a person.
Having a mechanism that prevents people from seeing such content or even just warning them of it might help a lot with that I think.
You know, what I was calling a "label" below is probably much better described as a "disclaimer" like you're mentioning here.
For instance, if you look at our terms you'll see the phrase:
I was thinking of this when mentioning the affiliate label, but this is totally more of a disclaimer than label.
Just wanted to clear that up as we're thinking about something quite similar.