Ok, so apparently #Sharkey has ListenBrainz integration, but I'm not sure how it works :neofox_googly_shocked:
There's a text field in the user settings that just says "ListenBrainz", but doesn't explain what I'm supposed to type here. Do I just need to type my username, or am I supposed to copy and paste my user token? :neofox_googly_shocked:
Hey, @bumble, do you happen to know if lists will work properly soon in #Sharkey? I have the same problem with lists as over at Firefish: They only ever show the last added account's posts. Tried to remake the list already - but the problem persists. :blobbee_sob:
What’s a good #Sharkey client on #iOS? It almost seemed like I was able to log into my instance on #IceCubes but it kept just pushing me back after the consent release. The #PWA works really, really well though and is actually better looking vs #Firefish.
one issue i'm having with is that with lists you can't tell it to 'hide from home timeline' which was very convenient because it allowed me to follow news bots without clogging up my home feed #sharkey
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.
For anyone who has moved from Mastodon to any *key variant, do you feel like your engagement is different?
I feel like I don't get quite as much interaction as I did on mastodon. Part of it could be the instance I was on (shout-out to urusai.social for being awesome!) But I feel like it's different since I moved to Firefish and now to Sharkey. I try to use hashtags in my posts too, but I don't know if that is helping or not. #fedi#sharkey#firefish#mastodon
i may have mistranslated some of #Sharkey while translating it to #Turkish 'cause I forgot some of the contexts and I am conducting this with very little thinking so if any error occurs please let me know! At the end of the day I'm a human and to err is human.
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.
2 Months ago: #sharkey is shit, its basicly misskey, why would anyone use this, firefish is way better
Now: #sharkeyhype, firefish is on fire help, sharkey so good, there was a calckey hype now theres a sharkey hype the cycle is repeating itself
How in the fuck did this happen xD
That said instead of shilling and hyping sharkey, u should actualy help the project by making issues, making pr's or just involving yourself in the project any other-way, having a community that is actively involved is way better than high user numbers
We finally have a statement from the former Firefish owner/lead Developer. It seems that the Firefish site and Gitlab is given to one of the maintainers. Still, I kind of consider it EOL as the new person in charge isn't a programmer. It's pretty much doesn't change anything unless a new lead developer decides to take on the project. I do wish Kainoa the best in his future endeavors.
There are other options, such as Sharkey, IceShrimp and Catodon. However, IceShrimp is doing a rewrite in C#, so it's basically going to be it's own thing, which might be interesting to try, but not something I would use outside of personal use. Same with Catodon, which might use IceShrimp's C# rewrite.
I have a lot of trust in Sharkey's team in making sure something like this doesn't happen while making it community driven. Taking the Glitch-soc approach like with Mastodon will make Sharkey a more viable option since it’s just Misskey with extra features, some making it to mainline Misskey like with some things from Glitch-Soc making it to vanilla Mastodon.
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. 🙂
I really wish there's a draft feature for #Sharkey/#Fediverse (or for it to be more common to have if it's available somewhere) so I can stop using #Signal to note down posts I'd like to write about but can't be bothered to do so just yet.
The reality is, you always take a chance when contributing to an open source development or projects. Just because you made a contribution, does not mean you own the project or can decide the path that project takes. Those of us who donated understood the risk (or at least, I hope most people did).
That said, when someone takes a proactive driving stance claiming they will deliver, you kind of hope you can take them for their word. And expecting the main website to be online is not a big ask, especially when that serves as a gateway for people to learn about and use the project you are funding. That, after all, was the reason I donated.