-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AP => Bluesky: content warnings #1001
Comments
Thanks for filing! Ah, content warnings, takes me all the way back to #47. And agreed, not good, we can definitely do better. Thanks for the ideas. |
This goes in the direction of bikeshedding a little, but I'd like to see something like
with "CN" (content notice) instead "CW" because in practice people do use that function very broadly and afaik not everything calls it a content warning. I'd prefer the in-body link over a link preview attachment here because the latter can be obtrusively large in the GUI (which runs counter to CN/CW-use to collapse posts intentionally) and would most likely just duplicate some information already present otherwise, like name, handle, avatar and |
Is there an update on this |
Sorry, no, not a high priority right now. Should be straightforward though, PRs are welcome! The new code would go in (Note that we'd want to do this only when both |
Thinking about this again. Out of curiosity, how much would you all dislike it if BF included the content notice/warning and the actual content in the bridged Bluesky post? I get that this isn't the spirit of content notices, and that content notices are an important part of fediverse culture for at least some people there, but they're obviously not part of the Bluesky culture. I wonder if it would be overall better UX for bridged posts to include both, instead of making Bluesky users constantly open external links in order to read a significant minority of bridged posts. |
To and from me that'd be fine, ideally with Be mindful of media attachments though, since AP lacks a real separate adult content system. (I guess Bsky could just label on their end if someone overdoes it tho.) |
I'd be fine with that, back on Twitter people were doing, so I don't think it's a problem "CW: things hi everyone it's things" |
…ing content summary is often [ab]used for content warnings in the fediverse. snarfed/bridgy-fed#1001
Thanks all! I've deployed a first pass at this. Fediverse posts with content warnings/notices should now get bridged to Bluesky as:
Let's see how that goes. |
As an example example: this AP note gets bridged over as this bsky post. losing all the context and making a post that, while potentially funny out of context (depending on the CW used) the first few times, could end up annoying towards people from bsky.
While there really isn't a great way to solve this problem without bsky getting a similar feature, simply prepending "CW: " or something of that sort, potentially with a link back to the original post (??? unsure on this part) should at least avoid most of the confusion this could result in.
The text was updated successfully, but these errors were encountered: