Post AcubppmasaoFuZPY5Q by tallship@neenster.org
(DIR) More posts by tallship@neenster.org
(DIR) Post #AcubppmasaoFuZPY5Q by tallship@neenster.org
2023-12-17T19:54:23.031393Z
1 likes, 3 repeats
Okay I stopped plugging Firefish about three months ago. I thought the issue was just local to me but then I discovered this is likely systemic - at least on this, the “new” flagship, reference server.I’m merely going to copypasta below, because I was completely unable to respond directly as a local user on the firefish.social instance itself.The problem has been so bad, for so long, that I had some time ago resolved to just use my Fedilab Android client for all interactions on my Firefish account, but over the past few days I haven’t even been able to perform remote boosts and web access is so broken…. Well, here I am, posting that copypasta from a reliable Pleroma server instance.From most platforms, I couldn’t even pull up the user (Erik Harris) or the post itself, including masto servers, but Pleroma has always been a surprisingly capable when the chips are down.I’ve included two screenies too. The breakages are obvious in a visual way so I’m not going to provide alt-tags - suffice it to say it’s virtually equivalent to a Microsoft BSOD.Kainoa, please help.I’m hoping, after reading so many mentions and pleas from others with local accounts on Firefish.Social, this post will be of some help in fixing some seemingly very serious bugs making the Firefish instance in question almost completely unusable, so without any further adieu….Originally attempted post follows:@ErikHarris @kainoa I’ve been hearing about and even myself having major issues like that which you describe (Brave, Vivaldi, Chromium, Firefox - each tested on both Android and Desktop (win/Linux).I can often click the retry/submit button several times over and over and eventually have a semi-usable state, but still cannot tell when replying to a post will fail or changing feed scope will bork the interface. I never not have major error issues, and sometimes it’s just a black screen or one with a single caricature in the middle of the black background. Sometimes a refresh will yield more, more likely it won’t on those particular days.I never not have problems trying to expand a thread, it’s almost completely unworkable, so I end up copying the URL and pasting it into another Fediverse instance’s interface to follow threads that I want to read.This has been a persistent problem since attempting the account migration from Calckey to Firefish - the steps were followed a few times and migration was never sufficiently successful but at some point the migration just appeared to be completed… But half-broken ever since.I just figured it would work itself out eventually, following an update or DB maintenance, but the issues have remained pretty consistent - enough to stop pumping the advocacy for Firefish for a bit until the issues are cleaned up anyway and I don’t see reports about it regularly. Usually, a bug is something rather singular and reliably recreated, this is rather comprehensive and inadvertent enough that documenting the behavior would fail to produce something reliably recreated.At first, I thought that it was a result of me borking the migration - I did seek support help and that was what was related to me. Later, after carefully re-reading the instructions, I was able to determine that I did follow the somewhat vague instructions to the letter and in the proper order, so the borkage occured when the process was properly applied. The sad thing is, I was merely going to just start with a completely fresh account but wanted to undergo the official process for migration and report any irregularities.My original account was on the flagship/reference Calckey instance, which was migrated over to this instance in the midst of the period when the product renaming was underway, IIRC. I hope this info helps, as much as it’s mired in generalizations and dependent on vague memories of the transistion. #tallship #calckey #migration #Firefish ⛵.