#calckey — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #calckey, aggregated by home.social.
-
CW: Misskey only allows for 512 characters of alt-text which is bad for my image posts; CW: long (over 8,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, character limit meta, content warning meta
Just the other day, I found something out. Something very inconvenient about Misskey and maybe also the Forkeys.
It should be commonly known that Misskey has a local limit of 3,000 characters for posts (which it refers to as "notes"). What is not so well-known is that Misskey has a limit of about 8,000 characters, probably 8,192 or so, for inbound messages, ironically fewer than this post is long. Also, it has a limit of 512 characters for alt-text, both locally and in-bound.
Mastodon has a character limit for in-bound content, too, at least for Note-type objects (not for Article-type objects because it refuses to render them fully and links to the original instead). To my best knowledge, it rejects messages with over 100,000 characters. As for its 1,500-charater limit for alt-text, it enforces that by truncating alt-text that's longer.
Misskey, in contrast, truncates everything that exceeds its limits while still letting it in. If your post is longer than the inbound limit of ca. 8,000, all excess characters are chopped off and thrown away. If your alt-text is longer than 512 characters, all excess characters are chopped off and thrown away.
I don't know which Forkey behaves how in this regard, seeing as all Forkeys I know about have a configurable local post character limit that can be adjusted to well over 8,000. But even if the inbound limit is configurable, too, I don't think any *key admin cranks it over 60,000 or over 70,000 or over 100,000. It's simply unimaginable that someone, anyone, could ever post that much at once if your idea of the Fediverse is pure microblogging.
Also, I don't know what *key users do when they come across a truncated post or what blind or visually-impaired *key users do when they come across a truncated alt-text. Do they even suspect that it's a truncated copy of something that's longer at its source and then go check the source? Either way, it's very inconvenient.
It's especially inconvenient for me. My longest posts by a gigantic margin are image posts with original images. They always have a long image description block in the post itself that tends to be tens of thousands of characters long. It contains highly detailed visual descriptions of all images in the post. It contains all explanations necessary to understand the post, the images and the descriptions. It contains verbatim transcripts of all bits of text within the borders of the image that I can read, no matter whether or not my audience can.
In addition, each image has a shorter description in the alt-text, along with a bit that announces the long description, including where to find it. I even used to explain how to get to that description for Mastodon users for whom the summary and content warning hides the post text, but not the images, depending on which Mastodon version and frontend they use. This alone took up several hundred characters in the alt-text. All in all, I got to a point in which my alt-texts always ended up either at precisely 1,500 characters or just a few characters short.
I myself am not really bound to character limits. I used to post images here on Hubzilla where I have over 16.7 million characters for the post, including all alt-texts. Now I post them on (streams) where I have over 24 million characters. I could theoretically write alt-texts as long as I want to, seeing as, unlike on Mastodon, they aren't separate text fields; instead, they're being woven into the image-embedding markup code in the post text.
Still, I stick to a maximum of 1,500 characters for alt-text to keep Mastodon from truncating it. If you post images into the Fediverse, the main audience for your alt-text is on Mastodon, and most of them don't understand that there's something, anything, out there in the Fediverse that does not work exactly like Mastodon. And 1,500 characters can be tight already.
But if I have to stay within Misskey's limits, I can hardly post images anymore. At least not with appropriate descriptions and explanations.
Since late 2024, I have been working on-and-off on a series of fairly simple avatar portraits or rather their image descriptions. The idea is for the long description to consist of a preamble that starts with a general summary, followed by explanations, then followed by visual descriptions of what all images in the post have in common. Next come the individual descriptions of each image. Each post shall have three or four images with three or four portraits each, all in the same pose, all with only minor differences in outfits, all with a neutral, bright white background.
In addition, of course, each image shall have an alt-text, and none of the alt-texts shall depend on each other.
Now, the problem is that I have to describe three or four individual portraits in each alt-text. I'm actually struggling to squeeze such a description plus the note that announces the long description into 1,500 characters, especially if I want to fulfill Veronica Lewis a.k.a. Veronica With Four Eyes' requirements for outfit descriptions to a tee in the alt-text as well (https://veroniiiica.com/how-to-write-alt-text-for-casual-outfits/, https://veroniiiica.com/writing-image-descriptions-for-red-carpet-outfits/; see also https://veroniiiica.com/how-to-write-alt-text-image-descriptions-visually-impaired/ and https://veroniiiica.com/how-to-create-visual-descriptions/).
But in 512 characters so that even Misskey users won't get a severely truncated version? This is absolutely impossible. Even if I limit the long description announcement to some 100 characters, even if I didn't walk people through how to get to the long description, I'd have fewer than 140 characters on average to describe each individual outfit.
The long description won't fare any better. Currently, the preamble starts with some 14,000 characters of explanations, most of which are necessary to understand the visual descriptions. But when Misskey goes and truncates the post at the 8,000-something mark, Misskey users won't even get to any visual description because all visual descriptions would be chopped off.
What makes matters worse is that the preamble grows the longer, the easier to understand I make it and the less I leave people with unexplained technical or jargon terms which you shouldn't use in image descriptions at all anyway. So the next time I go through it and rewrite it to make it easier to understand, I'll also make it even longer than it already is.
But what if I simply cut all the explanations? For one, I'd leave people to their own devices to understand extremely obscure niche content. They won't. My explanations aren't 14,000 characters long because I've artificially inflated them, but because there is so much to know before you understand the post and the images and the descriptions.
Besides, the visual descriptions alone won't fit into 8,192 characters either. What I currently have is over 5,000 characters of common visual description for all portraits in all images plus about 2,500 characters of individual visual description for the three portraits in the first image. That's over 7,500 characters altogether already. And I still have to describe nine portraits in another three images. The post will end up with some 15,000 characters of visual descriptions unless they grow longer when I simplify them again.
I guess users of Misskey or any Forkey will still have to put up with truncated alt-texts and truncated long descriptions in the future. But my future image posts will contain a paragraph at the beginning that explains that the post and/or the alt-text may be truncated on Misskey and the Forkeys, and that both are uncut at the source. Still, this means that *key users will have to put up with the extra hassle of opening my original post at a source with a quite cumbersome UI. And I've got my doubts that this UI is really accessible.
Unfortunately, this also means that *key users won't get any hashtags along with these posts. But then again, the handling of Identi.ca-style/Friendica-style hashtags with the number sign outside the link is broken on all *keys and will remain so for the foreseeable future.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Iceshrimp-JS #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #A11y #Accessibility -
CW: Misskey only allows for 512 characters of alt-text which is bad for my image posts; CW: long (over 8,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, character limit meta, content warning meta
Just the other day, I found something out. Something very inconvenient about Misskey and maybe also the Forkeys.
It should be commonly known that Misskey has a local limit of 3,000 characters for posts (which it refers to as "notes"). What is not so well-known is that Misskey has a limit of about 8,000 characters, probably 8,192 or so, for inbound messages, ironically fewer than this post is long. Also, it has a limit of 512 characters for alt-text, both locally and in-bound.
Mastodon has a character limit for in-bound content, too, at least for Note-type objects (not for Article-type objects because it refuses to render them fully and links to the original instead). To my best knowledge, it rejects messages with over 100,000 characters. As for its 1,500-charater limit for alt-text, it enforces that by truncating alt-text that's longer.
Misskey, in contrast, truncates everything that exceeds its limits while still letting it in. If your post is longer than the inbound limit of ca. 8,000, all excess characters are chopped off and thrown away. If your alt-text is longer than 512 characters, all excess characters are chopped off and thrown away.
I don't know which Forkey behaves how in this regard, seeing as all Forkeys I know about have a configurable local post character limit that can be adjusted to well over 8,000. But even if the inbound limit is configurable, too, I don't think any *key admin cranks it over 60,000 or over 70,000 or over 100,000. It's simply unimaginable that someone, anyone, could ever post that much at once if your idea of the Fediverse is pure microblogging.
Also, I don't know what *key users do when they come across a truncated post or what blind or visually-impaired *key users do when they come across a truncated alt-text. Do they even suspect that it's a truncated copy of something that's longer at its source and then go check the source? Either way, it's very inconvenient.
It's especially inconvenient for me. My longest posts by a gigantic margin are image posts with original images. They always have a long image description block in the post itself that tends to be tens of thousands of characters long. It contains highly detailed visual descriptions of all images in the post. It contains all explanations necessary to understand the post, the images and the descriptions. It contains verbatim transcripts of all bits of text within the borders of the image that I can read, no matter whether or not my audience can.
In addition, each image has a shorter description in the alt-text, along with a bit that announces the long description, including where to find it. I even used to explain how to get to that description for Mastodon users for whom the summary and content warning hides the post text, but not the images, depending on which Mastodon version and frontend they use. This alone took up several hundred characters in the alt-text. All in all, I got to a point in which my alt-texts always ended up either at precisely 1,500 characters or just a few characters short.
I myself am not really bound to character limits. I used to post images here on Hubzilla where I have over 16.7 million characters for the post, including all alt-texts. Now I post them on (streams) where I have over 24 million characters. I could theoretically write alt-texts as long as I want to, seeing as, unlike on Mastodon, they aren't separate text fields; instead, they're being woven into the image-embedding markup code in the post text.
Still, I stick to a maximum of 1,500 characters for alt-text to keep Mastodon from truncating it. If you post images into the Fediverse, the main audience for your alt-text is on Mastodon, and most of them don't understand that there's something, anything, out there in the Fediverse that does not work exactly like Mastodon. And 1,500 characters can be tight already.
But if I have to stay within Misskey's limits, I can hardly post images anymore. At least not with appropriate descriptions and explanations.
Since late 2024, I have been working on-and-off on a series of fairly simple avatar portraits or rather their image descriptions. The idea is for the long description to consist of a preamble that starts with a general summary, followed by explanations, then followed by visual descriptions of what all images in the post have in common. Next come the individual descriptions of each image. Each post shall have three or four images with three or four portraits each, all in the same pose, all with only minor differences in outfits, all with a neutral, bright white background.
In addition, of course, each image shall have an alt-text, and none of the alt-texts shall depend on each other.
Now, the problem is that I have to describe three or four individual portraits in each alt-text. I'm actually struggling to squeeze such a description plus the note that announces the long description into 1,500 characters, especially if I want to fulfill Veronica Lewis a.k.a. Veronica With Four Eyes' requirements for outfit descriptions to a tee in the alt-text as well (https://veroniiiica.com/how-to-write-alt-text-for-casual-outfits/, https://veroniiiica.com/writing-image-descriptions-for-red-carpet-outfits/; see also https://veroniiiica.com/how-to-write-alt-text-image-descriptions-visually-impaired/ and https://veroniiiica.com/how-to-create-visual-descriptions/).
But in 512 characters so that even Misskey users won't get a severely truncated version? This is absolutely impossible. Even if I limit the long description announcement to some 100 characters, even if I didn't walk people through how to get to the long description, I'd have fewer than 140 characters on average to describe each individual outfit.
The long description won't fare any better. Currently, the preamble starts with some 14,000 characters of explanations, most of which are necessary to understand the visual descriptions. But when Misskey goes and truncates the post at the 8,000-something mark, Misskey users won't even get to any visual description because all visual descriptions would be chopped off.
What makes matters worse is that the preamble grows the longer, the easier to understand I make it and the less I leave people with unexplained technical or jargon terms which you shouldn't use in image descriptions at all anyway. So the next time I go through it and rewrite it to make it easier to understand, I'll also make it even longer than it already is.
But what if I simply cut all the explanations? For one, I'd leave people to their own devices to understand extremely obscure niche content. They won't. My explanations aren't 14,000 characters long because I've artificially inflated them, but because there is so much to know before you understand the post and the images and the descriptions.
Besides, the visual descriptions alone won't fit into 8,192 characters either. What I currently have is over 5,000 characters of common visual description for all portraits in all images plus about 2,500 characters of individual visual description for the three portraits in the first image. That's over 7,500 characters altogether already. And I still have to describe nine portraits in another three images. The post will end up with some 15,000 characters of visual descriptions unless they grow longer when I simplify them again.
I guess users of Misskey or any Forkey will still have to put up with truncated alt-texts and truncated long descriptions in the future. But my future image posts will contain a paragraph at the beginning that explains that the post and/or the alt-text may be truncated on Misskey and the Forkeys, and that both are uncut at the source. Still, this means that *key users will have to put up with the extra hassle of opening my original post at a source with a quite cumbersome UI. And I've got my doubts that this UI is really accessible.
Unfortunately, this also means that *key users won't get any hashtags along with these posts. But then again, the handling of Identi.ca-style/Friendica-style hashtags with the number sign outside the link is broken on all *keys and will remain so for the foreseeable future.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Iceshrimp-JS #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #A11y #Accessibility -
CW: Misskey only allows for 512 characters of alt-text which is bad for my image posts; CW: long (over 8,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, character limit meta, content warning meta
Just the other day, I found something out. Something very inconvenient about Misskey and maybe also the Forkeys.
It should be commonly known that Misskey has a local limit of 3,000 characters for posts (which it refers to as "notes"). What is not so well-known is that Misskey has a limit of about 8,000 characters, probably 8,192 or so, for inbound messages, ironically fewer than this post is long. Also, it has a limit of 512 characters for alt-text, both locally and in-bound.
Mastodon has a character limit for in-bound content, too, at least for Note-type objects (not for Article-type objects because it refuses to render them fully and links to the original instead). To my best knowledge, it rejects messages with over 100,000 characters. As for its 1,500-charater limit for alt-text, it enforces that by truncating alt-text that's longer.
Misskey, in contrast, truncates everything that exceeds its limits while still letting it in. If your post is longer than the inbound limit of ca. 8,000, all excess characters are chopped off and thrown away. If your alt-text is longer than 512 characters, all excess characters are chopped off and thrown away.
I don't know which Forkey behaves how in this regard, seeing as all Forkeys I know about have a configurable local post character limit that can be adjusted to well over 8,000. But even if the inbound limit is configurable, too, I don't think any *key admin cranks it over 60,000 or over 70,000 or over 100,000. It's simply unimaginable that someone, anyone, could ever post that much at once if your idea of the Fediverse is pure microblogging.
Also, I don't know what *key users do when they come across a truncated post or what blind or visually-impaired *key users do when they come across a truncated alt-text. Do they even suspect that it's a truncated copy of something that's longer at its source and then go check the source? Either way, it's very inconvenient.
It's especially inconvenient for me. My longest posts by a gigantic margin are image posts with original images. They always have a long image description block in the post itself that tends to be tens of thousands of characters long. It contains highly detailed visual descriptions of all images in the post. It contains all explanations necessary to understand the post, the images and the descriptions. It contains verbatim transcripts of all bits of text within the borders of the image that I can read, no matter whether or not my audience can.
In addition, each image has a shorter description in the alt-text, along with a bit that announces the long description, including where to find it. I even used to explain how to get to that description for Mastodon users for whom the summary and content warning hides the post text, but not the images, depending on which Mastodon version and frontend they use. This alone took up several hundred characters in the alt-text. All in all, I got to a point in which my alt-texts always ended up either at precisely 1,500 characters or just a few characters short.
I myself am not really bound to character limits. I used to post images here on Hubzilla where I have over 16.7 million characters for the post, including all alt-texts. Now I post them on (streams) where I have over 24 million characters. I could theoretically write alt-texts as long as I want to, seeing as, unlike on Mastodon, they aren't separate text fields; instead, they're being woven into the image-embedding markup code in the post text.
Still, I stick to a maximum of 1,500 characters for alt-text to keep Mastodon from truncating it. If you post images into the Fediverse, the main audience for your alt-text is on Mastodon, and most of them don't understand that there's something, anything, out there in the Fediverse that does not work exactly like Mastodon. And 1,500 characters can be tight already.
But if I have to stay within Misskey's limits, I can hardly post images anymore. At least not with appropriate descriptions and explanations.
Since late 2024, I have been working on-and-off on a series of fairly simple avatar portraits or rather their image descriptions. The idea is for the long description to consist of a preamble that starts with a general summary, followed by explanations, then followed by visual descriptions of what all images in the post have in common. Next come the individual descriptions of each image. Each post shall have three or four images with three or four portraits each, all in the same pose, all with only minor differences in outfits, all with a neutral, bright white background.
In addition, of course, each image shall have an alt-text, and none of the alt-texts shall depend on each other.
Now, the problem is that I have to describe three or four individual portraits in each alt-text. I'm actually struggling to squeeze such a description plus the note that announces the long description into 1,500 characters, especially if I want to fulfill Veronica Lewis a.k.a. Veronica With Four Eyes' requirements for outfit descriptions to a tee in the alt-text as well (https://veroniiiica.com/how-to-write-alt-text-for-casual-outfits/, https://veroniiiica.com/writing-image-descriptions-for-red-carpet-outfits/; see also https://veroniiiica.com/how-to-write-alt-text-image-descriptions-visually-impaired/ and https://veroniiiica.com/how-to-create-visual-descriptions/).
But in 512 characters so that even Misskey users won't get a severely truncated version? This is absolutely impossible. Even if I limit the long description announcement to some 100 characters, even if I didn't walk people through how to get to the long description, I'd have fewer than 140 characters on average to describe each individual outfit.
The long description won't fare any better. Currently, the preamble starts with some 14,000 characters of explanations, most of which are necessary to understand the visual descriptions. But when Misskey goes and truncates the post at the 8,000-something mark, Misskey users won't even get to any visual description because all visual descriptions would be chopped off.
What makes matters worse is that the preamble grows the longer, the easier to understand I make it and the less I leave people with unexplained technical or jargon terms which you shouldn't use in image descriptions at all anyway. So the next time I go through it and rewrite it to make it easier to understand, I'll also make it even longer than it already is.
But what if I simply cut all the explanations? For one, I'd leave people to their own devices to understand extremely obscure niche content. They won't. My explanations aren't 14,000 characters long because I've artificially inflated them, but because there is so much to know before you understand the post and the images and the descriptions.
Besides, the visual descriptions alone won't fit into 8,192 characters either. What I currently have is over 5,000 characters of common visual description for all portraits in all images plus about 2,500 characters of individual visual description for the three portraits in the first image. That's over 7,500 characters altogether already. And I still have to describe nine portraits in another three images. The post will end up with some 15,000 characters of visual descriptions unless they grow longer when I simplify them again.
I guess users of Misskey or any Forkey will still have to put up with truncated alt-texts and truncated long descriptions in the future. But my future image posts will contain a paragraph at the beginning that explains that the post and/or the alt-text may be truncated on Misskey and the Forkeys, and that both are uncut at the source. Still, this means that *key users will have to put up with the extra hassle of opening my original post at a source with a quite cumbersome UI. And I've got my doubts that this UI is really accessible.
Unfortunately, this also means that *key users won't get any hashtags along with these posts. But then again, the handling of Identi.ca-style/Friendica-style hashtags with the number sign outside the link is broken on all *keys and will remain so for the foreseeable future.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Iceshrimp-JS #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #A11y #Accessibility -
CW: Misskey only allows for 512 characters of alt-text which is bad for my image posts; CW: long (over 8,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, character limit meta, content warning meta
Just the other day, I found something out. Something very inconvenient about Misskey and maybe also the Forkeys.
It should be commonly known that Misskey has a local limit of 3,000 characters for posts (which it refers to as "notes"). What is not so well-known is that Misskey has a limit of about 8,000 characters, probably 8,192 or so, for inbound messages, ironically fewer than this post is long. Also, it has a limit of 512 characters for alt-text, both locally and in-bound.
Mastodon has a character limit for in-bound content, too, at least for Note-type objects (not for Article-type objects because it refuses to render them fully and links to the original instead). To my best knowledge, it rejects messages with over 100,000 characters. As for its 1,500-charater limit for alt-text, it enforces that by truncating alt-text that's longer.
Misskey, in contrast, truncates everything that exceeds its limits while still letting it in. If your post is longer than the inbound limit of ca. 8,000, all excess characters are chopped off and thrown away. If your alt-text is longer than 512 characters, all excess characters are chopped off and thrown away.
I don't know which Forkey behaves how in this regard, seeing as all Forkeys I know about have a configurable local post character limit that can be adjusted to well over 8,000. But even if the inbound limit is configurable, too, I don't think any *key admin cranks it over 60,000 or over 70,000 or over 100,000. It's simply unimaginable that someone, anyone, could ever post that much at once if your idea of the Fediverse is pure microblogging.
Also, I don't know what *key users do when they come across a truncated post or what blind or visually-impaired *key users do when they come across a truncated alt-text. Do they even suspect that it's a truncated copy of something that's longer at its source and then go check the source? Either way, it's very inconvenient.
It's especially inconvenient for me. My longest posts by a gigantic margin are image posts with original images. They always have a long image description block in the post itself that tends to be tens of thousands of characters long. It contains highly detailed visual descriptions of all images in the post. It contains all explanations necessary to understand the post, the images and the descriptions. It contains verbatim transcripts of all bits of text within the borders of the image that I can read, no matter whether or not my audience can.
In addition, each image has a shorter description in the alt-text, along with a bit that announces the long description, including where to find it. I even used to explain how to get to that description for Mastodon users for whom the summary and content warning hides the post text, but not the images, depending on which Mastodon version and frontend they use. This alone took up several hundred characters in the alt-text. All in all, I got to a point in which my alt-texts always ended up either at precisely 1,500 characters or just a few characters short.
I myself am not really bound to character limits. I used to post images here on Hubzilla where I have over 16.7 million characters for the post, including all alt-texts. Now I post them on (streams) where I have over 24 million characters. I could theoretically write alt-texts as long as I want to, seeing as, unlike on Mastodon, they aren't separate text fields; instead, they're being woven into the image-embedding markup code in the post text.
Still, I stick to a maximum of 1,500 characters for alt-text to keep Mastodon from truncating it. If you post images into the Fediverse, the main audience for your alt-text is on Mastodon, and most of them don't understand that there's something, anything, out there in the Fediverse that does not work exactly like Mastodon. And 1,500 characters can be tight already.
But if I have to stay within Misskey's limits, I can hardly post images anymore. At least not with appropriate descriptions and explanations.
Since late 2024, I have been working on-and-off on a series of fairly simple avatar portraits or rather their image descriptions. The idea is for the long description to consist of a preamble that starts with a general summary, followed by explanations, then followed by visual descriptions of what all images in the post have in common. Next come the individual descriptions of each image. Each post shall have three or four images with three or four portraits each, all in the same pose, all with only minor differences in outfits, all with a neutral, bright white background.
In addition, of course, each image shall have an alt-text, and none of the alt-texts shall depend on each other.
Now, the problem is that I have to describe three or four individual portraits in each alt-text. I'm actually struggling to squeeze such a description plus the note that announces the long description into 1,500 characters, especially if I want to fulfill Veronica Lewis a.k.a. Veronica With Four Eyes' requirements for outfit descriptions to a tee in the alt-text as well (https://veroniiiica.com/how-to-write-alt-text-for-casual-outfits/, https://veroniiiica.com/writing-image-descriptions-for-red-carpet-outfits/; see also https://veroniiiica.com/how-to-write-alt-text-image-descriptions-visually-impaired/ and https://veroniiiica.com/how-to-create-visual-descriptions/).
But in 512 characters so that even Misskey users won't get a severely truncated version? This is absolutely impossible. Even if I limit the long description announcement to some 100 characters, even if I didn't walk people through how to get to the long description, I'd have fewer than 140 characters on average to describe each individual outfit.
The long description won't fare any better. Currently, the preamble starts with some 14,000 characters of explanations, most of which are necessary to understand the visual descriptions. But when Misskey goes and truncates the post at the 8,000-something mark, Misskey users won't even get to any visual description because all visual descriptions would be chopped off.
What makes matters worse is that the preamble grows the longer, the easier to understand I make it and the less I leave people with unexplained technical or jargon terms which you shouldn't use in image descriptions at all anyway. So the next time I go through it and rewrite it to make it easier to understand, I'll also make it even longer than it already is.
But what if I simply cut all the explanations? For one, I'd leave people to their own devices to understand extremely obscure niche content. They won't. My explanations aren't 14,000 characters long because I've artificially inflated them, but because there is so much to know before you understand the post and the images and the descriptions.
Besides, the visual descriptions alone won't fit into 8,192 characters either. What I currently have is over 5,000 characters of common visual description for all portraits in all images plus about 2,500 characters of individual visual description for the three portraits in the first image. That's over 7,500 characters altogether already. And I still have to describe nine portraits in another three images. The post will end up with some 15,000 characters of visual descriptions unless they grow longer when I simplify them again.
I guess users of Misskey or any Forkey will still have to put up with truncated alt-texts and truncated long descriptions in the future. But my future image posts will contain a paragraph at the beginning that explains that the post and/or the alt-text may be truncated on Misskey and the Forkeys, and that both are uncut at the source. Still, this means that *key users will have to put up with the extra hassle of opening my original post at a source with a quite cumbersome UI. And I've got my doubts that this UI is really accessible.
Unfortunately, this also means that *key users won't get any hashtags along with these posts. But then again, the handling of Identi.ca-style/Friendica-style hashtags with the number sign outside the link is broken on all *keys and will remain so for the foreseeable future.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Iceshrimp-JS #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #A11y #Accessibility -
CW: Misskey only allows for 512 characters of alt-text which is bad for my image posts; CW: long (over 8,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, character limit meta, content warning meta
Just the other day, I found something out. Something very inconvenient about Misskey and maybe also the Forkeys.
It should be commonly known that Misskey has a local limit of 3,000 characters for posts (which it refers to as "notes"). What is not so well-known is that Misskey has a limit of about 8,000 characters, probably 8,192 or so, for inbound messages, ironically fewer than this post is long. Also, it has a limit of 512 characters for alt-text, both locally and in-bound.
Mastodon has a character limit for in-bound content, too, at least for Note-type objects (not for Article-type objects because it refuses to render them fully and links to the original instead). To my best knowledge, it rejects messages with over 100,000 characters. As for its 1,500-charater limit for alt-text, it enforces that by truncating alt-text that's longer.
Misskey, in contrast, truncates everything that exceeds its limits while still letting it in. If your post is longer than the inbound limit of ca. 8,000, all excess characters are chopped off and thrown away. If your alt-text is longer than 512 characters, all excess characters are chopped off and thrown away.
I don't know which Forkey behaves how in this regard, seeing as all Forkeys I know about have a configurable local post character limit that can be adjusted to well over 8,000. But even if the inbound limit is configurable, too, I don't think any *key admin cranks it over 60,000 or over 70,000 or over 100,000. It's simply unimaginable that someone, anyone, could ever post that much at once if your idea of the Fediverse is pure microblogging.
Also, I don't know what *key users do when they come across a truncated post or what blind or visually-impaired *key users do when they come across a truncated alt-text. Do they even suspect that it's a truncated copy of something that's longer at its source and then go check the source? Either way, it's very inconvenient.
It's especially inconvenient for me. My longest posts by a gigantic margin are image posts with original images. They always have a long image description block in the post itself that tends to be tens of thousands of characters long. It contains highly detailed visual descriptions of all images in the post. It contains all explanations necessary to understand the post, the images and the descriptions. It contains verbatim transcripts of all bits of text within the borders of the image that I can read, no matter whether or not my audience can.
In addition, each image has a shorter description in the alt-text, along with a bit that announces the long description, including where to find it. I even used to explain how to get to that description for Mastodon users for whom the summary and content warning hides the post text, but not the images, depending on which Mastodon version and frontend they use. This alone took up several hundred characters in the alt-text. All in all, I got to a point in which my alt-texts always ended up either at precisely 1,500 characters or just a few characters short.
I myself am not really bound to character limits. I used to post images here on Hubzilla where I have over 16.7 million characters for the post, including all alt-texts. Now I post them on (streams) where I have over 24 million characters. I could theoretically write alt-texts as long as I want to, seeing as, unlike on Mastodon, they aren't separate text fields; instead, they're being woven into the image-embedding markup code in the post text.
Still, I stick to a maximum of 1,500 characters for alt-text to keep Mastodon from truncating it. If you post images into the Fediverse, the main audience for your alt-text is on Mastodon, and most of them don't understand that there's something, anything, out there in the Fediverse that does not work exactly like Mastodon. And 1,500 characters can be tight already.
But if I have to stay within Misskey's limits, I can hardly post images anymore. At least not with appropriate descriptions and explanations.
Since late 2024, I have been working on-and-off on a series of fairly simple avatar portraits or rather their image descriptions. The idea is for the long description to consist of a preamble that starts with a general summary, followed by explanations, then followed by visual descriptions of what all images in the post have in common. Next come the individual descriptions of each image. Each post shall have three or four images with three or four portraits each, all in the same pose, all with only minor differences in outfits, all with a neutral, bright white background.
In addition, of course, each image shall have an alt-text, and none of the alt-texts shall depend on each other.
Now, the problem is that I have to describe three or four individual portraits in each alt-text. I'm actually struggling to squeeze such a description plus the note that announces the long description into 1,500 characters, especially if I want to fulfill Veronica Lewis a.k.a. Veronica With Four Eyes' requirements for outfit descriptions to a tee in the alt-text as well (https://veroniiiica.com/how-to-write-alt-text-for-casual-outfits/, https://veroniiiica.com/writing-image-descriptions-for-red-carpet-outfits/; see also https://veroniiiica.com/how-to-write-alt-text-image-descriptions-visually-impaired/ and https://veroniiiica.com/how-to-create-visual-descriptions/).
But in 512 characters so that even Misskey users won't get a severely truncated version? This is absolutely impossible. Even if I limit the long description announcement to some 100 characters, even if I didn't walk people through how to get to the long description, I'd have fewer than 140 characters on average to describe each individual outfit.
The long description won't fare any better. Currently, the preamble starts with some 14,000 characters of explanations, most of which are necessary to understand the visual descriptions. But when Misskey goes and truncates the post at the 8,000-something mark, Misskey users won't even get to any visual description because all visual descriptions would be chopped off.
What makes matters worse is that the preamble grows the longer, the easier to understand I make it and the less I leave people with unexplained technical or jargon terms which you shouldn't use in image descriptions at all anyway. So the next time I go through it and rewrite it to make it easier to understand, I'll also make it even longer than it already is.
But what if I simply cut all the explanations? For one, I'd leave people to their own devices to understand extremely obscure niche content. They won't. My explanations aren't 14,000 characters long because I've artificially inflated them, but because there is so much to know before you understand the post and the images and the descriptions.
Besides, the visual descriptions alone won't fit into 8,192 characters either. What I currently have is over 5,000 characters of common visual description for all portraits in all images plus about 2,500 characters of individual visual description for the three portraits in the first image. That's over 7,500 characters altogether already. And I still have to describe nine portraits in another three images. The post will end up with some 15,000 characters of visual descriptions unless they grow longer when I simplify them again.
I guess users of Misskey or any Forkey will still have to put up with truncated alt-texts and truncated long descriptions in the future. But my future image posts will contain a paragraph at the beginning that explains that the post and/or the alt-text may be truncated on Misskey and the Forkeys, and that both are uncut at the source. Still, this means that *key users will have to put up with the extra hassle of opening my original post at a source with a quite cumbersome UI. And I've got my doubts that this UI is really accessible.
Unfortunately, this also means that *key users won't get any hashtags along with these posts. But then again, the handling of Identi.ca-style/Friendica-style hashtags with the number sign outside the link is broken on all *keys and will remain so for the foreseeable future.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Iceshrimp-JS #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #A11y #Accessibility -
@crossgolf_rebel - kostenlose Kwalitätsposts @「 Jürgen 」:fedi_mastodon: So ist das. Es zeigt aber auch sehr deutlich den Unterschied zwischen dem Fediverse in der westlichen Welt und dem Fediverse in Ostasien.
So, wie bei uns im Westen das Fediverse im wesentlichen Mastodon ist, ist in Ostasien das Fediverse im wesentlichen *key. Die kennen auch Mastodon, aber das spielt da nur eine untergeordnete Rolle. Etwas, was dem Platzhirsch Misskey das Wasser nicht reichen kann, hat da einfach keine Chance.
In Ostasien gibt's im wesentlichen zwei Gründe für Forkeys. Zum einen ist Misskey eigentlich verbuggt bis zum Gehtnichtmehr. Die Bugs sind bekannt. Die Bugs sind in Issues auf GitHub dokumentiert. Aber es passiert einfach nix. Man könnte Pull Requests einreichen, mit denen ein Bug sofort aus der Welt geschafft werden könnte. Die werden aber einfach nicht gemerget.
Was machst du also? Du machst aus deinem Entwicklungsfork, mit dem du deinen Patch gebaut hast, ein eigenes Projekt mit eigenem Namen und haust das als direkte Konkurrenz zu Misskey raus. Also als Soft-Fork, wo du ab und an mal Commits von Misskey rüberholst und bei dir einpflegst. Oder wenn du an Misskeys Weiterentwicklung eh nicht glaubst, gleich als Hard-Fork, wo du letztlich die ganze Weiterentwicklung selbst machst.
Zum anderen gibt's immer wieder Ideen, wie die Usability von *key verbessert oder in andere Richtungen getrieben werden könnte. Das kann man natürlich nicht unbedingt mit Misskey selbst machen. Also macht man dafür eben einen Fork.
Die Featuritis westlicher Art in japanischen und südkoreanischen Forkeys kam doch eigentlich erst richtig auf, als man in Ostasien bemerkte, daß zum einen Misskey im Westen populärer wurde (immer mehr englische Notizen auf Misskey-Instanzen, immer mehr englische Issues auf GitHub, wo früher mal alle japanisch waren, etc.) und zum anderen Misskey im Westen geforkt wurde (ein Blick in die Liste der Forks des Misskey-Repository genügt).
Im Westen sind die Gründe für Forkeys etwas anders gelagert. Erstens wollten vermutlich besonders die ganz frühen westlichen Forkeys die Ästhetik verändern. Ich meine, vor ein paar Jahren hatte Misskey noch diese typische knallbunte Ästhetik von Shibuya und Akihabara und Manga und japanischen Verkaufsautomaten. Die Amis und Europäer wollten eher ein sachlicheres Aussehen haben, das Maid-Café in eine Studentenkneipe umgestalten, ungewohnte Melonenbrause durch gewohnte Cola ersetzen.
Zweitens, wo man schon mal dabei war: Features, Features, Features. Man war beeindruckt davon, was Misskey konnte, was das eigentlich als Standard und Goldstandard geltende Mastodon nicht konnte. Aber da ging noch was, da war noch Luft nach oben. Und weil verschiedene Entwickler verschiedene Vorstellungen hatten, was jetzt ein Forkey an Features haben soll, standen wohl einige Zeit vor allem FoundKey und Calckey in Konkurrenz zueinander.
Zu den Sachen, auf die sie sich einigen konnten, war, daß ein hartgecodetes Zeichenlimit von 3000 genauso Käse ist wie ein hartgecodetes Zeichenlimit von 500 auf Mastodon. Deswegen hat doch so ziemlich jeder Mastodon-Fork, der was auf sich hält, ein konfigurierbares Zeichenlimit. Und jeder Forkey, der was auf sich hält, auch.
Drittens: Bugfixes. Allerdings nicht nur von Misskey-Bugs, die von den Forkeys geerbt wurden, sondern ebenso von Bugs, die mit der Featuritis Einzug gehalten haben. Deswegen war Sharkey ("Hauptsache, erstmal Features") vs. Iceshrimp ("Hauptsache, erstmal Stabilität") das neue FoundKey vs. Calckey.
Viertens, das habe ich noch gar nicht erwähnt: ein nicht cishet-normatives Fediverse. Sogar eine Nische im Fediverse ganz ausdrücklich für Transpersonen, deren serverseitiger Unterbau selbst von Transpersonen entwickelt und gepflegt wird. Warum? Weil der Admin von misskey.io, der größten Misskey-Instanz überhaupt, durch das Shadowbanning entsprechender Begriffe mal eine gewisse Homophobie, Transphobie und generelle Queerphobie impliziert hat. Wohlgemerkt, der Admin von misskey.io, nicht irgendeiner der Entwickler von Misskey. Aber damit stand Misskey als Ganzes und wohl auch die ganze japanisch-südkoreanische Forkey-Szene doof da.
Hajkey hatte ich ja schon erwähnt. Von einer Transfrau entwickelter Forkey für eine von einer Transfrau gegründete Instanz. Noch offensichtlicher geht's fast schon gar nicht mehr: Hajkey war inspiriert von und benannt nach dem IKEA Blåhaj, dem plüschigen Transgender-Wappentier. Und auch Sharkey wurde von trans Instanzadmins angeschoben, um eine Pro-2SLGBTQQIA+-Alternative zu Misskey mit besonderem Fokus auf Transpersonen zu haben, die Misskey selbst in den Schatten stellt. Ich meine, warum ist das Maskottchen von Sharkey ein Anime-Mädchen in einem blauen Haianzug?
Sharkeys Ziel dürfte auch gewesen sein, einen Fediverse-Alleskönner zu bauen. Egal, was man im Fediverse machen will, egal, was man für Features braucht, sie sollten auf jeden Fall auch erhältlich sein von trans Entwicklern und nicht nur von Cishet-Männern. Wohl auch deshalb wurde Sharkey aufgebläht zu einem Featuremonster, das im Rahmen der Möglichkeiten von *key Friendica und sogar Hubzilla Konkurrenz zu machen versucht. Transpersonen sollten anstelle dieser beiden Anwendungen, die praktisch komplett von Cishet-Männern entwickelt und gepflegt werden, mit möglichst wenig Einschränkungen auch Sharkey nutzen können.
Das Problem im Westen ist nur, Entwickler zu finden und zu halten. Wie gesagt, in Fernost dominiert *key alles. Hier im Westen ist *key eine Nische. Hier ist alles Nische, was nicht Mastodon ist. Ein erheblicher Teil der Fediverse-Nutzer kennt nur Mastodon, glaubt gar, das Fediverse sei nur Mastodon. Ein paar mehr glauben, das Fediverse sei nicht viel mehr als Mastodon, PeerTube und Pixelfed. Geschätzt mindestens die Hälfte aller Fediverse-Nutzer glaubt, Mastodon sei die einzige auf Microblogging ausgelegte Anwendung im Fediverse.
Dazu kommt die Konkurrenz. Neben Mastodon gibt's ja nicht nur *key. Auch Pleroma und Akkoma wollen ein Stück vom Kuchen abhaben, und die dürften mindestens so bekannt sein wie *key. Daneben gibt's noch sehr viele weitere Projekte in sehr vielen weiteren Größenordnungen von snac2 über GoToSocial bis Mitra, die alle dasselbe wollen wie Mastodon und die *keys.
Entsprechend verteilen sich dann auch die fähigen Entwickler. Die meisten forken entweder Mastodon, um daraus etwas zu bauen mit Features, die "das Fediverse" dringend haben müßte, die aber schon Misskey längst hat. Nur haben sie von Misskey nie gehört und auch nicht von Pleroma oder Friendica oder sonstwas. Oder sie fangen ihre eigene Microblogging-Anwendung an mit denselben Beweggründen und demselben Basiswissen bzw. Mangel daran. Ich schätze, von denen wissen auch einige bis heute nicht, daß es Misskey und Pleroma gibt. Oder sie bauen irgendwas ganz anderes direkt gegen Mastodon.
Unter denen, die Misskey kennen, gibt's nicht viele fähige Entwickler. Das sieht man ja auch an den Smartphone-Apps: Reine Mastodon-Apps kommen gefühlt im Monatstakt. Aber es hat eine Ewigkeit gedauert, bis es auch nur eine einzige App gab, die direkt auf Misskey und die Forkeys ausgelegt war, geschweige denn stabil und nicht nur auf Japanisch und vielleicht noch Hangul verfügbar. Das heißt auch: Die paar wenigen fähigen Entwickler, die Misskey kennen, sind entweder schon irgendwo eingebunden oder gebrannte Kinder (oder Ostasiaten, die kein Englisch können, was die Kommunikation ziemlich erschweren würde).
Wer also Mitstreiter fürs eigene Projekt sucht, vor allem so vertrauenswürdige, daß die dann auch committen dürfen, wird keine finden. Gleichzeitig ist es aber absoluter Wahnsinn, einen Soft-Fork von Misskey alleine ohne jegliche Hilfe zu pflegen und weiterzuentwickeln, insbesondere, wenn der an Fahrt aufnimmt und von mehr und mehr Leuten genutzt wird. Genau daran ist Firefish letzten Endes eingegangen.
Im Grunde braucht es heutzutage gar nicht mehr diesen Wust an Forkeys, jedenfalls nicht im Westen. Das heißt, im Grunde könnte CherryPick rein technisch die meisten Anforderungen erschlagen, und noch dazu soll es bombenstabil sein. Nur hat man dann etwas, das so aussieht, wie Matcha oder Melonenbrause schmeckt, und wo die meisten Commits, die nicht von Misskey kommen, auf Japanisch oder Hangul beschrieben sind.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #Sharkey #CherryPick #FoundKey #Hajkey -
@「 Jürgen 」:fedi_mastodon: @crossgolf_rebel - kostenlose Kwalitätsposts @Don di Dislessia Soweit ich weiß, war es so (man möge mich wiederum korrigieren; kursiv sind die "Forkeys höheren Grades", die nicht von Misskey geforkt wurden):
- Misskey
Der Ursprung in Japan. - Calckey
Soft-Fork von Misskey mit einigen Extrafeatures.
Entwickler hatte irgendwann keine Zeit/keinen Bock mehr. - Firefish
Fortführung von Calckey unter neuem Management. Wurde aufgrund einer massiven Werbeaktion eines begeisterten Nutzers mit viel Reichweite so populär, daß der Name "Calckey" irgendwann einfach doof war und das ganze Ding eine neue Identität bekam.
Entwickler verschwand irgendwann sang- und klanglos von der Bildfläche. Nach einem halben Jahr stellte sich raus: Entwickler hatte wegen Abschlußarbeit usw. keine Zeit mehr, nicht mal, sich zu verabschieden.
Wurde unter neuer Führung mit neuem Repository und neuer Leuchtturminstanz weitergeführt, aber ohne neue Website. Wurde wieder eingestellt, weil es für eine einzige Entwicklerin viel zuviel war, die ganzen alten Co-Entwickler von Firefish alle zu Iceshrimp gewechselt waren und keine neuen Mitentwickler angeheuert werden konnten. - Iceshrimp
Fork von Firefish von ehemaligen Firefish-Entwicklern. Rebased nach Misskey, weil es auf Firefish nicht weiterging. Erklärtes Ziel war, Stabilität über Calckeys Featuritis zu stellen.
Weil Misskeys Codebase an sich einiges an grundsätzlichen Macken hatte, wurde beschlossen, es ist einfacher, das ganze Zeugs von Grund auf neu zu schreiben, als zu versuchen, das alles auszubügeln. Und bei der Gelegenheit wollte man von JavaScript (TypeScript und Vue.js) weg. Also hat man angefangen, das ganze Ding in C# neu zu schreiben als Iceshrimp.NET. Ziel ist featuremäßige Deckungsgleichheit mit dem bisherigen Iceshrimp und gleichzeitig Anpassung an Mastodon. Iceshrimp.NET ist noch sehr unfertig.
Bei der Gelegenheit wurde das alte Iceshrimp in Iceshrimp-JS umbenannt und in den Wartungsmodus versetzt = gibt keine Weiterentwicklung und keine neuen Features mehr, nur Sicherheitspatches und evtl. Bugfixes. - Catodon
Soft-Fork von Firefish. Ziel war, ein Forkey zu haben, das sich in der Bedienung wie Mastodon anfühlt. Quasi Mastodon-Fassade mit *key-Struktur dahinter. Also ein Forkey für den möglichst leichten Umstieg von Mastodon nach *key.
Wurde, als Firefish endgültig eingestellt wurde und damit die Basis tot war, nach Iceshrimp rebased.
Nachdem Iceshrimp zu Iceshrimp-JS wurde und in den Wartungsmodus ging, hatte Catodon ein Problem: Man kann nicht einfach von etwas, das in TypeScript und Vue.js geschrieben ist, nach etwas rebasen, das in C# geschrieben ist (Iceshrimp.NET). Und zur Weiterentwicklung wäre ein Rebase nötig gewesen, weil man jetzt wieder eine fast tote Basis hatte. Aber nach Misskey wollte man nicht (siehe Hajkey weiter unten), und Sharkey war einerseits zu mächtig und andererseits zu kapriziös.
Inzwischen gehen Catodon die Instanzen ein. Die meisten dürften geschlossen worden sein. - Sharkey
Soft-Fork von Misskey mit dem Ziel, so ziemlich alles, was je für Forkeys an Features entwickelt worden war, in einen einzigen Forkey zu packen und noch mehr obendrauf.
Quasi das Yang zu Iceshrimps Yin. Machte lange den Eindruck, als gingen Features über Zuverlässigkeit. Sharkeys Implementation der Mastodon Client API war schon regelrecht legendär schlecht, und alle hofften auf den Retter, der daherkommt und die Implementation von Grund auf neu schreibt, weil sie als unrettbar im Eimer galt. Inzwischen soll Sharkey seine Zuverlässigkeit im Griff haben, zumindest insofern, wie auch Misskey zuverlässig ist.
Die Entwickler haben eine zweifelhafte Reputation. Unter anderem haben sie Crowdfunding-Gelder für einen Sharkey-Server gesammelt und von dem Geld einen Minecraft-Server aufgezogen, aber keinen Sharkey-Server. Mitunter wird deshalb zum Boykott von Sharkey aufgerufen. - CherryPick
Südkoreanischer Soft-Fork von Misskey. Tatsächlich älter als Sharkey, mindestens von 2021, aber später wurde wohl einiges von Sharkey nach CherryPick portiert. Das Ziel war, einen stabilen und zuverlässigen Forkey zu haben ohne die Macken von Sharkey und sogar ohne die Macken von Misskey, der aber gleichzeitig gut Features hat. Das ist wohl sogar weitestgehend gelungen.
Vom ästhetischen Stil her so ähnlich, wie Misskey früher mal war, also sehr auf den japanischen bzw. südkoreanischen Geschmack ausgelegt: bunt, grell, poppig, genki, kawaii. Alleine das zeigt, daß CherryPick von Misskey geforkt wurde, bevor Misskey gänzlich an den westlichen Geschmack angepaßt wurde.
Unklar, ob es Entwickler hat, die Englisch verstehen bzw. schreiben können; falls nicht, dann als Soft-Fork-Basis ungeeignet. Wäre ohne die Kommunikationsbarriere vermutlich der ultimative *key.
Mein letzter Stand: Bis auf eine Instanz im Großraum Washington, D.C. gibt es CherryPick-Instanzen nur in den Großräumen Tokyo und Seoul. War deshalb lange Zeit im westlichen Fediverse fast unbekannt. - FoundKey
Wohl der erste Forkey, der in PascalCase geschrieben wurde.
Meines Wissens direkter Soft-Fork von Misskey. Wird tatsächlich (oh Wunder) kleckerweise gepflegt, aber nicht für Instanzen mit mehr als 20 Nutzern empfohlen.
Ein paar andere *keys:- Hajkey
Soft-Fork von Calckey, der meines Wissens erst nach Firefish und dann nach Misskey rebased wurde. Wurde exklusiv nur für eine einzige Instanz entwickelt: transfem.social. Inzwischen eingestellt, weil wohl der Aufwand, so einen Wolpertinger nur für eine Instanz zu pflegen (man rebaset nicht mal eben von Firefish nach Misskey), zu groß war. transfem.social wurde entsprechend auf Sharkey umgestellt und ist da jetzt eine der größten Instanzen. - Neko
Soft-Fork von Misskey mit dem Ziel, es tauglich für Docker zu machen. Laut Repository nur für eine einzige Instanz gebaut. Ist nie released worden, was aber Wurscht ist, wenn es eh nur einen Admin als Zielgruppe hatte.git fetchkönnen Releases nämlich piepegal sein. - Meisskey
Japanischer Soft-Fork von Misskey von 2019 (!), der aber lange Zeit der Weiterentwicklung der Basis hinterherhinkte. Wird tatsächlich immer noch weiterentwickelt. - Leisskey
Wiederum japanischer Soft-Fork von Meisskey. Ist seit mindestens 2021 in Entwicklung, seit Februar 2023 aber eine ewige Beta, weil es seit damals keinen Release mehr gegeben hat. Dürfte zu den letzten noch in Entwicklung befindlichen "Forkeys 2. Grades" gehören. - Tanukey
Weiterer japanischer Soft-Fork von Misskey und daher so obskur im Westen, daß man schon die Websuche anstrengen muß, um das Repository zu finden (ist wohl im letzten Oktober von GitHub nach GitLab umgezogen). Noch ein Beispiel für *keys, bei denen selbst das Wissen über ihre Existenz Ostasien kaum je verlassen hat. - Backspacekey
Noch ein ambitionierter, aber eingeschlafener westlicher Misskey-Soft-Fork.
Siehe übrigens auch die Delightful Fediverse Experience: hier und hier.
Verglichen damit ist die Familie von Mistpark bis Forte schon wieder übersichtlich, vor allem, wenn die anderen mehreren Dutzend toten Forkeys mit dazugeholt werden. Immerhin stammt von Mistpark bis Forte über etwa 15 Jahre alles vom selben Schöpfer, der einfach nur sein eigenes Zeug geforkt hat.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #IceshrimpJS #Iceshrimp.NET #Catodon #Sharkey #CherryPick #FoundKey #Hajkey #Neko #Meisskey #Leisskey #Tanukey #Backspacekey - Misskey
-
Misskey und Derivate, steigt ihr da durch?
Ich hab mal versucht herauszufinden wie sich das mit Misskey, Foundkey, Calckey, Firefish, Sharkey, Iceshrimp und Iceshrimp.NET verhält. Gerne korrigieren.
Misskey ist wohl der Ursprung und immer noch sehr aktiv in der Entwicklung. ✅
Foundkey ein früher Fork von Misskey, mittlerweile eingestellt. ❌
Calckey ein Fork von Foundkey, scheinbar auch nicht mehr aktiv weiterentwickelt. ❌
Firefish war dann wohl irgendwann ein neuer Name von Calckey. Wurde ebenfalls 2023 aufgelöst durch den Hauptentwickler. ❌
Iceshrimp war dann wohl wiederum ein Fork von Firefish. Es kommen scheinbar keine neuen Features mehr, da das Team sich auf eine Neuimplementierung mit .NET konzentriert (Iceshrimp.NET). 🟡
Firefish (neu) kurzes Aufbäumen des Firefish Projekts, Seti 2024 keine weiteren Commits mehr im Git Repository. ❌
Sharkey ein Fork des neuen Firefish, wohl das einzige Projekt neben Misskey, das noch aktiv weiterentwickelt wird (Iceshrimp.NET hat keine gemeinsame Codebasis mit Misskey mehr). ✅
Irgendwie schade, dass so viele enthusiastische Entwickler es nicht fertig bringen über eine längere Zeit gemeinsam an einer Variante zu arbeiten 😭.
-
@Robert Frank Wenn man selbst nur Mastodon nutzt, fühlt es sich piepschnurzegal an. Dann nimmt man eh das ganze Fediverse als nur Mastodon wahr und die Unterschiede zwischen Mastodon und Nicht-Mastodon fast überhaupt nicht.
Wenn man selbst aber etwas ganz anderes im Fediverse nutzt als Mastodon, dann ist es immens wichtig.
Ich selbst bin nicht auf Mastodon. Ich bin auf Hubzilla (https://hubzilla.org, https://de.wikipedia.org/wiki/Hubzilla, https://hub.netzgemeinde.eu/item/0a75de76-eb27-4149-b708-f20b2f79d392). Das funktioniert völlig anders als Mastodon, das hat ein völlig anderes Konzept als Mastodon, das wird von Mastodon völlig unabhängig entwickelt. Es hat Features, die auf Mastodon unvorstellbar sind. Noch dazu ist es zehn Monate älter als Mastodon. Es geht sogar zurück auf Friendica, das mehr als fünfeinhalb Jahre älter ist als Mastodon.
Aber wie du mit eigenen Augen sehen kannst, kann ich Mastodon-Tröts nicht nur empfangen, sondern auch von Hubzilla aus kommentieren.
Wenn jemand das komplette Fediverse meint, es aber "Mastodon" nennt, dann meint er mich zwar damit, spricht mich aber nicht an. Ich bin ja nicht auf Mastodon.
Wenn jemand einen meiner Posts oder Kommentare als "Tröt" bezeichnet in der Annahme, ich sei auch auf Mastodon, dann ist beides sachlich falsch.
Wenn jemand sich wünscht, "das Fediverse" möge endlich ein bestimmtes Feature einführen, nur weil Mastodon es nicht hat, dann kann ich mir nur vor den Kopf schlagen. In den allermeisten Fällen hat Hubzilla genau dieses Feature schon zehn Monate länger, als es Mastodon überhaupt gibt. Sehr häufig hat Friendica dieses Feature schon etliche Jahre länger, als es Mastodon überhaupt gibt. Das Fediverse hat dieses Feature also. Mastodon hat es nicht, aber das Fediverse hat es.
Wenn jemand dagegen ist, daß "das Fediverse" ein bestimmtes Feature einführt, dem sei gesagt: Höchstwahrscheinlich hat das Fediverse dieses Feature schon. Mastodon nicht, aber das Fediverse. Denn höchstwahrscheinlich hatten Friendica und Hubzilla es schon immer, also auch wieder länger, als es Mastodon überhaupt gibt.
Am besten war noch der Widerstand gegen Quote-Posts. "Das Fediverse" sollte die auf gar keinen Fall einführen, sagten einige. Der Witz: Pleroma, Akkoma, Misskey, Calckey, Firefish, CherryPick, Sharkey, Iceshrimp, Catodon, GoToSocial, Mitra, Friendica, Hubzilla, (streams), Forte usw., sie alle haben Quote-Posts. Und zwar schon länger, als es diese Debatte auf Mastodon überhaupt gibt. Und sie alle (außer GoToSocial) können widerstandslos jeden, aber auch wirklich jeden Mastodon-Tröt quote-posten.
Oder damals der Widerstand gegen Volltextsuche. Auf gar keinen Fall sollte "das Fediverse" Volltextsuche haben. Nur hatte das Fediverse schon längst Volltextsuche: Friendica war schon im Mai 2010 mit eingebauter Volltextsuche an den Start gegangen.
Ach ja: Zeichenlimits. Wer "Mastodon" und "Fediverse" gleichsetzt, für den hat auch das Fediverse ein festgelegtes Limit von 500 Zeichen. Friendica und Hubzilla hatten aber nie wirklich Zeichenlimits. In deren Kultur kommen auch keine Zeichenlimits vor. Aktuell haben sie übrigens ein "Limit" von über 16,7 Millionen Zeichen. Bis auf Threads hat alles im Fediverse ein sehr viel höheres Zeichenlimit als Mastodon. Entsprechend kriegen Nicht-Mastodon-Nutzer ständig auf den Deckel, wenn sie das angeblich von Gargron für das ganze Fediverse festgeschriebene Limit von 500 Zeichen überschreiten.
Also: Das Fediverse ist nicht nur Mastodon. Das Fediverse war auch nie nur Mastodon. Das Fediverse ist nicht nur ein Twitter-Klon. Das Fediverse hat sehr viel mehr Features als Mastodon. Und das Fediverse hat auch nicht überall dieselbe Kultur und wird sie auch nie haben.
CC: @Knust @Katharina Nocun
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteTröt #QuoteTröts #QuoteBoost #QuoteBoosts #Zeichenlimit #Zeichenlimits #ZeichenlimitMeta #CWZeichenlimitMeta #Fediverse #Mastodon #NichtNurMastodon #Pleroma #Akkoma #Misskey #Calckey #Firefish #CherryPick #Sharkey #Iceshrimp #Catodon #GoToSocial #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #MastodonZentrizität #MastodonNormativität -
@Herr TurTur @crossgolf_rebel - kostenlose Kwalitätsposts @tux0r :openbsd: Die Idee hinter Sharkey war mal, in einen einzigen Forkey quasi alles auf einmal reinzuschmeißen bis hin zur Küchenspüle. Das fiel vor allem auf, als es noch mehr lebendige Forkeys zur Auswahl gab.
Und in der Zeit hatte Sharkey auch noch gewisse Macken, z. B. eine schon legendär unzuverlässige Implementation der Mastodon Client API, wo es hieß, am besten setzt sich einer hin und schreibt die neu. Wer was Zuverlässiges wollte, setzte damals auf Iceshrimp. Sharkey war für wagemutige Spielkinder, die sich an Hubzilla nicht rantrauten.
Inzwischen ist Calckey tot, Firefish ist tot, Iceshrimp-JS ist im Wartungsmodus (Iceshrimp.NET ist derweil noch meilenweit von "fertig" entfernt), Catodon ist auch schon siech, und das nur für eine Instanz gebaute Hajkey ist schon verwest.
CherryPick hat fast nur Server in den Großräumen Tokyo und Seoul und fühlt sich so auf den ostasiatischen Geschmack ausgelegt an wie vor ein paar Jahren noch Misskey selbst. Vielleicht erinnern sich ein paar noch daran, wie Misskey mal den Charme japanischer Verkaufsautomaten hatte.
Und der ganze noch lebende Rest scheint selbst mit Misskeys Entwicklung nicht mithalten zu können, also im Kern veraltet zu sein.
Derweil ist Sharkey wohl inzwischen ziemlich zuverlässig. So ist es zumindest im Westen zum einzigen noch nennenswerten Forkey avanciert.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Sharkey #Calckey #Firefish #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Catodon #Hajkey #CherryPick -
Mikroblogging ist eine Form des Bloggens, bei der kurze Textmitteilungen im Fokus stehen. Alle Beiträge einer Person oder Institution ergeben dann ein #Blog (Kurzform von #Weblog, einer Wortkreuzung aus englisch #Web und #Log für "#Logbuch" oder "#Tagebuch").
Im Fediverse existieren verschiedenen Plattformen, die sich auf diese Form der Veröffentlichung fokussiert haben.
Als Auswahl ein paar bekanntere Systeme gelistet:
➡️ #Mastodon und Varianten wie #Glitch-Soc und #Hometown.
➡️ #Pleroma und #Fork #Akkoma.
➡️ #Misskey und Ableitungen wie #Calckey bzw. #Firefish, #Catodon, #Sharkey, #Iceshrimp.
➡️ #GoToSocial
und weitere!
Wer sich also für das Thema Mikroblogging interessiert, hat im Fediverse durchaus Auswahl.
-
@Chris Alemany🇺🇦🇨🇦🇪🇸 The Mastodon devs are talking as if either the Fediverse is only Mastodon, or the Fediverse as a whole doesn't have quote-posts.
Neither of this is true. The Fediverse has had quote-posts since July 2nd, 2010 when Mistpark (now known as Friendica) was launched. Mastodon toots have been quote-post-able since Mastodon itself was launched, for when Mastodon was launched, it immediately federated with at least two Fediverse server applications that have quote-posts, namely Friendica and Hubzilla, a fork of a fork of Friendica by Friendica's own creator.
Nowadays, at least Pleroma, Akkoma, all other Pleroma forks, Misskey, Calckey, Firefish, Iceshrimp-JS, Iceshrimp.NET, CherryPick, Sharkey, all other Misskey forks, Mitra, Friendica, Hubzilla, (streams) and Forte can quote-post Mastodon toots with no problem.
And Mastodon won't be able to stop them. No, seriously, it won't. Not with a non-standard, proprietary, home-brew opt-in or opt-out switch that doesn't tie into anything that the other Fediverse server apps have. And whatever switch Mastodon is working on will not tie into anything that already exists.
Let me put it this way: Hubzilla has the second-most advanced and fine-grained permissions system in the Fediverse. It goes well beyond most people's imagination. It works on three levels: for the whole channel (that's similar to a Mastodon account), for individual contacts (that's "followers" in Mastodon lingo, but Hubzilla doesn't distinguish between followers and followed), for individual content. (streams) and Forte are the only ones with an even more advanced and fine-grained permissions system.
But even they don't have a quote-post permission setting. And they have permission settings for just about everything. You want reply control in the Fediverse? Hubzilla has reply control, and (streams) and Forte have reply control on steroids. But what they don't have is a quote-posting permission because that's next to impossible to control across the Fediverse even with the most advanced permissions system.
As @Mike Macgirvin ?️ (professional software developer for almost half a century, designer of two Fediverse protocols, creator of Friendica and Hubzilla, inventor of nomadic identity, creator and maintainer of (streams) and Forte) says: The only way to make your posts un-quote-post-able is by not posting in public and not allowing everyone in the Fediverse full access to your posts. Set your "Who can quote" however you want, I'll always be able to quote-post all your public posts with no problem and with no resistance.
So what chance does Mastodon have then? Mastodon which doesn't even know what permissions are? Developed by Eugen Rochko who actually has a history of head-butting with Mike Macgirvin, and who would never take any step towards anything that Mike has ever developed?
I'm commenting from Hubzilla right now, and I'm also on (streams). And I can tell you: If you make any of your posts "un-quote-post-able", this still won't make my Share buttons on Hubzilla and (streams) disappear.
CC: @Stefan Bohacek @FinchHaven sfba
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #Iceshrimp.NET #CherryPick #Sharkey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotePostDebate #QuoteTootDebate -
@PaulaToThePeople It isn't just a matter of consent. Besides, for example, I do have quote-post control here on Hubzilla.
I can give permission to quote-post my posts to- everyone in the Fediverse
- everyone on Hubzilla and (streams)
- everyone on this hub
- approved and unapproved connections
- only approved connections
- only those of my connections whom I explicitly give permission by contact role
- nobody but myself
Over on (streams), I can still give that permission to- everyone in the Fediverse
- all my connections
- only myself + specific connections whom I grant that permission either by permission role or by individual connection settings
It's much more a matter of technology.
Mastodon is about to completely re-invent the wheel with a non-standard, Mastodon-only setting. This setting will only work within Mastodon simply because it probably won't even be documented anywhere, especially not before it's officially rolled out.
There simply is no way that every last instance of Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp, CherryPick, Catodon, Meisskey, Tanukey, Neko, dozens of other Misskey forks, Friendica, Hubzilla, (streams), Forte etc. etc. will have that setting implemented before Mastodon rolls it out so that even the users on mastodon.social are perfectly safe from the first second on.
Besides, @Mike Macgirvin 🖥️, creator of Friendica, Hubzilla, (streams) and Forte and still the only maintainer of the latter two, will never introduce proprietary Mastodon features to them. He'd rather risk (streams) and Forte becoming incompatible with Mastodon. The same goes for @Mario Vavti and @Harald Eilertsen, Hubzilla's main maintainers.
If Mastodon wants to become a perfectly safe haven against unallowed quote-posting, it has only got one choice: It must introduce something like (streams)' and Forte's user agent filter and use it to block just everything that isn't Mastodon. Like, include a hard-coded allowlist that only includes Mastodon plus what little can't quote or quote-post anyway.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #CherryPick #Sharkey #Catodon #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate -
06 - Clips und oder Lesezeichen in Calckey/Firefish
https://tube.tchncs.de/w/j1PHwCJh2nmR36tqkx1RqQ
#Misskey #Calckey #Firefish #Sharkey #IceShrimp #Catodon #Fediverse #FediTip #FediTipp -
@Stefan Bohacek It has partly become a museum already.
Of Mike's projects, only Roadhouse is missing because it never really took off. But the Red Matrix is there, Mistpark is there, Osada is there, Zap is there.
Calckey is still there. Wildebeest is there which was so questionable I've got my doubts it still exists.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Calckey #Wildebeest #Mistpark #Mistpark2020 #Misty #RedMatrix #Osada #Zap #Fediverse -
@volkris The belief that each Fediverse project is a different graphical front-end app for the exact same technological back-end is complete non-sense. It sounds like all Fediverse projects run the self-same back-end Web server technology and just put different Web interfaces or mobile apps on top.
#Firefish, formerly known as #CalcKey, is quite a bit different from #Mastodon. And it's still microblogging based on #ActivityPub.
#Friendica is vastly different from Mastodon, also because its base protocol is #DFRN and not ActivityPub. It has an add-on for ActivityPub connectivity.
#Hubzilla and #Streams are even more different from Mastodon. They're based on two versions of #Zot, and they even have an architecture that's extremely different from all other Fediverse projects, even Friendica included, and that wouldn't even be possible with ActivityPub. -
🥥 I'm not ashamed at all to admit that I'm a #Firefish -- formerly #Calckey -- stan.
Hearing about what's going on there reminds me of walking past the Art Department when I was in school. I was always deeply moved -- blown away, actually -- by the creativity I'd be privileged to see there.
So now that I've buttered you up, can you kindly use your #MarkupMarkdown or whatever to create a #SarcasmFont to help disambiguate some of the confusion created by us snarkmeisters?
K?
TKS! 🥥 -
Es gibt einen Space zur Thematk "Moderation im fediverse" unter dem Projekt "Fediverse Moderationstreff": https://matrix.to/#/!MFQggasVSShIgghfmR:synod.im?via=synod.im&via=matrix.org
:boost_ok: :replyOk:
#Fediverse #Moderation #fediverseModeration #FediverseModerationsTreff #FMT #fedimins #Mastodon #Pleroma #MissKey #Firefish #Hubzilla #Pixelfed #Lemmy #Friendica #PeerTube #Owncast #WriteFreely #Knin #Flohmarkt #Mobilizon #BookWyrm #Funkwhale #Calckey #boostokay #replyok #followerpower #german #english
-
Are you looking for a User Guide to the #Fediverse?
https://thefedi.wiki We have #Mastodon and #Firefish (#calckey) sections live and full of great content.
We're always adding articles, and will be expanding to cover more services.
#theFediWiki #UserGuides -
PSA: QTs are available on some Mastodon servers. Also, they are available on all CalcKey servers.
To find a Mastodon server with them, go to instances.social and look for servers running 4.1.4+glitch.
To find a calckey server, go to https://calckey.online/explore or https://calckey.fediverse.observer/list.
You can create an account on Calckey, test it out, and if you like it, move your entire Mastodon account (followers, follows, posts) over very easily.
#mastodon #calckey #fediverse #activitypub #qts #qt #quotetoots -
#Calckey #July19 #WrongAnswersOnly
What do you think will be the new name of Calckey? (This will help pass the time, I hope.)
What does it mean to you? Also, get silly!
Atomickey - Just to tease Atomicpoet. 😆
Catkey - I mean, the ears are already here.
Monkey - All the ears are going to change! 😲
Schlotzkey - Mmmm. I wanna sammich for some reason.
And key is totally optional!
Chisme - Friend taught me that word a few years ago, cute Spanish word for gossip. 😁 Always thought it'd make an adorable chat product.
Revenge Sleep Procrastination - Still love doing it for y'all. 💜
Catnip - Cause we are all cat girls. Even if only in spirit. Yattai! -
@[email protected] ich hoffe, das bleibt auch nachhaltig.
Leider ist die AFDeppen Partei recht stark bei uns #Es #gibt #NichtNurMastodon #im #Fediverse, #geschrieben #mit #Calckey #calckey_experience -
@[email protected] Mist, dann hast du ja einen Vorsprung...
Ob ich das noch einhole...? #Es #gibt #NichtNurMastodon #im #Fediverse, #geschrieben #mit #Calckey #calckey_experience -
@maegul @Jeff Sikes @Kainoa @Chris Trottier This would have to happen on the server side. And this, in turn, would work the best if it happened directly on the instance servers, and if it was part of the #Fediverse projects themselves.
We've seen what happens when you rely on a third party. It tends to lean towards something centralised, either because someone deliberately only designs a centralised service for it, e.g. #Mastodon full-text search, or because nobody but the devs can be bothered to run an instance, e.g. #Guppe.
Also, decentralised third-party services will have to be connected to Fediverse instances by the admins manually because the admins will have to decide which instance to connect. Many admins won't take that step at all because they've stopped reading the manual the very moment their instance started working reasonably well, and so they don't even know that they have to connect to such a service.
That said, the Fediverse already speaks one common formatting language, and that's #RichText. #CalcKey translates the #Markdown in out-going messages to Rich Text. #Hubzilla translates the #BBcode in out-going messages to Rich Text. #Streams translates Markdown, BBcode and #HTML to Rich Text. And so forth.
Also, translation between message formats will remain half-useless as long as certain projects show a severe lack of capabilities of displaying messages, and this won't change anytime soon, if ever.
Like it or not, #Mastodon fans, but Mastodon is the worst offender. It can't have more than four images in one post, and it can't embed images within the text. All stuff that has been possible on projects older than Mastodon even before there was Mastodon.
On #Hubzilla (and not only there, but just to take one example), I can design any regular message like a blog post:Text block 1
Image 1
Text block 2
Image 2
Text block 3
Image 3
Text block 4
Image 4
Text block 5
Image 5
Text block 6
Image 6
Text block 7
Image 7
Text block 8
Image 8
Text block 9
This is perfectly normal. And this is perfectly legit. #Friendica, Hubzilla and #Streams were deliberately designed to make this possible. And while Hubzilla has an optional extra functionality for long-form articles, Friendica and (streams) only have this one way of long-form posting. So, again, this is normal and legit and intentional.
On Mastodon, however, the very same post looks like this:Text block 1
Text block 2
Text block 3
Text block 4
Text block 5
Text block 6
Text block 7
Text block 8
Text block 9
Image 8 | Image 7
Image 6 | Image 5
The images are ripped out of their context, reversed in their order, and only four even make it into what Mastodon displays.
The only thing a "translator" could possibly do here is put the images in the correct order. Still, only four would make it onto Mastodon timelines due to Mastodon's limitations, only that it'll be the first four instead of the last four. And also due to Mastodon's limitations, they will still end up after the end of the post instead of embedded between text blocks where they belong.
In the opposite direction, from Mastodon to Hubzilla, a "translator" could be a bit more useful. Currently, when a Mastodon toot with multiple images appears on Hubzilla, the images are put ahead of the text and in reverse order. What the "translator" could do (unless Hubzilla introduces that first) is embed the images at the end of the post in "reverse reverse" order. I'd suggest to also resize them (non-destructively; Hubzilla does that by default with its own images) so that four of them can be shown in a 2x2 arrangement just like on Mastodon, but on Hubzilla, that would cost them the alt-text. -
Nachdem es immer noch keine Final Version von #calckey v14 gibt muss ich wohl doch noch mal versuchen mir ein Docker Image davon zu builden.
Hat dies schon mal jemand ausprobiert und hat es geklappt.
Mein letzter Versuch von einigen Wochen hat nur dazu geführt das es nicht gestartet ist.
#docker #v14 #build -
I wrote a little #blog post about my #Calckey complaints - and how I resolved some of them with #CustomCSS. The code is available on the post if you'd like to give it a go.
https://whatwasidoingagain.com/interests/wordpress/improving-calckey-with-custom-css/
#CSS #HTML #UXUI #Fediverse #UserExperience #Design -
@Codex ☯️♈☮ @CynthesisToday I think the #Fediverse is the easiest to understand for those who halfway know their way around computer stuff if you start at the protocol level.
#ActivityPub is a digital communications protocol standard. Like e-mail or RSS or Atom or XMPP or Matrix, for example. Or like #StatusNet or the #Diaspora protocol or #DFRN or #Zot, now known as #Nomad in its latest incarnation.
The server application projects that are based on ActivityPub are different server-side software implementations of the same protocol. Some have more features, some have fewer, some specialise in particular tasks which is possible because ActivityPub is not specialised itself, not a one-trick pony.
Like, for XMPP, you have jabberd and ejabberd and Openfire and Prosody and Tigase. For e-mail, you've got various mail servers and MTAs.
The main difference here is that ActivityPub is so versatile in its capabilities that it can be used for a whole lot of different things. #Mastodon, #Pleroma, #Akkoma, #MissKey, #CalcKey etc. were made for microblogging. But ActivityPub can also be used for actual blogging platforms like #Plume or #WriteFreely, for video streaming like in the cases of #PeerTube and #Owncast, for audio streaming like in the cases of #Funkwhale and #Castopod and for link aggregators/discussion communities like in the cases of #Lemmy and #kbin. Only to name a few examples.
Still, there are enough parts of this protocol fixed so that all these projects, all these implementations of ActivityPub can connect to one another and ideally communicate with one another.
Now, why is all this made so that they can connect to one another?
That's because they all use the same protocol. The alternative would have been to do like Mike MacGirvin did with DFRN for #Mistpark, later #Friendika, today known as #Friendica, and create a whole new protocol from scratch, even though StatusNet was readily available. Well, only that Mike's intention was to federate Friendica with everything that moved, regardless of protocol.
Okay, better comparison: The alternative would have been to do like the four Diaspora* creators and create a whole new protocol from scratch with no intention whatsoever to connect to the outside world.
Well, instead, all those clones of YouTube and Instagram and Reddit and GoodReads and so forth chose ActivityPub. It was a win-win situation: They could use an existing protocol which actually worked for them instead of taking upon themselves designing a whole new protocol first and then their server application on top. And they could expect a wider audience, namely everything else that uses ActivityPub. Two birds, one stone.
Oh, and by the way: Neither the Fediverse nor ActivityPub was designed around Mastodon, nor was ActivityPub designed by Eugen Rochko (Mike Macgirvin did have some saying in it, though, AFAIK), and quite a few Fediverse projects already existed before Mastodon. Pleroma is three and a half weeks older. MissKey is two years older AFAIK. #Hubzilla was forked from Friendica four years before Mastodon came out. This means that Friendica has to be even older: six years older than Mastodon.
None of these projects will ever give in to Mastodon's limitations and reduce their own feature set for the convenience of Mastodon users. Oh, and neither will the projects that came after Mastodon. If something from another Fediverse project doesn't look good on Mastodon, it's Mastodon's problem. -
I just noticed a Custom CSS option in #Calckey's settings (go to /settings/custom-css)!
So I poked around the Page Source in my browser and figured out some #CSS to improve the experience here.
I loathe seeing replies, including the post the reply is to (especially when 'Show replies in timeline' is DISABLED 🤦🏽♂️🤦🏽♂️🤦🏽♂️). I also find avatars in replies to be a bit of a distraction, especially when multiple people are in the discussion.
With CSS I've managed to:
- Hide replies and the post being replied to
- Hide avatars in replies, but not the OP
I also had to add some CSS to show replies in Notifications, otherwise I didn't see replies to my posts.
So far this is HUGE improvement to my experience here. Let's see if I'm less-irritated moving forward.
(I have other complaints but these were the two I was able to resolve quickly with some #customCSS.)
#HTML #Fediverse -
@Dr. Jorge Caballero
Hear me out: 1-click privacy-conscious quoting.
@Dr. Jorge Caballero schrieb:Hear me out: 1-click privacy-conscious quoting.
>Hear me out: 1-click privacy-conscious quoting.
"Hear me out: 1-click privacy-conscious quoting."
«Hear me out: 1-click privacy-conscious quoting.»
(↑ All these were copy-pasted, by the way. But at least the upper two are fully legitimate quotes here. ↑)
I don't want to alarm you, but here on a bone-stock #Hubzilla 8.4 Web interface, I can gleefully circumvent any and all privacy safeguards any #Mastodon fork or any mobile app connected to any Mastodon instance could possibly present to me with absolutely no obstacles. And I have countless ways of quoting. I could #quote anyone.
That's because Hubzilla is neither a Mastodon fork nor an alternate Mastodon interface nor a Mastodon client app. It's a wholly separate project that's almost four years older than Mastodon, based on the #Zot protocol that's five years older than Mastodon and seven years older than #ActivityPub. It federates to Mastodon and everything else based on ActivityPub through an optional built-in connector, but internally, it speaks a language more powerful than ActivityPub.
By the way, the same goes for #Friendica, another separate project that's the direct predecessor of Hubzilla, based on the #DFRN protocol and six years older than Mastodon, as well as #Streams, another separate project that was launched last year as an "indirect" fork of a fork... of Hubzilla, based on the latest incarnation of Zot, now named #Nomad. Unlike Hubzilla, both have ActivityPub on by default.
Now I'm curious whether your privacy safeguards have any effect on other #Fediverse projects based on ActivityPub such as #Mitra, #Pleroma, #Akkoma, #MissKey, #CalcKey or #FoundKey.
#MastodonIsNotTheFediverse -
@Kaity A @Ada While I do appreciate your effort, how much of the Fediverse do you plan this to cover within less than, say, two months?
blahaj.zone?
All #Mastodon instances?
Or all instances of all #Fediverse projects?
The latter, so much I can tell you, will be impossible to achieve. First of all, of course, this would require extensive modification to many Fediverse projects that aren't Mastodon. Keep in mind that there are some projects that are both years older than Mastodon and based on a protocol that is not #ActivityPub.
#Friendica (6 years older than Mastodon) might have to dig deeply into its UI, its underlying #DFRN protocol (8 years older than ActivityPub), of course the ActivityPub connector and maybe actually also all the other connectors, of which Friendica has many. If bad comes to worse, Friendica would have to enforce Mastodon users' quote and interaction limits upon #Diaspora users, and Diaspora* and Mastodon aren't even federated with one another and only touch each other on a few projects that are federated with both.
Second, the development of some projects has slowed down to an almost or actual still-stand. You won't see #Plume integrate everything that you've planned before July. It'd be a miracle to see Plume even roll out a bugfix release until then.
Third, @Mario Vavti and @mike are very unlikely let anyone on Mastodon force them to design #Hubzilla and #Streams, or even the #Zot or #Nomad protocol, in any particular way. It's bad enough that the Mastodon core devs try to bully them into re-designing stuff that's many years older than Mastodon.
By the way, both Hubzilla and (streams) have part of what you want to introduce built in already now. Hubzilla actually had it before Mastodon even existed.
What you're trying to do is
a) re-invent the wheel
b) make your wheel design mandatory for the whole Fediverse
c) force Hubzilla and (streams) to discard their way of handling permissions which is firmly integrated with the Zot/Nomad protocol and its own very detailed and fine-grained permission control, the kind of which even the #CalcKey devs couldn't imagine in their wildest dreams, and which has seen some 11 years of daily operation, and replace it with yours
Fourth, there are still some instances of some projects out there that haven't seen a single update this whole year. Or for over a year. There still seem to be Hubzilla hubs alive that run 5.x or even 4.x while the current version is 8.2, and 8.4 is just around the corner. There are also still instances of the (indirect) Hubzilla forks #Osada and #Zap alive, and both projects have been EOL and discontinued since New Year's Eve. These instances will continue not having what you want the whole Fediverse to have.
Next question: How exactly do you want such limitations to be enforced? Do you simply want to keep offending posts/comments from being created? Or do you actually want to go as far as UI buttons being greyed out or disappearing altogether on the UIs of all Web interfaces of all projects and on all desktop and mobile apps?
In the case of quoting, either will be very difficult to achieve outside of Mastodon, especially on the old #FederatedSocialWeb projects Friendica and Hubzilla and their newest offspring, (streams).
See, when Mastodon will introduce quotes, it'd be a button, and everything else will be hocus-pocus happening in the background. On Friendica and Hubzilla, quotes, just like any kind of text formatting, are done with BBcode which is in the post/comment editor in plain sight and can be edited. In (streams)' case, Markdown and HTML come on top.
There are about a thousand and one ways for me to quote you or anyone else. I'd demonstrate a selection of them, but Mastodon's text formatting limitations won't let me, at least not short of taking a screenshot of both the source code and what it looks like. If you want to keep everyone on Friendica, Hubzilla and (streams) from quoting those who don't want to be quoted with 100% reliability, these three projects would need editors that could catch all possible ways of quoting someone. If you still want them to rule out false positives, it's really approaching impossibility. -
@[email protected] That, and #Mastodon is far from the only #microblogging service of the #Fediverse. You have #Akkoma #GoToSocial, the #keyApps (#Misskey, #Calckey & #Foundkey), #Kibou, #Pleroma, #Rebased, …
Most of which offer more functions than Masto does, and often add fuctions Twitter never had. (… Or have long since removed.) -
-
#Misskey, #Calckey, #Foundkey, #Antennen
Weiß jemand eine Möglichkeit wie man bei den Antennen die Schlüsselwörter als "genaue Phrase" markieren kann?
Im allgemeinen ist das schön. Man sucht "Katze" und er findet auch "KatzeN" und "Katzenspielzeug". Aber bei vielen Sachen ist das einfach nur nervig, insbesondere bei sehr kurzen Wörtern oder Abkürzungen, die auch noch wie Vorsilben sind. Ich sitze da immer und muss echt grübeln, warum ein total unpassender Beitrag bei der Antennensuche auftaucht.
Bisher weiß ich nur die Methode alle möglichen negativen Varianten in den Ausschluss zu packen. Gibt es da etwas einfacheres? -
Hey there, time for an introduction! I’m new to CalcKey (and CalcKey.social in particular), but not that new to the Fediverse, so this will not be my main profile for some time, but I’ll try to see if it can become that.
I’m half-astronomer, half-engineer, although the engineering part has been gaining more relevance with time.
I have worked for several observatories, among them the European Southern Observatory, the Square Kilometre Array Observatory, and since June 2022 the Joint ALMA Observatory.
The Joint ALMA Observatory just went through its 10th anniversary, and is ready now for its major overhaul: the Wideband Sensitivity Upgrade, which will change all the signal chain, including correlation and data processing, to get an huge multiple in speed gains for most projects, and at least a 4 times gain for most.
My role is to supervise the Systems Engineering efforts for all relevant subprojects, to make sure that a successful observatory upgrade is delivered which provides a lot of value to our community.
See you around!
ps. As my profile indicates, most of my activity will, anyway, happen at @[email protected]. At least, for the time being!
#Introduction #ALMA #AtacamaLargeMillimeterArray #AtacamaLargeMillimeterSubmillimeterArray
#JAO #JointAlmaObservatory
#WSU #WidebandSensitivityUpgrade #ESO #EuropeanSouthernObservatory #SKAO #SquareKilometreArrayObservatory #SystemEngineering #SystemsEngineering #Fediverse #Calckey -
Hey there, time for an introduction! I’m new to CalcKey (and CalcKey.social in particular), but not that new to the Fediverse, so this will not be my main profile for some time, but I’ll try to see if it can become that.
I’m half-astronomer, half-engineer, although the engineering part has been gaining more relevance with time.
I have worked for several observatories, among them the European Southern Observatory, the Square Kilometre Array Observatory, and since June 2022 the Joint ALMA Observatory.
The Joint ALMA Observatory just went through its 10th anniversary, and is ready now for its major overhaul: the Wideband Sensitivity Upgrade, which will change all the signal chain, including correlation and data processing, to get an huge multiple in speed gains for most projects, and at least a 4 times gain for most.
My role is to supervise the Systems Engineering efforts for all relevant subprojects, to make sure that a successful observatory upgrade is delivered which provides a lot of value to our community.
See you around!
ps. As my profile indicates, most of my activity will, anyway, happen at @[email protected]. At least, for the time being!
#Introduction #ALMA #AtacamaLargeMillimeterArray #AtacamaLargeMillimeterSubmillimeterArray
#JAO #JointAlmaObservatory
#WSU #WidebandSensitivityUpgrade #ESO #EuropeanSouthernObservatory #SKAO #SquareKilometreArrayObservatory #SystemEngineering #SystemsEngineering #Fediverse #Calckey -
Hi all, happy to join up and check out Calckey. Interests include #music like #everythingeverything #xtc the late great #prince #nothingbutthieves #totallyenormousextinctdinosaurs #gorillaz and a million more. I'm a #videogame enthusiast wallowing in the #psvr2 deep end currently. My background is #publishing and I now work in tech #SaaS #CustomerSuccess roles. (#fedihire me someone already!) Whew! I'm a home chef and author (#tbk #teddybearskitchen) and pet poppa of 3 dogs, 1 cat, and a proud gay husband of my man Sean. Lean left politically and by disposition; #blacklivesmatter and #transrights ...I am a #gadget geek and an #earlyadopter addict a weeeee bit. The #fediverse fascinates. Recent raves about #Calckey lured me to these greener pastures to poke about. Say howdy and let me know something about you!
-
Ooh, Kaiteki now has better feature compatilibity with Calckey (and presumably other fedi apps)
#fedi #kaiteki #Calckey #desktopApps -
#Calckey, does anyone care to explain how Antennas work? I'm seriously confused.
#FediHelp #INeedHelp -
@fastfinge What if I told you that just about the whole Fediverse supports quotes, only Mastodon doesn't?
What if I told you that #MastodonIsNotTheFediverse? What if I told you that I myself am not on Mastodon, although this post of mine has appeared on your timeline?
What if I told you that, in fact, the Fediverse has been around for much longer than Mastodon?
What if I told you that it started in 2008 with something called Laconi.ca, now known as #GNUsocial (#^https://en.wikipedia.org/wiki/GNU_social)
Okay, GNU social doesn't really count as part of today's Fediverse because it doesn't support #ActivityPub. And okay, it wasn't called the Fediverse back then but the #FederatedSocialWeb. But still, the whole concept isn't new. It was not invented by Eugen Rochko.
Still, even today's Fediverse is more than Mastodon and older than Mastodon. And just about everything that isn't Mastodon supports quotes while still being fully federated with Mastodon.
But let me elaborate (warning, this post is over 12 times as long as a toot can possibly be):
#Friendica (#^https://friendi.ca, #^https://en.wikipedia.org/wiki/Friendica, #^https://joinfediverse.wiki/Special:MyLanguage/What_is_Friendica%3F) was launched in July 2010. That was six years before Mastodon. It was created by a guy named Mike Macgirvin as a decentralised, distributed, federated replacement for Facebook. No, not Twitter. Facebook.
From the very beginning, it had many features which Mastodon users keep demanding today. Including quotes. Again, when Mastodon was launched, Friendica had had these features in daily productive use for six years already.
And yet, people don't use quotes to harass others by "stealing" discussions. This is technically impossible on Friendica due to its architecture which is more like Facebook or a blog or a forum and less like Twitter or Mastodon. Threads aren't stand-alone posts floating around the timelines, loosely tied together by increasing numbers of mentions. Instead, they're start-post-and-comments structures. Replies aren't stand-alone posts. Replies are comments firmly tied to one start post by Friendica's internal structure.
Oh, and Friendica doesn't run on ActivityPub. It has its own internal protocol, #DFRN. Still, Friendica quickly created an ActivityPub connector and federated with Mastodon, thus becoming part of the Fediverse. Friendica federates with a whole lot of projects and platforms. In fact, there is a growing number of forums mostly frequented by Mastodon users which run on Friendica, such as FediverseNews.
I myself am on #Hubzilla (#^https://hubzilla.org, #^https://joinfediverse.wiki/Special:MyLanguage/What_is_Hubzilla%3F). It started life in 2012, still four years before Mastodon, as a fork of Friendica, created by Friendica's own inventor. In 2011 already, Mike had conceived an even more powerful protocol named #Zot which comes with features that are outright utterly unimaginable for Mastodon users such as #NomadicIdentity. Hubzilla even had its first stable release before Mastodon was launched.
And Hubzilla still has almost all the features Friendica has with a whole lot more on top. Again, including quotes. Again, yes, before Mastodon refused to have them. And again, yes, without anyone misusing them for harassment.
And again, it's part of the Fediverse and federated with Mastodon. Otherwise you wouldn't be able to read this.
I should also mention that both Friendica and Hubzilla have technical barriers in the way of publicly quoting private or restricted posts, at least with references/a connection to the quoted post. Hubzilla in particular has access rights control on a level you couldn't possibly imagine in your wildest dreams.
And just about everything else in the Fediverse that's microblogging or macroblogging has official, built-in quote support.- #Pleroma (#^https://pleroma.social/, #^https://joinfediverse.wiki/What_is_Pleroma%253F) has quotes. And it's part of the Fediverse and federated with Mastodon.
- #Akkoma (#^https://akkoma.social/), a Pleroma fork, has quotes. And it's part of the Fediverse and federated with Mastodon.
- #MissKey (#^https://misskey-hub.net/en/, #^https://joinfediverse.wiki/What_is_Misskey%253F) has quotes. And it's part of the Fediverse and federated with Mastodon.
- #CalcKey (#^https://calckey.cloud/, #^https://joinfediverse.wiki/What_is_Calckey%3F) has quotes. And it's part of the Fediverse and federated with Mastodon.
- #FoundKey (#^https://akkoma.dev/FoundKeyGang/FoundKey) has quotes. And it's part of the Fediverse and federated with Mastodon.
- #GoToSocial (#^https://docs.gotosocial.org/, #^https://joinfediverse.wiki/What_is_GoToSocial%3F) has quotes. And it's part of the Fediverse and federated with Mastodon.
- #Socialhome (#^https://socialhome.network/) has quotes. And it's part of the Fediverse and federated with Mastodon.
Yes, they're all federated with Mastodon. This means that users of any of these projects, including Friendica and Hubzilla, can read Mastodon posts and quote them in their replies, and these replies, in turn, can be read on Mastodon.
Okay, so the Fediverse has two, three, four... ten projects, and all but Mastodon support quotes, and nowhere are there people demanding the feature be removed due to rampant harassment?
No, these are only the microblogging and macroblogging projects, and only those of the macroblogging projects that aren't primarily for long-form blogging, i.e. that aren't mimicking Medium, that aren't mimicking WordPress, that aren't #Wordpress itself. Yes, there are WordPress blogs in the Fediverse, federated with Mastodon.
In fact, the Fediverse is even much, much bigger than that (#^https://fediverse.party/en/miscellaneous/, #^https://the-federation.info/).
Now go block me for harassing you, for being an ableist swine because I treat blind people equally instead of mollycoddling them wherever possibly, even for being a fascist or just for shattering your worldview into itty bitty pieces. This post of mine stands.
CC @Patrick, the Linux guy so that you know that the Fediverse is more than Mastodon, too
Also CC @Ada @James - #Pleroma (#^https://pleroma.social/, #^https://joinfediverse.wiki/What_is_Pleroma%253F) has quotes. And it's part of the Fediverse and federated with Mastodon.
-
El nou codi de @fediverse obté el llistat més complet possible de servidors del #fedivers consultant el llistat de servidors federats que tenen tots els que donen aquesta informació en les seves #API.
Ara mateix obté aquest llistat des de 8.321 servidors diferents dels programaris #Akkoma, #Akkounfucked, #Bookwyrm, #Calckey, #Ched, #Ecko, #Fedibird, #Friendica, #Gotosocial, #Hometown, #Koyuspace, #Mastodon, #Meisskey, #Misskey, #Pleroma, #Smithereen i #Takahe. -
A fun way to understand the #fediverse: #roleplaying / #immersion!
---
Journal entry #1105
In this entry, I will try to describe how our reality is, in the hopes that our reality can be easily understood.
1. Our universe is called the Fediverse.
2. There is what we call #DarkMatter, it glues everything together preventing the universe from being torn apart. This dark matter is everywhere, and it is through this that communications across the universe is possible, we call this technology #ActivityPub.
3. There are countless of galaxies, some still being born, some already known, like: #Friendica #Calckey #Hubzilla #Rebased #Streams #Pixelfed #Bookwyrm #FunkWhale #PeerTube #WriteAs #Lemmy #GoToSocial and #Mastodon.
4. Each galaxy contains different worlds. Some are flat, some round, some a generational ship, and some wayward worlds dubbed #WanderingEarth. These are the worlds that I've visited so far:
* c.im - the people here believes the world is round, because of this unusual belief, they can say things up to 5,000 characters. This world is in the Mastodon galaxy, where many of the other worlds are flat 500 characters.
* hashi.icu - this world is a generational ship. They travel to different worlds, creating bridges, their motto: ICU (you know, I See You). Oh, be warned, they speak up to 300,000 characters! After all, they have plenty of stories to tell.
* c.wtf - this world was recently founded in the Rebased galaxy. Like their origin world, c.im, they can speak up to 5,000 characters.
* p.lu - the people of c.im are truly explorers. They discovered the PeerTube galaxy and were amazed by the technology there: hosting videos through the peer-to-peer protocol! They immediately established a colony in one of the worlds in the PeerTube galaxy.
* i.calckey.cloud - this is the primary world of the Calckey galaxy, and it is a world filled with clouds. Some think that it means its people are high, well, they are high, they live on (or in?) the clouds after all! However, its people are great calculators, I mean, at calculation. Did I not mention they can speak up to 3,000 characters?
* zotum.net - a “Wandering Earth” in the Hubzilla galaxy. This world is one of the oldest. Rumour has it that it used to be located in the Friendica galaxy. A wandering earth indeed!
Those are only a few of the worlds I have seen for myself. But, there is something far larger than this universe.
You see, my dear reader, the Friendica, Hubzilla, Streams, and #SocialHome galaxies developed technology to communicate with another universe. This universe is called #TheFederation and their communication technology, also based on dark matter, is called #diaspora.
That's not all. It was also discovered that there is another universe. The people in this universe calls it #Jabber and their dark matter based communication technology is called #XMPP. The technology to commmunicate with them is still in experimental stages, only few worlds in the fediverse are brave enough to test this technology.
My tip, if you are a migrant, find any world and start there. Understand the basics of our universe. You can always move to a new world with your social connections, or start all over again, with a fresh identity if you like.
PS
There is this thing called #Twitter, and most migrants are coming from there. It is probably a universe, though based on whispers, it is a #LostWorld floating between universes, in total darkness. I even heard one migrant comment that that world is about to implode.Note: If you are a citizen of the fediverse, please welcome and guide everyone in this #TwitterMigration. They are looking for a new home, and our universe can be confusing for them. If whispers are to be believed, Twitter is but a single world, and ours is a universe.
End of journal entry #1105
---
^_^
(Edit: typos)
-
Hey Calckey! Decided to try out this platform as well, spread out my wings a bit. I like the 3k post limit, neat feature.
#notaprilfoolin #forreal #fediverse #calckey -
@gordoooo_z @PhenomX6 @futurebird @ink8 Whatever Eugen decides at this point it’s irrelevant. He’s pretty much lost his grip over holding the Fediverse brand as secondary to the notion of a fantasy “mastodon network” when he gave that Time Magazine interview two months ago in which the word “Fediverse” appeared not one single time - that caused enormous, untold damages including confusion that remains in the news media and disenfranchisement of large swaths of developers and users alike on not just other platforms, but mastodon instances themselves.
There’s really no such thing as toots anymore, Eugen himself refers to “Posts” and “Quote Posts”, and the submit button in mastodon now says “publish”. The reason #Misskey calls them “notes” is because that’s what they are actually called in #ActivityPub - there are also other types, that other platforms use as well, including “article”, although, instances like #qoto have set the character count for notes at 65535 🙂
It’s been covered in this thread already that Quote Posts are simply beyond the control of mastodon devs, Eugen’s edicts, or local mastodon users or admins, because most other platforms support it and there isn’t anything #mastopub can do about it. In Misskey, users can disallow it, but that only affects other local users, so it’s s moot point (except for silo instances).
There are very few Fediverse platforms that aren’t taking advantage of most things that are possible, for example, #Soapbox now has federated events, and introduced custom emoji reactions like Misskey has, and live chat - Misskey’s traditionally led the way with these federating features with #Calckey going even further.
Some platforms however, intentionally incorporate a leaner set of features; #Smithereen is one example, it doesn’t even sccomodate boosts, which harkens back to #Myspace, #VKontakte (aka, “VK” - not sure I spelled that right), and very early #Faceplant days. #Epicyon has anti-silo capabilities baked in.
#Mitra has #Substack style subscriptions at it’s core. Anyone can subscribe remotely from any Fediverse server instance where the user can receive DMs - and in congruence with privacy concerns that are typically expected for Fediverse implementations, it’s based on #Monero (XMR).
Most platforms also support #Markdown, with Cakckey being perhaps supporting the greatest superset IIRC, including #LaTEX, and #Friendica, being much older than msstodon, has continued to evolve over the past decade and still has support for #BBCode too, and direct links for uploading images for those who prefer to.
I didn’t see any mention of Markdown support when I bothered to look at the mastopub roadmap, yet even on that platform, Quote Posts are all throughout the stream and people boost and reply to them as the time - and, as mentioned earlier, anyone can create a post, simply pasting the link from someone else’s post, and then boost that… Voila! Local #Quote_Post.
mastodon was successful in its arrogance of leveraging some pretty graphics and welcoming verbiage into a brand that Eugen weaponized against virtually all other Fediverse platforms, and now, with all of the fine forks like #Hometown and several newcomers, we’ll soon be seeing hardforking as a result of that hostility.
But not just forks, funding and ambitious development as evidenced by existing and emerging platforms like #Cloudflare’s #Wildebeest, Tumbler, and the very unique, #Django based Takahē Fediverse server that I wrote about here:
https://tallship.writeas.com/takahe-a-new-fediverse-paradigm
Average people are already migrating in larger numbers everyday away from the archaic mastodonian resource hog to other, more capable and promising (and friendlier) platforms elsewhere in the Fediverse that have integrated and fully support #masto_migration, and even ones that don’t (yet) haver that feature.
Unlike other dinosaurs and the eponymous mammal for which Eugen chose the namesake of his #TootSuite product, we shouldn’t expect extinction for his platform, but the apathy and indifference levels are rising, as is the enmity in many sectors of the community for what others perceive as a betrayal (or sellout), and that kind of self-inflicted damage is often difficult to mitigate, with waves of disenchantment reverberating get into the future… Just look at what happened to #SourceForge - it still technically exists, but never recovered after the community betrayal it committed years ago.
And finally, there’s a irony so obvious that’s it’s not even plausible to deny… Eugen subverted the very rudimentary principal that the Fediverse network is ideologically predicated upon - #DeSoc… There’s no question that his goals shifted to that if building a silo for himself, at least to some great degree. Very sad.
An interesting thing about condescending others, you find yourself alone and isolated in an otherwise vibrant, busy world.
#tallship #Takahe #ActivityPub #privacy #community_values #FOSS
⛵
.
-
This is my second #fediverse instance installation, this time with #calckey - so I suppose that I should go ahead and have a second #introduction post.
For those that may - or may not - be curious, my other account is @[email protected]
I'm a #parent to five boys, including a pair of #twins - so you may or may not see some postings of #family related activities around these parts. I have a love of all things #tech or #technology related, whether or not that's a good thing is yet to be determined.
I work in #HigherEducation as what is basically an #ApplicationAdministrator with daily experience in #Oracle and #DataWarehousing while trying to maintain my sanity. Ha.
I like to learn new things and have dabbled in #Lisp and #Clojure and while I am able to use #vim I do find myself veering towards the #emacs camp when I can.
You'll find that I post about a good variety of things, I hope, including #movies, #television, #books and other stuff.