ernest

For the past few days, I've patched up a few minor errors that there was never time for. I also took a short break from coding, but I'm still working on planning the federation. I'm trying to spend a bit more time with my family and recharge for the upcoming week.

Quiet tests of the latest changes and patching of outstanding errors are ongoing on the instance. The remaining changes will be implemented by the end of the week. I have also completed all outstanding formalities related to the project and everyday matters. Starting from next week, work will pick up pace. Until then, I would like to observe what is happening.

The weekend tasks are taking longer for me, I found another bug that causes a 500 error, I'm still working on it.. This evening and tomorrow, I will be testing the changes on the kbin.social. If there are any issues, please mention me in the post or contact me directly through the contact form.

Today, a very quick update. I addressed the errors that occurred during voting and the link to the comment in the notification.

All changes from the weekend will be on the instance on Monday at noon.

Today, I took care of several overdue formalities related to the project that were weighing on me. Besides the routine refactoring and work on the ActivityPub module, there are a few things I would like to do this weekend:

• Launch the API on the main instance (yeah... again ;))
• Add Aggregate view, collections, and additional filters to the API
• Ultimately fix the issue of errors during voting
• Correct the link to comments appearing in notifications
• Sort out the recent comments and feedback

Is there anything else that should be added to or replace items on this list? :)

//edit: Ah, there's one more thing I forgot. I would like adding a new post/thread to be done asynchronously to reduce client-side time, but this might extend to next week because even though I have the foundation prepared, I want to thoroughly test it.

I just got back from a over five-hour walk with my dog. I had promised him that for a long time, and both of us really needed it ;-) Now, a quick lunch, and I still have an evening workout ahead of me. Today, I decided to take a break from coding, although I probably won't resist doing something, and at night I'll probably tweak something on the project website or work on something that doesn't require too much thinking. Tomorrow morning, I have to finish a few formalities and get back to work.

Another day has passed for me working on code refactoring and federation development. In the process, I'm also creating better documentation that can be utilized for other apps integrations. I also had a few formalities related to the project to take care of today, and there are more to address tomorrow.

Closer to the weekend, there might be something more concrete that will be visible on the instance.

Today, a really quick update - I continue working on the federation and begin adapting the API to the new codebase, implementing the latest changes and features.

Today marks the 40th day of the devlog, and the new federation module is expanding on the whiteboard. In Poland, the flu season is in full swing, and due to reasons beyond our control, we had to slightly postpone the launch of the API on kbin.social. Fortunately, @jwr1 reminded me that I had previously launched it on another instance – which was exactly what I was supposed to do today :p So, something is happening regarding mobile applications here and here.

Moreover, today I improved the account deletion process, some requests were stuck in queues a few moments ago – now everything is fine. In the coming days, I also plan to create an additional form for repeating deletion from all known remote instances, as sometimes, due to unavailability or limits, not everything gets deleted. I already have an idea of how to do it.

Today, I will probably be offline until the end of the day as I am setting up a new internet connection in a new location. So far, I've been struggling with a mobile one.

Today, I am continuing work on the new ActivityPub module. I am also adapting the test environment that I will use during further development. Work on launching the API on the instance will continue tomorrow.

@testing Can you repeat your tests regarding tags between kbin and other instances? It should be significantly better ;)

#kbinMeta

Today, we successfully addressed most of the recent issues on the instance. As the database continues to grow, proactive measures are essential to address and improve any weak points. The aggregate view introduced additional benefits, such as filters on the tag page and the search page, making implementation seamless through these mechanics.

As mentioned earlier, there might be some instability over the weekend as we collaborate with @piotrsikora to deploy the API on kbin.social. A big thank you for his time amidst the busy pre-holiday/new year period.

Additionally, I made improvements to the reputation page, where users can now filter activities for specific days. While it's not perfect yet, continuous enhancements are underway for a better user experience.