@rcombs I think at some point you mentioned you were going to hide cw'd text behind a spoiler? that doesn't seem to be happening
(really appreciate your work on this! it's a massive improvement)
@Radgryd @Gaelan Yeah, this was the team's decision on how to handle sensitive-flagged posts. It brings mastodon posts into alignment with the handling for other sites, and makes a bit more sense for chat-embed usage. On discord, embeds exist in channels (with their own community, context, and moderation), rather than when boosted onto people's general-purpose timelines (where users have ways to configure filters on an individual basis)
Users who want to obscure the content of an embed can wrap the link in ||pipes|| (put a space after the link if you want to have it still embed, but behind a spoiler block), which applies to links from any site
@rcombs @Gaelan That's unfortunate. I've felt the Fediverse was CW-sensitive more than other platforms, which I've enjoyed.
I let my feed be posted on my Discord via an RSS bot, so I have no control over spoilering the link/embed itself.
The embed ignores Mastodon's spoiler feature as well. I don't really know what the solution for this is.
@Radgryd I'm confused; as far as I can tell, this isn't a feature Mastodon has? That post just contains the plaintext string "||Test||", which doesn't have any special meaning in a Mastodon post.
As for solutions to your issue, I'd suggest using a bot that makes smarter decisions about what posts to forward where, or whether to obscure the embeds, based on the content of the post.
@rcombs I input the spoiler tags for Discord to see how it would display in the embed posted on Discord, of course it doesn't do anything on Mastodon..
It *did* use to obscure the embeds, as shown before. Thanks anyway.