@melroy@kbin.melroy.org avatar

melroy

@melroy@kbin.melroy.org

Software Engineer & DevOps Architect. Mbin contributor (and creator of the fork).

He/him 🇳🇱

Mastodon - Matrix - Homepage - Donate me

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

melroy,
@melroy@kbin.melroy.org avatar

Searching on the handler should indeed find & create the user if not present:, eg. https://fedia.io/search?q=%40Gaeilge%40kbin.social However, fedia.io still seems to return "Empty". I tried to do the same on my instance and that worked.

I'm not sure what goes wrong, assuming kbin.social didn't block fedia, then I suspect some kind of issue at fedia.io. I believe we need to debug this issue on the server-side. Hopefully @jerry can have a look at his logs when trying to execute the search query above and maybe find the root-cause that way.

melroy,
@melroy@kbin.melroy.org avatar

He user only now seems to exists (created 1 day ago it says): https://fedia.io/m/Gaeilge@kbin.social. So yes it seems to work fine!

@FarraigePlaisteach @kbal be sure you are logged-in before doing this search.

melroy,
@melroy@kbin.melroy.org avatar

Mbin was created to get kbin to the next level.

melroy,
@melroy@kbin.melroy.org avatar

It is good to really see your true nature now. I'm also think the fork is the best thing that could have happened for the community. It's a pity that you never started a conversation, but instead you still try to do mean things like this.

melroy,
@melroy@kbin.melroy.org avatar

Ow.. it was 100% intentional. You said it yourself: "Wiem, szczerze mówiąc było to celowe. Zauważyłem, że forki synchronizują od razu zmiany z /kbin.". https://karab.in/m/karabin/p/340377/Usterka-z-crosspostami-nie-zawsze-sa-przyporzadkowane-odpowiedniemu-watkowi-matce-at-ernest#post-comment-510980

melroy,
@melroy@kbin.melroy.org avatar

I know your approach on PRs. Hence the main reason of the fork. The community does believe in their people and the good in mankind. Only 1 approval is required from another maintainer for now. We are using C4 way of working.

melroy,
@melroy@kbin.melroy.org avatar

Well I don't have a bad opinion about him (those are your assumptions), we just didn't agree on how a community project would/can work.

If however he did introduce intentionally a bug in kbin, just because of Mbin that's downright childish. The Mbin community does try to test all the incoming PRs (not just kbin sync PRs) on various instances apart from unit-tests, etc. We just do not want to depend on a single maintainer, hence a different way of working in the project.

He saying Mbin can't handle the kbin changes that is just not true (Odpowiedź: nie radzą sobie), at least we try to keep in sync (eg. for API comparability for upcoming mobile clients). But I'll leave it this, I'm not going to waste any more energy. I hope you understand.

Thanks for your recommendation.

melroy,
@melroy@kbin.melroy.org avatar

Thanks for your feedback.

We do have code reviews in GitHub and discussions on Matrix. We updated the README that reflect our latest way of working. As stated in the comment section we are also working on it in PR: https://github.com/MbinOrg/mbin/pull/34. Feel free to comment on that.

melroy,
@melroy@kbin.melroy.org avatar

That is correct, we do not have an "official" instance or an "official" magazine. What follows now is MY OWN opinion, other community members might think differently.

Mbin is aiming for a federated and decentralized social network, I think the whole point of the fediverse is that there shouldn't be one main instance, right? Feel free to create a magazine where ever you want! Isn't that the beauty of activitypub? Maybe the idea takes some getting used to.

melroy,
@melroy@kbin.melroy.org avatar

kbin.social is the official instance of kbin ;)

melroy,
@melroy@kbin.melroy.org avatar

Despite the fork. I hope we can learn from each other indeed. That will only benefit both of us.

Although we merge into main it's not a release, we use GitHub/Docker tags to mark releases. And use semantic versioning if needed for minor and patch releases.

melroy,
@melroy@kbin.melroy.org avatar

I feel a bit of negativity from you. This will be my last reply in this thread. She has resolved it herself by creating a magazine by herself on Mbin for Mbin: https://kbin.run/m/Mdev

melroy,
@melroy@kbin.melroy.org avatar

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!

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.

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.

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.

melroy,
@melroy@kbin.melroy.org avatar

https://kbin.melroy.org is running the latest Mbin version. Which is a fork of Kbin.

melroy,
@melroy@kbin.melroy.org avatar

Which is now also running the forked version (Mbin).

melroy,
@melroy@kbin.melroy.org avatar

The more the merrier ;)

melroy,
@melroy@kbin.melroy.org avatar

I also pinged Piotr.

media.kbin.social has an expired certificate (kbin.social)

Not sure where to report this exactly but media.kbin.social has an expired Let's Encrypt certificate (expired Tue, 03 Oct 2023 14:47:25 GMT) and this is causing problems loading various images across the site -- e.g. user avatars (sometimes), images copied from various Lemmy instances, and image threads made on kbin....

melroy,
@melroy@kbin.melroy.org avatar

I also pinged Piotr directly.

melroy,
@melroy@kbin.melroy.org avatar

Ps. these are Let's Encrypt certificates. Something isn't correctly configured on the server. Failing to renew this media.kbin.social domain. I do not have the correct credentials to help out here, but I do know certbot program should NORMALLY auto-renew these TLS certificates. To avoid this issue in the first place from happening.

melroy,
@melroy@kbin.melroy.org avatar

API is part of the latest develop branch. And live at: https://kbin.melroy.org (Docs: https://kbin.melroy.org/api/docs).

melroy,
@melroy@kbin.melroy.org avatar

API is part of the kbin code base (on latest develop branch). For example https://kbin.melroy.org also have API enabled. But kbin.social is still not upgraded until this day.

melroy,
@melroy@kbin.melroy.org avatar

Don't forget to donate to other contributors as well. All core developers are doing voluntary work and for free. We all try to do our best to keep the project going.

If you wish to support me as well 😉.. Can do so here: https://www.buymeacoffee.com/melroy or other ways as well : https://melroy.org/thanks.html

melroy,
@melroy@kbin.melroy.org avatar

Indeed, nobody is asking you (Ernest) to step down.

melroy,
@melroy@kbin.melroy.org avatar

In general there are still maybe different issues with federation. For instance lemmy constantly changes there api after software updates. Causes federation issues.
Federation protocol isn't fully standardized at all! Meaning that all platforms can do whatever they please. Mastodon did lay out the foundation of the standard. But that was mainly about posts and microblogging.

melroy,
@melroy@kbin.melroy.org avatar

We have an open pull request for comment collapsing. But Ernest won't merge this until after the first kbin release I'm afraid.

melroy,
@melroy@kbin.melroy.org avatar

No problem!

e569668, to fedia
@e569668@fedia.io avatar

deleted_by_author

    •
    melroy,
    @melroy@kbin.melroy.org avatar

    @hitstun

    @e569668 @e569668 @hitstun @Pauliehedron @Pauliehedron Thanks ^^

    melroy,
    @melroy@kbin.melroy.org avatar

    Turning off federation doesn't mean it will delete all the content on your/the instance.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • meta
  • Macbeth
  • All magazines
    •