ernest @ ernest @kbin.social

Working on /kbin

---

Read more

Posts

122

Comments

345

Joined

2 yr. ago

I have an eye on this issue. I can't reproduce it myself, but I will have a few additional devices for testing this week.

@1Fuji2Taka3Nasubi Hey, during the server migration, I had to unload the queue (the previous week). I added several addresses to the blocked instances that were either unresponsive or generating errors at that time. Lemmy.zip ended up on that list - probably by mistake. My bad. Now, after the initial verification, most of those instances are still dead, but I will verify it more thoroughly today. Now that I have sorted out the infrastructure issue, a series of federation fixes will follow - perhaps even this week.

With additional tools for moderators, a system for taking over abandoned magazines will be created. I want to automate this, but it will take some time. I am in the process of finalizing the last formalities. I will soon post a status update.

Try @curiosityLynx@kglitch.social
I will add the issue, thanks.

The magazine owner can also add other hashtags such as #flowers #garden ;)

Hey, a month ago I would have simply pressde the button and not thought too much about it. Now the situation looks completely different. I have bookmarked all the discussions I came across, and next week I will read every single post to have a complete picture. I owe you that.

However, we need to think about additional privacy features, as priorities have drastically changed in recent weeks, and I will have to carefully consider that. Now that I have dealt with infrastructure issues, I will focus on the most important matters.

TEST2

@blazera lemmy.ml is blocking incoming traffic from the kbin.social server.

https://kbin.social/m/kbinMeta/t/145248/Is-Kbin-defederated-from-Lemmy-ml#entry-comment-568968

@rodhlann

Anyway, there are preparations for improvements in the way kbin is deployed. Soon, there will be a lot of significant fixes.

It may be related to Redis cache or instance key changes.

Have they told you protocol compatibility is the reason?

Nope, we don't have any contact with each other. I simply associated it with the fact that both lemmy.ml and kbin were having issues handling the overall traffic at that time. That's all I know right now.

That's strange, at first glance, everything seems fine. Tomorrow, I'll try to dig into the logs or attempt one thing on a test instance.

Likely true, the preview is working on test instances.

@jon I'm pretty sure that Kibby would explain the intricacies of the fediverse to newcomers perfectly ( ͡° ͜ʖ ͡°)

@minnieo

I'm convinced I saw it somewhere in the issues, but could you provide me with the address of your instance now? You can send it via pm, I'll check it right away.

why not both gif

It seems to me that the simplest explanation is that kbin handles additional actions, such as user content boosting, and the AP structure is also slightly different. While Lemmy - Lemmy cooperate well with each other, kbin can cause confusion through erroneous server queries, significantly increasing the load. I have been working on reducing unnecessary requests, which was a result of migrating to a new server and discovering weak points. Work in this area will be continued to ensure that we do not harm each other primarily.

Hell yeah ;) It seems like I've got one thing off my mind so far, so things will start getting organized here soon.

These renders are incredible. I enjoy playing around with Blender sometimes myself, but my skills are limited to placing a few simple blocks ;)