fedia

This magazine is from a federated server and may be incomplete. Browse more on the original instance.

elouboub, in Big update for Fedia.io - it’s not going anywhere
@elouboub@kbin.social avatar

mbin? Is kbin dead?

jerry,
@jerry@fedia.io avatar

It appears so

melroy,
@melroy@kbin.melroy.org avatar

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.

elouboub,
@elouboub@kbin.social avatar

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?

melroy,
@melroy@kbin.melroy.org avatar

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.

melroy,
@melroy@kbin.melroy.org avatar

Ps. this issue was already going on for the past few months. Causing Kbin development to slowly halt further and further.

elouboub,
@elouboub@kbin.social avatar

Thanks you for the background. Pity codeberg was down so often. Probably german internet, lul.

Hadn't heard of C4Wow. Looks like you could add MBin to the list of implementations at the bottom of the page.

Good luck! I hope it works out :)

melroy,
@melroy@kbin.melroy.org avatar

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.

nisik, in Big update for Fedia.io - it’s not going anywhere
@nisik@fedia.io avatar

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.

Australis13, in Big update for Fedia.io - it’s not going anywhere

Thanks for all your hard work! I was not looking forward to Fedia going offline...

hitstun, in Big update for Fedia.io - it’s not going anywhere
@hitstun@fedia.io avatar

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.

jerry,
@jerry@fedia.io avatar

Melroy deserves all the credit

bentoh, in Big update for Fedia.io - it’s not going anywhere
@bentoh@mastodon.online avatar
yoasif, in Big update for Fedia.io - it’s not going anywhere
@yoasif@mastodon.social avatar

@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!

jerry,
@jerry@fedia.io avatar

There are a few specific issues like that I have yet to solve.

jerry,
@jerry@fedia.io avatar

Ok. I found the problem and will have this fixed shortly

jerry,
@jerry@fedia.io avatar

this is fixed now

yoasif,
@yoasif@mastodon.social avatar

@jerry Thank you for the fix and fast turnaround!

petterroea, in Big update for Fedia.io - it’s not going anywhere
@petterroea@infosec.exchange avatar

@jerry it really does take a crisis to make changes some times, doesn't it. I'm glad you found a solution!

jerry,
@jerry@fedia.io avatar

Me too!

jerry, in Big update for Fedia.io - it’s not going anywhere
@jerry@infosec.exchange avatar

Hello everyone. If you care about fedia.io, please read this: https://fedia.io/m/fedia/t/350673

Note: it’s good news-ish

annika,
@annika@xoxo.zone avatar

@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:

jerry,
@jerry@fedia.io avatar

ok - this is fixed now

skullgiver, in Cannot reply… Snubbed by the machine. (Cloudflare problem?)
@skullgiver@popplesburger.hilciferous.nl avatar

Is this a Cloudflare problem? Without any error messages this may as well just be a Fedia bug. Every other Kbin user seems to be posting comments just fine.

the client is javascript after all

How edgy! It’s written in Typescript, though.

Best advice I can give you is to open up the dev tools and look for the exact error message that Kbin is hiding from you for some reason. Also do the usual checks (disable adblockers/all addons, try another browser, etc) for browser related issues.

ciferecaNinjo,

Is this a Cloudflare problem?

I guess not. Today I was able to post there.

Though there’s another odd behavior: my profile shows all my own posts except the posts in that #lemmyWorld thread. But I do get notifcations if someone replies to me in that thread.

Every other Kbin user seems to be posting comments just fine.

I don’t see how you could know that. If someone is blocked, there’s no metric AFAIK.

kubica, in Cannot reply… Snubbed by the machine. (Cloudflare problem?)
@kubica@kbin.social avatar

If you retry it doesn't let you? From kbin I saw an error trying to reply to a post, but then I retried and it worked.

ciferecaNinjo,

I’ve retried several times, even with a long delay. I also tried re-entering the thread (which is often the fix for kbin-specific failures) and that did not work either.

(edit)
Note that to send this reply to you here in this pure kbin mag I had to submit twice. But in that #LemmyWorld even many retries makes no difference. I would love to have a text-based client about now.

skullgiver,
@skullgiver@popplesburger.hilciferous.nl avatar

I would love to have a text-based client about now.

Lemmy has github.com/mrusme/neonmodem

The same person who runs Fedia.io also runs infosec.pub, so you could try using neonmodem with that Lemmy server without handing your data over to a new person.

MHLoppy, in 404 error when trying to visit external mag !orgmode@kbin.social
@MHLoppy@fedia.io avatar

I know I'm rather late on the response here, but my understanding is that each instance takes some time to discover the existence of a mag/community on another instance, particularly as it only checks the first time somebody searches for it (on that instance). I have unfortunately noticed that Fedia is often very slow for this. It took a week or two to pick up a small visual novels community I looked at a couple months back, and it still hasn't picked up @RimWorldPorn_General (SFW), which I searched for 3+ weeks ago.

Whether this is a Fedia-specific issue, a kbin issue, or something else I'm not sure. You might be able to get more input from asking on one of the larger fediverse-focused subs like @fediverse or @fediverse .

e569668, in 500 server error when trying to visit external magazine
@e569668@fedia.io avatar

Maybe gremlins, looks like it's working now. (I have noticed some 500s, but I assume jerry is still running his auto-null-image-fixer script and it will start working eventually). It's empty though as is the case with federation they don't automatically pull in things until added so the past content isn't there

e569668, in What determines the landing page timeline <https://fedia.io/>?
@e569668@fedia.io avatar

You can set the default landing page here https://fedia.io/settings/general it's the first option for homepage. The options are all, subscribed, favorites, and moderated, make sure to click save near the bottom and not the delete account button.

The closest you can get is blocking those domains, it won't remove everything from them but there isn't a block instance option at the moment, so remote link posts will still appear from them.

LiquidApricity, in Quick update

Cheers Jerry

shiihs, in Quick update

Extra points for perseverance to you!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • fedia@fedia.io
  • random
  • meta
  • Macbeth
  • All magazines