Reading this, made me realise that waiting for #firefish to return with some sort of action/decision about helping (or not helping) me to export my notes which I haven't received for over a month now might not be the best idea.
Things could get worse and firefish.social could simply go down (permanently) and I might just lose my account/connections entirely (instead of just my posts). I'd migrate my FF account here and now, but while this instance is great and snappy and have a much better lead/maintainer at the helm, it's getting frequent downtimes that doesn't seem to be easily solvable from my POV.
I'm getting some things straight now and hopefully I'll be able to migrate and dump FF for good, here or elsewhere I have in mind.
#Misskey and #Firefish Advent Calendars - learn something new about these platforms each day of December! It feels very indieweb / geocities and I love it.
My fellow english speakers - it will require the use of a translation service, but those are in about every browser nowadays, so no excuses.
Side note: What word keeps being translated as "mackeral" - is it "platform" or "instance"? 😆
Went to #firefish dot social just to see how it’s going, having heard bad things a couple of weeks ago.
It was errors everywhere, nothing working at all. The server’s own numbers show a major fall in users since sept.
So I think I’ll call it a day for me and firefish … that little fedi-episode was sure interesting.
Sad part is it’s main effect seems to have fragmented the whole misskey fork subset of the Fedi, which could have really done with a solid English-lang *key against masto-dominance
The scaling issues aren't entirely the fault of the devs. Until servers got popular enough this issue lay dormant, and we've seen some herculean efforts by instance runners to keep things working but sadly it appears to be a fundamental issue with the misskey v12 codebase, that was also affecting Misskey itself.
Iceshrimp is similarly afflicted, I believe.
But Sharkey is based on the v13 codebase which saw Misskey work hard to overcome the scaling problems. If they've done enough then Sharkey might be the stable platform with longevity we all thought Firefish was back in March.
Not all of the current state of affairs is technical, however. Firefish also suffered from concerted attacks on the lead dev, started by Mastodon.art (who else?). Additionally, support cooled and then split off almost immediately as Iceshrimp appeared. Disagreements about the direction Firefish was taking, the alleged focus on Fun features over User Safety, and even grumbles about finance partners all combined to damage Firefish as a venture.
Hopefully lessons have been learned so Sharkey can have a decent chance. I find Mastodon really lacking, and even Pleroma/Akkoma don't quite nail what Calkey et al got so very right.
I have some very exciting news to share - or at least they are exciting to me! Drumroll... we've started working with @namekuji on a new #fediverse project! It will be based on #firefish but the idea is not to create an "improved firefish" (or #misskey), but more or less a new platform. We wanna get creative with it! That's all I can say at this point - we'll have more info to share soon. I can tell you one thing: This will be an amazing ride!
Is https://firefish.social usually so slow? Was looking to see how things changed since I last heard about it and man that instance is SUPER slow to load everything, is this an instance issue or a firefish issue?
@Arataka at the moment it seems to be a dead instance. Too many problems too often with an admin distracted by other things now and not actively maintaining the instance.
Unless there’s contrary information and I’m out of the loop I’d say stay away and consider firefish to be a bit more hype than it’s worth. Other Misskey forks are out there.
@maegul Ah, yeah I was looking to mess around with some other federated software, I might see how Sharkey is seeing that is also uses the Mastodon API which is a must if you want to use any good mobile apps lol.
Because of the antenna issue on firefish I spent the last few days testing other software...
What I discovered is basically I didn't understand how federation works and it actually works a lot worse than I thought :blob_notlikethis:
I thought it was something like: if your server is connected to mastodon.social, your server will pull mastodon.social.
It's actually that if your server is connected to mastodon.social, it will only pull posts from people that are followed by people on your server from mastodon.social, and posts boosted by those people.
This makes the antenna issue a lot less important because realistically if I want to discover other artists and other esperantists who aren't already known to me, I basically need to have an alt on mastodon.social to follow those hashtags to identify new people for my main account to follow.
Why not just move to mastodon? Well, *key instances have the feature set that I am interested in using for my actual posts. Aspects of fedi-culture which stress other people out like alt-text do not really bother me... needing to keep my posts within 500 characters, and being unable to react with an appropriate emoji is what stresses me out :blob_sweats:
I guess this leaves a question: why not a better federated misskey instance? Well, I feel comfortable here.
Also tbh learning that this is how federation works makes the constant defederation drama on here even more inexplicable. Users receive posts from awful people in timelines because someone in your group is following awful people or someone one of you follow is boosting awful people. Awful people find users to harass thru well federated servers like mastodon.social... same as I will find more artists to follow thru there. The only way out of that is allow-listing rather than block-listing is my guess.
I have been seeing lots of talk about #Firefish and the "dumpster fire" that FF social has devolved into. I have a lot of sympathy for the dev team finding as we have here at blahaj.zone that FF/IS doesn't scale well. The devolution has been more public over at FF social cos Fedi's own Guy Kawasaki was hyping it up and was part of the team until it wasn't producing the results he expected and he slinked off. I wonder if the seed funders have done the same. Chris and Kainoa had separate funders, both involved in political tech. I think they were hoping to throw some seed money at something that wouldn't drag the chain like Mastodon development and be the new Twttr for liberal politics to electioneer on. 🤮 Kainoa told me who his funder was and from that point I haven't promoted Calckey/Firefish since.
Gotta love the "but we're the good guys" tech VC people, male, white, older, cishet, been "around" social tech for a while, looking to ride this Fedi thing into "significance"/"success", who found their side project who they fed "advice" to without any real stakes/responsibility. And when Kainoa wasn't the 10x dev they hoped, they've jumped ship, not that they could do any better.
It would be nice for the sake of transparency that there was some kind of repository where such funding was disclosed. Ironic when one of the funders is about protecting democracy. #Fediverse#FediDev#FediDevs
is my shit completely broken or is firefish fucked now? i cant use stop.voring.me at all the site doesnt even load; i tried signing up for ff.social and i cant post, tf is going onn? #fediverse#fedi#mastodon#firefish#calckey#pleroma
Ich poste im Moment längere Beiträge auf Firefish und muss aber dann von meinem Mastodon Account aus weiter kommunizieren, weil die Antworten nicht auf dem Firefish Account ankommen. Sehr, sehr merkwürdig 🤔 #Firefish
What's the status of federation between Lemmy/KBin and Misskey/Sharkey/Firefish/Iceshrimp? I just tried loading several Lemmy and Kbin posts in Sharkey and it doesn't work. I remember having the same issue with Firefish, and I vaguely recall hearing awhile back it was something related to authorized fetch. Have their been any recent developments on that front? #FediQuestions#FediverseQuestions#Threadiverse#Lemmy#KBin#Misskey#Sharkey#Firefish#Iceshrimp
@183231bcb
lemmy posts are not visible on the *keys > regarding kbin: it depends - adding a link on kbin will result in invisibility on the *keys > every other kbin post type (thread, post, photo) should appear on *keys timelines
#firefish sieht nett aus. Ich hätte aber Fragen dazu und leider ist es schon wieder so, dass ein Administrator dieses Netzwerks es nicht für nötig erachtet, eine höfliche Anfrage mit Beachtung zu beschenken.
Und? Hast du dein Anliegen nach mehreren Empfehlungen aus diesem Thread schon an die @askfedi_de gerichtet oder hast du ein Problem UND die Kenntnis, dass dein Problem NUR von einem echten, einem ganz bestimmten Admin gelöst werden könnte?
Eins ist sicher: solange du dein Anliegen nur an Admins richtest, können dir defintiv NUR Admins helfen!
Hmmm apparently if you move from server A to server B then back to server A, your followers don’t come back with you.
Looks like 2/3rds of my followers didn’t migrate back when I moved from @therealahall. I don’t think there’s anything @jerry can do but good to know for fellow #mastodon and #firefish migrators like myself.
I have all of the data, maybe there’s something I can do on an import?
@jerry@therealahall yeah I kind of figured that was the case since you don’t own the external servers but figured I’d shout it out anyway. My loss of ~50 followers won’t kill me even though that is well north of of half of what I had 😂
This just means, much like the Bears, I’m in rebuilding mode.
Hi ! i'm trying to connect my firefish.social account to lemmy : jlai.lu. It's stuck in a never ending loop : "processing"
I searched some info about it without any success. Does Firefish support Lemmy ? Anyway, it works very well with Mastodon. Thank a lot for your help ! :)