> If you post a reblog of an affected post, then edit the reblog and add a content warning at that time, you *will* be able to add the content warning *within the interface*— however, nothing will actually happen. Example: this post https://cohost.org/mcc/post/2140369-a-weird-extra-detail which should have a CW but does not.
I promise that I did do this and I'm nearly certain I did it correctly (IE I tabbed to complete the CW add before posting). On a repeat try, after a couple edits, I WAS able to add a CW and it stuck. I cannot explain this at all.
I've actually seen the same issue, however typing something out and clicking the CW button does not work. What that does is CW only your addition to the post. (See attached image for an example, which has been edited to censor the images)
Even if you type something out, add the CW, and then delete your text, this will just reblog without adding the CW, since it's trying to add it to your addition, and there is no addition to CW. If you then edit your reblog to include text, that text and only that text will be CW'd, same as if you had reblogged with no text and no CW.
The model Alice describes makes a lot of sense to me.
However, I think there is still a UI issue here, because the reason the spoiler tag cannot be added to an empty post is unclear, especially from a new user perspective. Maybe the grayed out spoiler button should have a tooltip saying "Must write something to add a spoiler" or whatevs
Andi McClure
Repro:
- Click "reblog" on this post https://cohost.org/mcc/post/1939371-twitter-s-policies-h
- Click at the bottom of the post to add a CW.
- You will not be able to because the CW icon is grayed out.
- This is bad. A reblog of a post with a content warning also will likely need the same content warning for the same reason.
Additional oddities:
- If you post a reblog of an affected post, then edit the reblog and add a content warning at that time, you *will* be able to add the content warning *within the interface*— however, nothing will actually happen. Example: this post https://cohost.org/mcc/post/2140369-a-weird-extra-detail which should have a CW but does not.
- I wondered at first if this is because the specific magic post above is "old"/from a previous age of posting. So I created a new post, which had a content warning from the moment I posted it, and attempted to reblog it and add a content warning. In my test, I got the same behavior (content warning could not be applied to reblog). I deleted this post.
- While performing this test, I found something unusual. If you post a post which *initially* has *no* content warning, then you post the post, then you edit the post and ADD a content warning (this sounds contrived but is easy to do by accident because of https://help.antisoftware.club/support/discussions/topics/62000185045 ), and THEN you reblog this edited post to add a content warning, you ARE able to add content warnings to reblogs of this specially prepared CW'd post. My successful test here I saved in a draft: https://cohost.org/mcc/post/2140468-testing-something-pl/b37bd38b2ace485eac220a86399adb42
2 people have this problem