#characterlimits — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #characterlimits, aggregated by home.social.
-
@DopeGhoti @Andrew How many characters would be sufficient for Mastodon to not count as ableist anymore?
If you say, 1,500, who or what says that 1,500 characters are sufficient to describe any and all images, but a lower limit is not?
For comparison, look at my cover photo. The one with the weird building. I have a post with just about the same image in it; here's the link.
In this post, the image has two separate image descriptions. One is in the alt-text. The alt-text is exactly 1,500 characters long, a bit over 1,400 of which are image description. And that's the short description. It doesn't even have room for any text transcripts. It actually isn't much more than an "alibi description". It's only there because many people on Mastodon demand there be a 100% accurate and sufficiently detailed image description in the alt-text of each image in the Fediverse.
Only that "sufficiently detailed" isn't always possible even in 1,500 characters.
That's why there is an additional long description in the post text. It's sufficiently detailed, as in, fully detailed. An image like this requires a fully detailed description. It comes with transcripts of all bits of text within the borders of the image, and it comes with all explanations necessary to understand the image and the description. It's over 60,000 characters long.
Yes, over 60,000 characters in one post. Your character limit is 500. Mine is over 16 million.
Oh, and yes, it's guaranteed to be 100% hand-written. It took me two full days, morning to evening, to research for and write the long description with literally absolutely no help from any AI whatsoever. In fact, I've described details that no AI on the planet will ever be able to see in the image.
So ideally, all Fediverse server platforms should have two image description fields for each profile image, one being the alt-text behind the image, one being a long description next to the image. The latter should not have an arbitrarily-chosen character limit.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism #AbleismMeta #CWAbleismMeta -
@DopeGhoti @Andrew How many characters would be sufficient for Mastodon to not count as ableist anymore?
If you say, 1,500, who or what says that 1,500 characters are sufficient to describe any and all images, but a lower limit is not?
For comparison, look at my cover photo. The one with the weird building. I have a post with just about the same image in it; here's the link.
In this post, the image has two separate image descriptions. One is in the alt-text. The alt-text is exactly 1,500 characters long, a bit over 1,400 of which are image description. And that's the short description. It doesn't even have room for any text transcripts. It actually isn't much more than an "alibi description". It's only there because many people on Mastodon demand there be a 100% accurate and sufficiently detailed image description in the alt-text of each image in the Fediverse.
Only that "sufficiently detailed" isn't always possible even in 1,500 characters.
That's why there is an additional long description in the post text. It's sufficiently detailed, as in, fully detailed. An image like this requires a fully detailed description. It comes with transcripts of all bits of text within the borders of the image, and it comes with all explanations necessary to understand the image and the description. It's over 60,000 characters long.
Yes, over 60,000 characters in one post. Your character limit is 500. Mine is over 16 million.
Oh, and yes, it's guaranteed to be 100% hand-written. It took me two full days, morning to evening, to research for and write the long description with literally absolutely no help from any AI whatsoever. In fact, I've described details that no AI on the planet will ever be able to see in the image.
So ideally, all Fediverse server platforms should have two image description fields for each profile image, one being the alt-text behind the image, one being a long description next to the image. The latter should not have an arbitrarily-chosen character limit.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism #AbleismMeta #CWAbleismMeta -
CW: Good image descriptions require a much bigger effort than you may think; CW: long (over 5,300 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, character limit meta, content warning meta, hashtag meta, alt-text meta, image description meta, AI mentioned (AI-)
Image descriptions are important in the Fediverse, at least if your posts have a chance to reach Mastodon. But is it only about having image descriptions in general? Is it only about having image descriptions at all? Or is it about image description quality as well?
Blind or visually-impaired users say that anything is better than nothing. But seriously, the image file name as the alt-text is useless. So is a copy of the post text as the alt-text; at least one mobile app for Mastodon seems to do that automatically. So is some gibberish written into the alt-text, just so that there's some alt-text.
So you write a short image description for your alt-text. That should be much better than nothing.
But then you're criticised and sanctioned because your image description lacks detail.
Since you can't or don't want to write a longer description, you leave that to an AI.
But then you're criticised and sanctioned because your image description is obvious AI slop. The AI is inaccurate, it hallucinates, it misidentifies things and it still leaves out details.
Okay, so you sit down and put quite some time and effort into a hand-written image description that's both accurate and detailed. At least you think so.
And still, someone may come and criticise and/or sanction you for having left out certain details.
If you don't fix your image description to their satisfaction, you're insulted as ableist and blocked very publicly so that as many other users as possible block you, too.
Now, minimum quality standards for image descriptions are evolving over time. What matters now didn't necessarily matter two years ago. Things that don't matter now may matter in two years or in five years. Even today, alt-text activists criticise image posts that are several years old for image descriptions that they consider less than optimal. This means the image descriptions that you write today must be good enough for as long as your image posts stay available. If they aren't, have fun going through all your old image posts, editing them and upgrading the image descriptions to the latest minimum requirements.
There's only way to be safe from Mastodon's alt-text police in the long run: First of all, you must educate yourself about all the rules and guidelines of alt-texts and image descriptions, and there are dozens of websites about these. You can't know beforehand which ones of these rules will be declared mandatory by someone from the alt-text police in the future, so you'd better follow them to a tee already now. Of course, when two rules contradict each other, you must know which one to follow.
Also, you must know that the requirements and quality standards for good alt-texts and image descriptions on Mastodon are different from the entire rest of the Web. What's good enough for the Web isn't necessarily good enough for Mastodon.
Lastly, you must know your audience. And normally, your audience can be anyone anywhere in the Fediverse or even on the Web. There are only very few places in the Fediverse where you can control who will be able to read your stuff, and Mastodon isn't one of them. You must know your audience, and you must at least be able to estimate what they know about the contents of your image, what they don't know and what they need to know. If your audience doesn't necessarily know what something is, explain it, but please do so in the post text and not in the alt-text! If your audience doesn't necessarily know what something looks like, but it may want to know, describe what it looks like.
As for my own images, my strategy is to write two image descriptions for each image. One is the short image description; it goes into the alt-text. I'm going to limit that to a maximum of 512 characters because Misskey and its forks delete alt-texts that are over 512 characters long. The other one is the long image description; it goes into the post text. The long image description is fully detailed, it contains all explanations necessary to understand the image and its descriptions, and it contains transcripts of every last bit of text anywhere within the borders of the image, readable in the image or not.
Posting memes is a bit easier. There is only one image description that's hopefully short enough to go into the alt-text. But I still need to explain a whole lot of things, and as I can't always rely upon links to websites like KnowYourMeme for explanations, I often have to write a whole lot of explanations into the post.
Ideally, the worst that could happen to me is being criticised for my alt-text exceeding 200 characters or my post exceeding 500 characters or being blocked for the latter. I reduce the chance for that to happen with a summary that includes a long post content warning with the rough length of the post and the hashtags #Long, #LongPost, #CWLong and #CWLongPost that can be filtered. I almost always add hashtags for folks to filter.
But I hope that nobody can say I haven't tried hard enough.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
CW: Good image descriptions require a much bigger effort than you may think; CW: long (over 5,300 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, character limit meta, content warning meta, hashtag meta, alt-text meta, image description meta, AI mentioned (AI-)
Image descriptions are important in the Fediverse, at least if your posts have a chance to reach Mastodon. But is it only about having image descriptions in general? Is it only about having image descriptions at all? Or is it about image description quality as well?
Blind or visually-impaired users say that anything is better than nothing. But seriously, the image file name as the alt-text is useless. So is a copy of the post text as the alt-text; at least one mobile app for Mastodon seems to do that automatically. So is some gibberish written into the alt-text, just so that there's some alt-text.
So you write a short image description for your alt-text. That should be much better than nothing.
But then you're criticised and sanctioned because your image description lacks detail.
Since you can't or don't want to write a longer description, you leave that to an AI.
But then you're criticised and sanctioned because your image description is obvious AI slop. The AI is inaccurate, it hallucinates, it misidentifies things and it still leaves out details.
Okay, so you sit down and put quite some time and effort into a hand-written image description that's both accurate and detailed. At least you think so.
And still, someone may come and criticise and/or sanction you for having left out certain details.
If you don't fix your image description to their satisfaction, you're insulted as ableist and blocked very publicly so that as many other users as possible block you, too.
Now, minimum quality standards for image descriptions are evolving over time. What matters now didn't necessarily matter two years ago. Things that don't matter now may matter in two years or in five years. Even today, alt-text activists criticise image posts that are several years old for image descriptions that they consider less than optimal. This means the image descriptions that you write today must be good enough for as long as your image posts stay available. If they aren't, have fun going through all your old image posts, editing them and upgrading the image descriptions to the latest minimum requirements.
There's only way to be safe from Mastodon's alt-text police in the long run: First of all, you must educate yourself about all the rules and guidelines of alt-texts and image descriptions, and there are dozens of websites about these. You can't know beforehand which ones of these rules will be declared mandatory by someone from the alt-text police in the future, so you'd better follow them to a tee already now. Of course, when two rules contradict each other, you must know which one to follow.
Also, you must know that the requirements and quality standards for good alt-texts and image descriptions on Mastodon are different from the entire rest of the Web. What's good enough for the Web isn't necessarily good enough for Mastodon.
Lastly, you must know your audience. And normally, your audience can be anyone anywhere in the Fediverse or even on the Web. There are only very few places in the Fediverse where you can control who will be able to read your stuff, and Mastodon isn't one of them. You must know your audience, and you must at least be able to estimate what they know about the contents of your image, what they don't know and what they need to know. If your audience doesn't necessarily know what something is, explain it, but please do so in the post text and not in the alt-text! If your audience doesn't necessarily know what something looks like, but it may want to know, describe what it looks like.
As for my own images, my strategy is to write two image descriptions for each image. One is the short image description; it goes into the alt-text. I'm going to limit that to a maximum of 512 characters because Misskey and its forks delete alt-texts that are over 512 characters long. The other one is the long image description; it goes into the post text. The long image description is fully detailed, it contains all explanations necessary to understand the image and its descriptions, and it contains transcripts of every last bit of text anywhere within the borders of the image, readable in the image or not.
Posting memes is a bit easier. There is only one image description that's hopefully short enough to go into the alt-text. But I still need to explain a whole lot of things, and as I can't always rely upon links to websites like KnowYourMeme for explanations, I often have to write a whole lot of explanations into the post.
Ideally, the worst that could happen to me is being criticised for my alt-text exceeding 200 characters or my post exceeding 500 characters or being blocked for the latter. I reduce the chance for that to happen with a summary that includes a long post content warning with the rough length of the post and the hashtags #Long, #LongPost, #CWLong and #CWLongPost that can be filtered. I almost always add hashtags for folks to filter.
But I hope that nobody can say I haven't tried hard enough.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
CW: Good image descriptions require a much bigger effort than you may think; CW: long (over 5,300 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, character limit meta, content warning meta, hashtag meta, alt-text meta, image description meta, AI mentioned (AI-)
Image descriptions are important in the Fediverse, at least if your posts have a chance to reach Mastodon. But is it only about having image descriptions in general? Is it only about having image descriptions at all? Or is it about image description quality as well?
Blind or visually-impaired users say that anything is better than nothing. But seriously, the image file name as the alt-text is useless. So is a copy of the post text as the alt-text; at least one mobile app for Mastodon seems to do that automatically. So is some gibberish written into the alt-text, just so that there's some alt-text.
So you write a short image description for your alt-text. That should be much better than nothing.
But then you're criticised and sanctioned because your image description lacks detail.
Since you can't or don't want to write a longer description, you leave that to an AI.
But then you're criticised and sanctioned because your image description is obvious AI slop. The AI is inaccurate, it hallucinates, it misidentifies things and it still leaves out details.
Okay, so you sit down and put quite some time and effort into a hand-written image description that's both accurate and detailed. At least you think so.
And still, someone may come and criticise and/or sanction you for having left out certain details.
If you don't fix your image description to their satisfaction, you're insulted as ableist and blocked very publicly so that as many other users as possible block you, too.
Now, minimum quality standards for image descriptions are evolving over time. What matters now didn't necessarily matter two years ago. Things that don't matter now may matter in two years or in five years. Even today, alt-text activists criticise image posts that are several years old for image descriptions that they consider less than optimal. This means the image descriptions that you write today must be good enough for as long as your image posts stay available. If they aren't, have fun going through all your old image posts, editing them and upgrading the image descriptions to the latest minimum requirements.
There's only way to be safe from Mastodon's alt-text police in the long run: First of all, you must educate yourself about all the rules and guidelines of alt-texts and image descriptions, and there are dozens of websites about these. You can't know beforehand which ones of these rules will be declared mandatory by someone from the alt-text police in the future, so you'd better follow them to a tee already now. Of course, when two rules contradict each other, you must know which one to follow.
Also, you must know that the requirements and quality standards for good alt-texts and image descriptions on Mastodon are different from the entire rest of the Web. What's good enough for the Web isn't necessarily good enough for Mastodon.
Lastly, you must know your audience. And normally, your audience can be anyone anywhere in the Fediverse or even on the Web. There are only very few places in the Fediverse where you can control who will be able to read your stuff, and Mastodon isn't one of them. You must know your audience, and you must at least be able to estimate what they know about the contents of your image, what they don't know and what they need to know. If your audience doesn't necessarily know what something is, explain it, but please do so in the post text and not in the alt-text! If your audience doesn't necessarily know what something looks like, but it may want to know, describe what it looks like.
As for my own images, my strategy is to write two image descriptions for each image. One is the short image description; it goes into the alt-text. I'm going to limit that to a maximum of 512 characters because Misskey and its forks delete alt-texts that are over 512 characters long. The other one is the long image description; it goes into the post text. The long image description is fully detailed, it contains all explanations necessary to understand the image and its descriptions, and it contains transcripts of every last bit of text anywhere within the borders of the image, readable in the image or not.
Posting memes is a bit easier. There is only one image description that's hopefully short enough to go into the alt-text. But I still need to explain a whole lot of things, and as I can't always rely upon links to websites like KnowYourMeme for explanations, I often have to write a whole lot of explanations into the post.
Ideally, the worst that could happen to me is being criticised for my alt-text exceeding 200 characters or my post exceeding 500 characters or being blocked for the latter. I reduce the chance for that to happen with a summary that includes a long post content warning with the rough length of the post and the hashtags #Long, #LongPost, #CWLong and #CWLongPost that can be filtered. I almost always add hashtags for folks to filter.
But I hope that nobody can say I haven't tried hard enough.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
CW: Good image descriptions require a much bigger effort than you may think; CW: long (over 5,300 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, character limit meta, content warning meta, hashtag meta, alt-text meta, image description meta, AI mentioned (AI-)
Image descriptions are important in the Fediverse, at least if your posts have a chance to reach Mastodon. But is it only about having image descriptions in general? Is it only about having image descriptions at all? Or is it about image description quality as well?
Blind or visually-impaired users say that anything is better than nothing. But seriously, the image file name as the alt-text is useless. So is a copy of the post text as the alt-text; at least one mobile app for Mastodon seems to do that automatically. So is some gibberish written into the alt-text, just so that there's some alt-text.
So you write a short image description for your alt-text. That should be much better than nothing.
But then you're criticised and sanctioned because your image description lacks detail.
Since you can't or don't want to write a longer description, you leave that to an AI.
But then you're criticised and sanctioned because your image description is obvious AI slop. The AI is inaccurate, it hallucinates, it misidentifies things and it still leaves out details.
Okay, so you sit down and put quite some time and effort into a hand-written image description that's both accurate and detailed. At least you think so.
And still, someone may come and criticise and/or sanction you for having left out certain details.
If you don't fix your image description to their satisfaction, you're insulted as ableist and blocked very publicly so that as many other users as possible block you, too.
Now, minimum quality standards for image descriptions are evolving over time. What matters now didn't necessarily matter two years ago. Things that don't matter now may matter in two years or in five years. Even today, alt-text activists criticise image posts that are several years old for image descriptions that they consider less than optimal. This means the image descriptions that you write today must be good enough for as long as your image posts stay available. If they aren't, have fun going through all your old image posts, editing them and upgrading the image descriptions to the latest minimum requirements.
There's only way to be safe from Mastodon's alt-text police in the long run: First of all, you must educate yourself about all the rules and guidelines of alt-texts and image descriptions, and there are dozens of websites about these. You can't know beforehand which ones of these rules will be declared mandatory by someone from the alt-text police in the future, so you'd better follow them to a tee already now. Of course, when two rules contradict each other, you must know which one to follow.
Also, you must know that the requirements and quality standards for good alt-texts and image descriptions on Mastodon are different from the entire rest of the Web. What's good enough for the Web isn't necessarily good enough for Mastodon.
Lastly, you must know your audience. And normally, your audience can be anyone anywhere in the Fediverse or even on the Web. There are only very few places in the Fediverse where you can control who will be able to read your stuff, and Mastodon isn't one of them. You must know your audience, and you must at least be able to estimate what they know about the contents of your image, what they don't know and what they need to know. If your audience doesn't necessarily know what something is, explain it, but please do so in the post text and not in the alt-text! If your audience doesn't necessarily know what something looks like, but it may want to know, describe what it looks like.
As for my own images, my strategy is to write two image descriptions for each image. One is the short image description; it goes into the alt-text. I'm going to limit that to a maximum of 512 characters because Misskey and its forks delete alt-texts that are over 512 characters long. The other one is the long image description; it goes into the post text. The long image description is fully detailed, it contains all explanations necessary to understand the image and its descriptions, and it contains transcripts of every last bit of text anywhere within the borders of the image, readable in the image or not.
Posting memes is a bit easier. There is only one image description that's hopefully short enough to go into the alt-text. But I still need to explain a whole lot of things, and as I can't always rely upon links to websites like KnowYourMeme for explanations, I often have to write a whole lot of explanations into the post.
Ideally, the worst that could happen to me is being criticised for my alt-text exceeding 200 characters or my post exceeding 500 characters or being blocked for the latter. I reduce the chance for that to happen with a summary that includes a long post content warning with the rough length of the post and the hashtags #Long, #LongPost, #CWLong and #CWLongPost that can be filtered. I almost always add hashtags for folks to filter.
But I hope that nobody can say I haven't tried hard enough.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
CW: Good image descriptions require a much bigger effort than you may think; CW: long (over 5,300 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, character limit meta, content warning meta, hashtag meta, alt-text meta, image description meta, AI mentioned (AI-)
Image descriptions are important in the Fediverse, at least if your posts have a chance to reach Mastodon. But is it only about having image descriptions in general? Is it only about having image descriptions at all? Or is it about image description quality as well?
Blind or visually-impaired users say that anything is better than nothing. But seriously, the image file name as the alt-text is useless. So is a copy of the post text as the alt-text; at least one mobile app for Mastodon seems to do that automatically. So is some gibberish written into the alt-text, just so that there's some alt-text.
So you write a short image description for your alt-text. That should be much better than nothing.
But then you're criticised and sanctioned because your image description lacks detail.
Since you can't or don't want to write a longer description, you leave that to an AI.
But then you're criticised and sanctioned because your image description is obvious AI slop. The AI is inaccurate, it hallucinates, it misidentifies things and it still leaves out details.
Okay, so you sit down and put quite some time and effort into a hand-written image description that's both accurate and detailed. At least you think so.
And still, someone may come and criticise and/or sanction you for having left out certain details.
If you don't fix your image description to their satisfaction, you're insulted as ableist and blocked very publicly so that as many other users as possible block you, too.
Now, minimum quality standards for image descriptions are evolving over time. What matters now didn't necessarily matter two years ago. Things that don't matter now may matter in two years or in five years. Even today, alt-text activists criticise image posts that are several years old for image descriptions that they consider less than optimal. This means the image descriptions that you write today must be good enough for as long as your image posts stay available. If they aren't, have fun going through all your old image posts, editing them and upgrading the image descriptions to the latest minimum requirements.
There's only way to be safe from Mastodon's alt-text police in the long run: First of all, you must educate yourself about all the rules and guidelines of alt-texts and image descriptions, and there are dozens of websites about these. You can't know beforehand which ones of these rules will be declared mandatory by someone from the alt-text police in the future, so you'd better follow them to a tee already now. Of course, when two rules contradict each other, you must know which one to follow.
Also, you must know that the requirements and quality standards for good alt-texts and image descriptions on Mastodon are different from the entire rest of the Web. What's good enough for the Web isn't necessarily good enough for Mastodon.
Lastly, you must know your audience. And normally, your audience can be anyone anywhere in the Fediverse or even on the Web. There are only very few places in the Fediverse where you can control who will be able to read your stuff, and Mastodon isn't one of them. You must know your audience, and you must at least be able to estimate what they know about the contents of your image, what they don't know and what they need to know. If your audience doesn't necessarily know what something is, explain it, but please do so in the post text and not in the alt-text! If your audience doesn't necessarily know what something looks like, but it may want to know, describe what it looks like.
As for my own images, my strategy is to write two image descriptions for each image. One is the short image description; it goes into the alt-text. I'm going to limit that to a maximum of 512 characters because Misskey and its forks delete alt-texts that are over 512 characters long. The other one is the long image description; it goes into the post text. The long image description is fully detailed, it contains all explanations necessary to understand the image and its descriptions, and it contains transcripts of every last bit of text anywhere within the borders of the image, readable in the image or not.
Posting memes is a bit easier. There is only one image description that's hopefully short enough to go into the alt-text. But I still need to explain a whole lot of things, and as I can't always rely upon links to websites like KnowYourMeme for explanations, I often have to write a whole lot of explanations into the post.
Ideally, the worst that could happen to me is being criticised for my alt-text exceeding 200 characters or my post exceeding 500 characters or being blocked for the latter. I reduce the chance for that to happen with a summary that includes a long post content warning with the rough length of the post and the hashtags #Long, #LongPost, #CWLong and #CWLongPost that can be filtered. I almost always add hashtags for folks to filter.
But I hope that nobody can say I haven't tried hard enough.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Truth Collector Do you mean people who know how to write long posts? Who have it in themselves to write long posts?
Or people who have the technical means in the Fediverse to write long posts?
Either way, I guess a major issue is that 99% of all Fediverse newbies came from Twitter to Mastodon, believing that the Fediverse is only Mastodon, that Mastodon is an enclosed network and only connected to itself. Most of them still think that. Many of the rest want that back. Long posts, i.e. anything with more than 500 characters, are very unwelcome on Mastodon.
Part of the issue is that most Mastodon users are on phones, usually only ever on phones. Pretty much all of them use apps. And especially the newbies use the official Mastodon app. Unlike just about all other apps as well as Mastodon's own Web interface, the official Mastodon app can't fold long posts in. It's built under the assumption that there will never be any messages in the Fediverse that exceed 500 characters. But if a long post appears in this app, it appears as a long wall of text in your timeline that you have to scroll past.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Truth Collector Do you mean people who know how to write long posts? Who have it in themselves to write long posts?
Or people who have the technical means in the Fediverse to write long posts?
Either way, I guess a major issue is that 99% of all Fediverse newbies came from Twitter to Mastodon, believing that the Fediverse is only Mastodon, that Mastodon is an enclosed network and only connected to itself. Most of them still think that. Many of the rest want that back. Long posts, i.e. anything with more than 500 characters, are very unwelcome on Mastodon.
Part of the issue is that most Mastodon users are on phones, usually only ever on phones. Pretty much all of them use apps. And especially the newbies use the official Mastodon app. Unlike just about all other apps as well as Mastodon's own Web interface, the official Mastodon app can't fold long posts in. It's built under the assumption that there will never be any messages in the Fediverse that exceed 500 characters. But if a long post appears in this app, it appears as a long wall of text in your timeline that you have to scroll past.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Truth Collector Do you mean people who know how to write long posts? Who have it in themselves to write long posts?
Or people who have the technical means in the Fediverse to write long posts?
Either way, I guess a major issue is that 99% of all Fediverse newbies came from Twitter to Mastodon, believing that the Fediverse is only Mastodon, that Mastodon is an enclosed network and only connected to itself. Most of them still think that. Many of the rest want that back. Long posts, i.e. anything with more than 500 characters, are very unwelcome on Mastodon.
Part of the issue is that most Mastodon users are on phones, usually only ever on phones. Pretty much all of them use apps. And especially the newbies use the official Mastodon app. Unlike just about all other apps as well as Mastodon's own Web interface, the official Mastodon app can't fold long posts in. It's built under the assumption that there will never be any messages in the Fediverse that exceed 500 characters. But if a long post appears in this app, it appears as a long wall of text in your timeline that you have to scroll past.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Truth Collector Do you mean people who know how to write long posts? Who have it in themselves to write long posts?
Or people who have the technical means in the Fediverse to write long posts?
Either way, I guess a major issue is that 99% of all Fediverse newbies came from Twitter to Mastodon, believing that the Fediverse is only Mastodon, that Mastodon is an enclosed network and only connected to itself. Most of them still think that. Many of the rest want that back. Long posts, i.e. anything with more than 500 characters, are very unwelcome on Mastodon.
Part of the issue is that most Mastodon users are on phones, usually only ever on phones. Pretty much all of them use apps. And especially the newbies use the official Mastodon app. Unlike just about all other apps as well as Mastodon's own Web interface, the official Mastodon app can't fold long posts in. It's built under the assumption that there will never be any messages in the Fediverse that exceed 500 characters. But if a long post appears in this app, it appears as a long wall of text in your timeline that you have to scroll past.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Truth Collector Do you mean people who know how to write long posts? Who have it in themselves to write long posts?
Or people who have the technical means in the Fediverse to write long posts?
Either way, I guess a major issue is that 99% of all Fediverse newbies came from Twitter to Mastodon, believing that the Fediverse is only Mastodon, that Mastodon is an enclosed network and only connected to itself. Most of them still think that. Many of the rest want that back. Long posts, i.e. anything with more than 500 characters, are very unwelcome on Mastodon.
Part of the issue is that most Mastodon users are on phones, usually only ever on phones. Pretty much all of them use apps. And especially the newbies use the official Mastodon app. Unlike just about all other apps as well as Mastodon's own Web interface, the official Mastodon app can't fold long posts in. It's built under the assumption that there will never be any messages in the Fediverse that exceed 500 characters. But if a long post appears in this app, it appears as a long wall of text in your timeline that you have to scroll past.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Sean C. @Stefan Bohacek @Blorbo Admin Chicken @Justin Ferrell I've once encountered someone who seemed to suffer from such extreme PTSD that they demanded everyone CW literally absolutely everything. And, of course, the Mastodon way by forciing all these CWs upon absolutely everyone all the same.
Now, I'm not even on Mastodon myself. I'm on Hubzilla which is doing CWs way differently from Mastodon, which has been doing that for longer than Mastodon has even existed, much less has had CWs.
We don't do CWs poster-side. We don't write CWs into the summary field. In fact, the summary field, which Mastodon has been using as a CW field since 2017, is still a summary field here. A summary field makes a whole lot of sense here, for while most Mastodon servers have a hard-coded character limit of 500, Hubzilla doesn't really have any character limit at all.
Also, we can't do Mastodon-style CWs in replies which are called "comments" here. Like on Facebook, like on Tumblr, like on every last blog out there, but very much unlike on Mastodon, our post editor and our comment editors are wholly separate things. The comment editor can't do summaries. Why not? Because, have you ever seen a blog comment with a summary?
No, we have our CWs automatically generated and reader-side. We have a kind of filter called "NSFW" that can automatically hide content behind a CW. It's basically Mastodon's "Hide with a warning", but as its own keyword filter list and seven years before Mastodon introduced "Hide with a warning". (Twelve years actually because Hubzilla inherited that feature from Friendica.)
When we post sensitive or disturbing content, we make sure that those who may not want to see that content have their filters triggered. We do so by making sure that appropriate keywords are in the post text (easy-peasy when you can post over 33,000 times more characters than on Mastodon) or by adding hashtags. The latter is what I do, hence the many hashtags down there.
It's also the only way to have a comment hidden. Again, Hubzilla doesn't have a summary field (= Mastodon CW field) for replies, so it has to rely on people making filters for uncomfortable content.
This could be a thing on Mastodon as well. After all, in October, 2022, Mastodon 4.0 introduced "Hide with a warning" to its filters which does the exact same thing as NSFW on Friendica and Hubzilla: hide messages depending on keywords. However, Mastodon's entire culture was defined in mid-2022 by those who had fled from Twitter in early 2022, so it's based on Mastodon 3.x without "Hide with a warning".
Besides, the vast majority of Mastodon users don't even know that Mastodon has "Hide with a warning", much less what it does. Precious few even seem to know that Mastodon has filters in the first place. And next to nobody knows what the non-Mastodon Fediverse has, nor do they care, also because most Mastodon users don't even know that the Fediverse goes beyond Mastodon, Pixelfed and PeerTube.
In addition, while Hubzilla is all about empowering its users to self-moderate their stream, the "Mastodon experience" is generally perceived as being coddled and pampered all over. By mods who remove unwanted content and by all the other users who hide uncomfortable content. Hide it from everyone all the same, regardless of whether or not someone needs that, just because one person needs it.
So back to the beginning: This person took Mastodon's culture to the absolute extreme. And they demanded that I a) adopted Mastodon's way even though it'd b) clash with Hubzilla's culture which is my native culture and c) exaggerate it to the maximum.
Of course, my suggestion to use "Hide with a warning" filters didn't come to fruition. For one, that would have required an infinite number of individual filters on Mastodon. Besides, that person felt entitled to have protection from literally absolutely any and all kinds of content served to them on a silver platter.
I think I ended up Superblocking them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #MastodonCulture -
@Sean C. @Stefan Bohacek @Blorbo Admin Chicken @Justin Ferrell I've once encountered someone who seemed to suffer from such extreme PTSD that they demanded everyone CW literally absolutely everything. And, of course, the Mastodon way by forciing all these CWs upon absolutely everyone all the same.
Now, I'm not even on Mastodon myself. I'm on Hubzilla which is doing CWs way differently from Mastodon, which has been doing that for longer than Mastodon has even existed, much less has had CWs.
We don't do CWs poster-side. We don't write CWs into the summary field. In fact, the summary field, which Mastodon has been using as a CW field since 2017, is still a summary field here. A summary field makes a whole lot of sense here, for while most Mastodon servers have a hard-coded character limit of 500, Hubzilla doesn't really have any character limit at all.
Also, we can't do Mastodon-style CWs in replies which are called "comments" here. Like on Facebook, like on Tumblr, like on every last blog out there, but very much unlike on Mastodon, our post editor and our comment editors are wholly separate things. The comment editor can't do summaries. Why not? Because, have you ever seen a blog comment with a summary?
No, we have our CWs automatically generated and reader-side. We have a kind of filter called "NSFW" that can automatically hide content behind a CW. It's basically Mastodon's "Hide with a warning", but as its own keyword filter list and seven years before Mastodon introduced "Hide with a warning". (Twelve years actually because Hubzilla inherited that feature from Friendica.)
When we post sensitive or disturbing content, we make sure that those who may not want to see that content have their filters triggered. We do so by making sure that appropriate keywords are in the post text (easy-peasy when you can post over 33,000 times more characters than on Mastodon) or by adding hashtags. The latter is what I do, hence the many hashtags down there.
It's also the only way to have a comment hidden. Again, Hubzilla doesn't have a summary field (= Mastodon CW field) for replies, so it has to rely on people making filters for uncomfortable content.
This could be a thing on Mastodon as well. After all, in October, 2022, Mastodon 4.0 introduced "Hide with a warning" to its filters which does the exact same thing as NSFW on Friendica and Hubzilla: hide messages depending on keywords. However, Mastodon's entire culture was defined in mid-2022 by those who had fled from Twitter in early 2022, so it's based on Mastodon 3.x without "Hide with a warning".
Besides, the vast majority of Mastodon users don't even know that Mastodon has "Hide with a warning", much less what it does. Precious few even seem to know that Mastodon has filters in the first place. And next to nobody knows what the non-Mastodon Fediverse has, nor do they care, also because most Mastodon users don't even know that the Fediverse goes beyond Mastodon, Pixelfed and PeerTube.
In addition, while Hubzilla is all about empowering its users to self-moderate their stream, the "Mastodon experience" is generally perceived as being coddled and pampered all over. By mods who remove unwanted content and by all the other users who hide uncomfortable content. Hide it from everyone all the same, regardless of whether or not someone needs that, just because one person needs it.
So back to the beginning: This person took Mastodon's culture to the absolute extreme. And they demanded that I a) adopted Mastodon's way even though it'd b) clash with Hubzilla's culture which is my native culture and c) exaggerate it to the maximum.
Of course, my suggestion to use "Hide with a warning" filters didn't come to fruition. For one, that would have required an infinite number of individual filters on Mastodon. Besides, that person felt entitled to have protection from literally absolutely any and all kinds of content served to them on a silver platter.
I think I ended up Superblocking them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #MastodonCulture -
@Sean C. @Stefan Bohacek @Blorbo Admin Chicken @Justin Ferrell I've once encountered someone who seemed to suffer from such extreme PTSD that they demanded everyone CW literally absolutely everything. And, of course, the Mastodon way by forciing all these CWs upon absolutely everyone all the same.
Now, I'm not even on Mastodon myself. I'm on Hubzilla which is doing CWs way differently from Mastodon, which has been doing that for longer than Mastodon has even existed, much less has had CWs.
We don't do CWs poster-side. We don't write CWs into the summary field. In fact, the summary field, which Mastodon has been using as a CW field since 2017, is still a summary field here. A summary field makes a whole lot of sense here, for while most Mastodon servers have a hard-coded character limit of 500, Hubzilla doesn't really have any character limit at all.
Also, we can't do Mastodon-style CWs in replies which are called "comments" here. Like on Facebook, like on Tumblr, like on every last blog out there, but very much unlike on Mastodon, our post editor and our comment editors are wholly separate things. The comment editor can't do summaries. Why not? Because, have you ever seen a blog comment with a summary?
No, we have our CWs automatically generated and reader-side. We have a kind of filter called "NSFW" that can automatically hide content behind a CW. It's basically Mastodon's "Hide with a warning", but as its own keyword filter list and seven years before Mastodon introduced "Hide with a warning". (Twelve years actually because Hubzilla inherited that feature from Friendica.)
When we post sensitive or disturbing content, we make sure that those who may not want to see that content have their filters triggered. We do so by making sure that appropriate keywords are in the post text (easy-peasy when you can post over 33,000 times more characters than on Mastodon) or by adding hashtags. The latter is what I do, hence the many hashtags down there.
It's also the only way to have a comment hidden. Again, Hubzilla doesn't have a summary field (= Mastodon CW field) for replies, so it has to rely on people making filters for uncomfortable content.
This could be a thing on Mastodon as well. After all, in October, 2022, Mastodon 4.0 introduced "Hide with a warning" to its filters which does the exact same thing as NSFW on Friendica and Hubzilla: hide messages depending on keywords. However, Mastodon's entire culture was defined in mid-2022 by those who had fled from Twitter in early 2022, so it's based on Mastodon 3.x without "Hide with a warning".
Besides, the vast majority of Mastodon users don't even know that Mastodon has "Hide with a warning", much less what it does. Precious few even seem to know that Mastodon has filters in the first place. And next to nobody knows what the non-Mastodon Fediverse has, nor do they care, also because most Mastodon users don't even know that the Fediverse goes beyond Mastodon, Pixelfed and PeerTube.
In addition, while Hubzilla is all about empowering its users to self-moderate their stream, the "Mastodon experience" is generally perceived as being coddled and pampered all over. By mods who remove unwanted content and by all the other users who hide uncomfortable content. Hide it from everyone all the same, regardless of whether or not someone needs that, just because one person needs it.
So back to the beginning: This person took Mastodon's culture to the absolute extreme. And they demanded that I a) adopted Mastodon's way even though it'd b) clash with Hubzilla's culture which is my native culture and c) exaggerate it to the maximum.
Of course, my suggestion to use "Hide with a warning" filters didn't come to fruition. For one, that would have required an infinite number of individual filters on Mastodon. Besides, that person felt entitled to have protection from literally absolutely any and all kinds of content served to them on a silver platter.
I think I ended up Superblocking them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #MastodonCulture -
@Stefan Bohacek @Blorbo Admin Chicken Yes, I wish more servers had this rule and enforced it.
Officially appointed moderators only go by the server's written rules, and they only enforce them against local users.
The HOA, on the other hand, have some rules in their heads. Everyone has different rules. And they enforce them against everyone, even regardless of where everyone actually is. Like, they attack Friendica users for allegedly misusing the CW field because they neither know that these users are not on Mastodon, much less where they actually are, nor that Mastodon's CW field has been an abstract field on Friendica for seven years longer than it has been a CW field on Mastodon.
This is part of what makes the Fediverse a minefield once your messages start reaching Mastodon.
I can't say that I'll stop being so overly careful with everything and putting such a big effort particulary into image descriptions, summaries/content warnings and hashtags for filter-triggering purposes if more or even most Mastodon servers adopt and enforce this rule. The irony is that this rule actually protects my long hashtag lines.
In fact, rules like these also ought to include that nobody must be policed for writing "too long" posts because there are places in the Fediverse that neither have character limits to worry about nor a character-limiting culture.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta -
@Stefan Bohacek @Blorbo Admin Chicken Yes, I wish more servers had this rule and enforced it.
Officially appointed moderators only go by the server's written rules, and they only enforce them against local users.
The HOA, on the other hand, have some rules in their heads. Everyone has different rules. And they enforce them against everyone, even regardless of where everyone actually is. Like, they attack Friendica users for allegedly misusing the CW field because they neither know that these users are not on Mastodon, much less where they actually are, nor that Mastodon's CW field has been an abstract field on Friendica for seven years longer than it has been a CW field on Mastodon.
This is part of what makes the Fediverse a minefield once your messages start reaching Mastodon.
I can't say that I'll stop being so overly careful with everything and putting such a big effort particulary into image descriptions, summaries/content warnings and hashtags for filter-triggering purposes if more or even most Mastodon servers adopt and enforce this rule. The irony is that this rule actually protects my long hashtag lines.
In fact, rules like these also ought to include that nobody must be policed for writing "too long" posts because there are places in the Fediverse that neither have character limits to worry about nor a character-limiting culture.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta -
@Stefan Bohacek @Blorbo Admin Chicken Yes, I wish more servers had this rule and enforced it.
Officially appointed moderators only go by the server's written rules, and they only enforce them against local users.
The HOA, on the other hand, have some rules in their heads. Everyone has different rules. And they enforce them against everyone, even regardless of where everyone actually is. Like, they attack Friendica users for allegedly misusing the CW field because they neither know that these users are not on Mastodon, much less where they actually are, nor that Mastodon's CW field has been an abstract field on Friendica for seven years longer than it has been a CW field on Mastodon.
This is part of what makes the Fediverse a minefield once your messages start reaching Mastodon.
I can't say that I'll stop being so overly careful with everything and putting such a big effort particulary into image descriptions, summaries/content warnings and hashtags for filter-triggering purposes if more or even most Mastodon servers adopt and enforce this rule. The irony is that this rule actually protects my long hashtag lines.
In fact, rules like these also ought to include that nobody must be policed for writing "too long" posts because there are places in the Fediverse that neither have character limits to worry about nor a character-limiting culture.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta -
@Stefan Bohacek @Blorbo Admin Chicken Yes, I wish more servers had this rule and enforced it.
Officially appointed moderators only go by the server's written rules, and they only enforce them against local users.
The HOA, on the other hand, have some rules in their heads. Everyone has different rules. And they enforce them against everyone, even regardless of where everyone actually is. Like, they attack Friendica users for allegedly misusing the CW field because they neither know that these users are not on Mastodon, much less where they actually are, nor that Mastodon's CW field has been an abstract field on Friendica for seven years longer than it has been a CW field on Mastodon.
This is part of what makes the Fediverse a minefield once your messages start reaching Mastodon.
I can't say that I'll stop being so overly careful with everything and putting such a big effort particulary into image descriptions, summaries/content warnings and hashtags for filter-triggering purposes if more or even most Mastodon servers adopt and enforce this rule. The irony is that this rule actually protects my long hashtag lines.
In fact, rules like these also ought to include that nobody must be policed for writing "too long" posts because there are places in the Fediverse that neither have character limits to worry about nor a character-limiting culture.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta -
@Stefan Bohacek @Blorbo Admin Chicken Yes, I wish more servers had this rule and enforced it.
Officially appointed moderators only go by the server's written rules, and they only enforce them against local users.
The HOA, on the other hand, have some rules in their heads. Everyone has different rules. And they enforce them against everyone, even regardless of where everyone actually is. Like, they attack Friendica users for allegedly misusing the CW field because they neither know that these users are not on Mastodon, much less where they actually are, nor that Mastodon's CW field has been an abstract field on Friendica for seven years longer than it has been a CW field on Mastodon.
This is part of what makes the Fediverse a minefield once your messages start reaching Mastodon.
I can't say that I'll stop being so overly careful with everything and putting such a big effort particulary into image descriptions, summaries/content warnings and hashtags for filter-triggering purposes if more or even most Mastodon servers adopt and enforce this rule. The irony is that this rule actually protects my long hashtag lines.
In fact, rules like these also ought to include that nobody must be policed for writing "too long" posts because there are places in the Fediverse that neither have character limits to worry about nor a character-limiting culture.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta -
@Cassian [main] This matches my observation here in the Fediverse.
Blind or visually-impaired users, those who actually need image descriptions, are happy to have alt-texts or image descriptions at all. Their requirements don't go much beyond that. And they don't personally attack or sanction anyone.
And then there's the alt-text police of Mastodon's HOA. They're sighted, all of them. It's them who attack, ostracise, sanction, block and sometimes even report other users. For missing alt-text, for completely useless alt-text, for inaccurate alt-text, even for alt-text that isn't detailed enough. For whichever definition of "detailed enough" because the alt-text police don't coordinate their standards. They literally don't talk to each other, so they all assume they all think alike.
In addition, the alt-text police know nothing about the actual rules and guidelines for good alt-texts and image descriptions. Everything they know, they know from Mastodon's culture and from what's going on on Mastodon. And thanks to Mastodon's culture, the Fediverse is a place where you can post an image with a detailed 1,000+-character alt-text and not only get away with it, but be cheered for it.
Never mind that users on Misskey and the Forkeys won't see alt-texts with over 512 characters due to a nasty bug. But tell that to users who don't even know that Misskey exists.
In order to save yourself and your reach in the Fediverse from the wrath of the alt-text police, you basically have to be constantly ahead of their minimum requirements which at least some of them appear to raise every now and then. This means you have to exceed their current minimum requirements to keep yourself from being sanctioned in four years for image descriptions that you've written today. You have to play by the book, and with that, I mean every book, because you never know who in the alt-text police goes by which alt-text guides.
That is, my current impression is that if an image shows something that's obscure enough, Fediverse users are obliged to deliver explanations as well. I understand that as enough explanations so that nobody will ever have to look anything up to understand the image or its description or any of the explanations.
I myself only rarely post images anymore, especially no original images. All my original images are renderings from very obscure 3-D virtual worlds. Images like these require a humongous amount of work to describe them in a way that keeps you safe from even the most zealous of the alt-text police.
I've once taken two full days, morning to evening, to describe one image. The outcome was an alt-text of exactly 1,500 characters plus an additional long description of over 60,000 characters in the post text that also contained all necessary explanations as well as transcripts of every last bit of text within the border of the image, readable or not.
Blind users with screen readers might proverbially be at my throat for their screen reader spending three hours rambling down the description of one measly image. But they probably won't attack or insult or block me for that. They may actually be thankful to have some description.
It's the sighted members of the alt-text police who attack or insult or block other users for less than optimal image descriptions. At the same time, I've yet to see one of them attack or insult or block someone for taking image descriptions to extremes. I guess they'd rather attack or insult or block me for exceeding Mastodon's holy 500-character limit because that long description with over 20 text transcripts and with the various explanations had to go somewhere.
Sad but true: If you want to survive in the Fediverse, you have to pander those who can be dangerous to you and your reach. And not so much to those who really need it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #MastodonHOA -
@Brett Coulstock You should care if you think that Gargron has invented the Fediverse as a pure Mastodon network. If you think that e.g. Friendica and Hubzilla came into the Mastodon Fediverse after the fact. If you use this thinking as a justification to force Mastodon's rules and Mastodon's culture upon Friendica and Hubzilla users because you take them for intruders in a place where they don't rightfully belong.
Because Friendica and Hubzilla did not intrude into Mastodon's Fediverse. They were in the Fediverse before Mastodon.
You should care if you think that posting more than 500 characters is bad behaviour as it goes against "the Fediverse culture".
Because that "Fediverse culture" is only Mastodon's culture. And the culture on Friendica and Hubzilla, which pre-dates Mastodon itself by years, knows no character limits.
You should care if you think that Gargron is evil for introducing quote-posts to the Fediverse.
Because it was actually Mike Macgirvin, creator of Friendica and Hubzilla, who did that. In 2010. 16 years before now. Almost 6 years before Mastodon was even made.
And because just about everything that isn't Mastodon could quote-post Mastodon toots before Mastodon users even considered quote-posts evil.
You should care if you wish for "the Fediverse" to introduce certain new features. Like reply control. Or better list handlings. Or groups. Or even only more characters.
Because "the Fediverse" does have all these features. Just Mastodon doesn't have them. But Mastodon is not the Fediverse.
You should care if you don't want "the Fediverse" to ever introduce certain features. Like a higher default character limit. Or text formatting.
Because the Fediverse already has such features. As in, it can use these features in posts which it then sends to Mastodon. And there's nothing, absolutely nothing that Mastodon and its users can do against it. Except for muting and blocking.
You should care if you find it easier to use "Mastodon" and "Fediverse" synonymously, and all this "nitpicking" about when it's "Mastodon" and when it's "Fediverse" enrages you.
Because it enrages users in the non-Mastodon Fediverse when people say right into their faces that they toot. And/or that they're on Mastodon and therefore bound to the exact same rules and the exact same culture as everyone else on Mastodon. And they will so very much not let you have your way.
All these are things which, unfortunately, those who have never experienced anything else in the Fediverse than Mastodon will hardly ever understand.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Brett Coulstock You should care if you think that Gargron has invented the Fediverse as a pure Mastodon network. If you think that e.g. Friendica and Hubzilla came into the Mastodon Fediverse after the fact. If you use this thinking as a justification to force Mastodon's rules and Mastodon's culture upon Friendica and Hubzilla users because you take them for intruders in a place where they don't rightfully belong.
Because Friendica and Hubzilla did not intrude into Mastodon's Fediverse. They were in the Fediverse before Mastodon.
You should care if you think that posting more than 500 characters is bad behaviour as it goes against "the Fediverse culture".
Because that "Fediverse culture" is only Mastodon's culture. And the culture on Friendica and Hubzilla, which pre-dates Mastodon itself by years, knows no character limits.
You should care if you think that Gargron is evil for introducing quote-posts to the Fediverse.
Because it was actually Mike Macgirvin, creator of Friendica and Hubzilla, who did that. In 2010. 16 years before now. Almost 6 years before Mastodon was even made.
And because just about everything that isn't Mastodon could quote-post Mastodon toots before Mastodon users even considered quote-posts evil.
You should care if you wish for "the Fediverse" to introduce certain new features. Like reply control. Or better list handlings. Or groups. Or even only more characters.
Because "the Fediverse" does have all these features. Just Mastodon doesn't have them. But Mastodon is not the Fediverse.
You should care if you don't want "the Fediverse" to ever introduce certain features. Like a higher default character limit. Or text formatting.
Because the Fediverse already has such features. As in, it can use these features in posts which it then sends to Mastodon. And there's nothing, absolutely nothing that Mastodon and its users can do against it. Except for muting and blocking.
You should care if you find it easier to use "Mastodon" and "Fediverse" synonymously, and all this "nitpicking" about when it's "Mastodon" and when it's "Fediverse" enrages you.
Because it enrages users in the non-Mastodon Fediverse when people say right into their faces that they toot. And/or that they're on Mastodon and therefore bound to the exact same rules and the exact same culture as everyone else on Mastodon. And they will so very much not let you have your way.
All these are things which, unfortunately, those who have never experienced anything else in the Fediverse than Mastodon will hardly ever understand.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Brett Coulstock You should care if you think that Gargron has invented the Fediverse as a pure Mastodon network. If you think that e.g. Friendica and Hubzilla came into the Mastodon Fediverse after the fact. If you use this thinking as a justification to force Mastodon's rules and Mastodon's culture upon Friendica and Hubzilla users because you take them for intruders in a place where they don't rightfully belong.
Because Friendica and Hubzilla did not intrude into Mastodon's Fediverse. They were in the Fediverse before Mastodon.
You should care if you think that posting more than 500 characters is bad behaviour as it goes against "the Fediverse culture".
Because that "Fediverse culture" is only Mastodon's culture. And the culture on Friendica and Hubzilla, which pre-dates Mastodon itself by years, knows no character limits.
You should care if you think that Gargron is evil for introducing quote-posts to the Fediverse.
Because it was actually Mike Macgirvin, creator of Friendica and Hubzilla, who did that. In 2010. 16 years before now. Almost 6 years before Mastodon was even made.
And because just about everything that isn't Mastodon could quote-post Mastodon toots before Mastodon users even considered quote-posts evil.
You should care if you wish for "the Fediverse" to introduce certain new features. Like reply control. Or better list handlings. Or groups. Or even only more characters.
Because "the Fediverse" does have all these features. Just Mastodon doesn't have them. But Mastodon is not the Fediverse.
You should care if you don't want "the Fediverse" to ever introduce certain features. Like a higher default character limit. Or text formatting.
Because the Fediverse already has such features. As in, it can use these features in posts which it then sends to Mastodon. And there's nothing, absolutely nothing that Mastodon and its users can do against it. Except for muting and blocking.
You should care if you find it easier to use "Mastodon" and "Fediverse" synonymously, and all this "nitpicking" about when it's "Mastodon" and when it's "Fediverse" enrages you.
Because it enrages users in the non-Mastodon Fediverse when people say right into their faces that they toot. And/or that they're on Mastodon and therefore bound to the exact same rules and the exact same culture as everyone else on Mastodon. And they will so very much not let you have your way.
All these are things which, unfortunately, those who have never experienced anything else in the Fediverse than Mastodon will hardly ever understand.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Brett Coulstock You should care if you think that Gargron has invented the Fediverse as a pure Mastodon network. If you think that e.g. Friendica and Hubzilla came into the Mastodon Fediverse after the fact. If you use this thinking as a justification to force Mastodon's rules and Mastodon's culture upon Friendica and Hubzilla users because you take them for intruders in a place where they don't rightfully belong.
Because Friendica and Hubzilla did not intrude into Mastodon's Fediverse. They were in the Fediverse before Mastodon.
You should care if you think that posting more than 500 characters is bad behaviour as it goes against "the Fediverse culture".
Because that "Fediverse culture" is only Mastodon's culture. And the culture on Friendica and Hubzilla, which pre-dates Mastodon itself by years, knows no character limits.
You should care if you think that Gargron is evil for introducing quote-posts to the Fediverse.
Because it was actually Mike Macgirvin, creator of Friendica and Hubzilla, who did that. In 2010. 16 years before now. Almost 6 years before Mastodon was even made.
And because just about everything that isn't Mastodon could quote-post Mastodon toots before Mastodon users even considered quote-posts evil.
You should care if you wish for "the Fediverse" to introduce certain new features. Like reply control. Or better list handlings. Or groups. Or even only more characters.
Because "the Fediverse" does have all these features. Just Mastodon doesn't have them. But Mastodon is not the Fediverse.
You should care if you don't want "the Fediverse" to ever introduce certain features. Like a higher default character limit. Or text formatting.
Because the Fediverse already has such features. As in, it can use these features in posts which it then sends to Mastodon. And there's nothing, absolutely nothing that Mastodon and its users can do against it. Except for muting and blocking.
You should care if you find it easier to use "Mastodon" and "Fediverse" synonymously, and all this "nitpicking" about when it's "Mastodon" and when it's "Fediverse" enrages you.
Because it enrages users in the non-Mastodon Fediverse when people say right into their faces that they toot. And/or that they're on Mastodon and therefore bound to the exact same rules and the exact same culture as everyone else on Mastodon. And they will so very much not let you have your way.
All these are things which, unfortunately, those who have never experienced anything else in the Fediverse than Mastodon will hardly ever understand.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Brett Coulstock You should care if you think that Gargron has invented the Fediverse as a pure Mastodon network. If you think that e.g. Friendica and Hubzilla came into the Mastodon Fediverse after the fact. If you use this thinking as a justification to force Mastodon's rules and Mastodon's culture upon Friendica and Hubzilla users because you take them for intruders in a place where they don't rightfully belong.
Because Friendica and Hubzilla did not intrude into Mastodon's Fediverse. They were in the Fediverse before Mastodon.
You should care if you think that posting more than 500 characters is bad behaviour as it goes against "the Fediverse culture".
Because that "Fediverse culture" is only Mastodon's culture. And the culture on Friendica and Hubzilla, which pre-dates Mastodon itself by years, knows no character limits.
You should care if you think that Gargron is evil for introducing quote-posts to the Fediverse.
Because it was actually Mike Macgirvin, creator of Friendica and Hubzilla, who did that. In 2010. 16 years before now. Almost 6 years before Mastodon was even made.
And because just about everything that isn't Mastodon could quote-post Mastodon toots before Mastodon users even considered quote-posts evil.
You should care if you wish for "the Fediverse" to introduce certain new features. Like reply control. Or better list handlings. Or groups. Or even only more characters.
Because "the Fediverse" does have all these features. Just Mastodon doesn't have them. But Mastodon is not the Fediverse.
You should care if you don't want "the Fediverse" to ever introduce certain features. Like a higher default character limit. Or text formatting.
Because the Fediverse already has such features. As in, it can use these features in posts which it then sends to Mastodon. And there's nothing, absolutely nothing that Mastodon and its users can do against it. Except for muting and blocking.
You should care if you find it easier to use "Mastodon" and "Fediverse" synonymously, and all this "nitpicking" about when it's "Mastodon" and when it's "Fediverse" enrages you.
Because it enrages users in the non-Mastodon Fediverse when people say right into their faces that they toot. And/or that they're on Mastodon and therefore bound to the exact same rules and the exact same culture as everyone else on Mastodon. And they will so very much not let you have your way.
All these are things which, unfortunately, those who have never experienced anything else in the Fediverse than Mastodon will hardly ever understand.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@Brett Coulstock You should care if you think that Gargron has invented the Fediverse as a pure Mastodon network. If you think that e.g. Friendica and Hubzilla came into the Mastodon Fediverse after the fact. If you use this thinking as a justification to force Mastodon's rules and Mastodon's culture upon Friendica and Hubzilla users because you take them for intruders in a place where they don't rightfully belong.
Because Friendica and Hubzilla did not intrude into Mastodon's Fediverse. They were in the Fediverse before Mastodon.
You should care if you think that posting more than 500 characters is bad behaviour as it goes against "the Fediverse culture".
Because that "Fediverse culture" is only Mastodon's culture. And the culture on Friendica and Hubzilla, which pre-dates Mastodon itself by years, knows no character limits.
You should care if you think that Gargron is evil for introducing quote-posts to the Fediverse.
Because it was actually Mike Macgirvin, creator of Friendica and Hubzilla, who did that. In 2010. 16 years before now. Almost 6 years before Mastodon was even made.
And because just about everything that isn't Mastodon could quote-post Mastodon toots before Mastodon users even considered quote-posts evil.
You should care if you wish for "the Fediverse" to introduce certain new features. Like reply control. Or better list handlings. Or groups. Or even only more characters.
Because "the Fediverse" does have all these features. Just Mastodon doesn't have them. But Mastodon is not the Fediverse.
You should care if you don't want "the Fediverse" to ever introduce certain features. Like a higher default character limit. Or text formatting.
Because the Fediverse already has such features. As in, it can use these features in posts which it then sends to Mastodon. And there's nothing, absolutely nothing that Mastodon and its users can do against it. Except for muting and blocking.
You should care if you find it easier to use "Mastodon" and "Fediverse" synonymously, and all this "nitpicking" about when it's "Mastodon" and when it's "Fediverse" enrages you.
Because it enrages users in the non-Mastodon Fediverse when people say right into their faces that they toot. And/or that they're on Mastodon and therefore bound to the exact same rules and the exact same culture as everyone else on Mastodon. And they will so very much not let you have your way.
All these are things which, unfortunately, those who have never experienced anything else in the Fediverse than Mastodon will hardly ever understand.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@craftxbox No, it's about more than every other Mastodon user thinking that the Fediverse equals Mastodon.
Most of the rest still think (or they think they know):- The Fediverse started with Mastodon. Gargron has invented the Fediverse.
- Everything that isn't Mastodon is either designed as a Mastodon add-on (Pixelfed, PeerTube etc.), or if it clearly isn't that, it's an intruder into the Mastodon Fediverse.
- If Mastodon doesn't have a feature, the Fediverse doesn't have that feature. This also means that if they succeed at keeping Mastodon from introducing a feature that they don't want, the whole Fediverse will never have it.
There are Mastodon users who wish for "the Fediverse" (they mean Mastodon because that's all they know) to introduce some feature, blissfully unaware that this feature is all over the Fediverse outside of Mastodon.
There are Mastodon users who "know for a fact" that Mastodon has just introduced quote-posts to the Fediverse, including an opt-out that works Fediverse-wide. They're blissfully unaware that a) Friendica and Hubzilla have been able to quote-post literally every single last public Mastodon toot since Mastodon's launch in 2016, and b) they both still are, opt-out or not.
And then there are those who spend two years or more thinking the entire Fediverse is a 500-character microblogging service, and who shit brix in sheer terror and hammer on the block button in sheer panic whenever a "toot" with more than 500 characters shows up in their timeline.
And, of course, those who try hard to force Mastodon's culture and Mastodon's rules, both of which are geared towards Mastodon and Mastodon only, upon users of server applications that are very very much not Mastodon. Because they think that Mastodon culture = Fediverse culture. And who, at the same time, fight everyone who suggests they do something that isn't inline with their perception of Mastodon's culture and rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@craftxbox No, it's about more than every other Mastodon user thinking that the Fediverse equals Mastodon.
Most of the rest still think (or they think they know):- The Fediverse started with Mastodon. Gargron has invented the Fediverse.
- Everything that isn't Mastodon is either designed as a Mastodon add-on (Pixelfed, PeerTube etc.), or if it clearly isn't that, it's an intruder into the Mastodon Fediverse.
- If Mastodon doesn't have a feature, the Fediverse doesn't have that feature. This also means that if they succeed at keeping Mastodon from introducing a feature that they don't want, the whole Fediverse will never have it.
There are Mastodon users who wish for "the Fediverse" (they mean Mastodon because that's all they know) to introduce some feature, blissfully unaware that this feature is all over the Fediverse outside of Mastodon.
There are Mastodon users who "know for a fact" that Mastodon has just introduced quote-posts to the Fediverse, including an opt-out that works Fediverse-wide. They're blissfully unaware that a) Friendica and Hubzilla have been able to quote-post literally every single last public Mastodon toot since Mastodon's launch in 2016, and b) they both still are, opt-out or not.
And then there are those who spend two years or more thinking the entire Fediverse is a 500-character microblogging service, and who shit brix in sheer terror and hammer on the block button in sheer panic whenever a "toot" with more than 500 characters shows up in their timeline.
And, of course, those who try hard to force Mastodon's culture and Mastodon's rules, both of which are geared towards Mastodon and Mastodon only, upon users of server applications that are very very much not Mastodon. Because they think that Mastodon culture = Fediverse culture. And who, at the same time, fight everyone who suggests they do something that isn't inline with their perception of Mastodon's culture and rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@craftxbox No, it's about more than every other Mastodon user thinking that the Fediverse equals Mastodon.
Most of the rest still think (or they think they know):- The Fediverse started with Mastodon. Gargron has invented the Fediverse.
- Everything that isn't Mastodon is either designed as a Mastodon add-on (Pixelfed, PeerTube etc.), or if it clearly isn't that, it's an intruder into the Mastodon Fediverse.
- If Mastodon doesn't have a feature, the Fediverse doesn't have that feature. This also means that if they succeed at keeping Mastodon from introducing a feature that they don't want, the whole Fediverse will never have it.
There are Mastodon users who wish for "the Fediverse" (they mean Mastodon because that's all they know) to introduce some feature, blissfully unaware that this feature is all over the Fediverse outside of Mastodon.
There are Mastodon users who "know for a fact" that Mastodon has just introduced quote-posts to the Fediverse, including an opt-out that works Fediverse-wide. They're blissfully unaware that a) Friendica and Hubzilla have been able to quote-post literally every single last public Mastodon toot since Mastodon's launch in 2016, and b) they both still are, opt-out or not.
And then there are those who spend two years or more thinking the entire Fediverse is a 500-character microblogging service, and who shit brix in sheer terror and hammer on the block button in sheer panic whenever a "toot" with more than 500 characters shows up in their timeline.
And, of course, those who try hard to force Mastodon's culture and Mastodon's rules, both of which are geared towards Mastodon and Mastodon only, upon users of server applications that are very very much not Mastodon. Because they think that Mastodon culture = Fediverse culture. And who, at the same time, fight everyone who suggests they do something that isn't inline with their perception of Mastodon's culture and rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@craftxbox No, it's about more than every other Mastodon user thinking that the Fediverse equals Mastodon.
Most of the rest still think (or they think they know):- The Fediverse started with Mastodon. Gargron has invented the Fediverse.
- Everything that isn't Mastodon is either designed as a Mastodon add-on (Pixelfed, PeerTube etc.), or if it clearly isn't that, it's an intruder into the Mastodon Fediverse.
- If Mastodon doesn't have a feature, the Fediverse doesn't have that feature. This also means that if they succeed at keeping Mastodon from introducing a feature that they don't want, the whole Fediverse will never have it.
There are Mastodon users who wish for "the Fediverse" (they mean Mastodon because that's all they know) to introduce some feature, blissfully unaware that this feature is all over the Fediverse outside of Mastodon.
There are Mastodon users who "know for a fact" that Mastodon has just introduced quote-posts to the Fediverse, including an opt-out that works Fediverse-wide. They're blissfully unaware that a) Friendica and Hubzilla have been able to quote-post literally every single last public Mastodon toot since Mastodon's launch in 2016, and b) they both still are, opt-out or not.
And then there are those who spend two years or more thinking the entire Fediverse is a 500-character microblogging service, and who shit brix in sheer terror and hammer on the block button in sheer panic whenever a "toot" with more than 500 characters shows up in their timeline.
And, of course, those who try hard to force Mastodon's culture and Mastodon's rules, both of which are geared towards Mastodon and Mastodon only, upon users of server applications that are very very much not Mastodon. Because they think that Mastodon culture = Fediverse culture. And who, at the same time, fight everyone who suggests they do something that isn't inline with their perception of Mastodon's culture and rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@craftxbox No, it's about more than every other Mastodon user thinking that the Fediverse equals Mastodon.
Most of the rest still think (or they think they know):- The Fediverse started with Mastodon. Gargron has invented the Fediverse.
- Everything that isn't Mastodon is either designed as a Mastodon add-on (Pixelfed, PeerTube etc.), or if it clearly isn't that, it's an intruder into the Mastodon Fediverse.
- If Mastodon doesn't have a feature, the Fediverse doesn't have that feature. This also means that if they succeed at keeping Mastodon from introducing a feature that they don't want, the whole Fediverse will never have it.
There are Mastodon users who wish for "the Fediverse" (they mean Mastodon because that's all they know) to introduce some feature, blissfully unaware that this feature is all over the Fediverse outside of Mastodon.
There are Mastodon users who "know for a fact" that Mastodon has just introduced quote-posts to the Fediverse, including an opt-out that works Fediverse-wide. They're blissfully unaware that a) Friendica and Hubzilla have been able to quote-post literally every single last public Mastodon toot since Mastodon's launch in 2016, and b) they both still are, opt-out or not.
And then there are those who spend two years or more thinking the entire Fediverse is a 500-character microblogging service, and who shit brix in sheer terror and hammer on the block button in sheer panic whenever a "toot" with more than 500 characters shows up in their timeline.
And, of course, those who try hard to force Mastodon's culture and Mastodon's rules, both of which are geared towards Mastodon and Mastodon only, upon users of server applications that are very very much not Mastodon. Because they think that Mastodon culture = Fediverse culture. And who, at the same time, fight everyone who suggests they do something that isn't inline with their perception of Mastodon's culture and rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@craftxbox No, it's about more than every other Mastodon user thinking that the Fediverse equals Mastodon.
Most of the rest still think (or they think they know):- The Fediverse started with Mastodon. Gargron has invented the Fediverse.
- Everything that isn't Mastodon is either designed as a Mastodon add-on (Pixelfed, PeerTube etc.), or if it clearly isn't that, it's an intruder into the Mastodon Fediverse.
- If Mastodon doesn't have a feature, the Fediverse doesn't have that feature. This also means that if they succeed at keeping Mastodon from introducing a feature that they don't want, the whole Fediverse will never have it.
There are Mastodon users who wish for "the Fediverse" (they mean Mastodon because that's all they know) to introduce some feature, blissfully unaware that this feature is all over the Fediverse outside of Mastodon.
There are Mastodon users who "know for a fact" that Mastodon has just introduced quote-posts to the Fediverse, including an opt-out that works Fediverse-wide. They're blissfully unaware that a) Friendica and Hubzilla have been able to quote-post literally every single last public Mastodon toot since Mastodon's launch in 2016, and b) they both still are, opt-out or not.
And then there are those who spend two years or more thinking the entire Fediverse is a 500-character microblogging service, and who shit brix in sheer terror and hammer on the block button in sheer panic whenever a "toot" with more than 500 characters shows up in their timeline.
And, of course, those who try hard to force Mastodon's culture and Mastodon's rules, both of which are geared towards Mastodon and Mastodon only, upon users of server applications that are very very much not Mastodon. Because they think that Mastodon culture = Fediverse culture. And who, at the same time, fight everyone who suggests they do something that isn't inline with their perception of Mastodon's culture and rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
@Leonardo Giovanni Scur First of all, it isn't about my requirements. Just like, surprise, surprise, Mastodon's alt-text police is not blind.
It's about general accessibility. And it's about Mastodon users acting inclusively towards blind or visually-impaired people and, at the same time, ableistically towards people with other physical disabilities. Just because they cling hard to the extra 1,500 characters that alt-text gives them per image to their meagre character count for posts.
Except for professional Web accessibility experts, literally nobody on Mastodon seems to know what alt-text really is for. Alt-text is meant to be a 1:1 stand-in for an image, in case the image can't be perceived for whichever reason.
Alt-text is not meant to be an additional source of information beyond what information the image conveys.
Mastodon's use of alt-text for extra information beyond the post character limit is just as much alt-text misuse as cramming alt-text with keywords for SEO on websites. Unfortunately, it is so deeply engrained into Mastodon's culture that even the Mastodon devs have played along and added that "ALT" button which most Mastodon users think is the default and the standard Fediverse-wide now.
But let me tell you something:
Mastodon and its forks are most likely the only Fediverse server applications with an alt-text button. And they're far from making up the whole Fediverse.
Misskey and its various forks don't have an alt-text button.
AFAIK, Pleroma-FE and Akkoma-FE don't have an alt-text button, and neither has Mangane.
Friendica, Hubzilla, (streams), Forte, they all don't have an alt-text button.
Lemmy doesn't have an alt-text button. /kbin and Mbin don't have an alt-text button. PieFed doesn't have an alt-text button.
WriteFreely doesn't have an alt-text button. Plume doesn't have an alt-text button. WordPress doesn't have an alt-text button either.
Blogs in general don't have an alt-text button. Forums don't have an alt-text button. Static websites don't have an alt-text button.
Twitter/𝕏 doesn't have an alt-text button. Facebook doesn't have an alt-text button. Instagram doesn't have an alt-text button. Threads doesn't have an alt-text button. Tumblr doesn't have an alt-text button. Flickr doesn't have an alt-text button. Pinterest doesn't have an alt-text button. And so forth.
The W3C doesn't mention alt-text buttons. The WCAG don't mention alt-text buttons.
Why not? Because they're all way behind Mastodon in accessibility?
No, but because their developers know that alt-text is not an additional source of information for sighted people.
Literally the only place anywhere in the Web where alt-text both counts and is actively used as an additional source of information for sighted people is Mastodon. Plus its forks.
How I handle that? I put all needed extra information into the post text. But I'm not on Mastodon. I'm on Hubzilla. My character limit is over 30,000 times higher than on Mastodon.
Seriously, if missing alt-text is sanctioned as ableist, if useless alt-text is sanctioned as ableist, if inaccurate alt-text is sanctioned as ableist, if too lacking alt-text is sanctioned as ableist, then putting exclusive information into alt-text must be sanctioned as ableist just as well.
To those on Mastodon who oh so desperately need more than 500 characters: Move someplace in the Fediverse that has more than 500 characters. There's Fediverse server software from 3,000 characters to over 24,000,000 characters that, nonetheless, is federated with Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Ableism #AbleismMeta #CWAbleismMeta -
@Leonardo Giovanni Scur First of all, it isn't about my requirements. Just like, surprise, surprise, Mastodon's alt-text police is not blind.
It's about general accessibility. And it's about Mastodon users acting inclusively towards blind or visually-impaired people and, at the same time, ableistically towards people with other physical disabilities. Just because they cling hard to the extra 1,500 characters that alt-text gives them per image to their meagre character count for posts.
Except for professional Web accessibility experts, literally nobody on Mastodon seems to know what alt-text really is for. Alt-text is meant to be a 1:1 stand-in for an image, in case the image can't be perceived for whichever reason.
Alt-text is not meant to be an additional source of information beyond what information the image conveys.
Mastodon's use of alt-text for extra information beyond the post character limit is just as much alt-text misuse as cramming alt-text with keywords for SEO on websites. Unfortunately, it is so deeply engrained into Mastodon's culture that even the Mastodon devs have played along and added that "ALT" button which most Mastodon users think is the default and the standard Fediverse-wide now.
But let me tell you something:
Mastodon and its forks are most likely the only Fediverse server applications with an alt-text button. And they're far from making up the whole Fediverse.
Misskey and its various forks don't have an alt-text button.
AFAIK, Pleroma-FE and Akkoma-FE don't have an alt-text button, and neither has Mangane.
Friendica, Hubzilla, (streams), Forte, they all don't have an alt-text button.
Lemmy doesn't have an alt-text button. /kbin and Mbin don't have an alt-text button. PieFed doesn't have an alt-text button.
WriteFreely doesn't have an alt-text button. Plume doesn't have an alt-text button. WordPress doesn't have an alt-text button either.
Blogs in general don't have an alt-text button. Forums don't have an alt-text button. Static websites don't have an alt-text button.
Twitter/𝕏 doesn't have an alt-text button. Facebook doesn't have an alt-text button. Instagram doesn't have an alt-text button. Threads doesn't have an alt-text button. Tumblr doesn't have an alt-text button. Flickr doesn't have an alt-text button. Pinterest doesn't have an alt-text button. And so forth.
The W3C doesn't mention alt-text buttons. The WCAG don't mention alt-text buttons.
Why not? Because they're all way behind Mastodon in accessibility?
No, but because their developers know that alt-text is not an additional source of information for sighted people.
Literally the only place anywhere in the Web where alt-text both counts and is actively used as an additional source of information for sighted people is Mastodon. Plus its forks.
How I handle that? I put all needed extra information into the post text. But I'm not on Mastodon. I'm on Hubzilla. My character limit is over 30,000 times higher than on Mastodon.
Seriously, if missing alt-text is sanctioned as ableist, if useless alt-text is sanctioned as ableist, if inaccurate alt-text is sanctioned as ableist, if too lacking alt-text is sanctioned as ableist, then putting exclusive information into alt-text must be sanctioned as ableist just as well.
To those on Mastodon who oh so desperately need more than 500 characters: Move someplace in the Fediverse that has more than 500 characters. There's Fediverse server software from 3,000 characters to over 24,000,000 characters that, nonetheless, is federated with Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Ableism #AbleismMeta #CWAbleismMeta -
@Quasit I wouldn't build it on Mastodon. Nor would I build it from scratch and then against Mastodon, only Mastodon and nothing but Mastodon. The Fediverse is not only much more than Mastodon, but technologically much more diverse than just Mastodon.
The best way would be to build it as an add-on (a so-called "app") for (streams) or Forte. That way, you would neither have to deal with Mastodon's limitations (yes, Mastodon is very limited although this isn't apparent to those of its users who don't know anything else), nor would you have to develop Fediverse server software from scratch.
In case you don't know them:
(streams) is the unofficial community name of a very powerful but technically nameless Fediverse application whose code is in the streams repository (https://codeberg.org/streams/streams). It's essentially a Facebook-style social networking application with quite a number of extra features and the second-most recent member of a software family that dates all the way back to Friendica from 2010 (https://friendi.ca). It's a fork of a fork of three forks of a fork (of a fork?) of Hubzilla (https://hubzilla.org) which, in turn, was reworked from a fork of a fork of what's now Friendica.
And Forte (https://codeberg.org/fortified/forte) is a fork of the streams repository that's very similar to (streams) itself.
All this was originally done by one and the same developer, a professional in IT and software for close to half a century.
Here is an article I've put together with tables that compare Mastodon, Friendica, Hubzilla, (streams) and Forte: https://hub.netzgemeinde.eu/item/0a75de76-eb27-4149-b708-f20b2f79d392
Unlike Mastodon which has only got four general-purpose profile fields in addition to the profile text, both (streams) and Forte already come with the profile fields that a good dating app would need such as:- pronouns (pick one out of 3 or none at all)
- birthday (from which the age is calculated)
- six free-text location fields, even including Facebook-style "hometown" where you used to live; you can select for yourself how far you want to go into detail with revealing your location
- gender (pick one out of 14 or none at all)
- marital status (pick one out of 31 or none at all) plus who plus date since
- sexual preference (pick one out of 9 or none at all)
- a separate keyword field
- political views
- religious views
- hobbies/interests
- likes
- dislikes
- other channels/Fediverse identities
- musical interests
- books/literature
- television
- film/dance/culture/entertainment
- love/romance
- work/employment
- school/education
A dating app could easily tie into the directory and make use of these profile fields. It could use a tag of its own in the keyword field so that it only shows channels that use this app (I'm not sure if it's possible to detect which channel has which apps installed).
One big advantage for users is that they don't have to use their daily-driver channel for the dating app. On Mastodon and in most of the Fediverse, your account is both your login and your identity. On (streams) and Forte, you can have multiple fully independent identities, each with its own name, its own ID, its own profile, its own contacts, its own posts and conversations, its own settings etc. etc., all behind one and the same login. It's like having multiple Mastodon accounts behind one login. That way, users don't have to reveal to everyone who knows their official daily-driver channel that they're using this dating app.
Also, Mastodon is hard-coded to 500 characters. You literally have to soft-fork it and edit the source code to change the limit. Both (streams) and Forte are essentially unlimited in characters (their actual character limit is over 24 million).
Privacy and security are much higher on (streams) and Forte than on Mastodon, in fact, much higher than most Fediverse users can even imagine. Private messages are actually literally private. On Mastodon, a direct message only defines whom it's sent to. On (streams) and Forte, permissions come into play. The start post in a conversation defines who is allowed to see the conversation. Not only that post, but all comments as well. It's literally impossible to pull someone else into an existing private conversation by mentioning because that someone simply isn't allowed to see anything in the conversation.
So when you're chatting with a woman via PM, and she dislikes you, she can't shame or dogpile you by pulling her friends into the conversation.
On top of that, although even Friendica already had quote-posts since 2010, private messages cannot be quote-posted.
For a developer, all it takes to build this is PHP plus database know-how. Like the whole rest of the family, (streams) and Forte don't need anything more than a LAMP stack. No Ruby on Rails, no Elixir, no TypeScript or Vue.js or any other JavaScript, no .NET.
Deploying a (streams) or Forte app is easy, too: Create a public git repository for it, keep it there, and server admins can add your repository to their servers and activate your app server-side. Both (streams) and Forte are very modular and designed to be easy to expand.
Most of this would be possible with Hubzilla as well which is much bigger in terms of users and available servers. However, Hubzilla has got one disadvantage: Its directory only shows Hubzilla and (streams) channels, i.e. channels that use Hubzilla's native Zot protocol. That's because ActivityPub support on Hubzilla is provided by another app, it's optional, it's off by default, and the directory can't tie into it. On (streams), ActivityPub support is still optional, but more advanced than on Hubzilla, built into the core and on by default. And Forte doesn't support anything else than ActivityPub.
In theory, it should be possible to build such a dating app for all three.
Also, yes, in theory, channels that use such a dating app can connect to Mastodon. But Mastodon users couldn't use that dating app. Mastodon simply doesn't have any support for profile fields which it itself doesn't have. Also, Mastodon is too unsecure, and meaningful conversations are difficult if one side is limited to 500 characters. And I would hate to see this dating app bound hard to Mastodon's culture and Mastodon's unwritten rules, neither of which take the Fediverse outside of Mastodon into account.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #MastodonCulture #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #FediDate -
@Quasit I wouldn't build it on Mastodon. Nor would I build it from scratch and then against Mastodon, only Mastodon and nothing but Mastodon. The Fediverse is not only much more than Mastodon, but technologically much more diverse than just Mastodon.
The best way would be to build it as an add-on (a so-called "app") for (streams) or Forte. That way, you would neither have to deal with Mastodon's limitations (yes, Mastodon is very limited although this isn't apparent to those of its users who don't know anything else), nor would you have to develop Fediverse server software from scratch.
In case you don't know them:
(streams) is the unofficial community name of a very powerful but technically nameless Fediverse application whose code is in the streams repository (https://codeberg.org/streams/streams). It's essentially a Facebook-style social networking application with quite a number of extra features and the second-most recent member of a software family that dates all the way back to Friendica from 2010 (https://friendi.ca). It's a fork of a fork of three forks of a fork (of a fork?) of Hubzilla (https://hubzilla.org) which, in turn, was reworked from a fork of a fork of what's now Friendica.
And Forte (https://codeberg.org/fortified/forte) is a fork of the streams repository that's very similar to (streams) itself.
All this was originally done by one and the same developer, a professional in IT and software for close to half a century.
Here is an article I've put together with tables that compare Mastodon, Friendica, Hubzilla, (streams) and Forte: https://hub.netzgemeinde.eu/item/0a75de76-eb27-4149-b708-f20b2f79d392
Unlike Mastodon which has only got four general-purpose profile fields in addition to the profile text, both (streams) and Forte already come with the profile fields that a good dating app would need such as:- pronouns (pick one out of 3 or none at all)
- birthday (from which the age is calculated)
- six free-text location fields, even including Facebook-style "hometown" where you used to live; you can select for yourself how far you want to go into detail with revealing your location
- gender (pick one out of 14 or none at all)
- marital status (pick one out of 31 or none at all) plus who plus date since
- sexual preference (pick one out of 9 or none at all)
- a separate keyword field
- political views
- religious views
- hobbies/interests
- likes
- dislikes
- other channels/Fediverse identities
- musical interests
- books/literature
- television
- film/dance/culture/entertainment
- love/romance
- work/employment
- school/education
A dating app could easily tie into the directory and make use of these profile fields. It could use a tag of its own in the keyword field so that it only shows channels that use this app (I'm not sure if it's possible to detect which channel has which apps installed).
One big advantage for users is that they don't have to use their daily-driver channel for the dating app. On Mastodon and in most of the Fediverse, your account is both your login and your identity. On (streams) and Forte, you can have multiple fully independent identities, each with its own name, its own ID, its own profile, its own contacts, its own posts and conversations, its own settings etc. etc., all behind one and the same login. It's like having multiple Mastodon accounts behind one login. That way, users don't have to reveal to everyone who knows their official daily-driver channel that they're using this dating app.
Also, Mastodon is hard-coded to 500 characters. You literally have to soft-fork it and edit the source code to change the limit. Both (streams) and Forte are essentially unlimited in characters (their actual character limit is over 24 million).
Privacy and security are much higher on (streams) and Forte than on Mastodon, in fact, much higher than most Fediverse users can even imagine. Private messages are actually literally private. On Mastodon, a direct message only defines whom it's sent to. On (streams) and Forte, permissions come into play. The start post in a conversation defines who is allowed to see the conversation. Not only that post, but all comments as well. It's literally impossible to pull someone else into an existing private conversation by mentioning because that someone simply isn't allowed to see anything in the conversation.
So when you're chatting with a woman via PM, and she dislikes you, she can't shame or dogpile you by pulling her friends into the conversation.
On top of that, although even Friendica already had quote-posts since 2010, private messages cannot be quote-posted.
For a developer, all it takes to build this is PHP plus database know-how. Like the whole rest of the family, (streams) and Forte don't need anything more than a LAMP stack. No Ruby on Rails, no Elixir, no TypeScript or Vue.js or any other JavaScript, no .NET.
Deploying a (streams) or Forte app is easy, too: Create a public git repository for it, keep it there, and server admins can add your repository to their servers and activate your app server-side. Both (streams) and Forte are very modular and designed to be easy to expand.
Most of this would be possible with Hubzilla as well which is much bigger in terms of users and available servers. However, Hubzilla has got one disadvantage: Its directory only shows Hubzilla and (streams) channels, i.e. channels that use Hubzilla's native Zot protocol. That's because ActivityPub support on Hubzilla is provided by another app, it's optional, it's off by default, and the directory can't tie into it. On (streams), ActivityPub support is still optional, but more advanced than on Hubzilla, built into the core and on by default. And Forte doesn't support anything else than ActivityPub.
In theory, it should be possible to build such a dating app for all three.
Also, yes, in theory, channels that use such a dating app can connect to Mastodon. But Mastodon users couldn't use that dating app. Mastodon simply doesn't have any support for profile fields which it itself doesn't have. Also, Mastodon is too unsecure, and meaningful conversations are difficult if one side is limited to 500 characters. And I would hate to see this dating app bound hard to Mastodon's culture and Mastodon's unwritten rules, neither of which take the Fediverse outside of Mastodon into account.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #MastodonCulture #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #FediDate -
@Quasit I wouldn't build it on Mastodon. Nor would I build it from scratch and then against Mastodon, only Mastodon and nothing but Mastodon. The Fediverse is not only much more than Mastodon, but technologically much more diverse than just Mastodon.
The best way would be to build it as an add-on (a so-called "app") for (streams) or Forte. That way, you would neither have to deal with Mastodon's limitations (yes, Mastodon is very limited although this isn't apparent to those of its users who don't know anything else), nor would you have to develop Fediverse server software from scratch.
In case you don't know them:
(streams) is the unofficial community name of a very powerful but technically nameless Fediverse application whose code is in the streams repository (https://codeberg.org/streams/streams). It's essentially a Facebook-style social networking application with quite a number of extra features and the second-most recent member of a software family that dates all the way back to Friendica from 2010 (https://friendi.ca). It's a fork of a fork of three forks of a fork (of a fork?) of Hubzilla (https://hubzilla.org) which, in turn, was reworked from a fork of a fork of what's now Friendica.
And Forte (https://codeberg.org/fortified/forte) is a fork of the streams repository that's very similar to (streams) itself.
All this was originally done by one and the same developer, a professional in IT and software for close to half a century.
Here is an article I've put together with tables that compare Mastodon, Friendica, Hubzilla, (streams) and Forte: https://hub.netzgemeinde.eu/item/0a75de76-eb27-4149-b708-f20b2f79d392
Unlike Mastodon which has only got four general-purpose profile fields in addition to the profile text, both (streams) and Forte already come with the profile fields that a good dating app would need such as:- pronouns (pick one out of 3 or none at all)
- birthday (from which the age is calculated)
- six free-text location fields, even including Facebook-style "hometown" where you used to live; you can select for yourself how far you want to go into detail with revealing your location
- gender (pick one out of 14 or none at all)
- marital status (pick one out of 31 or none at all) plus who plus date since
- sexual preference (pick one out of 9 or none at all)
- a separate keyword field
- political views
- religious views
- hobbies/interests
- likes
- dislikes
- other channels/Fediverse identities
- musical interests
- books/literature
- television
- film/dance/culture/entertainment
- love/romance
- work/employment
- school/education
A dating app could easily tie into the directory and make use of these profile fields. It could use a tag of its own in the keyword field so that it only shows channels that use this app (I'm not sure if it's possible to detect which channel has which apps installed).
One big advantage for users is that they don't have to use their daily-driver channel for the dating app. On Mastodon and in most of the Fediverse, your account is both your login and your identity. On (streams) and Forte, you can have multiple fully independent identities, each with its own name, its own ID, its own profile, its own contacts, its own posts and conversations, its own settings etc. etc., all behind one and the same login. It's like having multiple Mastodon accounts behind one login. That way, users don't have to reveal to everyone who knows their official daily-driver channel that they're using this dating app.
Also, Mastodon is hard-coded to 500 characters. You literally have to soft-fork it and edit the source code to change the limit. Both (streams) and Forte are essentially unlimited in characters (their actual character limit is over 24 million).
Privacy and security are much higher on (streams) and Forte than on Mastodon, in fact, much higher than most Fediverse users can even imagine. Private messages are actually literally private. On Mastodon, a direct message only defines whom it's sent to. On (streams) and Forte, permissions come into play. The start post in a conversation defines who is allowed to see the conversation. Not only that post, but all comments as well. It's literally impossible to pull someone else into an existing private conversation by mentioning because that someone simply isn't allowed to see anything in the conversation.
So when you're chatting with a woman via PM, and she dislikes you, she can't shame or dogpile you by pulling her friends into the conversation.
On top of that, although even Friendica already had quote-posts since 2010, private messages cannot be quote-posted.
For a developer, all it takes to build this is PHP plus database know-how. Like the whole rest of the family, (streams) and Forte don't need anything more than a LAMP stack. No Ruby on Rails, no Elixir, no TypeScript or Vue.js or any other JavaScript, no .NET.
Deploying a (streams) or Forte app is easy, too: Create a public git repository for it, keep it there, and server admins can add your repository to their servers and activate your app server-side. Both (streams) and Forte are very modular and designed to be easy to expand.
Most of this would be possible with Hubzilla as well which is much bigger in terms of users and available servers. However, Hubzilla has got one disadvantage: Its directory only shows Hubzilla and (streams) channels, i.e. channels that use Hubzilla's native Zot protocol. That's because ActivityPub support on Hubzilla is provided by another app, it's optional, it's off by default, and the directory can't tie into it. On (streams), ActivityPub support is still optional, but more advanced than on Hubzilla, built into the core and on by default. And Forte doesn't support anything else than ActivityPub.
In theory, it should be possible to build such a dating app for all three.
Also, yes, in theory, channels that use such a dating app can connect to Mastodon. But Mastodon users couldn't use that dating app. Mastodon simply doesn't have any support for profile fields which it itself doesn't have. Also, Mastodon is too unsecure, and meaningful conversations are difficult if one side is limited to 500 characters. And I would hate to see this dating app bound hard to Mastodon's culture and Mastodon's unwritten rules, neither of which take the Fediverse outside of Mastodon into account.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #MastodonCulture #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #FediDate -
@Quasit I wouldn't build it on Mastodon. Nor would I build it from scratch and then against Mastodon, only Mastodon and nothing but Mastodon. The Fediverse is not only much more than Mastodon, but technologically much more diverse than just Mastodon.
The best way would be to build it as an add-on (a so-called "app") for (streams) or Forte. That way, you would neither have to deal with Mastodon's limitations (yes, Mastodon is very limited although this isn't apparent to those of its users who don't know anything else), nor would you have to develop Fediverse server software from scratch.
In case you don't know them:
(streams) is the unofficial community name of a very powerful but technically nameless Fediverse application whose code is in the streams repository (https://codeberg.org/streams/streams). It's essentially a Facebook-style social networking application with quite a number of extra features and the second-most recent member of a software family that dates all the way back to Friendica from 2010 (https://friendi.ca). It's a fork of a fork of three forks of a fork (of a fork?) of Hubzilla (https://hubzilla.org) which, in turn, was reworked from a fork of a fork of what's now Friendica.
And Forte (https://codeberg.org/fortified/forte) is a fork of the streams repository that's very similar to (streams) itself.
All this was originally done by one and the same developer, a professional in IT and software for close to half a century.
Here is an article I've put together with tables that compare Mastodon, Friendica, Hubzilla, (streams) and Forte: https://hub.netzgemeinde.eu/item/0a75de76-eb27-4149-b708-f20b2f79d392
Unlike Mastodon which has only got four general-purpose profile fields in addition to the profile text, both (streams) and Forte already come with the profile fields that a good dating app would need such as:- pronouns (pick one out of 3 or none at all)
- birthday (from which the age is calculated)
- six free-text location fields, even including Facebook-style "hometown" where you used to live; you can select for yourself how far you want to go into detail with revealing your location
- gender (pick one out of 14 or none at all)
- marital status (pick one out of 31 or none at all) plus who plus date since
- sexual preference (pick one out of 9 or none at all)
- a separate keyword field
- political views
- religious views
- hobbies/interests
- likes
- dislikes
- other channels/Fediverse identities
- musical interests
- books/literature
- television
- film/dance/culture/entertainment
- love/romance
- work/employment
- school/education
A dating app could easily tie into the directory and make use of these profile fields. It could use a tag of its own in the keyword field so that it only shows channels that use this app (I'm not sure if it's possible to detect which channel has which apps installed).
One big advantage for users is that they don't have to use their daily-driver channel for the dating app. On Mastodon and in most of the Fediverse, your account is both your login and your identity. On (streams) and Forte, you can have multiple fully independent identities, each with its own name, its own ID, its own profile, its own contacts, its own posts and conversations, its own settings etc. etc., all behind one and the same login. It's like having multiple Mastodon accounts behind one login. That way, users don't have to reveal to everyone who knows their official daily-driver channel that they're using this dating app.
Also, Mastodon is hard-coded to 500 characters. You literally have to soft-fork it and edit the source code to change the limit. Both (streams) and Forte are essentially unlimited in characters (their actual character limit is over 24 million).
Privacy and security are much higher on (streams) and Forte than on Mastodon, in fact, much higher than most Fediverse users can even imagine. Private messages are actually literally private. On Mastodon, a direct message only defines whom it's sent to. On (streams) and Forte, permissions come into play. The start post in a conversation defines who is allowed to see the conversation. Not only that post, but all comments as well. It's literally impossible to pull someone else into an existing private conversation by mentioning because that someone simply isn't allowed to see anything in the conversation.
So when you're chatting with a woman via PM, and she dislikes you, she can't shame or dogpile you by pulling her friends into the conversation.
On top of that, although even Friendica already had quote-posts since 2010, private messages cannot be quote-posted.
For a developer, all it takes to build this is PHP plus database know-how. Like the whole rest of the family, (streams) and Forte don't need anything more than a LAMP stack. No Ruby on Rails, no Elixir, no TypeScript or Vue.js or any other JavaScript, no .NET.
Deploying a (streams) or Forte app is easy, too: Create a public git repository for it, keep it there, and server admins can add your repository to their servers and activate your app server-side. Both (streams) and Forte are very modular and designed to be easy to expand.
Most of this would be possible with Hubzilla as well which is much bigger in terms of users and available servers. However, Hubzilla has got one disadvantage: Its directory only shows Hubzilla and (streams) channels, i.e. channels that use Hubzilla's native Zot protocol. That's because ActivityPub support on Hubzilla is provided by another app, it's optional, it's off by default, and the directory can't tie into it. On (streams), ActivityPub support is still optional, but more advanced than on Hubzilla, built into the core and on by default. And Forte doesn't support anything else than ActivityPub.
In theory, it should be possible to build such a dating app for all three.
Also, yes, in theory, channels that use such a dating app can connect to Mastodon. But Mastodon users couldn't use that dating app. Mastodon simply doesn't have any support for profile fields which it itself doesn't have. Also, Mastodon is too unsecure, and meaningful conversations are difficult if one side is limited to 500 characters. And I would hate to see this dating app bound hard to Mastodon's culture and Mastodon's unwritten rules, neither of which take the Fediverse outside of Mastodon into account.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #MastodonCulture #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #FediDate -
@Hazelnoot My goal is to get alt-texts and image descriptions right. As right as possible.
My goal is to not be sanctioned and/or lectured by the alt-text police for allegedly being lazy and/or careless.
In order to achieve that, I must be ahead of everyone's requirements. Whatever these requirements may be.
But in order to achieve that, I must know their requirements. Everyone's requirements.
If you want me to follow your rules, I need to know your rules.
Right now, I'm probably vastly overcompliant with everyone's rules with only a few exceptions that I can't comply with (alt-texts must not be longer than 200 or 125 or 100 characters, posts in the Fediverse must not be longer than 500 characters, all of the text in an image must always be transcribed in the alt-text etc.).
This way, I hope that my image posts will stay in compliance with existing image description quality standards for a few years, and when they no longer are, they're so old that nobody demands I upgrade my image descriptions to then-current standards.
tl;dr: "Just do it" doesn't cut it. Just doing it is likely to get you sanctioned because you don't do it well enough. And something is no longer better than nothing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #MastodonCulture -
@Hazelnoot My goal is to get alt-texts and image descriptions right. As right as possible.
My goal is to not be sanctioned and/or lectured by the alt-text police for allegedly being lazy and/or careless.
In order to achieve that, I must be ahead of everyone's requirements. Whatever these requirements may be.
But in order to achieve that, I must know their requirements. Everyone's requirements.
If you want me to follow your rules, I need to know your rules.
Right now, I'm probably vastly overcompliant with everyone's rules with only a few exceptions that I can't comply with (alt-texts must not be longer than 200 or 125 or 100 characters, posts in the Fediverse must not be longer than 500 characters, all of the text in an image must always be transcribed in the alt-text etc.).
This way, I hope that my image posts will stay in compliance with existing image description quality standards for a few years, and when they no longer are, they're so old that nobody demands I upgrade my image descriptions to then-current standards.
tl;dr: "Just do it" doesn't cut it. Just doing it is likely to get you sanctioned because you don't do it well enough. And something is no longer better than nothing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #MastodonCulture -
@Hazelnoot My goal is to get alt-texts and image descriptions right. As right as possible.
My goal is to not be sanctioned and/or lectured by the alt-text police for allegedly being lazy and/or careless.
In order to achieve that, I must be ahead of everyone's requirements. Whatever these requirements may be.
But in order to achieve that, I must know their requirements. Everyone's requirements.
If you want me to follow your rules, I need to know your rules.
Right now, I'm probably vastly overcompliant with everyone's rules with only a few exceptions that I can't comply with (alt-texts must not be longer than 200 or 125 or 100 characters, posts in the Fediverse must not be longer than 500 characters, all of the text in an image must always be transcribed in the alt-text etc.).
This way, I hope that my image posts will stay in compliance with existing image description quality standards for a few years, and when they no longer are, they're so old that nobody demands I upgrade my image descriptions to then-current standards.
tl;dr: "Just do it" doesn't cut it. Just doing it is likely to get you sanctioned because you don't do it well enough. And something is no longer better than nothing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #MastodonCulture -
@Hazelnoot My goal is to get alt-texts and image descriptions right. As right as possible.
My goal is to not be sanctioned and/or lectured by the alt-text police for allegedly being lazy and/or careless.
In order to achieve that, I must be ahead of everyone's requirements. Whatever these requirements may be.
But in order to achieve that, I must know their requirements. Everyone's requirements.
If you want me to follow your rules, I need to know your rules.
Right now, I'm probably vastly overcompliant with everyone's rules with only a few exceptions that I can't comply with (alt-texts must not be longer than 200 or 125 or 100 characters, posts in the Fediverse must not be longer than 500 characters, all of the text in an image must always be transcribed in the alt-text etc.).
This way, I hope that my image posts will stay in compliance with existing image description quality standards for a few years, and when they no longer are, they're so old that nobody demands I upgrade my image descriptions to then-current standards.
tl;dr: "Just do it" doesn't cut it. Just doing it is likely to get you sanctioned because you don't do it well enough. And something is no longer better than nothing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #MastodonCulture -
@Hazelnoot My goal is to get alt-texts and image descriptions right. As right as possible.
My goal is to not be sanctioned and/or lectured by the alt-text police for allegedly being lazy and/or careless.
In order to achieve that, I must be ahead of everyone's requirements. Whatever these requirements may be.
But in order to achieve that, I must know their requirements. Everyone's requirements.
If you want me to follow your rules, I need to know your rules.
Right now, I'm probably vastly overcompliant with everyone's rules with only a few exceptions that I can't comply with (alt-texts must not be longer than 200 or 125 or 100 characters, posts in the Fediverse must not be longer than 500 characters, all of the text in an image must always be transcribed in the alt-text etc.).
This way, I hope that my image posts will stay in compliance with existing image description quality standards for a few years, and when they no longer are, they're so old that nobody demands I upgrade my image descriptions to then-current standards.
tl;dr: "Just do it" doesn't cut it. Just doing it is likely to get you sanctioned because you don't do it well enough. And something is no longer better than nothing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #MastodonCulture