I started out, like many, on #Mastodon, during the great Twitter migration. Not that I migrated from Twitter. No... I never had a Twitter account. Rather, I hoped that Mastodon could obtain the Network Effect, and help fundamentally alter the shape of social media for the foreseeable future.
So I made my own solo Masto instance and ran it for a good six months. It was cool. But then there was a glittery thing -- #Calckey -- that caught my eye. So I joined that. Pretty soon the maintainer of Calckey (young BTW) dropped out, but forks forked. I waited. Then #Firefish was the shit. But no...
Then, today, the admin of my former instance calckey.world made a new sharkey.world instance public, and I joined. #Sharkey is the new shit.
Because that's how I roll. On the Cutting Edge, baby.
I’m considering migrating backwards from Firefish to Mastodon. The “why” doesn’t matter. It’s something I’m contemplating for reasons.
I’m currently using #SpaceHost to run my single user Firefish instance, and my plan is to use them (or another) to host my single user Mastodon instance.
Same domain, btw.
I can’t find any info on this reverse migration. But it’s gotta be possible, right?
#Sharkey looks nice. I will write up a brief guide on how to migrate from #Firefish to Sharkey, and then urge users of calckey.world to migrate to sharkey.world.
I'll also re-install my own ruud.social to use Sharkey instead of #Akkoma.
Sadly it looks like #firefish is going to die a slow unmaintained death now, and I need to pick a successor to run.
#iceshrimp and/or #catodon appear to be the spiritual successors, but I think I'll be waiting to see who publishes and maintains a public Docker image first.
Just learned about the demise of #Firefish (head is M.I.A.). It's unfortunate for the thousands of instances running it, but with that comes #IceShrimp, #Sharkey, and #Catodon. All of them (I think) are being developed by former Firefish devs. Options.
Hopefully, current FF users are all, if they want to, able to move to another actively-developed community easily.
HEY YOU, YEAH YOU. I FUCKIN' LOVE YOU BUNCHES MANG.
Seriously, refugee here from the twinazi facestagram linkedspace kermudgeon-space. It's been rough out there, and it'll go through more rough patches when we get Threads and Tumblr and stuff.
But you're real people. I've already found my raw, real people here even though I don't really know any of the people I talk to on the daily in real life. That's how awesome this place is. It's gonna get filled with more people I do know, and tons more I don't, but the algorithm is nada and the filtration system to whatever I want to see is there. And so are you. And that makes it PERFECT!.
Finally made the jump off #FireFish, and swapped the live server over to #IceShrimp. Not an entirely smooth process if I'm honest - the migration instructions take a bit too much for granted. I've made records though, so I'll try to suggest alterations. Anyway, nice to be here 👋
I absolutely love the #Sharkey instance I'm on, #sakurajima.social. Being able to load it up at any random time I want and finding it available and waiting for me rather than me waiting for it to be back up again is a privilege I do not take lightly.
That being said, I kinda wish there's a way to personalise (Sharkey) for myself further since there are 2 things I miss about kitsunes.club, another Sharkey instance. The default "Like" emote on there was a red heart, it's a star on here - which is fine, but I wish there's a way to set our default "Like" reaction to be for our account. Another thing I missed from kitsunes is its font was a lot more pleasant/readable for me? I've no idea what typeface they're using, but I'd love to be able to configure a font for Sharkey specifically for my account but that's probably tougher to implement. The font used on here is more akin to the one used on #firefish.social.
UPDATE:
THERE IS a way to set the default like emoji for your account on Sharkey. The setting for it resides in Settings > Emoji picker > Default like emoji.
The typeface used on kitsunes.club is the default font used by Sharkey, Lexend. sakurajima.social made a change to use the font, Myriad Pro. You can restore the default font used by adding the provided code block from the following link to your Settings > General > Custom CSS.
I just discovered that my #firefish account (@irfan) might have already been "migrated" to this account, but my connections/followers did not come with lol - so I'm gonna probably initiate following my (old) connections on here first from an old backup of my following list on there.
It doesn't matter if you are new to the #fediverse or if you have been here forever, it's always good to keep in mind that (a) what server you pick, and (b) what software that server runs, matter.
I should admit am fairly new at this. I created my first fediverse account only a year ago. It was a #mastodon server with about 8,000 users. And while it "worked" there was something missing from the experience.
While researching the idea of hosting my own server, I discovered #FireFish which in turn led to discovering #IceShrimp. It's hard to describe how much better the experience is with IceShrimp.
The #UI is just so much better, and the feature set way more robust. The way it handles replies, the ability to quote, to use multiple emojis, etc.
If you have friends or family thinking about joining the Fediverse or are feeling unimpressed with your mastodon experience, I highly recommend getting an account running IceShrimp or other similar software.
Probably also worth mentioning that I also looked at using a #Wordpress integration and #Hubzilla#GoToSocial#Pleroma#Humhub and #Streams. I found them to be clunky; reminding me of how email was in the early 90s.
If the fediverse is going to thrive, then it needs to make a good first impression. Moving beyond mastodon is a good step in the right direction.
An interesting feature of the Misskey forks (#Forkeys) is Pages, long form posts with a CMS editor. I wrote about it, and the changes you can expect over the next year! Check it out.
After giving this a lot of thought and discussing with the wonderful people that build Iceshrimp, #Catodon will rebase to #Iceshrimp. We feel that it's the right decision for the road ahead, as Iceshrimp is another #firefish fork that focuses in improving performance and they have already done some amazing improvements, like full Mastodon API support. With Firefish's future uncertain, we think it's better to stay closer to an actively maintained project. The two projects will stay distinct, as we have different design goals, but we have a common codebase so we feel this makes sense.
Just to be clear on all fronts and to answer the obvious question in advance, yes, Iceshrimp is also currently doing a full rewrite in C#, which is a few months away, and we haven't decided if we'll adopt this yet - it's a strong possibility, but we're keeping our options open. We're confident they're doing a great job, still, we'll weigh what the best decision for Catodon is on this when it's ready and the time comes.
Just wanted to let you know that this might push Catodon's development back a little, as it's sort of a structural change, but we feel that it's worth it, and that it might be better for the broader community. Catodon development will resume once rebasing to Iceshrimp is finished, and then we'll have better foundations to build this on.
This development makes me very happy. #Iceshrimp is a project that involves many people who were important in #firefish development but were unhappy with how things were handled there, so at some level it feels like righting a wrong and bringing the broader community closer together - even if we've ended up with two projects, both of which I feel that cover different needs though. This is also an answer to everyone who thought that our corner in the fediverse was falling apart. We have a healthy ecosystem, we have ways to communicate and stay on good terms - let's build bridges, not walls! I like the place we are right now. Nature is healing =)
Ich werde der ein oder andere Person einen #Fediverse#Account auf meinen #Server ermöglichen und habe dazu eine allgemeinere #Domain als meine eigene crazy-to-bike.de registriert.
Nun stellt sich noch die Frage nach der richtgen #Software für die #Instanz.
Das gefällt mir aber im Vergleich zu anderen Möglichkeiten weder optisch, noch finde ich die #Zeichenlimitierung gut.
Derzeit bin ich ja auf #Firefish unterwegs, aber das scheint den letzen Prognosen zu Folge ein höchstwahrscheinlich totes Pferd zu sein.
#Sharkey als weiteren #Misskey-Nachfolger #Fork teste ich gerade auch, was für mich eine mögliche Alternative zu Firefish ist. Aber auch dieses Projekt ist ja noch sehr frisch und in meinen Augen einfach nicht absehbar, wie dauerhaft das Ganze fortbesteht.
Auf #Friendica war ich ja auch schon eine Zeit lang unterwegs, aber das ist optisch auch sehr angestaubt und hat bei mir auf dem Server auch datenbanktechnisch rebelliert.
Ich weiß, dass es noch eine ganze Reihe Alternativen gibt, will und kann aber nicht alles durchprobieren.
Daher hoffe ich auf gute Tipps.
Wichtig ist
kein, hohes oder einstellbares Zeichenlimit
gute Strukturierung und Kategoriesierung von Lesezeichen (wie bei Firefish und Sharkey mit den Clips)
Folgen von #Hastags und / oder Begriffen (wie bei Firefish und Sharkey mit den Newspickern / Antennen)
gutes, ansprechendes und leicht bedienbares responsive Design für die Nutzung auf dem Smartphone (oder volle Unterstützung durch eine App wie bei Mastodon)
Schön wäre
Konfigurierbarkeit des Speicherverbrauchs durch die Föderation (was wird wie lange auf dem eigenen Server vorgehalten) wie bei Mastodon
automatische Löschung von Beiträgen konfigurierbar wie bei Mastodon
hohe Wahscheinlichkeit einer nachhaltigen Weiterentwicklung
Moderierte Kontoerstellung wie bei Mastodon
Je länger ich hier schreibe, denke ich, dass Mastodon für sehr vieles davon wohl die richtige Software wäre - will ich aber eigentlich aus Gründen nicht.
How did we go from way too many semi popular english Misskey forks to literally only having one soon (Sharkey)
Firefish kinda had its moment but currently doesn't seem that much will happen
Foundkey while still maintained is not really meant for more than one user instances
Iceshrimp is currently doing an full C# or well rather they are doing their own thing not using the MisskeyAPI and also rewriting the frontend, which means when thats done they aren't really part of the Misskey Family of forks anymore
Catodon, from the start is not trying to be anything like misskey and more like a user friendly mastodon-key mix, but they are also interested in using Iceshrimp as a kinda upstream meaning they would also not be part of the Misskey Family of Forks
how did we go from #Sharkey being hated on for being another #misskey fork, to it being the only major true english misskey fork left, if #firefish doesn't comeback to life and if iceshrimp continues its rewrite