Yes, I say this fully aware - there are many things that I have failed at. Much of what I said, I failed to achieve. However, I never wanted to keep people on a leash; I am more of a person who prefers to stay on the sidelines and engage in what brings me the greatest pleasure - coding, just like any other contributor.
Believe me, I tried to delegate tasks, had many private conversations and discussions. Perhaps it wasn't visible from the outside. However, in that mental state, the last thing I wanted to do was resolve conflicts among adults, and it all started to boil down to that. As @BaldProphet mentioned - "microcosm of the open-source community."
Moreover, there were too many different visions of the project, ignoring requests, etc. That's precisely why I decided to temporarily halt development, to secure the future of kbin. It was my decision, and as I mentioned, forking turned out to be the best thing that could happen. As you can see, the differences are not that significant, but it will be easier for all of us - especially since we can always draw inspiration from each other, and I don't think anyone has a problem with that.
However, I still maintain contact with many people, and sometimes they mention to me the attitude of certain individuals on mbin's Matrix - it is at least puzzling. In any case, I want to stay away from that and focus on my work with contributors who understand and prefer my approach.
This feature stopped working for some reason during the development of these software. In the coming weeks, I'll be working intensively to improve communication in the fediverse, including moderation.
Yeah, that's true. Real-life stuff was kinda more important for me at the moment than managing the project.
For me, it's straightforward: I pushed some dev code that wasn't even a complete feature, and it got approved in your pull request. That's why I was advocating for everyone to only merged their own PRs in the /kbin repository – so that each person could take responsibility for their own work. I won't go on about this any further.
Permanently Deleted
- kbin has a tag view - you can click on it, and it will display content from the fediverse, merged with Mastodon posts and other microblogs. The type of content found there depends on the instance and any relay connections. Personally, I've never been a fan of the chaos in large Mastodon instances.
https://kbin.social/tag/NewYork
https://kbin.social/tag/silenthill
- It's something I'll be working on in the future. I'm focused on integrations with various platforms and convenient browsing of multimedia content coming from them. Currently, it's done provisionally and is not the final solution.
I won't comment on the rest because I've always hated the Twitter format. But I know that there are many people who find it appealing. Mastodon didn't suit me either, despite several attempts to use it.
Hey, the API is on board.
https://kbin.social/m/kbinMeta/t/612526/kbin-social-update#entry-comment-3480170
Yep, another way is to choose abandoned from the list of magazines, soon it will be more sensibly sorted ;)
I will check what's going on.
Yep, I intentionally did not enable the API. After the update, I want to wait through the weekend, make necessary corrections, gather some metrics. If everything is fine, we will enable the API!
Could you send me a message, as I'm quite behind, to be honest.
I'll try to work on it over the weekend.
I also prefer the comment box at the bottom ;)
Yep, in Polish we call it skrót myślowy
I assure you that I didn't intentionally push incorrect code into the repository. These were my first lines of code in a really long time. I simply got involved in other things that I wanted to finish first, and I noticed the edge case in the meantime, but it wasn't a priority. I saw that you were syncing and I was hoping to benefit a bit from it once you fixed it. I didn't expect the review to happen so quickly. By the way, I was genuinely curious about how this project management method works because, you know, I've always avoided such an approach. Merloy, you know how much I owe you, and I appreciate what you've done for the project, as well as the other Mbin contributors. Our overall visions haven't always been the same, and I think it's great that kbin has been forked. You see for yourself how my work looks until the release - there are many things I'll be refining over time. That's why I've put a hold on all other PRs, and now I want to focus on this.
Oh c'mon, don't be mad. It's just a wrong sorting of posts, it's in an edge case, and seriously it wasn't intentional. I just wanted to check how such management looks in practice, how many merge accepts are needed, etc. I didn't mean to do anything wrong that could cause harm. I even push the same code to my instance to facilitate your tests ;)
But you're right - that's just my nature. I approach PR with very limited trust, whether they're mine or from others.
I'm back in the game now. The issue with spam will be addressed next week.
It wasn't entirely intentional, it was actually my mistake. But I held off on pushing the hotfix for a while. It was a development branch, so these kinds of bugs were permissible - in this case, it just changed the order of related posts, nothing serious. It was quite easy to spot and fix. Slow and cautious acceptance of pull requests, something I spent a lot of time on, was the main accusation from the creators of forks. Hastily accepting them was a problem for me. I personally considered a consensus similar to that, but now I see it doesn't make sense. Someone needs to take responsibility. Personally, I believe that forks are the best thing that could have happened to the project.
Zdecydowanie tak, zastanawiam się tylko czy nie zrobić domyślnego filtrowania języka na polski.
karab.in planuję ogarnąć w najbliższym czasie, w przyszłym tygodniu. Jest chyba jakiś problem z aktualizacji dockerowych zależności, których nie mogę szybko ogarnąć. Mam wszystkie backupy w razie gdyby stała się jakaś tragedia, ale w najbliższych dniach będę próbował z tym walczyć, być może nawet postawić go z najnowszym kodem co będzie dobrym testem przed kbin.social. Na pewno nie zamierzam rezygnować z tej instancji.