#iceshrimp — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #iceshrimp, aggregated by home.social.
-
@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 -
@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 -
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 -
@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 -
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 -
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 -
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 -
@「 Jürgen 」:fedi_mastodon: @crossgolf_rebel - kostenlose Kwalitätsposts @Don di Dislessia Soweit ich weiß, war es so (man möge mich wiederum korrigieren; kursiv sind die "Forkeys höheren Grades", die nicht von Misskey geforkt wurden):
- Misskey
Der Ursprung in Japan. - Calckey
Soft-Fork von Misskey mit einigen Extrafeatures.
Entwickler hatte irgendwann keine Zeit/keinen Bock mehr. - Firefish
Fortführung von Calckey unter neuem Management. Wurde aufgrund einer massiven Werbeaktion eines begeisterten Nutzers mit viel Reichweite so populär, daß der Name "Calckey" irgendwann einfach doof war und das ganze Ding eine neue Identität bekam.
Entwickler verschwand irgendwann sang- und klanglos von der Bildfläche. Nach einem halben Jahr stellte sich raus: Entwickler hatte wegen Abschlußarbeit usw. keine Zeit mehr, nicht mal, sich zu verabschieden.
Wurde unter neuer Führung mit neuem Repository und neuer Leuchtturminstanz weitergeführt, aber ohne neue Website. Wurde wieder eingestellt, weil es für eine einzige Entwicklerin viel zuviel war, die ganzen alten Co-Entwickler von Firefish alle zu Iceshrimp gewechselt waren und keine neuen Mitentwickler angeheuert werden konnten. - Iceshrimp
Fork von Firefish von ehemaligen Firefish-Entwicklern. Rebased nach Misskey, weil es auf Firefish nicht weiterging. Erklärtes Ziel war, Stabilität über Calckeys Featuritis zu stellen.
Weil Misskeys Codebase an sich einiges an grundsätzlichen Macken hatte, wurde beschlossen, es ist einfacher, das ganze Zeugs von Grund auf neu zu schreiben, als zu versuchen, das alles auszubügeln. Und bei der Gelegenheit wollte man von JavaScript (TypeScript und Vue.js) weg. Also hat man angefangen, das ganze Ding in C# neu zu schreiben als Iceshrimp.NET. Ziel ist featuremäßige Deckungsgleichheit mit dem bisherigen Iceshrimp und gleichzeitig Anpassung an Mastodon. Iceshrimp.NET ist noch sehr unfertig.
Bei der Gelegenheit wurde das alte Iceshrimp in Iceshrimp-JS umbenannt und in den Wartungsmodus versetzt = gibt keine Weiterentwicklung und keine neuen Features mehr, nur Sicherheitspatches und evtl. Bugfixes. - Catodon
Soft-Fork von Firefish. Ziel war, ein Forkey zu haben, das sich in der Bedienung wie Mastodon anfühlt. Quasi Mastodon-Fassade mit *key-Struktur dahinter. Also ein Forkey für den möglichst leichten Umstieg von Mastodon nach *key.
Wurde, als Firefish endgültig eingestellt wurde und damit die Basis tot war, nach Iceshrimp rebased.
Nachdem Iceshrimp zu Iceshrimp-JS wurde und in den Wartungsmodus ging, hatte Catodon ein Problem: Man kann nicht einfach von etwas, das in TypeScript und Vue.js geschrieben ist, nach etwas rebasen, das in C# geschrieben ist (Iceshrimp.NET). Und zur Weiterentwicklung wäre ein Rebase nötig gewesen, weil man jetzt wieder eine fast tote Basis hatte. Aber nach Misskey wollte man nicht (siehe Hajkey weiter unten), und Sharkey war einerseits zu mächtig und andererseits zu kapriziös.
Inzwischen gehen Catodon die Instanzen ein. Die meisten dürften geschlossen worden sein. - Sharkey
Soft-Fork von Misskey mit dem Ziel, so ziemlich alles, was je für Forkeys an Features entwickelt worden war, in einen einzigen Forkey zu packen und noch mehr obendrauf.
Quasi das Yang zu Iceshrimps Yin. Machte lange den Eindruck, als gingen Features über Zuverlässigkeit. Sharkeys Implementation der Mastodon Client API war schon regelrecht legendär schlecht, und alle hofften auf den Retter, der daherkommt und die Implementation von Grund auf neu schreibt, weil sie als unrettbar im Eimer galt. Inzwischen soll Sharkey seine Zuverlässigkeit im Griff haben, zumindest insofern, wie auch Misskey zuverlässig ist.
Die Entwickler haben eine zweifelhafte Reputation. Unter anderem haben sie Crowdfunding-Gelder für einen Sharkey-Server gesammelt und von dem Geld einen Minecraft-Server aufgezogen, aber keinen Sharkey-Server. Mitunter wird deshalb zum Boykott von Sharkey aufgerufen. - CherryPick
Südkoreanischer Soft-Fork von Misskey. Tatsächlich älter als Sharkey, mindestens von 2021, aber später wurde wohl einiges von Sharkey nach CherryPick portiert. Das Ziel war, einen stabilen und zuverlässigen Forkey zu haben ohne die Macken von Sharkey und sogar ohne die Macken von Misskey, der aber gleichzeitig gut Features hat. Das ist wohl sogar weitestgehend gelungen.
Vom ästhetischen Stil her so ähnlich, wie Misskey früher mal war, also sehr auf den japanischen bzw. südkoreanischen Geschmack ausgelegt: bunt, grell, poppig, genki, kawaii. Alleine das zeigt, daß CherryPick von Misskey geforkt wurde, bevor Misskey gänzlich an den westlichen Geschmack angepaßt wurde.
Unklar, ob es Entwickler hat, die Englisch verstehen bzw. schreiben können; falls nicht, dann als Soft-Fork-Basis ungeeignet. Wäre ohne die Kommunikationsbarriere vermutlich der ultimative *key.
Mein letzter Stand: Bis auf eine Instanz im Großraum Washington, D.C. gibt es CherryPick-Instanzen nur in den Großräumen Tokyo und Seoul. War deshalb lange Zeit im westlichen Fediverse fast unbekannt. - FoundKey
Wohl der erste Forkey, der in PascalCase geschrieben wurde.
Meines Wissens direkter Soft-Fork von Misskey. Wird tatsächlich (oh Wunder) kleckerweise gepflegt, aber nicht für Instanzen mit mehr als 20 Nutzern empfohlen.
Ein paar andere *keys:- Hajkey
Soft-Fork von Calckey, der meines Wissens erst nach Firefish und dann nach Misskey rebased wurde. Wurde exklusiv nur für eine einzige Instanz entwickelt: transfem.social. Inzwischen eingestellt, weil wohl der Aufwand, so einen Wolpertinger nur für eine Instanz zu pflegen (man rebaset nicht mal eben von Firefish nach Misskey), zu groß war. transfem.social wurde entsprechend auf Sharkey umgestellt und ist da jetzt eine der größten Instanzen. - Neko
Soft-Fork von Misskey mit dem Ziel, es tauglich für Docker zu machen. Laut Repository nur für eine einzige Instanz gebaut. Ist nie released worden, was aber Wurscht ist, wenn es eh nur einen Admin als Zielgruppe hatte.git fetchkönnen Releases nämlich piepegal sein. - Meisskey
Japanischer Soft-Fork von Misskey von 2019 (!), der aber lange Zeit der Weiterentwicklung der Basis hinterherhinkte. Wird tatsächlich immer noch weiterentwickelt. - Leisskey
Wiederum japanischer Soft-Fork von Meisskey. Ist seit mindestens 2021 in Entwicklung, seit Februar 2023 aber eine ewige Beta, weil es seit damals keinen Release mehr gegeben hat. Dürfte zu den letzten noch in Entwicklung befindlichen "Forkeys 2. Grades" gehören. - Tanukey
Weiterer japanischer Soft-Fork von Misskey und daher so obskur im Westen, daß man schon die Websuche anstrengen muß, um das Repository zu finden (ist wohl im letzten Oktober von GitHub nach GitLab umgezogen). Noch ein Beispiel für *keys, bei denen selbst das Wissen über ihre Existenz Ostasien kaum je verlassen hat. - Backspacekey
Noch ein ambitionierter, aber eingeschlafener westlicher Misskey-Soft-Fork.
Siehe übrigens auch die Delightful Fediverse Experience: hier und hier.
Verglichen damit ist die Familie von Mistpark bis Forte schon wieder übersichtlich, vor allem, wenn die anderen mehreren Dutzend toten Forkeys mit dazugeholt werden. Immerhin stammt von Mistpark bis Forte über etwa 15 Jahre alles vom selben Schöpfer, der einfach nur sein eigenes Zeug geforkt hat.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #IceshrimpJS #Iceshrimp.NET #Catodon #Sharkey #CherryPick #FoundKey #Hajkey #Neko #Meisskey #Leisskey #Tanukey #Backspacekey - Misskey
-
CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:
#[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)
Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!
Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.
Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.
On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:
#Hashtag
Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)
On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:
#Hashtag
Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.
But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.
The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.
Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.
But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.
You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.
This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.
Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.
Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.
When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.
Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.
So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.
And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.
I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte -
@Herr TurTur @crossgolf_rebel - kostenlose Kwalitätsposts @tux0r :openbsd: Die Idee hinter Sharkey war mal, in einen einzigen Forkey quasi alles auf einmal reinzuschmeißen bis hin zur Küchenspüle. Das fiel vor allem auf, als es noch mehr lebendige Forkeys zur Auswahl gab.
Und in der Zeit hatte Sharkey auch noch gewisse Macken, z. B. eine schon legendär unzuverlässige Implementation der Mastodon Client API, wo es hieß, am besten setzt sich einer hin und schreibt die neu. Wer was Zuverlässiges wollte, setzte damals auf Iceshrimp. Sharkey war für wagemutige Spielkinder, die sich an Hubzilla nicht rantrauten.
Inzwischen ist Calckey tot, Firefish ist tot, Iceshrimp-JS ist im Wartungsmodus (Iceshrimp.NET ist derweil noch meilenweit von "fertig" entfernt), Catodon ist auch schon siech, und das nur für eine Instanz gebaute Hajkey ist schon verwest.
CherryPick hat fast nur Server in den Großräumen Tokyo und Seoul und fühlt sich so auf den ostasiatischen Geschmack ausgelegt an wie vor ein paar Jahren noch Misskey selbst. Vielleicht erinnern sich ein paar noch daran, wie Misskey mal den Charme japanischer Verkaufsautomaten hatte.
Und der ganze noch lebende Rest scheint selbst mit Misskeys Entwicklung nicht mithalten zu können, also im Kern veraltet zu sein.
Derweil ist Sharkey wohl inzwischen ziemlich zuverlässig. So ist es zumindest im Westen zum einzigen noch nennenswerten Forkey avanciert.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Sharkey #Calckey #Firefish #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Catodon #Hajkey #CherryPick -
I think we're back to the "where to move this account" question. (and I have yet to find an answer.)
- First, when Firefish died, I thought the answer was going to be the new #Iceshrimp, but it's been more than a year and I'm not sure it's going to be a thing ever. (And I never fully liked Sharkey, for reasons)
- Next, I tried #Akkomane. I thought it was going to be the place, but a few things were deal breakers (I forgot which ones, whoops... but they did greatly bother me at the time)
- Then came #Wafrn. Despite the unpractical name, I love the idea (it uses both ActivityPub and ATProtocol natively), but the UI is just not for me.
- I've been waiting for #Ghost 6.0 release for a little while now. It's imminent. However, it doesn't seem that they will release a full #microblogging platform. I doubt that it'll be much different from the beta (which is great, but can't replace a full-blown platform)
- And I'm extremely interested in #Bonfire, but it won't be ready for users like me for another few months I believe...
Meanwhile, my feed hasn't been working for weeks on my account's #Firefish page, and now, the notifications have stopped working with #Phanpy (I've used this account, partly with the native UI and partly with Phanpy for a little while).
I guess a temporary #Mastodon account will have to be it until something that can replace it comes along (I'm confident that Bonfire will be the one, but I was confident Iceshrimp and Akkomane were going to be the ones too... So... 🤷) -
Enklaste sättet att starta en egen Fediversuminstans är att använda sig av ett Fediversum-hotell (Fedihotell). Det är som ett webbhotell men för Fediversumprogramvaror. Fediversumprogramvaror är program som kan kommunicera med varandra med ett gemensamt protokoll som heter ActivityPub.
https://blog.zaramis.se/2025/02/24/enklaste-sattet-att-starta-en-egen-fediversuminstans/
-
#SpaceHost provides fully-managed hosting for the Fediverse.
For Mastodon as well as other Fediverse software, such as Akkoma (Akkomane = Akkoma + Mangane), Castopod, Friendica, Iceshrimp, Lemmy, Pixelfed, Pleroma, Sharkey, and more.
(As well as some other non-Fediverse DeSo, too. Ex: Matrix, etc.)
#DeSo #Fediverse #Akkoma #Akkomane #Castopod #Friendica #Iceshrimp #Lemmy #Mangane #Mastodon #Pixelfed #Pleroma #Sharkey
-
Found 62 new servers and 24 servers died off since 3 hours ago.
22,778 servers checked. 13,720,891 Total Users with 1,051,008 Active Users today. Check out the stats!
New #fediverse servers found:
write.pouet.it a #writefreely server from Germany
santacruz.photos a #pixelfed server from United States
acties.todon.nl a #gancio server from The Netherlands
mastodon.kurau.tokyo a #mastodon server from Germany
gts.foggymtndrifter.com a #gotosocial server from Private
themes.69.mu a #writefreely server from France
rad.talesofmy.life a #iceshrimp server from United States
ice.kugetsu.blog a #iceshrimp.net server from Japan
videa.inspirujici.cz a #peertube server from Germany
herebox.org a #wordpress server from Private
mondary.design a #wordpress server from France
mcschluberson.com a #wordpress server from United States
geniemedius.com a #wordpress server from United States
alexvielmav.com a #wordpress server from United States
social.gwsberlin.de a #mastodon server from Germany
exploreviews.online a #wordpress server from Private
deskinvestor.com a #wordpress server from United States
live.theindiebeat.fm a #owncast server from Finland
destabled.xyz a #mastodon server from Private
jixifox.me a #wordpress server from United States
nerdinfekt.de a #wordpress server from Germany
remimarenco.com a #wordpress server from United States
gatherpress.org a #wordpress server from Private
hikercarl.com a #wordpress server from United States
feminegra.com a #wordpress server from United States
smart7line.net a #wordpress server from United States
arges-stiri.ro a #wordpress server from Romania
thepanvelite.com a #wordpress server from United States
citizenspoint.com a #wordpress server from United States
bobonbooks.com a #wordpress server from United States
cmrosens.com a #wordpress server from United States
coot.vabl.dev a #takahe server from Private
funime.de a #wordpress server from Germany
tldr.pramari.de a #gotosocial server from Germany
svenruppert.com a #wordpress server from United States
trendblogz.com a #wordpress server from United States
christianpure.com a #wordpress server from United States
www.kamikazeanimated.com a #wordpress server from United States
tscnewschannel.com a #wordpress server from United States
samupress.ca a #wordpress server from United States
theandressegovia.com a #wordpress server from United States
rollingstonesdata.com a #wordpress server from United States
mastodon.cixoelectronic.pl a #mastodon server from Poland
blog.igv.com a #wordpress server from Private
greenvillager.com a #wordpress server from United States
ortetesekusoccerinfo.co.uk a #wordpress server from United States
pleasethepalate.com a #wordpress server from United States
dailyazerbaijan.com a #wordpress server from United States
mariaisquixotic.com a #wordpress server from United States
weston.ruter.net a #wordpress server from United States
peopletalky.com a #wordpress server from United States
www.lancescurv.com a #wordpress server from Private
rsoemardja.com a #wordpress server from United States
www.nerdandtie.com a #wordpress server from United States
daviemactile.com a #wordpress server from United States
chipsandcheese.com a #wordpress server from Private
doctor-multiverse.com a #wordpress server from United States
md.ghostnoise.ru a #mastodon server from Russia
events.ijug.eu a #mobilizon server from Germany
speacqua.net a #misskey server from Japan
snowfinch.zone a #mastodon server from Germany
guelph.social a #mastodon server from PortugalHelp others find a home, send them to fediverse.observer
-
Found 60 new servers and 23 servers died off since 3 hours ago.
22,780 servers checked. 13,720,891 Total Users with 1,051,008 Active Users today. Check out the stats!
New #fediverse servers found:
acties.todon.nl a #gancio server from The Netherlands
mastodon.kurau.tokyo a #mastodon server from Germany
gts.foggymtndrifter.com a #gotosocial server from Private
themes.69.mu a #writefreely server from France
rad.talesofmy.life a #iceshrimp server from United States
ice.kugetsu.blog a #iceshrimp.net server from Japan
videa.inspirujici.cz a #peertube server from Germany
herebox.org a #wordpress server from Private
mondary.design a #wordpress server from France
mcschluberson.com a #wordpress server from United States
alexvielmav.com a #wordpress server from United States
geniemedius.com a #wordpress server from United States
social.gwsberlin.de a #mastodon server from Germany
exploreviews.online a #wordpress server from Private
deskinvestor.com a #wordpress server from United States
arges-stiri.ro a #wordpress server from Romania
thepanvelite.com a #wordpress server from United States
smart7line.net a #wordpress server from United States
feminegra.com a #wordpress server from United States
remimarenco.com a #wordpress server from United States
cmrosens.com a #wordpress server from United States
hikercarl.com a #wordpress server from United States
bobonbooks.com a #wordpress server from United States
citizenspoint.com a #wordpress server from United States
destabled.xyz a #mastodon server from Private
nerdinfekt.de a #wordpress server from Germany
live.theindiebeat.fm a #owncast server from Finland
jixifox.me a #wordpress server from United States
funime.de a #wordpress server from Germany
coot.vabl.dev a #takahe server from Private
gatherpress.org a #wordpress server from Private
tldr.pramari.de a #gotosocial server from Germany
svenruppert.com a #wordpress server from United States
theandressegovia.com a #wordpress server from United States
trendblogz.com a #wordpress server from United States
mastodon.cixoelectronic.pl a #mastodon server from Poland
www.kamikazeanimated.com a #wordpress server from United States
tscnewschannel.com a #wordpress server from United States
samupress.ca a #wordpress server from United States
christianpure.com a #wordpress server from United States
blog.igv.com a #wordpress server from Private
rollingstonesdata.com a #wordpress server from United States
pleasethepalate.com a #wordpress server from United States
mariaisquixotic.com a #wordpress server from United States
dailyazerbaijan.com a #wordpress server from United States
daviemactile.com a #wordpress server from United States
ortetesekusoccerinfo.co.uk a #wordpress server from United States
www.lancescurv.com a #wordpress server from Private
www.nerdandtie.com a #wordpress server from United States
weston.ruter.net a #wordpress server from United States
greenvillager.com a #wordpress server from United States
peopletalky.com a #wordpress server from United States
rsoemardja.com a #wordpress server from United States
doctor-multiverse.com a #wordpress server from United States
chipsandcheese.com a #wordpress server from Private
md.ghostnoise.ru a #mastodon server from Russia
events.ijug.eu a #mobilizon server from Germany
speacqua.net a #misskey server from Japan
snowfinch.zone a #mastodon server from Germany
guelph.social a #mastodon server from PortugalHelp others find a home, send them to fediverse.observer
-
Remember a few weeks ago, I tested a few Fediverse services to see what to do with this account (to move or not to move?)
Here are some "results":
- IceShrimp: not different enough from Firefish to justify a move (but I warmly advise if you want to move away from Mastodon to something with more features)
- Sharkey: I haven't tested enough, but very probably the same conclusion as with IceShrimp.
- I didn't mention it previously, but I also briefly tested Friendica. The number of features is quite amazing and a move there was tempting but... the learning curve is steeper than anywhere else, mostly because the UI is just not that good (but it can be used with many apps for basic use). One big issue, it doesn't seem possible to migrate an account there from another platform. So, that's a no.
- Akkomane: I really like it, it's just a better Mastodon and if I were to choose between Mastodon and Akkomane, it'd be a no-brainer. However, while it offers things Firefish doesn't, the opposite is also true.
And to make things more complicated, while I like the mobile experience with Akkomane better (it also can use lots of different apps, and the mobile experience with Firefish really is its weakest point), I still think that the desktop experience on Firefish is the best of all the platforms I know (those plugins, I'm telling you, difficult to live without them now).
And because I'm old school, I mostly use social media on my computer (even more so now that I need glasses to read and write, and I rarely have them on my nose when I have a phone in my hand, but that's another topic - if you think I make a lot of typos at times, you know why).
So as a conclusion. I still don't know what to do... 🤷♂️
Which means this account will stay on Firefish for now. But I'd like to keep on using Akkomane. But I can't justify having three active micro-blogging accounts on the Fediverse (my Mastodon account stays where it is, this whole thing doesn't concern it). What would I talk about on that third account that I don't already talk about here or on Mastodon?
🤔
#fediverse #Firefish #IceShrimp #Mastodon #Friendica #Akkoma #Akkomane -
Testing #Akkomane and #Iceshrimp :
After a couple of days trying both, one thing that's obvious right away is that Iceshrimp is just too similar to Firefish to justify a move there. I'm hearing there's a major overhaul coming. I'll check it out then, but right now, there is no point (actually, I am becoming a fan of Firefish's new feature: an auto-switch for language, very useful for people like me who post in several languages)
I really like Akkomane so far, but I don't love it.
As far as I know, the only features it has that #Firefish doesn't have are the ability to use different clients (especially useful on mobile, the mobile experience with Firefish is not the best) and the ability to follow hashtags (something sorely missing in the Misskey-verse - yes, I know there are antennas, but I want followed hashtags in my main feed, not on a separate one).
Is it enough to justify a move (and leave the Misskey-verse and its amazing desktop UI - I have become a huge fan of the widgets)? I do not know.
Also, I'm not a big fan of replies not being threaded.
Okay, that's all for now. I'll keep testing Akkomane, but right now, I'm unsure if I should move.
And what about having one more Fediverse account? Hmmm... I already have my Mastodon account (and this one is not going anywhere), I'm not sure if it's a good idea to have three active accounts (unless I separate French and English content like I used to do on Twitter? Well, I stopped doing this for a reason)
#Fediverse -
Hi, this is your friendly neighborhood David B. Himself. Over the next few days, I'll be testing #Akkomane (and possibly move here?)
So don't be surprised by any crossposting, following, and more.
(I'm also testing #IceShrimp there: @DavidBHimself ) -
No, I don't have doppelgangers, nor a multiple personality disorder (that I know of) but I guess the best way to know if I should move to #Akkomane or #Iceshrimp (or stay on #Firefish) is to actually use them.
(in my previous post on the topic, I also mentioned #Sharkey but I'm leaving it aside for now. While the UI is very similar to IceShrimp's, the latter feels nicer and smoother. Hard to explain.)
So, over the next few days, I'll be juggling three accounts (crossposting and/or boosting). The current one as well as @[email protected] and @[email protected]
Feel free to follow them. I'll also very likely export my follow list over there to populate timelines.
Stay tuned for the mess that's going to happen in the next few days, and hopefully some conclusions in a week or two??? -
Maybe, it's time to leave #Firefish after all (a couple of weeks ago, it seemed alive and well, but a few bugs are showing up more and more often. Now, it's the search bar that is acting up.
Now the question is where to move? (and this is where my chronic indecisiveness is kicking in)
I have a few options.
1. Stay on Firefish after all.
- Pros: That will save me time and energy. I have a wonderful admin on my instance.
If it's actually actively maintained by the new owners, maybe nice things will come out of it (the automatic language selector seems new and unique to Firefish, right?)
- Cons: There have been bugs appearing lately and they give me bad flashbacks from last year when firefish.social imploded.
A feeling of hanging on to a sinking ship (a sunken ship?)
2. Another #Misskey fork, either #IceShrimp or #Sharkey.
- Pros: Similar to Firefish but more alive I could move all my old posts to the new platform.
- Cons: Well, first, the fact that they're hard to tell apart from each other doesn't help making a choice.
Do I really need that many customization options?
Regarding the question above, one reason I'd like to stick with a Misskey fork is the "channels" function. It's basically a mini-private forum on the instance. And I have the crazy dream of bringing my non-terminally-online friends to the #Fediverse, and that would be awesome if we all shared the same instance, and also have a private section but... And that's a big "but." I tried and I have yet to convince a single one of them to give a shot to this idea. So maybe I'm wasting my hopes with this pipe dream.
Another con for the Misskey forks is that you can't follow hashtags, which is one of my favorite functions on #Mastodon and that is sorely missing on Firefish, IceShrimp, and Sharkey.
3. #Akkoma, especially #Akkomane
- Pros: It's lightweight, it's sleek, and it allows long posts, and following hashtags too.
You can use it with Elk and Phanpy and probably most Fediverse apps (which is not the case for the MissKey forks).
If I want to self-host a solo instance, it's also the cheapest option (it matters, I'm poor these days and with the state of the Japanese economy, I doubt it'll change anytime soon) - of course, I don't have to have a solo instance.
- Cons:
I'd lose all my old posts. Not a terrible issue, but still a negative.
It's a platform I'm not too familiar with, which is only a problem for the short term, and it seems stable and reliable long term.
Also, it's silly, but I really dislike the default color of the UI (light magenta?) and I don't think I can change it. Of course, I don't have to use the default UI as I can use another app with it, but for some reason, I tend to like using the default interface when I use it on my computer (which remains the place where I use social media the most).
(1/2) -
@[email protected] It's weird how folks miss that it's literally one or two people doing most of the day-to-day on #Iceshrimp and #Sharkey. Folks keep wanting the feature set of something much bigger. Kind of sad to see how many folks keep wanting fedi bling but BIPOC efforts to increase fedi safety get silence from same kind of folks willing to silence Sharkey over their technical peeve.
Make it make sense.
#sharkey #misskey #FediverseSafety #fediadmins #fediverse -
Found 33 new servers found and 27 servers de-listed since 13 hours ago. Check out the Monthly and Daily Stats by software or server or the entire fediverse.
24,720 servers checked. 12,751,063 Total Users, 1,751,799 Monthly Active Users today vs 1,757,797 yesterday for the entire fediverse.
New #fediverse servers found:
sys.alizas.blog a #akkoma server from United States
plusi.moe a #firefish server from Germany
pleroma.uii.pt a #pleroma server from Portugal
twt.turqtoise-soup.com a #mastodon server from South Korea
occommu.xyz a #mastodon server from South Korea
f.kw8.eu a #friendica server from Germany
streaming.gnieh.org a #owncast server from France
msky.launchpencil.f5.si a #misskey server from Japan
lemmy.sieprawski.pl a #lemmy server from France
firefish.crazy-to-bike.de a #firefish server from Germany
ikusi.izarkom.eus a #owncast server from France
nextcloud.s06w.webhosting-waldhufe.de a #nextcloud social server from Germany
shao.life a #mastodon server from Private
eri.narandu.de a #friendica server from Germany
foruq.ir a #lotide server from Iran
testbed.sdf.org a #mastodon server from United States
peer.madiator.cloud a #peertube server from Germany
ein.shg-blog.de a #pleroma server from Germany
rechtscafe.de a #friendica server from Germany
ff.mer.moe a #firefish server from Private
gts.octopusx.de a #gotosocial server from Germany
morphnet.de a #mastodon server from Germany
social.mrdonaldson.net a #pleroma server from United Kingdom
noplacelikeholmes.masto.host a #mastodon server from France
social.horrid-creatu.re a #akkoma server from The Netherlands
mastodon.feraltodayfriendtomorrow.org a #mastodon server from France
social.paris12.pcf.fr a #pleroma server from France
host.blahaj.date a #gotosocial server from Germany
dorothys.vision a #misskey server from Australia
mirage-afb8.unit520.wtf a #lemmy server from United States
soc.cameronmonagle.com a #microblogpub server from Canada
social.fediversumi.fi a #iceshrimp server from Sweden
5deology.masto.host a #mastodon server from FranceDe-Listed servers: social.toonimal.xyz
ap.etherealhearth.io
lemmy.magnatranquillo.it
fennec.org.uk
vidya.dev
masto.oyd.app
blip.cf
macro.gay
cast.dagamant.com
lemmy.fnkysloth.net
akkoma.newt.li
mastodon.bastion.travisthieman.com
nunu.dev
social.bardia.tech
lemmy.probabilitydegeneration.xyz
lemmy.thesharpcheddar.net
writing.lol
hbjy.io
namknat.win
blog.main-vision.com
m.b1nk.net
lemmy.fediverse.jp
friendica.ownyourdata.site
kbin.mararead.com
1.test.jorisgutjahr.eu
posts.yasty.org
hanson.socialHelp others find a home, send them to fediverse.observer
-
It's interesting sitting here on an old version of #Calckey seeing someone on #Mastodon server telling their fellow user that posting to unlisted will opt-out of #search when I can see Unlisted posts in my antennas quite easily [though I believe this has been rightly rectified in the newest versions of #Firefish / #Iceshrimp but need to confirm]. Being hidden from the Explore tab on Mastodon is not the same as being unsearchable across the fediverse. Frankly, there's little understanding even among admins across the #fediverse about what's a Mastodon / Mastodon API function that is federated to other Mastodon servers but doesn't translate well outside of Mastodon on other #ActivityPub connected platforms like #Misskey and it's forks, #Hubzilla and #Friendica, or rapidly growing platforms like #Lemmy and #Kbin. Kbin also scrapes posts from across the fediverse and puts them into its own magazines.
Unfortunately simple, up-to-date documentation doesn't really exist to explain the realities of federation vs what your admin said was the reality. AP was not built with privacy in mind, and 'security through obscurity' was mostly a Mastodon thing from when folks thought either the Mastoverse was almost the dark web, or the whole fediverse [which has never been the case], and Google et al weren't interested in scraping it.
Unfortunately we have a cadre of devs across all fedi platforms who'll give glowing lip-service to both the fedi and ActivityPub histories of being built by queer or other minority identities but still won't work on giving folks the granular #privacy and #safety controls that weren't included in those protocols, and whose feature roadmaps now just look like bird site 2.0 funded by the milquetoast liberals in political tech who provide their seed money.
Beyond Mastodon and GoToSocial, every other fediverse project treats posting to public as opting in to search and indexing. Indeed, this is pretty much how the ActivityPub protocol handles such too.
#FediverseSafety #Mastodev #Fedidev -
Tbh, I'm on a proactively moderated server that has preemptively kept a lot of the worst folks from being able to reach us queers here, and the feedback from a handful of black users here is that #blahajzone has also been generally been harassment free in comparison to other servers they've been on.
Imo, it's actually not to hard as a queer or trans person to find #servers on the #fediverse that will protect you from harassment, but that it is harder to find servers that will also protect indigenous, black, Asian users from racist harassment. And too many queer white folks get a free pass for ignorance tbh, a privilege that many of us have had for far too long.
It's much the same on #Bluesky where I haven't been harassed for being #queer and trans - again there's large communities and plenty of allies - but anti-black racism has been in the spotlight again recently and the devs called out for lagging behind on safety and moderation features that bigots exploit for harassment campaigns.
Far too many fediverse projects are led by men, mostly white men, who are lionised, promoted and financed by another layer of mostly white men. They ultimately get the veto on minority protections.
#Mastodon #Firefish #Iceshrimp #FindAServer #FediverseSafety
RE: https://firefish.social/notes/9hs7vrern5ptmu66 -
Statement by @supakaity regarding the future of the #Hajkey fork of #Calckey #Firefish . It's becoming a downstream fork of #Iceshrimp #fediverse #FediverseSafety
RE: https://blahaj.zone/notes/9hl866g89i -
I hope #Hajkey keeps developing for blahaj.zone and similar communities, particularly the long sought after #FediverseSafety features that never seem to arrive on the #Fediverse and become more important as greater adoption occurs and user culture changes - like the amount of transphobic users that Lemmy has brought here and the dev bros think this is progress. #Firefish #Calckey #IceShrimp @[email protected]
RE: https://hachyderm.io/users/maegul/statuses/110767208159622462