You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When I share a review or note for a book or movie in my collection, this is nicely rendered as hidden in the NeoDB UI and rendered with Content Warnings on other platforms like Mastodon, the RSS item contains no indication of the spoilers.
Describe the solution you'd like
Would be to include a or similar markup that RSS feed implementers can render with blurry text just like NeoDB does in its website.
Describe alternatives you've considered
The simplest solution would be to include a prefix content warning message to every feed item that contains a spoiler tag, emulating at a very basic level the Content Warning as seen via Mastodon. This way RSS implementers don't have to do anything.
Additional context
Would be nice to provide both solutions though. I'm using RSS as an alternative to ActivityPub to easily embed my NeoDB content on my website, so I have control of the CSS that will be in effect so I'd love to implement blurry text with onClick visibility on my embedded content as well.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When I share a review or note for a book or movie in my collection, this is nicely rendered as hidden in the NeoDB UI and rendered with Content Warnings on other platforms like Mastodon, the RSS item contains no indication of the spoilers.
Describe the solution you'd like
Would be to include a or similar markup that RSS feed implementers can render with blurry text just like NeoDB does in its website.
Describe alternatives you've considered
The simplest solution would be to include a prefix content warning message to every feed item that contains a spoiler tag, emulating at a very basic level the Content Warning as seen via Mastodon. This way RSS implementers don't have to do anything.
Additional context
Would be nice to provide both solutions though. I'm using RSS as an alternative to ActivityPub to easily embed my NeoDB content on my website, so I have control of the CSS that will be in effect so I'd love to implement blurry text with onClick visibility on my embedded content as well.
The text was updated successfully, but these errors were encountered: