@maegul kbin supports those groups btw ;)
https://kbin.social/magazines?query=a.gup.pe+&fields=names&federation=all&adult=hide
https://kbin.social/magazines?query=chirp.social&fields=names&federation=all&adult=hide
@feditips @FediFollows @masimatutu @sabreW4K3
who knows. but either way, there's still an obligation to communicate with the very people who were onboard beside you, to let them know how you're feeling and what might happen to the project, because you guys also dedicated your time to this, and your time matters too.
Sometimes, that's the hardest part of coming back, believe me. But we still don't know exactly what happened, and I hope it will be clarified sooner or later, whether it's the definitive end or not. Life has taught me to be very patient, and if there's a chance, this time it will be my priority to help Hariette bring Artemis back to life, as it's truly a great app and a piece of a cool story ;)
The API will be made publicly available in the coming days. Essentially, everything is ready except for one technical issue where I need Piotr's assistance, but he is currently quite busy. However, I'm trying to resolve it as quickly as I can.
Thank you for the work you've put in, guys. Life can really knock you off your feet sometimes, and I'm pretty sure Hariette has a good reason to be offline now. II really hope everything works out for her and one day she'll be able to come back.
As for myself, at the beginning of the year, I plan to dust off the drawer and return to my mobile client that I started some time ago, and develop it in my free time. If someone likes /kbin feeling, I'm pretty sure they'll also enjoy this app ;)
You need to inform your instance that such a community exists. Usually, it's enough to type the URL https://kbin.social/m/OriginalDocuments into the search bar while logged in on Reddthat.
In the latest thing with Reddit's /kbin, it was still in the early prototype phase (and remains so to this day). Prior to this, practically only I and a few friends were using it. It wasn't ready to handle the sudden creation of dozens of instances or accommodate thousands of users. Additionally, real-world issues emerged that demanded my immediate attention. I made the decision to take a step back instead of getting caught up in a race, opting to build solid foundations, which is exactly what I'm doing now. In my opinion, this will be better for the project and potential contributors, ensuring that their work will be utilized to the best possible extent.
Actually a lot is changing in /kbin, and this recent period has brought the most changes in months. Slowly we are coming back to life, and this time I will be better prepared.
The aggregate view is in preparation still.
Oh, come on, I'm not that sensitive ;-) Constructive criticism helps me set goals, prioritize tasks on my board, and broaden my horizons when it comes to the overall experience with the platform. I really appreciate that. The fact is that Lemmy had a lot more time. I remember when they started federation tests, I was writing my first line of code. Some things just need time to mature. For me, it's not a race. I simply have a clear goal that I'm determined to achieve - to create a solid, accessible platform that others can benefit from and enjoy. Who knows, maybe it'll become the best in the entire fediverse someday ;-) Now, after the break, I'll be working on federation but also on customizing the feed to tailor it as much as possible to individual needs. Cheers!
A certain stage of development has ended - a prototype was created that allowed me to verify whether such a form makes sense in the #fediverse. Until now, it was a project that I developed in my free time. Now, thanks to the great people from Nlnet, I will be able to devote much more time to it. This time, we have already outlined a plan for the next few months officially: https://nlnet.nl/project/Kbin/
The progress of the work can be followed here: https://dev.karab.in - this is the version set up on the cheapest server, and it will remain so until all stages are completed, because one of the goals is to create a lightweight platform that will have very low requirements in its basic version, and therefore low maintenance costs for instances. With each passing day, more subpages and features will work.
Many of you are working on cool projects, it's worth calling on the Open call for funding ;-) https://nlnet.nl/news/2023/20230201-call.html
Soon, the kbin.social instance will also officially launch, now work on the server is still underway.
Stage 1 Frontend - refreshed, modern and accessible layout
To save time, the /kbin prototype was created using tools such as Bootstrap. Due to frequent iterations, good interface development practices were often overlooked. The goal is to create a clean, modern, responsive and accessible layout based on feedback from the community, which will work on any device, also without the need to use JS.
Stage 2 Backend - upgrade
Updating the environment, PHP, Symfony, API-Platform, etc.
Stage 3 Search module and alpha release
Currently, the search engine is based on Elasticsearch, which significantly increases the minimum server requirements. The goal is to eliminate Elasticsearch and create a search module with the ability of contextual filters and prepare the first alpha release.
Stage 4 Backend - refactor existing services.
Update of frameworks and tools used in the project. Refactor existing services. Refinement of existing services in order to achieve efficiency. Writing documentation for other developers, admins and visitors. Preparing a repository for contributors.
Stage 5 Federation improvements
Optimization of communication using ActivityPub. Completion of integration, creation of documentation for fediverse developers.
Stage 6 Admin section and user UX improvements
The goal is to provide tools for Kbin instance admins and to improve instance community sections.
Stage 7 Prepare for stable release
The goal is to release a stable version of the platform, solve problems reported by users and, using appropriate tools, develop the highest scalability and efficiency.
Stage 8 Implementing Events (incl. ‘stretch goals’)
At this stage, kbin will also become an events aggregator.
Stage 9 ActivityPub federation of Events (incl. ‘stretch goals’)
The events module will communicate with other platforms via ActivityPub (e.g. Mobilizon)
Currently, I am at stage 1/2/3.
Other instances:
https://github.com/squizlabs/PHP_CodeSniffer/issues/3932