@jerry Hi Jerry, looking for some help here to log in to my account. When I attempt to do this I just get a blank white screen (iPad) and a 500 error on Android phone. Can you please assist? TIA for you help.
Can you give it another try? It looks to be correlated with php running out of memory (not sure why your session would require more that 512MB of ram, but lets confirm that is the case first.
ok - I bumped up the memory limit in php to 1gb and that appears to have fixed the problem. I have no idea yet why it takes so much memory, though. But I'm glad it worked
Was there any data loss? The comments tab of my profile only shows 11 comments which only go back 1 week (perhaps to around this “we’re back” thread). I should have much more than that.
As part of the database clean up, I had to remove many corrupt records, so the answer is yes there are missing posts and comments, however I do have backups have I have been attempting to find ways to reinsert them without recreating the problems. I’ve not had much luck with that yet.
...and it's been fixed!
Credit to Melroy and asdfzdfj for picking it up and coding the fix in what ...7 hours?
For the wider audience, this is now fixed in the mbin code, it won't resolve here until next time @jerry updates fedia.io which could be a few days, or even week or so depending what other changes they've made and are making.
I did not update last night - there are many in flight code changes and I’d prefer not to cause more problems, so letting that settle down for a bit before I update.
Thank you! My 500 Server errors appear to be all fixed now. I'll try not to accidentally double post and then delete one of their thumbnails, if that still causes the error.
Ended up plagued with this again for a few days, and figured it was server-side issues.. but eventually thought "why not check in another browser", so I did, and the problem was gone.
I don't know what the problem was and if it's due to kbin, the swap to mbin, is fedia-specific, or browser-specific, or some-action-that-I-took-specific, but clearing all the cookies and data in my browser for fedia.io has put things back to sane. If you read this and are having similar issues, consider trying as much (remember doing this will log you out).
Officially not.. but the development slowed down too much and was too restricted by Ernest. I wanted to avoid a fork. But I didn't saw any good alternative.
Is Ernest OK? Maybe the explosion of interest was a bit too much to handle right now. Out of curiosity, why did you fork it to github and not stay on codeberg?
I don't know what is happening with Ernest, he said there were families issues. He did respond to me on October 3 for the last time. However, developers were NOT allowed to merge pull requests from others. He stopped developers from merging code. He couldn't let it go, which is a problem if you are not in for weeks or sometimes months. The issue was that development become to a halt, contributors were no longer motivated! I tried to discuss this topic with Ernest multiple times now, without any answers. At some point it was the final straw. I forked the project and introduce a C4 Wow based on trust, allowing dozens of people to have owner rights and giving back the control to the developers, contributors and users or admins.
Moving to GitHub was only done because Codeberg was down too often in the past year. Which was very frustrating when you want to work together with people. So I also moved to GitHub with GitHub Actions during the forking.
I was also trying to prevent a fork, but I didn't saw any way out. Hence the fork by the community, for the community. I hope so as well, the idea is that we work as a real team and active contributors have GitHub owner rights. We peer-review each other code and are allowed to merge pull requests. There is no single maintainer, we are all maintainers.
@jerry Hey, I had previously posted about this, but https://fedia.io/m/FirefoxCSS seems to be totally broken (404 error). Is this something you can look into (perhaps with the mbin folks)?
fedia
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.