Big update for Fedia.io - it’s not going anywhere
Big update for Fedia.io - it’s not going anywhere
First, I want to thank those who pointed me to mbin. I spent about 14 hours today with help from the mbin team on and off and found/fixed many problems.
Second, this post may not be very intelligible. I’ve been awake for a very long time.
In transparency, at one point today we were pretty convinced that fedia.io had been hacked. But it turns out that sometimes companies go out of business, cancel their servers but leave their domain pointing to that server. And sometimes a person like me is the next person to rent a server with that former customers IP address and then hilarity ensues when your nascent software recognizes that domain is pointing to itself and starts remaining links using the former company’s domain.
During the time I thought it was hacked, I rebuilt it. In doing so, it appears that I’ve fixed many issues that accumulated over the months as kbin went through successive updates.
We did also find a nagging bug in the markdown parser Fedia was running, which caused many (perhaps most) of the remaining error 500’s. I am not clear whether that is fixed now, but if not, we know where to look.
Based on my experience today with the mbin team and the progress of fixing issues, I am fully retracting my intention to shut down Fedia.io and will start working with the mbin team on some performance issues.
Thanks for the patience, everyone.
Glad I could help! I wasn't aware either you were giving up hope.
Since Mbin is community-focused I really hope this will result in a better connection, collaboration and both bug fixes and new features what the users and the admins wants. Again, Mbin isn't about me, I forked it because I want to create a community build on trust giving back the control to the developers and users. You now also have GitHub owner rights on the organization as you know. We are all maintainers!@jerry it really does take a crisis to make changes some times, doesn't it. I'm glad you found a solution!
Me too!
This is great news! I'm so glad that you found a solution that didn't involve killing the instance. Also, I've been trying to connect with Linus Torvalds account on social.kernel.org since I started on fedia but it never worked. Well it finally is! Thank you for working so hard on it.
youve prolly seen this by now, but...
Thanks for all your hard work! I was not looking forward to Fedia going offline...
@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)?
Thanks for everything you have done!
There are a few specific issues like that I have yet to solve.
Ok. I found the problem and will have this fixed shortly
this is fixed now
@jerry Thank you for the fix and fast turnaround!
Thank you for all your hard work. You and @melroy haven't given up on this community, and I'll stand by you too. I embrace the jank and appreciate the fine communities we've made here.
Melroy deserves all the credit
Hello everyone. If you care about fedia.io, please read this: https://fedia.io/m/fedia/t/350673
Note: it’s good news-ish
@jerry This is an interesting one! Too-aggressive nginx pattern match? https://fedia.io/m/fedia/t/350673/Big-update-for-Fedia-io-it-s-not-going-anywhere#entry-comment-2075163
Hope you get some rest :blobcatheart:
ok - this is fixed now
mbin? Is kbin dead?
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.
It appears so