#firefish — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #firefish, aggregated by home.social.
-
Das Fediverse im Stadt-Modell erläutert
Im #Fediverse ist die Rede von Instanzen, die zusammen kommunizieren und gemeinsam das föderierte Universum bilden. Da kommen technische Begriffe ins Spiel wie Server, Software, Protokoll usw. usf. - und Produkte wie #Mastodon, #Friendica, #Pixelfed und viele mehr sowie Protokolle wie #ActivityPub... und viele Details mehr.
Wie kann man sich das vorstellen, wenn wir mal davon ausgehen würden, daß Instanzen Städte auf einem Planeten sind?
Nehmen wir also mal an, eine #Instanz bzw. ein #Server bzw. ein #Knotenpunkt im #Fediversum wäre eine Stadt auf einem Planeten. Inklusive Bevölkerung. Diese Stadt kann auf einem Eigenbau basieren oder sie nutzt einen Bauplan für eine spezielle Art von Stadt. Dieser Bauplan wäre dann eine Serversoftware wie Mastodon oder #Firefish oder eine andere.
Leute können sich in einer bereits gebauten Stadt ansiedeln oder eine eigene Stadt aufbauen. Da viele Baupläne für speziell ausgerichtete Städte frei verfügbar existieren (Open Source!), kann diese neue Gemeinschaft auf Basis eines solchen Bauplans eine neue Stadt errichten. Oder etwas eigenes bauen, weil... und hier kommen wir zum nächsten Punkt.
Die Städte auf diesem Planeten sind durch Wege verbunden. Diese Wege sind genormt, damit die Städte sich untereinander austauschen können und die jeweiligen Stadtverwaltungen wissen, wie sie mit Informationen und Botschaften, die über diese Wege übermittelt werden, umgehen und nicht wie ein Ochs' vorm Berg dastehen. Viele Wege nutzen die Norm "ActivityPub". Dies erlaubt dann auch komplett neue Typen von Städten, sofern diese über standardisierte Wege an vorhandene Städe angeschlossen werden.
Soweit so klar?
Instanzen entsprechen Städten, die #User der Instanzen der jeweiligen Stadtbevölkerung, die #Administration einer Instanz entspricht der Stadtverwaltung einer Stadt, unterschiedliche Arten von #Serversoftware bzw. Baupläne regeln die Art des Stadtaufbaus und Protokolle entsprechen genormten Wegen zwischen Städten.
Was passiert nun, wenn ein Bewohner in Stadt A einer Bewohnerin in Stadt B folgen will? Im Hintergrund wird die Stadtverwaltung von Stadt A tätig und schickt über den Weg (zwischen den Städten) eine Botschaft zu Stadt B. Dort nimmt die Stadtverwaltung von Stadt B den Folgewunsch entgegen und bearbeitet ihn. Akzeptiert die Bewohnerin von Stadt B Folgeanfragen ohne manuelle Überprüfung ihrerseits, kann ihre Stadtverwaltung gleich im Hintergrund eine Bestätigungsbotschaft über den Weg zu Stadt A zurückschicken. Die Stadtverwaltungen der Städte A und B kennen nun die Folgebeziehung zwischen den beiden Bewohnenden und können gewissermaßen einen Vermerk im Stadtarchiv vornehmen. Wenn nun die Bewohnerin in Stadt B einen neuen Beitrag verfaßt, weiß ihre Stadtverwaltung, daß sie eine Botschaft mit diesem Beitrag über die Wegeverbindung zu Stadt A schicken muß, weil dort ein Bewohner Interesse angemeldet hat bzw. folgt. Die Stadtverwaltung von Stadt A weiß auch Bescheid und kann den Beitrag aus Stadt B für ihren Bewohner präsentieren.
Immer noch klar?
Macht dieses Städtegleichnis den Aufbau des föderierten Universums nun verständlicher, ändert es nichts oder wird es noch komplizierter? ;-)
Achso, die Fediverse-Adresse entspricht gewissermaßen dem Namen und der Anschrift der jeweiligen Bewohnenden der Städte. Die Adresse beinhaltet den Namen und die Stadt. Innerhalb einer Stadt reicht der Name aus, aber bei Botschaften zwischen Städten muß Namen und Stadt genannt werden. Und ja, das ist einer Telefonnummer mit Vorwahl nicht unähnlich.
Völlig verwirrt? Oder bestens ins Bild gesetzt?
Viel Spaß im Fediverse!
-
I think you'd like Misskey. Anytime some development here pops up, the source is always Misskey.
I first joined the Fediverse on May 30, 2023, so Firefish was on its way out and buggy at the time, since its last update came before the project was all but abandoned. I'm told that before then, it was fun to use. But nevertheless, it was still Misskey under the hood.
-
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 -
06 - Clips und oder Lesezeichen in Calckey/Firefish
https://tube.tchncs.de/w/j1PHwCJh2nmR36tqkx1RqQ
#Misskey #Calckey #Firefish #Sharkey #IceShrimp #Catodon #Fediverse #FediTip #FediTipp -
👋 Hallo zusammen!
Ich bin Marcel, Baujahr '95, und habe eine Leidenschaft für Fotografie sowie Server-Projekte. Besonders fasziniert mich die Digitalisierung und Optimierung von Prozessen. Auch wenn ich erst mit dem Coden begonnen habe, kriege ich die meisten Dinge zum Laufen. 😄
Nach meiner Registrierung am 1.4.2023 auf @[email protected] habe ich mich jetzt dazu ermutigt, auf Procial umzuziehen. Ich war schon lange ein Fan von Misskey (oder Firefish) und habe endlich eine deutsche Instanz gefunden, die zu mir passt.
Freue mich auf den Austausch mit euch! 🚀
#Fediverse #Misskey #Firefish #ServerLife #Digitalisierung #Fotografie #Docker #TechLife #Coding #OpenSource #Umzug #Photographer #TechCommunity -
#Frage an deutschsprachige #FireFish Nutzer:
DieBeitrag teilenSchaltfläche verdeckt teilweise das Eingabefeld bei neuen #Posts mit mobilen Geräten.
@[email protected] schlägt vor, den Text zu kürzen.
Was meint Ihr wenn das geändert würde aufSenden?
Oder habt ihr einen besseren Vorschlag?
Würde nächste Woche versuchen die Übersetzung anzupassen.
#Useability #Interface #Design -
@[email protected] Did I say that I like #self-hosting? Let me count:
- Alderaan - RPi4 - GravCMS & #Postmarks
- Jakku - RPi4 - #Mastodon
- Corellia - RPi4 - #Pixelfed & #Firefish
- Coruscant - RPi3 - #MagicMirror
- Dantooine - RPi2 - Python bots farm
- Dagobah - RPi3 - Local DNS & ReverseProxy
- Tatooine - RPi4 - #Nextcloud
- Butxaca - RPi1 - Retired Torrent box
- GameBoy - RPiZero - #RetroPie
🥰 -
CozyFish UI - Gitlab → voici la page Gitlab de mes fichiers custom CSS et thèmes pour Firefish :chick_aww:
Les 2 ont été créés pour aller ensemble mais le custom CSS fonctionne normalement très bien avec les autres thèmes par défaut de Firefish (j'utilise les variables de couleurs dans le css)
Vous pouvez me conseiller, me réprimander parceque j'ai mal fait la page gitlab, contribuer (en rendant le code plus propre ou en ajoutant des fonctionnalités), ou partager si le projet vous plaiiit :boost_requested:
#UiUx #UiDesign #Ui #Ux #CustomCSS #Firefish #UserExperience #CSS #Fediverse #Design #Theme #CustomTheme -
olalala fuat que j'aille dormir, je suis retombé dans le rabbit hole de la customisation
j'ai changé totalement de thème en m'inspirant en partie de kwak.cab, jai redesigné les hashtags, mentions et URL et quelques autres trucs d'accessibilité (vrai thème opaque notamment)
j'essaie d'avoir quelque chose de cohérent, lisible et simple
#customCSS #firefish #iceshrimp -
It would be nice, #FireFish where able to store the last reading position of all the timelines and starting at this position after next login or reopen the apps.
Maybe, there is such a #setting, that I'm not found yet?
#Timeline #Start #lastReading #Useability #Kaiteki
@[email protected] @[email protected] -
I wonder when we'll see custom domain #WebFinger in the #Fediverse / #ActivityPub ?
For example, I want to use:
* @-live.youronly.one for my #Streams account
* @-sns.youronly.one for my #Firefish account
* @-photos.youronly.one for my #Pixelfed account
* @-mblog.youronly.one for my #Mastodon account
* @-reading.youronly.one for my #BookWyrm accountIdeally, even if I move to a new host/service, I can use the same WebFinger.
#MycelialWeb #MyceliumNetwork #ActivityPub2 #AP #AP2 #Portability #AccountPortability #Nomadic #NomadicIdentity #SNS #SocialWeb #SocialMedia #SocialNetwork
-
Since this is my #personal #friendica server, I'll add #YetAnotherIntroduction post. 😃
I am what I would consider a pretty boring dad to five kiddos, from Lawrence KS. I'm most definitely #introverted, and in a past life I'd much rather be #reading a good book or playing some #JRPG on whatever system is current.
These days, I can generally be found at home, doing the #WorkFromHome thing as an application #SystemAdministrator dealing with lots of #OracleCloud fun (...not).
Downtime has me learning #clojure, #typescript, #angular, #emacs and basically anything shiny that catches my eye.
I've been #keto for the last few years, doing maintenance mode for most of that time, with no plans to change any time soon. It's a lifestyle for me, not a diet.
I've got a handful of accounts on the #fediverse, one of which is my single user #mastodon instance. I'm trying different things out to see which I prefer most.
@swrogers -- My First Friendica Account
@swrogers -- My Main Friendica Account, and main fedi account
@swrogers -- My personal mastodon instance
@swrogers -- My personal #FireFish instance
@[email protected] -- Over on the official Fire Fish instance
@[email protected] -- Over on Infosec Exchange
@swrogers -- My main image uploading section, on #pixelfed socialI'm sure I've got more fediverse account out there, somewhere...it's not quite a #GottaGetThemAll deal, but it sure does seem like it!
-
One of the most confusing aspects of the #Fediverse for newcomers is how to follow someone. Especially if the person is not on your own server -- it is not immediately obvious.
Here are three simple ways to follow people:
On #Mastodon: https://thefedi.wiki/mastodon/user/following
On #Firefish: https://thefedi.wiki/firefish/user/following
#thefediwiki #userguide -
Nachdem ich ein paar Jahre vorwiegend #Mastodon nutzte, gefällt mir #Firefish immer besser.
Meine #Follower könnte ich zu dem neuen #Account umziehen...aaber Followerzahlen sind hier ja nicht >das< #Kriterium sondern eher die #Qualität des Mitteilens und Austauschens, auch deshalb meine Bitte:
Wer weiterhin mit mir und dem was ich so mache und denke in #Verbindung bleiben möchte, folge mir gern hier:
Würde mich freuen, Euch dort zu sehen ...
-
Custom CSS pour Firefish]
Modifications esthétiques
- Modification des ombres
- Cache la flèche dans les threads (celle pour aller au post du dessus)
- Cache les popups quand on hover un pseudo
- Cache les emojis des pseudos (dans les boosts)
- Cache l'image de fond sur les profils (qd le flou est activé)
- Notification : réglage du padding des icones (boosts, reply, favori, etc) et changement de la couleur des icones de boosts (pour coller avec celle des boosts)
- Changement des icônes de : URL, upload, plugin / extension, copie de lien, boost, reply, post public, non-listé, local et message privé
- Modification des contours des notes
- Modification du label des instances (sur les posts)
- Content warning : typo plus grande, majuscule + couleur et contour pour plus de visibilité
- Boosts : ajout de dégradé et grain pour plus de visibilité, cache la date et style du boost, déplace le texte de boost vers la gauche
- Cache partiellement le post parent d'une réponse
- Cacher les séparateurs de date (dans les feeds)
Modifications de fonctionnalités
- Cache nos propres boosts, réponses et posts dans les feeds
- Cache le bouton boost si une image n'a pas de description
Résolutions de bugs
- Possibilité de redimensionner une zone de texte verticalement
#UiUx #UiDesign #Ui #Ux #CustomCSS #Firefish #UserExperience #CSS #Fediverse #Design -
Toutes mes customs sont sur cette page
Soucis et solutions pour Firefish
Vous y trouverez mes thèmes, codes CSS et les problèmes que je rencontre avec Firefish (expérience, bug, etc)
Si vous avez aussi des soucis ou des solutions, vous pouvez m'envoyer un MP ou répondre à ce post pour que je les ajoute :ablobcat_sip_zoom:
:boost_requested:
#UiUx #UiDesign #Ui #Ux #CustomCSS #Firefish #UserExperience #CSS #Fediverse #Design -
Hoping my Firefish community finds this content useful.
:firefish: Deep Dive - Group Chats :firefish:
TL;DR - Firefish Chat provides some much desired safety guardrails compared to Mastodon. There's some needed polish, but the bones are solid.
#Firefish #Fediverse #DirectMessages -
Conversations, Group chats, Private mentions, Direct messages, Channels - all features on fediverse platforms, but are they the same?
I examined the specifics of Firefish Group Chats and explored the differences between it and other fedi platforms with similar functionality.
-
Imagine being able to curate your own lists of posts, and the option to share that list with anyone on the internet.
#Firefish has the answer, in Clips: https://thefedi.wiki/firefish/user/clips
#theFediWidi #UserGuide -
Found 83 new servers and 140 servers died off since 9 hours ago. Check out the Monthly and Daily Stats by software or server or the entire fediverse.
25,956 servers checked. 12,755,199 Total Users, 2,232,478 Monthly Active Users today vs 2,257,849 yesterday for the entire fediverse.
New #fediverse servers found:
nonprofits.masto.host a #mastodon server from France
mastodon.pandapa.ws a #mastodon server from Private
mastodon.hotmilk.space a #mastodon server from United States
ccf.sh a #lemmy server from United States
wf.sofita.noho.st a #writefreely server from Greece
tenfoot.social a #mastodon server from Private
social.fromabyss.com a #mastodon server from United States
fire9.de a #firefish server from Germany
social.learnaddict.academy a #mastodon server from France
relyma.club a #lemmy server from Private
hexbear.net a #lemmy server from France
mastodon.girondi.net a #mastodon server from Sweden
social.aimeee.site a #firefish server from United States
vunzi.com a #lemmy server from Finland
lemmy.enfugue.ai a #lemmy server from United States
emil.nexus a #firefish server from United States
thehanger.social a #mastodon server from Portugal
firefish.boo a #firefish server from United States
lemmy.kirby.run a #lemmy server from United States
gts.romeov.me a #gotosocial server from United States
drykath.red a #mastodon server from United States
akbkuku.org a #mastodon server from United States
msk.mozc-plasma.tech a #misskey server from Private
mk.mii.gay a #misskey server from Germany
soc.dudenas.lt a #firefish server from Lithuania
osplin.monster a #mastodon server from Finland
pl.teleyal.blog a #pleroma server from Germany
mastodon.tsubame-jnr.f5.si a #mastodon server from Japan
bitl.dev a #microblogpub server from Private
fastcompany.social a #mastodon server from Portugal
from-tw.xyz a #baca server from Japan
lemmy.tigor.web.id a #lemmy server from Private
mastodon.lug.ts.it a #mastodon server from France
a.bnuuy.fyi a #gotosocial server from Netherlands
go.warpspeedtv.com a #owncast server from United States
magpie.depht.com a #pleroma server from Netherlands
social.zop.se a #mastodon server from France
mast.yourautisticlife.com a #mastodon server from United States
ohuton.ippainetai.com a #misskey server from Private
ticker.hostdon.ne.jp a #mastodon server from Singapore
faerie.monster a #mastodon server from Portugal
skree.social a #mastodon server from United States
lemmy.co.nz a #lemmy server from Australia
sumanko.com a #mastodon server from Private
pixelfed.techguy.social a #pixelfed server from United States
embracethevoid.net a #mastodon server from United States
vrch.hostdon.ne.jp a #mastodon server from Japan
yetanother.catin.space a #gotosocial server from Private
smilodon.chatslibres.com a #mastodon server from France
misskey.wichi.jp a #misskey server from Private
un.petitp.eu a #mastodon server from Germany
gtsfeditest.zackboe.hm a #gotosocial server from United States
social.lobster.city a #akkoma server from United States
firefish.keks.club a #firefish server from Germany
live.birdcat.cafe a #owncast server from United States
mi.kimama-lab.net a #misskey server from Private
borderland.tokyo a #mastodon server from Japan
tracyverse.social a #mastodon server from Private
fedi.wondernetwork.com a #mastodon server from France
mastodon.accolade.digital a #mastodon server from United States
takanoriskey.toppu.jp a #misskey server from Japan
furuyoni-misskey.morphball.net a #misskey server from Japan
stream.nocci.xyz a #owncast server from Germany
ferry.pm a #mastodon server from United States
owncast.rabidlogic.net a #owncast server from United States
peertube.shadowfr69.eu a #peertube server from France
cld2a.ains-no-misskey.com a #misskey server from Private
linglings.party a #misskey server from South Korea
social.nltech.fr a #mastodon server from France
social.arediss.com a #mastodon server from France
mellowcodelabs.social a #mastodon server from Portugal
social.aleteoryx.me a #mastodon server from United States
essjax.com a #mastodon server from Portugal
mastodon.gregnilsen.com a #mastodon server from France
ssul.one a #pleroma server from Singapore
uni.vuwuv.com a #akkoma server from Japan
eepy.moe a #firefish server from United States
ff.pikopublishing.page a #firefish server from United Kingdom
eei-misskey.com a #misskey server from Private
7a4.pp.ua a #pleroma server from Ukraine
pickey.net a #misskey server from Japan
stormwaltz.net a #mastodon server from Portugal
zlatex.club a #mastodon server from PortugalDead servers: topia.hostdon.ne.jp
hydrocelestis.com
fed.astar.moe
art.librepunk.club
lemmy.giggly.de
social.plant-based.place
skabel.se
git.nuls.dev
moefan-mastodon.net
social.ralsina.me
ma.zcx.cc
fedi.timmorgner.de
mastodon3.stibma.com
mastodon.hutt.social
roguerevan.com
den6262.hostdon.ne.jp
momoirodouhu.mydns.jp
choirofeyes.social
sns.mzyy94.com
mastodon.bleh.au
not.alazy.dev
toot.kingj.net
s.carltheobesecat.online
misskey.styxem.xyz
lemmy.gsp8181.co.uk
mi.torpedo.works
lemmy.recursed.net
mastodon.suzy.is
lemmy.grygon.com
cit-msky.14kw13.com
diggit.xyz
mastodon.k6qw.com
lemmy.davidbuckley.ca
ucn.social
mastodon.smither.org
m.soopy.moe
blog.optional.page
phoebus.cc
pix.campbellwireless.net
misskey.yeonji.net
lemmy.bulwarkob.com
mastodon.fenix-cantina.com
mastodon.firefly.land
fedi.mpthl.ee
indg.club
lemmy.k6qw.com
mast.liaw.me
lemmy.bayern
lemmy.eldarerathis.com
lemmy.coeus.icu
twit.cryolog.in
gay.fesse.pet
sowhois.gay
pilk.social
f.soopy.moe
valentinekindahot.fr
gts.bmgn.rs
ioc.dev
fedi.somedevfox.ru
md.ggtea.org
misskey.fenix-cantina.com
www.omgwtfbbq1337.de
social.logilab.org
mastodan.infra.enoki.tech
lunsford.xyz
mastodon.miao.dev
linkall.uk
mastodon.fi
gaygeeks.nl
videos.mattwilson.org
tube.frischesicht.de
amicale.net
bslounge.com
gnusocial.wmsci.com
m.iamkonstantin.eu
social.kcseb.digital
pixel.jabbxi.de
estrella.misskey.masato.jp
gnubox.org
masto.reiuji.chat
azunyan.info
mastodon.mindlesstux.com
social.styxem.xyz
loli.exposed
sunspot.icu
forsaken.technology
sad.cab
social.freyachat.eu
pleroma.tcweb.org
fedi.fullvoid.de
navinot.com
elephant.ugrash.org
www.librepunk.club
mastodon.campbellwireless.net
pals.chat
f.tkte.ch
sevvie.ltd
toot.cryolog.in
calckey.geppaku.com
mastodon.cmnr.eu
www.melyanna.net
mstdn.vector1.dev
mastodon.pachamamita.de
social.spainco.net
misfitropolis.club
mstdn.tenjuu.net
pleroma.diyarciftci.xyz
p.lu
calckey.nz
brieseland.de
producers.social
mdx.ggtea.org
ap.wolnespoleczenstwo.org
gts.han.do
pleroma.foxarmy.org
axwax.eu
dyfed.saintnet.tech
kuicker.koogle.sk
mastodon.cyprin.eu
a.soopy.moe
hackers.radio
social.hecker.xyz
theden.gay
friendica.donky.social
hub.adrelien.com
coredump.social
thisis.nosocialnet.work
social.circles.fi
social.pigelet.org
500.social
mastotest.jmessage.org
microblog.heavy.rocks
catholicchurch.social
0xa1.social
modak.boo
baudigital.social
gts.kelbie.scot
mk.paritybit.ca
mstdn.ja1ykl.com
cloudfiction.socialHelp others find a home, send them to fediverse.observer
-
@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. -
#Introduction / #NeuHier / #Pinned / #FireFish
Griaß Eich! Mein Name ist Markus und ich komm aus #Wien, #Österreich.
Dieser 🌟private Account🌟 ist nur für Freunde und Familie gedacht ist, die ich persönlich kenne. Also bitte nicht bös sein, wenn ich Deine Follow-Anfrage nicht annehme 🥺
Neben privatem Shitposting und Herumgesuder treib ich mich auch in den Bereichen #IT #Linux #InformationSecurity #Gaming usw. herum.
Meine öffentlichen #Fotografie Accounts gibt es hier
⤵️⤵️⤵️⤵️⤵️
Silver, Light, and Skin 🔞
#Boudoir / #Aktfotografie / #NudePhotography / #SilverLightAndSkin
@[email protected]
WET-Photo 🎸
#KonzertFotografie / #ConcertPhotography / #wetphoto
@[email protected]
@[email protected]
Alter #Mastodon Account (hierher migriert)
@[email protected]
