From a #sharkey Dev to People On Fedi (pls boost):
While i understand that there's lots of drama around firefish, please do actual research. Sharkey is not and has NEVER been a firefish/#calckey fork, it didn't spring of from firefish. it started off as just an indipendent Misskey soft-fork(updates with misskey), there is no relation at all to firefish, it is incredibly damaging to call it a firefish fork, as the sharkey team actually spends lots of time just implementing features that people wish for (this include some features firefish has), while also spending time on making sure they work decently unlike (firefish some times)
also it's just as damaging to call Iceshrimp an offspring of the whole firefish drama now, Iceshrimp while an actual fork of firefish existed way before the entire recent firefish drama the only recent ofspring of firefish is #catodon and then again catodon is not trying to be firefish, catodon is its own thing it wants to sit inbetween mastodon and *key as a more userfriendly thing with alot of the "fun" misskey stuff removed, and #iceshrimp is doing a full rewrite of firefish in c#, none of these projects are even remotly similar to the firefish way of doing things, some of them aren't even in any relation to #firefish
tldr: stop calling things firefish sucessor, esspecialy don't call sharkey a firefish ofspring it was never in any way related to firefish
Okay, #Fediverse explorers with way more knowledge than I. What, exactly, are the differences between #Mastodon, #Firefish, and #Iceshrimp? I'm interested in what Iceshrimp has to offer, but I'm not finding a good explanation of the differences between the three forks. Any input is greatly appreciated. Thanks.
#FirefishEnde: >>Meiner Ansicht nach ist das kein Fundament für eine Plattform, die lang und zuverlässig betrieben werden kann, von daher gibt es Gedanken, zu alternativen Plattformen zu migrieren.
Wie einige vielleicht wissen, ist #Firefish keine vollkommen eigene Kreation, sondern eine Abspaltung von Misskey, dem "Hauptprojekt". Mittlerweile gibt es weitere Abspaltungen von Firefish und Misskey, die alle ihre eigenen Ideen umsetzen, wie beispielsweise #Iceshrimp, #Sharkey, #Catodon etc.<< so eine Ankündigung hier.
Ist es möglich, dass der Admin / die Admina einen kompletten
Umzug macht oder muss jedmensch selbst suchen was passen könnte?
Welche deutschsprachigen Instanzen gibt es, die von einem Admin-Team betreut werden, so dass ein ähnliches Problem wie bei Firefish nicht so leicht entsteht?
Gerne #Retroets, da das Thema ja sicher etliche hier betrifft...
Ich habe die Gruppe "FirefishTalk" (umbenannt in "KeyTalk", wobei das leider lediglich den Titel, aber nicht das Handle änderte) geschlossen und eine neue Gruppe"MisskeyTalk" erstellt. Ich hoffe, auch hier entstehen interessante Threads, die Nutzern und Admins ggf. weiterhelfen können:
Eine Gruppe für Nutzer und Administratoren des Fediverse-Dienstes Misskey für Fragen, Diskussionen, Anleitungen, Nutzererfahrungen, Hilfsgesuche, Hilfe und mehr...
In der Gruppe sind auch Nutzer und Admins der Dienste Sharkey, Iceshrimp, Catodon, Firefish und vergleichbare willkommen.
I have closed the group "FirefishTalk" (renamed to "KeyTalk", which unfortunately only changed the title but not the handle) and created a new group "MisskeyTalk". I hope that interesting threads will also be posted here, which may help users and admins:
A group for users and administrators of the Fediverse service Misskey for questions, discussions, instructions, user experiences, help requests, help and more...
Users and admins of the services Sharkey, Iceshrimp, Catodon, Firefish and similar are also welcome in the group.
Im honestly kinda disappointed in all the people jumping on catodon now and calling it firefish successor its kinda very bad as the devs don't intend it to be a firefish successor nor is it trying to be anything like firefish or misskey in general, talking about migrating to catodon while also calling it firefish sucessor is like punching the catodon devs in the face
as they try to create something simple for newer users, not something for existing key users that enjoy fun shit like MFM
please everyone do you research before spreading shit this is also very harmful to the project at least from my POV. if everyone starts hyping the project for something that it is not.
please just give @panos and @catodon some time, and don't put them under pressure for something its not.
If you want a Misskey fork that is unlikely to die as its a softfork (updates with misskey) anytime soon and is community focused and includes #firefish inspired changes go with #sharkey
if you really really want to stick with the firefish sort of thing of doing things try the firefish fork #iceshrimp
and if u want something new more geared towards new users / casual users try looking into #catodon
but don't just jump the gun on things u don't even know fully about
#Firefish hat sich aus #Misskey entwickelt, hat einige neue Ideen rein gebracht und den "asiatischen Touch" für uns leichter verdaulich gemacht.
#Iceshrimp ist ein Fork von Firefish 1.0.3, was wert auf Stabilisierung des Codes legt (also Bugs bereinigt bevor es an neue Features geht), ansonsten sich aber sehr stark nach FF anfühlt.
#Sharkey startete offenbar mit der Prämisse, dass der Code von FF inzwischen kaputt ist, und deshalb wurde so zu sagen zurück gespult: Sie setzen wieder auf Misskey auf und wollen eigene Änderungen so machen, dass sie Änderungen von Misskey einfach re-integrieren können. Das fühlt sich noch sehr nach Misskey an, aber die Dev Version sieht schon deutlich interessanter aus und zeigt, dass sie tatsächlich Community Wünsche umsetzen wollen.
#Catalon ist ein Projekt eines Teils des FF Teams. Laut eigenen Aussagen wollen sie trotzdem an FF weiter mitarbeiten. Catalon ist jedenfalls ein Projekt, dass in naher Zukunft nicht veröffentlicht werden wird.
So ist aktuell mein Wissensstand.
Aktuell sind all diese Projekte noch recht jung, deshalb ist es schwer abzuschätzen, welches davon ausreichend Puste haben wird.
Ich muss mir IceShrimp (und das Team) noch mal genauer ansehen, aber Sharkey geht in eine Richtung, die mir zumindest aktuell am viel versprechendsten aussieht.
Aber.. Firefish 1.0.5.RC läuft bei mir (und vielen anderen) gerade völlig reibungslos. Es gibt für mich also gerade keinen Grund zur Hektik. Ich teste und beobachte vermutlich noch ein bisschen die Alternativen. :)
.. und irgendwie warte ich auch noch auf ein offizielles Statement vom Firefish Team. Bisher kenne ich nur die Sorgen Dritter ..
Ich habe vorhin mal ein wenig mit #Sharkey herum gestestet, ich fand es bisher .. leider enttäuschend.
Verglichen mit #Firefish fühlt es sich wie ein (teilweise erhebliches) Downgrade an. Das ist schade, denn die Idee, eng am #Misskey Code zu bleiben, ist natürlich gut! Es lohnt sich auf jeden Fall, das weiter zu beobachten. :)
Ich werde mir als nächstes wohl #IceShrimp ansehen. Das ist eine Weiterentwicklung bzw eher Stabilisierung von #Firefish 1.0.3. Die Devs wollen fixen was da ist und gebraucht wird, anstatt auf immer neue Features zu setzen. Dürfte mir deutlich besser passen, aber es kann halt irgendwann auch "den selben Tod sterben", wie offenbar Firefish gerade: Zu wenige Devs.
Na mal schauen. Im Moment schnurrt meine Firefish Instanz ja, also keine Eile von Nöten. 🙂
Premier message posté depuis mon nouveau smartphone (qui me permet d'installer un client fediverse) :duck_disco:
En revanche, j'ai essayé #milktea sans succès, je me suis rabattu sur l'app mastodon classic qui fait le taff (même si bcp d'options manque à l'appel) #firefish#android#mastodon
Cc: @tournesol
Why is #iceshrimp repeatedly reminding me to post an #introduction even though I've already put up quite a posts? Keeps popping up, any time I refresh...
Rencontrez-vous aussi des soucis sur votre instance -key liés au flux principal ? Depuis que mon instance s' "agrandit" (en termes de pub/sub, pas en termes de comptes), le flux principal échoue de plus en plus à se charger avec la simple erreur "Une erreur est survenue".
Ca le faisait par moments il y a encore une ou deux semaines, mais maintenant c'est permanent...
Avez-vous rencontré ce souci ? Avez-vous trouvé une solution de contournement ?
J'ai vu un ticket sur le git de #iceshrimp mais ça n'a pas l'air d'avancer alors que c'est à mon avis un souci majeur...
I know that people who run #firefish servers are probably somewhat frustrated right now, since the project's last stable release was back in July. I do hope Kainoa gets more active and things start rolling again, however I checked the closest alternatives/firefish forks. Another thing that makes open source software great: you never run out of options!
So, #Iceshrimp still pretty much looks and feels like firefish, but they've added some nice (performance, mostly) improvements and also have better #mastodon api support. They also plan to do a full rewrite, which is quite an ambitious project. It's certainly a project worth watching.
#Sharkey on the other hand started as a firefish fork (from what I understood) but rebased to #Misskey v13 (Firefish had cut ties with upstream misskey on v12) and is building on top of that. This is also a great option if you like Misskey's direction but want improvements like post editing.
And finally with #Catodon, which is in the making and will soon be another option, we're taking a different approach. We'll implement some improvements from Iceshrimp, like the great work they've done on mastodon api support, but in general we won't exactly be taking the "improved misskey" direction. Instead, we'll be using Misskey/Firefish as our starting point, but we also want to simplify some things - as well as build extra functionality on top of the essentials. So some of the less important and useful features will be removed in order to offer a more consistent and user-friendly experience.
More on specific changes we're doing in a few days!
The number of Misskey forks continues to expand. How do we mention them collectively? I'm veering toward Forkeys, as in "Catodon is the latest Forkey to enter the stage." or "The Forkeys have one thing in common - emoji reactions."
I suggest checking them all out - each has their own strengths. :blobcatstrong:
I’m happy that I made the move to @Sharkey in late November as I was not really confident in the direction Firefish is heading. It was evident with the slow performance and local timeline would fail to load. Activity was decreasing on Sakurajima Social before the move because of how bad of an experience it was.
After the move, activity started to pick up again thanks to the improved performance. Misskey 13 resolved all the issues Misskey 12 forks are facing that caused Foundkey to go EOL with Firefish in the mess it’s currently in (Iceshrimp has the same scaling issues, but at least from what I heard, that team is at least responsive.
With Firefish Social in a worse mess as there are reports no new posts are being fetched, making the timeline 5 days old and the admins completely unresponsive. At this point, I don’t know if it’s even possible to migrate the account off Firefish Social if federation is not working on that server. This is why we dumped Firefish for Sharkey.
With that, besides our server, a handful of established Firefish servers are starting to jump ship to IceShimp or Sharkey. Infosec Exchange’s Firefish server transitioned to IceShimp. It should be even easier to migrate to Sharkey as there are documentation on how to do it.
I do recommend Sharkey over IceShrimp since it has a public timeline view (for visitors), more moderation tools and performance. The Sharkey Team is very responsive and helpful. Of course, they are adding back features that are in Firefish.
But I have a feeling that at the rate things are going for Firefish, it may have a bleak future ahead unless it can turn things around.
It’s unfortunate to see Firefish turn out like this, but it’s not surprising.
#firefish and #misskey seem to have problems with the WordPress Plugin. Could be the signature maybe!?! Is there someone who can help me debug this issue?
After looking at the changelog for #IceShrimp, I have to say I applaud their direction. They are focusing on the basics, and it may not seem flashy or new, but it sets the foundation for a more stable environment. Things like improved API performance, caching, and OAUTH enhancements have been re-worked. Kudos to the team for sticking to the core components instead of throwing out the razzle dazzle
I'm going to miss the longer post sizes and better post editing tools in #Iceshrimp or #Firefish. #Mastodon instances have some catching up to do in a lot of basic usability.
Oh well, it works, mostly, and I didn't feel like scrounging around for another Firefish or Iceshrimp server (or setting up my own).
:iceshrimp: Nouvelle MàJ 2023.12 Stable d’#IceShrimp !
Nous avons principalement consacré ce cycle de publication à l’amélioration des performances, nous espérons que vous aurez une expérience plus réactive !
Nouveautés principales :
Refonte de la recherche plein texte, retrait de Meili/Sonic/Elastic en faveur de Postgres gin_trgm avec prise en charge de filtres de recherche avancés.
Amélioration significative des performances du backend et de l’API.
Un cache HTML a été ajouté à l’API client de Mastodon, améliorant considérablement les performances (voir l’exemple de configuration pour plus de détails et d’options de configuration).
Les filtres de mise en sourdine des mots ont été complètement retravaillés pour améliorer les performances, en particulier à grande échelle.
Quelques régressions de Mastodon OAuth ont été corrigées.
Changement d’UI/UX
Les bugs des onglets «pages» et «galeries» ont été corrigés.
Les balises MFM centrale et petite s’auto-complètent désormais correctement.