home.social

#iceshrimp — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #iceshrimp, aggregated by home.social.

fetched live
  1. Bien c'est fantastique donc ça remarche, mais mon dieu la doc de Iceshrimp n'est plus du tout a jour ...

    NodeJS -> 20 bah non il dit qu'il faut la 22 minimum quand tu tente de lancer Iceshrimp, sauf que quand tu passe à la 22 le build fail, faut donc passer sur la 24
    ​:blobPikaFacepaw:​

    Le
    .service ne fonctionne plus impossible de lancer Iceschrimp avec (et a mon avis c'est la qu'a été mon gros problème à chaque fois en plus de NodeJS).

    Valkey mon cul j'ai réinstaller Redis ça tourne ... ... et de toute façon y a zéro explication sur de quoi comment passer de l'un a l'autre ...

    Bref je suis a jour, Iceshrimp tourne dans un Screen quoi ... en 2026 (le temps que je comprenne pourquoi le service ne fonctionne plus, si j'ai le courage)
    ​:blobPikaGlare:​

    #Iceshrimp

    @kazukyakayashi

  2. Bon la maj de iceshrimp c'est fait sans fail mais ... Iceshrimp ne semble plus rien faire a part Fail sans explication sinon c'est pas marrant.

    août 03 10:20:37 Iceshrimp systemd[1]: Started iceshrimp.service - Iceshrimp daemon.
    août 03 10:20:47 Iceshrimp iceshrimp[6769]: --- Iceshrimp (PID: 6769) ---
    août 03 10:20:47 Iceshrimp iceshrimp[6769]: INFO *        [core boot]        Iceshrimp v2026.5.1, initiali>
    août 03 10:20:47 Iceshrimp iceshrimp[6769]: INFO *        [core boot env]        NODE_ENV: production
    août 03 10:20:47 Iceshrimp iceshrimp[6769]: INFO *        [core boot nodejs]        Version v20.19.2 detec>
    août 03 10:20:47 Iceshrimp iceshrimp[6769]: ERR  *        [core boot nodejs]        At least Node.js v22.2>
    août 03 10:20:47 Iceshrimp iceshrimp[6769]: INFO *        [core]        The process is going to exit with >
    août 03 10:20:48 Iceshrimp systemd[1]: iceshrimp.service: Main process exited, code=exited, status=1/FAILU>
    août 03 10:20:48 Iceshrimp systemd[1]: iceshrimp.service: Failed with result 'exit-code'.
    août 03 10:20:48 Iceshrimp systemd[1]: iceshrimp.service: Consumed 14.809s CPU time, 488.7M memory peak.
    août 03 10:20:48 Iceshrimp systemd[1]: iceshrimp.service: Scheduled restart job, restart counter is at 53.
    août 03 10:20:48 Iceshrimp systemd[1]: Started iceshrimp.service - Iceshrimp daemon.
    

    #Iceshrimp

  3. @Chao-c'
    BTW I had account on identi.ca, which was StatusNet powered (I believe).

    It was. At least until Evan and Erin could no longer justify it running on that janky OStatus protocol. The result was the ActivityPump protocol, the pump.io software and Identi.ca's switch to pump.io with all hands on board.

    Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)

    This reminds me of how the Fediverse is all over the place in terms of programming languages. Everyone has their own Holy Grail.

    Friendica and its descendants are written in PHP. They may not be the fastest (even though what bogged down early Friendica were its heavyweight federation connectors to everywhere, especially the one for Facebook that came in 2011). Mike either discarded or rewrote these when he rewrote Red. But they happily run on a run-of-the-mill LAMP stack.

    Mastodon is written in Ruby on Rails. Hubzilla runs circles around it in terms of performance per account/channel, and that has to say something. The only thing that managed to top this was early diaspora*, written in Ruby on Rails for Mac with MongoDB as the database system.

    The *omas are built in Elixir. Granted, they're utter featherweights, especially considering their features. They're legendary for their low server impact. Then again, Pleroma apparently is spaghetti code straight from hell. Its own devs often don't have a clue where to go look for bugs, much less how to fix them. (Miraculously, the Akkoma devs do manage to get ride of quite a number of them.)

    The *keys are built in TypeScript and Vue.js. I guess one reason why Misskey is infamous for having so many forks and forks of forks is because there are tons of people who can code in JavaScript, the primary mobile programming language.

    Iceshrimp.NET is a still very incomplete "rewrite" of old Iceshrimp in C#. It was largely tackled to get rid of all those nasty bugs inherited from Misskey that even Misskey doesn't manage to get rid of. I've heard quite some outcry: Iceshrimp.NET is a sell-out to Microsoft. I guess whoever uttered that didn't go check who owns TypeScript.

    PieFed is a dead giveaway: Python. And PieFed makes more headlines in the Threadiverse for server politics than for its underlying technology, except that Lemmy pales in comparison.

    GoToSocial is a dead giveaway, too: Go. And it was one of the first Fediverse server applications to not come with a Web UI. Those who use it for a single-user server often don't even bother installing one and use some Mastodon app or other instead. Besides, why drag around a Web UI if there are much better third-party Web UIs than whatever you could whip up?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Iceshrimp #IceshrimpJS #Iceshrimp.NET #PieFed #GoToSocial #PHP #RubyOnRails #Elixir #JavaScript #TypeScript #VueJS #C# #Python #Go
  4. @Chao-c'
    BTW I had account on identi.ca, which was StatusNet powered (I believe).

    It was. At least until Evan and Erin could no longer justify it running on that janky OStatus protocol. The result was the ActivityPump protocol, the pump.io software and Identi.ca's switch to pump.io with all hands on board.

    Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)

    This reminds me of how the Fediverse is all over the place in terms of programming languages. Everyone has their own Holy Grail.

    Friendica and its descendants are written in PHP. They may not be the fastest (even though what bogged down early Friendica were its heavyweight federation connectors to everywhere, especially the one for Facebook that came in 2011). Mike either discarded or rewrote these when he rewrote Red. But they happily run on a run-of-the-mill LAMP stack.

    Mastodon is written in Ruby on Rails. Hubzilla runs circles around it in terms of performance per account/channel, and that has to say something. The only thing that managed to top this was early diaspora*, written in Ruby on Rails for Mac with MongoDB as the database system.

    The *omas are built in Elixir. Granted, they're utter featherweights, especially considering their features. They're legendary for their low server impact. Then again, Pleroma apparently is spaghetti code straight from hell. Its own devs often don't have a clue where to go look for bugs, much less how to fix them. (Miraculously, the Akkoma devs do manage to get ride of quite a number of them.)

    The *keys are built in TypeScript and Vue.js. I guess one reason why Misskey is infamous for having so many forks and forks of forks is because there are tons of people who can code in JavaScript, the primary mobile programming language.

    Iceshrimp.NET is a still very incomplete "rewrite" of old Iceshrimp in C#. It was largely tackled to get rid of all those nasty bugs inherited from Misskey that even Misskey doesn't manage to get rid of. I've heard quite some outcry: Iceshrimp.NET is a sell-out to Microsoft. I guess whoever uttered that didn't go check who owns TypeScript.

    PieFed is a dead giveaway: Python. And PieFed makes more headlines in the Threadiverse for server politics than for its underlying technology, except that Lemmy pales in comparison.

    GoToSocial is a dead giveaway, too: Go. And it was one of the first Fediverse server applications to not come with a Web UI. Those who use it for a single-user server often don't even bother installing one and use some Mastodon app or other instead. Besides, why drag around a Web UI if there are much better third-party Web UIs than whatever you could whip up?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Iceshrimp #IceshrimpJS #Iceshrimp.NET #PieFed #GoToSocial #PHP #RubyOnRails #Elixir #JavaScript #TypeScript #VueJS #C# #Python #Go
  5. @DavidM_yeg @Dennis What more is needed?

    A full visual description of the settings, the people (of course, avoiding their gender and describing their skin tone rather than their race), their outfits, the surroundings?

    The title of the film, including an explanation what this film is, who made it, what it is about, when it was released, who the characters are and who the actors are?

    Regardless of neither of this belonging into the alt-text because information that is neither available in the message text nor plainly visible to sighted users in the image does not belong into the alt-text? Because there are people who cannot access alt-text?

    https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Don(27)t(20)explain(20)things(20)or(20)give(20)other(20)information(20)only(20)in(20)alt-text(21)

    https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Can(20)everyone(20)access(20)alt-text(3f)

    And, pray tell, how is all this supposed to fit in 512 characters or fewer so that Misskey, Calckey, Firefish, Iceshrimp-JS, Sharkey, CherryPick and the other Misskey forks won't discard the alt-text?

    https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/How(20)long(20)can(20)alt-text(20)be(3f)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #Iceshrimp-JS #Sharkey #CherryPick #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
  6. @DavidM_yeg @Dennis What more is needed?

    A full visual description of the settings, the people (of course, avoiding their gender and describing their skin tone rather than their race), their outfits, the surroundings?

    The title of the film, including an explanation what this film is, who made it, what it is about, when it was released, who the characters are and who the actors are?

    Regardless of neither of this belonging into the alt-text because information that is neither available in the message text nor plainly visible to sighted users in the image does not belong into the alt-text? Because there are people who cannot access alt-text?

    https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Don(27)t(20)explain(20)things(20)or(20)give(20)other(20)information(20)only(20)in(20)alt-text(21)

    https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Can(20)everyone(20)access(20)alt-text(3f)

    And, pray tell, how is all this supposed to fit in 512 characters or fewer so that Misskey, Calckey, Firefish, Iceshrimp-JS, Sharkey, CherryPick and the other Misskey forks won't discard the alt-text?

    https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/How(20)long(20)can(20)alt-text(20)be(3f)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #Iceshrimp-JS #Sharkey #CherryPick #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
  7. CW: What the Mastodon overlords are allowed and justified to do, and what the non-Mastodon savages are not; CW: long (over 6,000 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, character limit meta, CW meta
    Yeah, I get it.

    Mastodon and its users rule supreme over the Fediverse. After all, the Fediverse was invented by Gargron. It started when Mastodon started, and everything that isn't Mastodon just latched onto Mastodon and its Fediverse.

    Mastodon users are the only civilised users in the Fediverse, the only ones with something like a culture. The Fediverse culture is Mastodon's culture as defined in the spring of 2022. All those who don't live by Mastodon's culture are uncivilised, uneducated, savage barbarians. And it isn't just the Mastodon users' right and privilege to educate them and shape them into good Mastodon users, it's their duty.

    Even when it turns out that these barbarians aren't even on Mastodon, that they're on something that's very much not Mastodon, they can't possibly have a culture of their own. After all, they don't live by Mastodon's culture, and if it isn't Mastodon's culture, it isn't culture at all. Not even if it predates Mastodon's current culture by over a decade like Friendica's culture does.

    Of course, this also means that when non-Mastodon users come and give Mastodon users unsolicited "advice" or recommend them to use Mastodon in a certain way that goes against Mastodon's culture, the Mastodon users are fully justified to silence them by any means available.

    What this means:


    When a Mastodon user uses "Fediverse" and "Mastodon" mutually synonymously, it's the right thing to do because that's part of Mastodon's culture. And it makes things easier to understand.

    When a non-Mastodon user explains that the Fediverse is not only Mastodon, and that "Fediverse" and "Mastodon" do not mean the same, it's evil and intrusive and deeply disturbing.

    When a Mastodon user refers to any message in the Fediverse as a "toot", it's the right thing to do because that's part of Mastodon's culture.

    When a Misskey or Forkey user talks about "notes", it's irritating. When a Friendica or Hubzilla or (streams) or Forte user distinguishes between "posts" and "comments", it has even less of a place in the Mastodon Fediverse.

    Features that only Mastodon has are actually mandatory for the whole Fediverse. Any Fediverse server software that hasn't got these features implemented in exactly the same way as Mastodon is broken.

    Features in non-Mastodon Fediverse server software that Mastodon doesn't have are wrong and evil and not allowed to be used.

    Mastodon users are allowed, justified and expected to tell non-Mastodon users to limit their posts to no more than 500 characters. It especially disturbs those who refuse to move away from the official Mastodon phone app.

    Non-Mastodon users are not allowed to tell Mastodon users to not cut their long posts into threads.

    Mastodon users are allowed, justified and expected to tell non-Mastodon users to put content warnings into their summary/abstract field.

    Mastodon users are allowed, justified and expected to tell non-Mastodon users to only use their summary/abstract field for content warnings. After all, that's what Gargron invented that field for.

    Non-Mastodon users are not allowed to tell non-Mastodon users that it was Evan Prodromou who invented that field as early as 2008. That he invented it as a summary field. That it was actually a Mastodon user who repurposed that field for CWs in 2017, the year after Mastodon was launched. Gargron only let it pass.

    Non-Mastodon users are not allowed to use that field for anything else than CWs.

    Non-Mastodon users are not allowed to add hashtags instead of CWs so that reader-side CWs can automatically be generated by filters. Even though Mastodon itself has literally introduced this very feature with version 4.0 in October, 2022.

    Mastodon users are allowed, justified and expected to tell non-Mastodon users to not only write alt-texts for all the images they post, but to write them nicely long and detailed. After all, they've got 1,500 characters for alt-texts.

    Misskey and Forkey users are not allowed to tell Mastodon users to limit their alt-texts to no more than 512 characters because that's the maximum that Misskey and the Forkeys accept, and on top of that, due to a bug, they delete all alt-texts longer than that. From a Misskey/Forkey point of view, writing long alt-texts is like not writing any alt-texts at all. But the Misskey/Forkey point of view is invalid in Mastodon's culture.

    Mastodon users are allowed, justified and expected to toot to Lemmy any way they want, and that's the Mastodon way. If it doesn't work properly on Lemmy, then Lemmy is broken.

    Lemmy users, even Lemmy moderators, and other users of Fediverse software that supports groups are not allowed to tell Mastodon users how to post to Lemmy in a way that Lemmy understands.

    Mastodon users are allowed, justified and expected to even tell Lemmy users to limit their "toots" to no more than 500 characters and use hashtags, but not too many of them.

    Lemmy users and even Lemmy moderators are not allowed to tell Mastodon users to stop spamming Lemmy with mentions and with hashtags that don't work on Lemmy anyway, also because both highly irritate the Lemmy users. Almost all of them came straight from Reddit after their third-party apps were killed, and almost none of them have ever been on Twitter or Mastodon.

    Mastodon users and Mastodon admins are allowed and justified to block any and all non-Mastodon servers because they misbehave by Mastodon's standards.

    (streams) and Forte admins are not allowed to block the entirety of Mastodon, all present and future servers, by user agent (which, by the way, they're totally capable of) because it misbehaves by their standards. Mastodon doesn't misbehave, and the Hubzilla/(streams)/Forte standards are all wrong if they differ from Mastodon's standards.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Misskey #Forkey #Forkeys #Iceshrimp #Iceshrimp-JS #Sharkey #CherryPick #Friendica #Hubzilla #Streams #(streams) #Forte #Lemmy #MastodonCulture #FediverseCulture #MastodonCentricity #MastodonNormativity
  8. CW: What the Mastodon overlords are allowed and justified to do, and what the non-Mastodon savages are not; CW: long (over 6,000 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, character limit meta, CW meta
    Yeah, I get it.

    Mastodon and its users rule supreme over the Fediverse. After all, the Fediverse was invented by Gargron. It started when Mastodon started, and everything that isn't Mastodon just latched onto Mastodon and its Fediverse.

    Mastodon users are the only civilised users in the Fediverse, the only ones with something like a culture. The Fediverse culture is Mastodon's culture as defined in the spring of 2022. All those who don't live by Mastodon's culture are uncivilised, uneducated, savage barbarians. And it isn't just the Mastodon users' right and privilege to educate them and shape them into good Mastodon users, it's their duty.

    Even when it turns out that these barbarians aren't even on Mastodon, that they're on something that's very much not Mastodon, they can't possibly have a culture of their own. After all, they don't live by Mastodon's culture, and if it isn't Mastodon's culture, it isn't culture at all. Not even if it predates Mastodon's current culture by over a decade like Friendica's culture does.

    Of course, this also means that when non-Mastodon users come and give Mastodon users unsolicited "advice" or recommend them to use Mastodon in a certain way that goes against Mastodon's culture, the Mastodon users are fully justified to silence them by any means available.

    What this means:


    When a Mastodon user uses "Fediverse" and "Mastodon" mutually synonymously, it's the right thing to do because that's part of Mastodon's culture. And it makes things easier to understand.

    When a non-Mastodon user explains that the Fediverse is not only Mastodon, and that "Fediverse" and "Mastodon" do not mean the same, it's evil and intrusive and deeply disturbing.

    When a Mastodon user refers to any message in the Fediverse as a "toot", it's the right thing to do because that's part of Mastodon's culture.

    When a Misskey or Forkey user talks about "notes", it's irritating. When a Friendica or Hubzilla or (streams) or Forte user distinguishes between "posts" and "comments", it has even less of a place in the Mastodon Fediverse.

    Features that only Mastodon has are actually mandatory for the whole Fediverse. Any Fediverse server software that hasn't got these features implemented in exactly the same way as Mastodon is broken.

    Features in non-Mastodon Fediverse server software that Mastodon doesn't have are wrong and evil and not allowed to be used.

    Mastodon users are allowed, justified and expected to tell non-Mastodon users to limit their posts to no more than 500 characters. It especially disturbs those who refuse to move away from the official Mastodon phone app.

    Non-Mastodon users are not allowed to tell Mastodon users to not cut their long posts into threads.

    Mastodon users are allowed, justified and expected to tell non-Mastodon users to put content warnings into their summary/abstract field.

    Mastodon users are allowed, justified and expected to tell non-Mastodon users to only use their summary/abstract field for content warnings. After all, that's what Gargron invented that field for.

    Non-Mastodon users are not allowed to tell non-Mastodon users that it was Evan Prodromou who invented that field as early as 2008. That he invented it as a summary field. That it was actually a Mastodon user who repurposed that field for CWs in 2017, the year after Mastodon was launched. Gargron only let it pass.

    Non-Mastodon users are not allowed to use that field for anything else than CWs.

    Non-Mastodon users are not allowed to add hashtags instead of CWs so that reader-side CWs can automatically be generated by filters. Even though Mastodon itself has literally introduced this very feature with version 4.0 in October, 2022.

    Mastodon users are allowed, justified and expected to tell non-Mastodon users to not only write alt-texts for all the images they post, but to write them nicely long and detailed. After all, they've got 1,500 characters for alt-texts.

    Misskey and Forkey users are not allowed to tell Mastodon users to limit their alt-texts to no more than 512 characters because that's the maximum that Misskey and the Forkeys accept, and on top of that, due to a bug, they delete all alt-texts longer than that. From a Misskey/Forkey point of view, writing long alt-texts is like not writing any alt-texts at all. But the Misskey/Forkey point of view is invalid in Mastodon's culture.

    Mastodon users are allowed, justified and expected to toot to Lemmy any way they want, and that's the Mastodon way. If it doesn't work properly on Lemmy, then Lemmy is broken.

    Lemmy users, even Lemmy moderators, and other users of Fediverse software that supports groups are not allowed to tell Mastodon users how to post to Lemmy in a way that Lemmy understands.

    Mastodon users are allowed, justified and expected to even tell Lemmy users to limit their "toots" to no more than 500 characters and use hashtags, but not too many of them.

    Lemmy users and even Lemmy moderators are not allowed to tell Mastodon users to stop spamming Lemmy with mentions and with hashtags that don't work on Lemmy anyway, also because both highly irritate the Lemmy users. Almost all of them came straight from Reddit after their third-party apps were killed, and almost none of them have ever been on Twitter or Mastodon.

    Mastodon users and Mastodon admins are allowed and justified to block any and all non-Mastodon servers because they misbehave by Mastodon's standards.

    (streams) and Forte admins are not allowed to block the entirety of Mastodon, all present and future servers, by user agent (which, by the way, they're totally capable of) because it misbehaves by their standards. Mastodon doesn't misbehave, and the Hubzilla/(streams)/Forte standards are all wrong if they differ from Mastodon's standards.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Misskey #Forkey #Forkeys #Iceshrimp #Iceshrimp-JS #Sharkey #CherryPick #Friendica #Hubzilla #Streams #(streams) #Forte #Lemmy #MastodonCulture #FediverseCulture #MastodonCentricity #MastodonNormativity
  9. @Roknrol Here are a few older alt-texts that I've written for original images of my own.

    Digital shaded rendering of the main building of the Universal Campus, a downloadable island location for 3-D virtual worlds based on OpenSimulator. The camera position is about three metres or ten feet above the ground. The camera is tilted slightly upward and rotated slightly to the left from the building's longitudinal axis. The futuristic building is over 200 metres long, stretching far into the distance, and its front is about 50 metres wide. Its structure is mostly textured to resemble brushed stainless steel, and almost everything in-between is grey tinted glass. The main entrance of the building in the middle of the front has two pairs of glass doors. They are surrounded by a massive complex geometrical structure, very roughly reminiscent of a vintage video game spacecraft with the front facing upward. Four huge cylindrical pillars carry the roof end, the outer two of which extend beyond it. All are tilted away from the landing area in front of the building and at the same time outward to the sides. The sides of the building are slightly tilted themselves. In the distance, a large geodesic dome rises from the building. There is a large circular area in front of the main entrance as well as several wide paths. They have light concrete textures, and they are lined with low walls with almost white concrete textures. Furthermore, various shrubs and trees decorate the scenery. A more detailed description including explanations and text transcripts can be found in the post.


    Digital rendering from OSgrid, one of the biggest out of thousands of 3-D virtual worlds based on OpenSimulator. It shows Juno Rowland, a female avatar, standing at the end of a wooden pier with the ocean in the background. The avatar is designed to resemble a woman who is no older than in her 30s. She is slim underneath loose-fitting clothes. She has light to medium-light skin, brown eyes and black hair which is styled as a neck-long bob. She is wearing a black tank top with the logo of the 17th birthday of OSgrid on it, a straight, lower-thigh-length, light-to-medium-light-brown denim miniskirt, a pair of black flat ballet shoes and a golden necklace with the OSgrid logo. The OSgrid logo is made up from five identical parallelograms arranged in a circular, star-like pattern. It is also part of the birthday logo which is mostly two tones of yellowish orange. The writing on the birthday logo reads, from top to bottom, “OSgrid”, “The Open Source Metaverse” and “17th Birthday”. A more detailed description of the image, including explanations, can be found in the post itself. If you are on Mastodon, Misskey or one of their forks, you can find it by opening the summary and content warning which includes, “CW: long (22,270 characters, including 20,377 characters of image descriptions), eye contact”, and then following the actual post text. If you are on Pleroma, Akkoma, another Pleroma fork, Friendica, Hubzilla or (streams), the full description will follow right after the images.


    Digital rendering from OSgrid, one of the biggest out of thousands of 3-D virtual worlds based on OpenSimulator. It shows Juno Rowland, a female avatar, standing at the end of a wooden pier with the ocean in the background. The avatar is designed to resemble a woman who is no older than in her 30s. She is slim underneath loose-fitting clothes. She has light to medium-light skin and black hair which is styled as a neck-long bob. She is wearing a black tank top, a straight, lower-thigh-length, light-to-medium-light-brown denim miniskirt, a pair of black flat ballet shoes and a golden necklace. She is looking at the cover of the Leonard Cohen album Recent Songs on a white easel. The cover is a painting of the musician's face. He is shown to be a middle-aged man with light skin, green eyes and black hair in a black shirt. A hummingbird is drawn hovering above his shoulder to the left. The background is medium blue. Cohen's name and the album title are written in the top corners. A more detailed description of the image, including explanations, can be found in the post itself. If you are on Mastodon, Misskey or one of their forks, you can find it by opening the summary and content warning which includes, “CW: long (22,270 characters, including 20,377 characters of image descriptions), eye contact”, and then following the actual post text. If you are on Pleroma, Akkoma, another Pleroma fork, Friendica, Hubzilla or (streams), the full description will follow right after the images.


    Good? Too long? Still not sufficiently detailed? If the latter, then rest assured: When the alt-text announces an additional, much longer image description in the message text, then there actually is one.

    That is, nowadays, my goal is to limit my alt-texts to a maximum of 512 characters. That's because if a post with a longer alt-text arrives on Misskey or Iceshrimp-JS or Sharkey or another Misskey fork, then the alt-text is deleted without any trace. It will look like there has never been any alt-text to begin with.

    When I post memes, it's usually easier to keep alt-texts shorter. The tricky part is to still have all the text transcripts in the alt-text because I only write one visual description for each of my meme images unless it's based on a virtual world rendering. I do give some explanations in my meme posts, though.

    These two are very recent:

    Image macro, based on a screen capture from the Disney and Pixar animated film Finding Nemo. At the top, there is a white space with a two-line caption: “OSgrid: offline for weeks to come,” and “Owners of other grids, looking at OSgrid residents:”. In the screen capture below, ten seagulls are perched on two mooring lines in the background. An eleventh seagull pokes its head into the image from the bottom right. They all look at the camera. Each one is labelled with the question, “Mine?”


    Image macro, based on a screen capture from the animated film Finding Nemo. At the top, there is a white space with a two-line caption: “Fediverse admin: announces the end of their instance and asks their users to migrate to other instances,” and “Admins of other instances:”. In the screen capture below, ten seagulls are perched on two mooring lines. An eleventh seagull pokes its head into the image from the bottom right. They all look at the camera. Each one is labelled with the question, “Mine?”


    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #Iceshrimp #Iceshrimp-JS #Sharkey #AltText #AltTextMeta #CWAltTextMeta
  10. @Roknrol Here are a few older alt-texts that I've written for original images of my own.

    Digital shaded rendering of the main building of the Universal Campus, a downloadable island location for 3-D virtual worlds based on OpenSimulator. The camera position is about three metres or ten feet above the ground. The camera is tilted slightly upward and rotated slightly to the left from the building's longitudinal axis. The futuristic building is over 200 metres long, stretching far into the distance, and its front is about 50 metres wide. Its structure is mostly textured to resemble brushed stainless steel, and almost everything in-between is grey tinted glass. The main entrance of the building in the middle of the front has two pairs of glass doors. They are surrounded by a massive complex geometrical structure, very roughly reminiscent of a vintage video game spacecraft with the front facing upward. Four huge cylindrical pillars carry the roof end, the outer two of which extend beyond it. All are tilted away from the landing area in front of the building and at the same time outward to the sides. The sides of the building are slightly tilted themselves. In the distance, a large geodesic dome rises from the building. There is a large circular area in front of the main entrance as well as several wide paths. They have light concrete textures, and they are lined with low walls with almost white concrete textures. Furthermore, various shrubs and trees decorate the scenery. A more detailed description including explanations and text transcripts can be found in the post.


    Digital rendering from OSgrid, one of the biggest out of thousands of 3-D virtual worlds based on OpenSimulator. It shows Juno Rowland, a female avatar, standing at the end of a wooden pier with the ocean in the background. The avatar is designed to resemble a woman who is no older than in her 30s. She is slim underneath loose-fitting clothes. She has light to medium-light skin, brown eyes and black hair which is styled as a neck-long bob. She is wearing a black tank top with the logo of the 17th birthday of OSgrid on it, a straight, lower-thigh-length, light-to-medium-light-brown denim miniskirt, a pair of black flat ballet shoes and a golden necklace with the OSgrid logo. The OSgrid logo is made up from five identical parallelograms arranged in a circular, star-like pattern. It is also part of the birthday logo which is mostly two tones of yellowish orange. The writing on the birthday logo reads, from top to bottom, “OSgrid”, “The Open Source Metaverse” and “17th Birthday”. A more detailed description of the image, including explanations, can be found in the post itself. If you are on Mastodon, Misskey or one of their forks, you can find it by opening the summary and content warning which includes, “CW: long (22,270 characters, including 20,377 characters of image descriptions), eye contact”, and then following the actual post text. If you are on Pleroma, Akkoma, another Pleroma fork, Friendica, Hubzilla or (streams), the full description will follow right after the images.


    Digital rendering from OSgrid, one of the biggest out of thousands of 3-D virtual worlds based on OpenSimulator. It shows Juno Rowland, a female avatar, standing at the end of a wooden pier with the ocean in the background. The avatar is designed to resemble a woman who is no older than in her 30s. She is slim underneath loose-fitting clothes. She has light to medium-light skin and black hair which is styled as a neck-long bob. She is wearing a black tank top, a straight, lower-thigh-length, light-to-medium-light-brown denim miniskirt, a pair of black flat ballet shoes and a golden necklace. She is looking at the cover of the Leonard Cohen album Recent Songs on a white easel. The cover is a painting of the musician's face. He is shown to be a middle-aged man with light skin, green eyes and black hair in a black shirt. A hummingbird is drawn hovering above his shoulder to the left. The background is medium blue. Cohen's name and the album title are written in the top corners. A more detailed description of the image, including explanations, can be found in the post itself. If you are on Mastodon, Misskey or one of their forks, you can find it by opening the summary and content warning which includes, “CW: long (22,270 characters, including 20,377 characters of image descriptions), eye contact”, and then following the actual post text. If you are on Pleroma, Akkoma, another Pleroma fork, Friendica, Hubzilla or (streams), the full description will follow right after the images.


    Good? Too long? Still not sufficiently detailed? If the latter, then rest assured: When the alt-text announces an additional, much longer image description in the message text, then there actually is one.

    That is, nowadays, my goal is to limit my alt-texts to a maximum of 512 characters. That's because if a post with a longer alt-text arrives on Misskey or Iceshrimp-JS or Sharkey or another Misskey fork, then the alt-text is deleted without any trace. It will look like there has never been any alt-text to begin with.

    When I post memes, it's usually easier to keep alt-texts shorter. The tricky part is to still have all the text transcripts in the alt-text because I only write one visual description for each of my meme images unless it's based on a virtual world rendering. I do give some explanations in my meme posts, though.

    These two are very recent:

    Image macro, based on a screen capture from the Disney and Pixar animated film Finding Nemo. At the top, there is a white space with a two-line caption: “OSgrid: offline for weeks to come,” and “Owners of other grids, looking at OSgrid residents:”. In the screen capture below, ten seagulls are perched on two mooring lines in the background. An eleventh seagull pokes its head into the image from the bottom right. They all look at the camera. Each one is labelled with the question, “Mine?”


    Image macro, based on a screen capture from the animated film Finding Nemo. At the top, there is a white space with a two-line caption: “Fediverse admin: announces the end of their instance and asks their users to migrate to other instances,” and “Admins of other instances:”. In the screen capture below, ten seagulls are perched on two mooring lines. An eleventh seagull pokes its head into the image from the bottom right. They all look at the camera. Each one is labelled with the question, “Mine?”


    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #Iceshrimp #Iceshrimp-JS #Sharkey #AltText #AltTextMeta #CWAltTextMeta
  11. Today in things I didn't want to figure out: why my #iceshrimp inbox had a giant queue of several thousand statuses, just sitting there, unprocessed. So I didn't figure it out. I just restarted the database and the server and then it processed the queue just fine. Go figure. Computers, amiright? Anyway, if you tooted me and heard nothing back, my server maybe threw it on the floor. Or maybe will process it sometime later, when it's in a better mood. Or maybe I just don't like you and am ignoring your toots. It's probably not that last one. You'd know if it was.
  12. Today in things I didn't want to figure out: why my #iceshrimp inbox had a giant queue of several thousand statuses, just sitting there, unprocessed. So I didn't figure it out. I just restarted the database and the server and then it processed the queue just fine. Go figure. Computers, amiright? Anyway, if you tooted me and heard nothing back, my server maybe threw it on the floor. Or maybe will process it sometime later, when it's in a better mood. Or maybe I just don't like you and am ignoring your toots. It's probably not that last one. You'd know if it was.
  13. ⚠️ Be sure your Fedi site is current. An updated current site is a happy site. 😇

    Mastodon: 4.6.2

    Misskey: 2026.6.0

    GoToSocial: 0.22.0

    Mitra: 5.6.0

    Iceshrimp: 2026.5.1

    Iceshrimp.NET: 2026.1.1-beta

    PeerTube: 8.2.1

    Owncast: 0.2.5

    Loops: 1.0.0-beta.12

    PixelFed: 0.12.7

    FunkWhale: 2.0.4

    Lemmy: 0.19.19

    Mbin: 1.10.0

    PieFed: 1.6.27

    Pleroma: 2.10

    Akkoma: 3.19.0 (2026.05)

    Sharkey: 2025.4.7

    #Fediverse #ActivityPub #Mastodon #Misskey #GoToSocial #Mitra #IceShrimp #PeerTube #OwnCast #Loops #PixelFed #FunkWhale #Lemmy #Mbin #PieFed #Pleroma #Akkoma #Sharkey

  14. ⚠️ Be sure your Fedi site is current. An updated current site is a happy site. 😇

    Mastodon: 4.6.2

    Misskey: 2026.6.0

    GoToSocial: 0.22.0

    Mitra: 5.6.0

    Iceshrimp: 2026.5.1

    Iceshrimp.NET: 2026.1.1-beta

    PeerTube: 8.2.1

    Owncast: 0.2.5

    Loops: 1.0.0-beta.12

    PixelFed: 0.12.7

    FunkWhale: 2.0.4

    Lemmy: 0.19.19

    Mbin: 1.10.0

    PieFed: 1.6.27

    Pleroma: 2.10

    Akkoma: 3.19.0 (2026.05)

    Sharkey: 2025.4.7

    #Fediverse #ActivityPub #Mastodon #Misskey #GoToSocial #Mitra #IceShrimp #PeerTube #OwnCast #Loops #PixelFed #FunkWhale #Lemmy #Mbin #PieFed #Pleroma #Akkoma #Sharkey

  15. Bon petit constat :

    - Iceshrimp : trop lourd niveau RAM (3,50go et il en faut au moins 4 pour installer/mettre à jour), trop chiant à maintenir (toujours impossible de maj mon instance ...), la réécriture n'est "toujours" pas prête, pas de scrap pour aller chercher les réponses aux posts des autres instances, pareil pour les profils. Le drive c'est cool le gain de place surtout si comme moi on aime les GIF et ça n'existe nul par ailleurs (outre Misskey et donc ses forks). Déménager semble complètement "péter", fonctionne qu'a moitier ... joie

    - Hollo : trop lourd aussi en RAM (2,50go et pour le moment il faut au minimum 3go pour mettre à jour la chose), et toujours pas de client web avec support des réactions (coucou phanpy, réactions uniquement en lecture) ... pourtant ça récupère les info des instances distante sur les post et les profils.

    - Mitra : ultra léger, paquet debian, bon j'aime pas trop le coté cryptomonaie mais why not vu que tu peux faire payer pour du contenu (pour celles et ceux que ça interesse), mais pas de scrap pour aller chercher les réponses aux posts des autres instances, pareil pour les profils. Client web de base sympa mais très loins de Phanpy mais qui ne supporte toujours pas les réactions (réactions uniquement en lecture), a priori y aurait du déménagement de compte mais forcément faut que l'instance vers laquelle on déménage support donc ... bah wala quoi

    Du coup revenir sur à la base sur Misskey ? je ne sais pas comment ça à évoluer (compatibilité avec les reste du fediverse) depuis mais y avait plus trop d'européen•nes dessus après la tétrachier de fork qui a vu le jour.

    Non je ne remettrais pas les pied sur Mastodon pour plein de raison. Go To Social hmm bof bof.

    #Hollo #Mitra #Iceshrimp #Fediverse

  16. Bon petit constat :

    - Iceshrimp : trop lourd niveau RAM (3,50go et il en faut au moins 4 pour installer/mettre à jour), trop chiant à maintenir (toujours impossible de maj mon instance ...), la réécriture n'est "toujours" pas prête, pas de scrap pour aller chercher les réponses aux posts des autres instances, pareil pour les profils. Le drive c'est cool le gain de place surtout si comme moi on aime les GIF et ça n'existe nul par ailleurs (outre Misskey et donc ses forks). Déménager semble complètement "péter", fonctionne qu'a moitier ... joie

    - Hollo : trop lourd aussi en RAM (2,50go et pour le moment il faut au minimum 3go pour mettre à jour la chose), et toujours pas de client web avec support des réactions (coucou phanpy, réactions uniquement en lecture) ... pourtant ça récupère les info des instances distante sur les post et les profils.

    - Mitra : ultra léger, paquet debian, bon j'aime pas trop le coté cryptomonaie mais why not vu que tu peux faire payer pour du contenu (pour celles et ceux que ça interesse), mais pas de scrap pour aller chercher les réponses aux posts des autres instances, pareil pour les profils. Client web de base sympa mais très loins de Phanpy mais qui ne supporte toujours pas les réactions (réactions uniquement en lecture), a priori y aurait du déménagement de compte mais forcément faut que l'instance vers laquelle on déménage support donc ... bah wala quoi

    Du coup revenir sur à la base sur Misskey ? je ne sais pas comment ça à évoluer (compatibilité avec les reste du fediverse) depuis mais y avait plus trop d'européen•nes dessus après la tétrachier de fork qui a vu le jour.

    Non je ne remettrais pas les pied sur Mastodon pour plein de raison. Go To Social hmm bof bof.

    #Hollo #Mitra #Iceshrimp #Fediverse

  17. CW: Asking Fedi apps to consider addding less addictive viewing options, :boost_request:

    Most (if not all?) #Fediverse clients (#Mastodon, #Miskey, #Sharkey, #Akoma, #IceShrimp,…) have an infinite scroll functionality, which is famously one of the big factors that makes social media addictive…

    To be clear, I don’t blame the Fedi devs for this, they mostly followed the common approach other social media platforms that did add them with actual malice established, but this might be a good point in time to ask whether doing so was the right call.

    Maybe a page mode, let’s say one page per day, or a similar well defined timeline (rather than number of posts) in the homefeed might be a good idea there? It might not even be necessary to remove infinite scroll, but maybe provide the paged option as the alternative (or even default).

    Thoughts on this, anyone?

    (Ping
    @[email protected], because that’s what I’m primarily on. 😉)

  18. CW: Asking Fedi apps to consider addding less addictive viewing options, :boost_request:

    Most (if not all?) #Fediverse clients (#Mastodon, #Miskey, #Sharkey, #Akoma, #IceShrimp,…) have an infinite scroll functionality, which is famously one of the big factors that makes social media addictive…

    To be clear, I don’t blame the Fedi devs for this, they mostly followed the common approach other social media platforms that did add them with actual malice established, but this might be a good point in time to ask whether doing so was the right call.

    Maybe a page mode, let’s say one page per day, or a similar well defined timeline (rather than number of posts) in the homefeed might be a good idea there? It might not even be necessary to remove infinite scroll, but maybe provide the paged option as the alternative (or even default).

    Thoughts on this, anyone?

    (Ping
    @[email protected], because that’s what I’m primarily on. 😉)

  19. @[email protected] Hallo, mit Moschidon kenne ich mich nicht genug aus bzw. gar nicht.
    Nach meiner Erfahrung kann das Mastodon nicht.

    Wenn man
    #Sharkey #Misskey #IceShrimp als zugang ins Fediverse nutzt, ist in der Hinsicht, sehr wohl viel mehr möglich.
    Nicht nur das du Hashtags Kombinieren kannst, diese Dienste haben auch einen Wortfilter, so das dir Treffer angezeigt werden, wo das Wort auftaucht.
    Diese kannst du auch noch UND ODER verknüpfen, wenn du das willst

    Ich selber schreibe dir diese Antwort von so einem Dienst, der ähnlich ist zu Sharkey
    https://tube.tchncs.de/w/w8bVvpfaZLsSbQQkPUPjy9

    #neuhier

  20. @nocci

    Moin
    Ich wünsche Dir kurzweiliges #IceShrimp durchdringen.
    Und Merci fürs Mitnehmen.
    🙋‍♀️

  21. wie gut das es Sharkey gibt
    Kommunikation im Fediverse in schön und gut, mit einem breiten satz an Features, die das Leben leichter machen.

    Wie auch die ganze Familie um Misskey, IceShrimp, Catodon, Foundkey

    https://tube.tchncs.de/w/w8bVvpfaZLsSbQQkPUPjy9

    #Misskey, #IceShrimp, #Catodon, #Foundkey #Sharkey #Fediverse #NeuHier

  22. wie gut das es Sharkey gibt
    Kommunikation im Fediverse in schön und gut, mit einem breiten satz an Features, die das Leben leichter machen.

    Wie auch die ganze Familie um Misskey, IceShrimp, Catodon, Foundkey

    https://tube.tchncs.de/w/w8bVvpfaZLsSbQQkPUPjy9

    #Misskey, #IceShrimp, #Catodon, #Foundkey #Sharkey #Fediverse #NeuHier

  23. Frage | Ist Misskey und darauf basierendes eigentlich noch Microblogging?


    Wenn ja, auf welcher Definition basiert das?

    #Frage #Misskey #Iceshrimp #sharky #Microblogging #askfedi #askfediverse @fragfeddit

  24. Frage | Ist Misskey und darauf basierendes eigentlich noch Microblogging?


    Wenn ja, auf welcher Definition basiert das?

    #Frage #Misskey #Iceshrimp #sharky #Microblogging #askfedi #askfediverse @fragfeddit

  25. Important Security Fix:

    Alle bei Weingärtner IT gehosteten #iceshrimp -Instanzen laufen ab jetzt auf v2026.5.1

    --------------------------------------------
    All #iceshrimp instances hosted at Weingärtner IT now running on version v2026.5.1

    --------------------------------------------

    ChangeLog:
    iceshrimp.dev/iceshrimp/iceshr

  26. Important Security Fix:

    Alle bei Weingärtner IT gehosteten #iceshrimp -Instanzen laufen ab jetzt auf v2026.5.1

    --------------------------------------------
    All #iceshrimp instances hosted at Weingärtner IT now running on version v2026.5.1

    --------------------------------------------

    ChangeLog:
    iceshrimp.dev/iceshrimp/iceshr

  27. J'en peux plus, pourquoi tant de haine ​:pikasob:​

    yarn build
        ____               __         _               
       /  _/_______  _____/ /_  _____(_)___ ___  ____ 
       / // ___/ _ \/ ___/ __ \/ ___/ / __ `__ \/ __ \
     _/ // /__/  __(__  ) / / / /  / / / / / / / /_/ /
    /___/\___/\___/____/_/ /_/_/  /_/_/ /_/ /_/ .___/ 
                                             /_/      
     Currently building Iceshrimp!
     Hang on for a moment, as this may take a while.
    
    [iceshrimp-sdk]: TypeError: Cannot convert undefined or null to object
    [iceshrimp-sdk]:     at JoyCon.recusivelyResolve (file:///home/fediverse/iceshrimp/.yarn/cache/joycon-npm-3.1.1-3033e0e5f4-4b36e34791.zip/node_modules/joycon/lib/index.js:80:30)
    [iceshrimp-sdk]:     at async loadTsupConfig (file:///home/fediverse/iceshrimp/.yarn/__virtual__/tsup-virtual-4b773fcf67/0/cache/tsup-npm-8.5.1-41f4f7d59b-f1927ec2dd.zip/node_modules/tsup/dist/chunk-VGC3FXLU.js:33:22)
    [iceshrimp-sdk]:     at async build (file:///home/fediverse/iceshrimp/.yarn/__virtual__/tsup-virtual-4b773fcf67/0/cache/tsup-npm-8.5.1-41f4f7d59b-f1927ec2dd.zip/node_modules/tsup/dist/index.js:1489:51)
    [iceshrimp-sdk]:     at async CAC. (file:///home/fediverse/iceshrimp/.yarn/__virtual__/tsup-virtual-4b773fcf67/0/cache/tsup-npm-8.5.1-41f4f7d59b-f1927ec2dd.zip/node_modules/tsup/dist/chunk-DI5BO6XE.js:143:5)
    [iceshrimp-sdk]:     at async main (file:///home/fediverse/iceshrimp/.yarn/__virtual__/tsup-virtual-4b773fcf67/0/cache/tsup-npm-8.5.1-41f4f7d59b-f1927ec2dd.zip/node_modules/tsup/dist/chunk-DI5BO6XE.js:148:3)
    The command failed in workspace iceshrimp-sdk@workspace:packages/iceshrimp-sdk with exit code 1
    The command failed for workspaces that are depended upon by other workspaces; can't satisfy the dependency graph
    Failed with errors in 1s 623ms

    #Iceshrimp

  28. Do MissKey & IceShrimp have the same DDos behaviour as Mastodon when doing link preview fetching?

    Looking at user agents in access logs to see what I should filter out to get a better understand on what's actually read..

    Since it's #caturday, here's some kind of cat 😽

    Mastodon preview fetching: github.com/mastodon/mastodon/i

    #misskey #iceshrimp

  29. Do MissKey & IceShrimp have the same DDos behaviour as Mastodon when doing link preview fetching?

    Looking at user agents in access logs to see what I should filter out to get a better understand on what's actually read..

    Since it's #caturday, here's some kind of cat 😽

    Mastodon preview fetching: github.com/mastodon/mastodon/i

    #misskey #iceshrimp

  30. Dites les admins de #iceshrimp : je remarque que j'ai énormément de place prise dans le répertoire files (+- 30 Go pour 160000 fichiers)
    Est-ce que je peux faire du nettoyage là dedans avant une MAJ ?
    J'ai des fichiers de 2023 qui trainent, je sais pas trop à quoi ça correspond.

  31. Dites les admins de #iceshrimp : je remarque que j'ai énormément de place prise dans le répertoire files (+- 30 Go pour 160000 fichiers)
    Est-ce que je peux faire du nettoyage là dedans avant une MAJ ?
    J'ai des fichiers de 2023 qui trainent, je sais pas trop à quoi ça correspond.

  32. Fedistar v1.12.6
    => fedistar.net

    Multi-column Fediverse client application for desktop

    - Supporting SNS
    - - Mastodon
    - - Pleroma
    - - Friendica
    - - Firefish
    - - Gotosocial
    - - Pixelfed
    - - Akkoma (Unofficial)
    - - Sharkey (Unofficial)
    - - Hometown (Unofficial)
    - - Iceshrimp (Unofficial)
    - Multiple accounts management
    - Multiple columns
    - You can see timelines without sign in
    - Desktop notification
    - Streaming update
    - Send reactions from another accounts
    - Change column width

    Changelog:
    => github.com/h3poteto/fedistar/r

    #Fediverse #Mastodon #Pleroma #Friendica #Firefish #Gotosocial #Pixelfed #Akkoma #Sharkey #Hometown #Iceshrimp

  33. Fedistar v1.12.6
    => fedistar.net

    Multi-column Fediverse client application for desktop

    - Supporting SNS
    - - Mastodon
    - - Pleroma
    - - Friendica
    - - Firefish
    - - Gotosocial
    - - Pixelfed
    - - Akkoma (Unofficial)
    - - Sharkey (Unofficial)
    - - Hometown (Unofficial)
    - - Iceshrimp (Unofficial)
    - Multiple accounts management
    - Multiple columns
    - You can see timelines without sign in
    - Desktop notification
    - Streaming update
    - Send reactions from another accounts
    - Change column width

    Changelog:
    => github.com/h3poteto/fedistar/r

    #Fediverse #Mastodon #Pleroma #Friendica #Firefish #Gotosocial #Pixelfed #Akkoma #Sharkey #Hometown #Iceshrimp

  34. As a reminder: I am offering free Iceshrimp.NET fediverse hosting on OP5+’s. Contact me for details.

    #orangepi #iceshrimp #iceshrimpnet #fediverse

  35. 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
  36. 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
  37. and while i'm on that topic, out of curiosity, is it easy to change the fedi server software while retaining accounts, files, posts, federation - data in general without major breaking changes?
    #fediadmin #misskey #sharkey #iceshrimp #pleroma

  38. and while i'm on that topic, out of curiosity, is it easy to change the fedi server software while retaining accounts, files, posts, federation - data in general without major breaking changes?
    #fediadmin #misskey #sharkey #iceshrimp #pleroma

  39. Vielleicht sollten wir Bewohner der föderierten Planeten des #Fediverse den Menschen, die #neuhier sind, etwas erklären:
    #DasFediverseIstMehr als Mastodon.

    In den unendlichen Weiten der digitalen Unabhängigkeit befinden sich so viele Möglichkeiten , das für jede*n etwas dabei ist. Das kann natürlich
    #Mastodon sein, aber auch:
    Microblogging Planeten
    #Akkoma
    #GoToSocial
    #Iceshrimp
    #Misskey
    #Pleroma
    #Sharkey
    Die Macroblogging Planeten
    #diaspora*
    #Friendica
    #Hubzilla
    #(streams)
    Die Fotografie Planeten
    #Pixelfed
    #Vernissage
    Die Publishing Planeten
    #Drupal
    #Ghost
    #Plume
    #WordPress
    #WriteFreely
    Die Video & Live Planeten
    #Loops
    #Owncast
    #Peer Tube
    Die Audio & Podcasts.Planeten
    #Castopod
    #Funkwhale
    Der Kalender & Events Planet
    #Mobilizon
    Der Foren & Diskussionen Planet
    Lemmy
    Und der Bücher Planet
    #BookWyrm

    Eine knappe Übersicht gibt es hier:
    https://fediversum.info/fediverse-software-und-dienste/

    Vielleicht sollten wir Bewohner der föderierten Planeten, aber auch berichten, warum wir unseren Planeten bewohnen und was wir an ihm lieben.
    Und wie spannend wäre es zu erfahren, was wie es ist seinen ganz eigenen Planeten zu haben und was man tun muss um ihn zu erschaffen und sich bei Bedarf Mitbewohner zu suchen.
    Das Fediverse ist so spannend. Wir sollten davon erzählen, damit die neuen Fediversebewohner neugierig werden und den perfekten Platz für sich finden können. Und auch wir alteingesessenen
    #Fedinauten lernen immer noch dazu.

    Also lasst uns unsere Geschichten erzählen, über unsere Heimatplaneten berichten.

    Unter den Hashtags
    #DasFediverseIstMehr #WirSindFedi #Fediliebe fange ich gleich mit einem ersten Post an. Und ihr, Fedinaut*innen der Planetenrunde?

    #DigitaleSouveränität #DIDit #diversität #DasFediverseErzählt

  40. Looking on @opencollective, and I notice that #Firefish (fka. #Calckey) is still receiving funding from users and yet the project has been dead for nearly 18 months.

    Kainoa handed the project over (and has dipped from Fedi, only on Bsky now) to naskya who announced its closure in September 2024 (fediversereport.com/last-week-)

    I think most server admins moved to #IceShrimp or #sharkey

    It was such a great project and I miss using it.

  41. Hallo liebe Fediverse-Admins,

    ich bin auf der Suche nach einer Botpolicy für Anubis in Kombination mit Iceshrimp.

    Meine aktuelle Policy ist folgende:
    paste.obco.pro/upload/dRGDKe

    Jedoch scheint damit das Iceshrimp UI nicht richtig zu laden. Also der Feed und die Benachrichtigungen laden nicht richtig.

    Hier ist der Browserlog:
    paste.obco.pro/upload/er0w4b

    Wenn jemand eine Idee oder eine Policy hat, welche mit Iceshrimp funktioniert, wäre ich sehr dankbar.

    ​:boost_animated:​ ​:blahaj:​ ​:rosahaj_thinking:​

    #fedimin #fedimins #iceshrimp #iceshrimpjs #anubis

  42. CW: iceshrimp behavior that’s bad for privacy

    So #Iceshrimp gives you notification when someone votes on your polls, including who… Which is kinda pretty invasive on privacy when you don’t expect it, especially if you watch the poll for the first couple of votes and can then infer voting behavior.

    Like, yes, technically this is of course available somewhere, but the rest of the Fediverse kinda keeps the votes private enough for the person starting them to at least not learn those votes by accident…

    And it kinda sucks that Iceshrimp now seems to break that expectation…

  43. @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
  44. @「 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 fetch kö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
  45. 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 😭.

    #misskey #foundkey #calckey #firefish #iceshrimp #sharkey