1 year ago
I'm not on Mastodon. I'm on Hubzilla, and I've got no way to hide sensitive pictures (e.g. eye contact, food, alcohol) in posts from Mastodon users. I could link to them, but that'd be inconvenient for you.
Also, I tend to have to write extremely long and detailed image descriptions of sometimes tens of thousands of characters. My image descriptions always go into the post text. But if the image is linked, it won't be where the description is.
How should I handle this?
Here are the options for those who can't read them on their apps with a bit of explanation:
#AskFedi #Poll #ImageDescription #ImageDescriptions #Accessibility #A11y #Inclusion #Inclusivity #SensitiveImages #SensitiveContent #ContentWarning #ContentWarnings #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #EyeContact #CWEyeContact #Food #CWFood #Alcohol #CWAlcohol
Image and full description in the post
Link to the image, full description in the post
Link to an article with the image and the full description
All three suck, don't post those pictures
Also, I tend to have to write extremely long and detailed image descriptions of sometimes tens of thousands of characters. My image descriptions always go into the post text. But if the image is linked, it won't be where the description is.
How should I handle this?
Here are the options for those who can't read them on their apps with a bit of explanation:
- Image and full description in the post
+ convenient
+ fairly interesting post with an image
+ image and description are together
+ guaranteed to work with screen readers
– extremely long post
– risk of triggering someone - Link to the image, full description in the post
+ reduced trigger risk
+ description is in the post
+ guaranteed to work with screen readers
– inconvenient for you
– uninteresting post with no image
– image and description are separate
– extremely long post - Link to an article with the image and the full description
+ even more reduced trigger risk
+ image and description are together
+ much shorter post
– inconvenient for you
– uninteresting post with no image
– might not work with screen readers - All three suck, don't post those pictures
+ most convenient
+ saves me hours of work
+ saves you an eternity of reading an image description
– I can no longer post images that might trigger someone
#AskFedi #Poll #ImageDescription #ImageDescriptions #Accessibility #A11y #Inclusion #Inclusivity #SensitiveImages #SensitiveContent #ContentWarning #ContentWarnings #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #EyeContact #CWEyeContact #Food #CWFood #Alcohol #CWAlcohol
Image and full description in the post
5 Votes | 71%
Link to the image, full description in the post
0 Votes | 0%
Link to an article with the image and the full description
1 Vote | 14%
All three suck, don't post those pictures
1 Vote | 14%
7 Votes in total
Poll has ended
Poll has ended
@jupiter_rowland Right, so we should encourage the Mastodon developers to focus on empowering users to make that kind of decision.
Mastodon should do better.
Mastodon should do better.
@volkris I'm tempted to say that Mastodon doesn't want to become more compatible with anything else. If anything, everything else shall either follow Mastodon's lead or suffer consequences.
But the last time I've filed a compatibility bug on Mastodon's GitHub that was clearly on Mastodon's side, it was fixed in dev the same evening and in the new stable release three days later.
But the last time I've filed a compatibility bug on Mastodon's GitHub that was clearly on Mastodon's side, it was fixed in dev the same evening and in the new stable release three days later.
1 year ago
I think it is just different philosophies on social media and lack of understanding. I have followed a lot of conversations about interoperability, and on the technical level, there is a lot of explaining that has to go on before both sides understand what each other is doing. So there is a information gap that, in some cases, gets in the way.