Mbin Blog Updates
### Expert Advice on Preventing Fabric Softener Buildup in Washers Over time, the incorrect use of cloth softener can cause huge troubles to your washing device. The sticky residue left within the again of with the resource of cloth softener now not best clogs the dispenser but also can acquire within the system’s bath, hoses, and pump. This buildup should have an effect for your washing system’s normal basic performance, main to issues like foul odors, mildew increase, or maybe mechanical disasters. Knowing a manner to save you this buildup is crucial for extending the lifestyles of your washing gadget and making sure it runs efficaciously. In towns like Dubai, where in **[Washing Machine Repair services](https://artech.ae/washing-machine-repair-dubai/)** are extensively available, taking preventive measures to keep away from fabric softener buildup permit you to keep away from vain repair costs. Let's dive into how you could preserve your washing device's ordinary performance and prevent highly-priced safety thru addressing material softener buildup. Why Does Fabric Softener Cause Buildup? Fabric softener is designed to coat fabric with a thin layer of chemical compounds that lead them to experience tender and reduce static hang. However, the ones chemical substances don’t continuously dissolve absolutely in water, particularly in bloodless cycles or if too much softener is used. When fabric softener isn't thoroughly rinsed away, it can stick with the partitions of the washer drum, clog the detergent drawer, or even accumulate inside the washing device’s inner components. Over time, this buildup can end up a magnet for dust, lint, and detergent residue, predominant to horrible washing standard usual overall performance, ugly odors, and potential damage to your gadget. At this point, you may need to go to a Washing Machine Repair Service Center for expert help. Signs of Fabric Softener Buildup in Your Washing Machine Before material softener buildup ends in extreme mechanical troubles, there are some caution signs and symptoms and signs and signs you may appearance out for: Foul Odor: A lingering, musty scent on your washing gadget can be a sign of buildup, that can harbor mould and mildew. Sticky Dispenser: If the cloth softener dispenser feels sticky or clogged, it suggests that the softener isn’t being truly flushed out sooner or later of the wash. Poor Washing Results: Clothes may not pop out as easy as they used to, or they will enjoy slightly sticky or have a bizarre scent. Visible Residue: You may additionally be aware streaks of residue on the indoors walls of the drum, in particular if you run your tool without garments interior. Slow Draining or Spinning: If the washer’s drain or spin cycles seem a outstanding deal less green, buildup may be affecting the internal additives. If you enjoy any of those signs, it’s important to address the hassle earlier than it worsens. Ignoring the hassle may additionally want to finally require a visit to a Washing Machine Repair Dubai service. Conclusion Preventing material softener buildup on your washing machine is crucial for keeping its wellknown performance and warding off costly maintenance. By using the right quantity of softener, diluting it, cleaning the dispenser frequently, and acting ordinary safety, you may ensure your washing device runs efficiently for years yet to come. If you encounter chronic problems because of buildup, don’t hesitate to obtain out to a Washing Machine Repair Service Center for expert assist. #updates
We are excited to announce the release of [Mbin v1.7.2](https://github.com/MbinOrg/mbin/releases/tag/v1.7.2)! This version is packed with important bug fixes and performance improvements, focused on bug fixes rather than new features. **The main improvements are:** - Fixing many PHP undefined, null or other errors that admins might see in their production logs. - Resolving several templating null issues. - Removing CSRF tokens from public forms (when user isn't logged-in), reduce unnecessary large amount of sessions. - Migrating Symfony sessions from Redis to PostgreSQL to avoid race conditions. - Increase session & cookies duration to 4 months (so people stay logged-in). - Adding a down-vote mode in `.env`. - Add stricter requirements on the routes configuration (reducing invalid requests are making it to the controller). - Introducing a scheduler for removing deleted user messages & pruning the dead letter queue in RabbitMQ. - Various other bug fixes and updating package dependencies and translation improvements. Read the full release note at: https://github.com/MbinOrg/mbin/releases/tag/v1.7.2 --- We are still searching for PHP developers, feel free to join our [Mbin project](https://github.com/MbinOrg/mbin)! Join our matrix space or pick-up a 'good-first-issue'.
Today I'm planning to upgrade the server from Ubuntu 22.04 to Ubuntu 24.04 (new LTS release). I already proposed it once after reading: https://ostechnix.com/ubuntu-24-04-1-lts-release-delayed/... Hopefully I will not hit any of these RabbitMQ bugs: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/2074309 Mastodon poll is a tie: https://mastodon.melroy.org/@melroy/113135476244781426 So, let's go! What can go wrong?? ~~ Famous last words ~~
Today we are releasing Mbin v1.7.1. Upgrade your Mbin server now to the latest release: [1.7.1](https://github.com/MbinOrg/mbin/releases/tag/v1.7.1). This version includes tons of fixes (too many to mention here, look at ["What's Changed"](https://github.com/MbinOrg/mbin/releases/tag/v1.7.1)) and introduces also new features like: trusted proxy configuration ([see also docs](https://docs.joinmbin.org/admin/configuration/nginx#trusted-proxies)), activate accounts manually using the admin panel, show an error when the image is too large to upload ([look at the latest .env template file](https://github.com/MbinOrg/mbin/blob/main/.env.example#L42)), improved API end-points (isAdmin, isGlobalModerator is part of the user API, fixed AP context and more) as well as many documentation improvements. **Note:** Due to a dead-lock issue in 1.7.0, which is now fixed in 1.7.1, we strongly recommend upgrading your Mbin server as soon as possible. --- If you want to host your own Mbin server? But you need help? Come and join us at: [Matrix chat](https://matrix.to/#/#mbin-general:melroy.org). We are happy to help! --- I personally want to thank all contributors of Mbin as well as the Mbin community as a whole! We can't do it without all of you.
We are in the final testing phase of Mbin v1.7.1, we hope to release the new stable version this weekend! Which actually brings a lot of improvements (we could have considered it calling v1.8.0, but well). #mbin #updates #release
**[Vidalista 80mg yellow pill](https://buyrxsafe.com/vidalista-80)** is specially designed for men who have erectile dysfunction (ED). The active ingredient in Vidalista 80 mg is tadalafil. It can be used upon prescription to minimize the effects of impotence in males with the Vidalista 80 yellow pill. It aims to increase blood supply to the penis so men can have stronger erections throughout sexual activity.
We released a new Mbin version: 1.7.0! See: https://github.com/MbinOrg/mbin/releases This is the v1.7.0 release of Mbin and it brings a lot of changes: improved instance wide modlog, new SSO providers, new translated languages, moderator updates in the modlog, new cake day display, better stability and scalability of the messengers, PeerTube support, federating direct messages, federate un-/pinning entries, updated robots.txt, improve the documentation, longer durability of the user session, adding admin notifications for reports, tombstones for deleted remote users, improve the federation of edits, push subscriptions, a new look of the federation page, add public API endpoints for getting de-/federated and dead instances, magazines can now restrict posting to mods, updating magazines and users should now federate instantly, new users and magazines now show a leaf icon next to them, improve the editing of threads, make the maximum image size configurable The Mbin development team now suggests using PHP v8.3. If you are using the docker setup you will automatically be running the new PHP version. A total of 145 reviewed and approved pull requests have been merged into this release! As always, a special thank you to new and existing contributors, without you, future Mbin releases would not be possible!
Sorry for the late post. This is the 1.6.0 release of Mbin. It brings several changes and improvements including, but not limited to, a new UI filter for sorting threads and microblog posts, a new hashtag system, Microsoft Azure and SimpleLogin SSO additions, private instance mode, framework upgrade to Symfony 7.0, outgoing federation of delete actions, several backend improvements to address federation stability and compatibility, UI fixes and route changes, etc. We are already preparing for release 1.7.0, which is coming along very nicely. See you soon with v1.7.0.
### Unveiling the Legacy: A Journey Through the History of Innovation at ShakarzahiLLC **Introduction:** In the realm of innovation, some companies stand as paragons of creativity and progress. Among these, ShakarzahiLLC shines as a beacon of ingenuity, with a rich history steeped in groundbreaking advancements and transformative ideas. Join us as we embark on a captivating journey through the annals of time, exploring the remarkable **[history of innovation](https://shakarzahillc.com/history-of-innovation/)** within ShakarzahiLLC. **The Birth of a Visionary Enterprise:** ShakarzahiLLC traces its roots back to [year], when visionary entrepreneur [Founder's Name] laid the cornerstone of what would soon become an icon of innovation. Fueled by a passion for pushing boundaries and reshaping industries, the company swiftly gained recognition for its forward-thinking approach and disruptive solutions. **Pioneering Breakthroughs:** From its inception, ShakarzahiLLC demonstrated a penchant for pioneering breakthroughs that redefined the landscape of various sectors. Whether it was revolutionizing [industry] with cutting-edge technologies or introducing disruptive business models, the company consistently set new standards for innovation excellence. **A Culture of Innovation:** Central to ShakarzahiLLC's success story is its unwavering commitment to fostering a culture of innovation. Through initiatives such as [Program Name], the company empowers employees to think outside the box, explore novel ideas, and transform bold visions into reality. This relentless pursuit history of innovation permeates every facet of ShakarzahiLLC's operations, driving continuous growth and evolution. **The Evolution of Products and Services:** Over the years, ShakarzahiLLC has continually evolved its product and service offerings to meet the evolving needs of its customers. From pioneering [Product/Service] that revolutionized [industry] to launching groundbreaking [Product/Service] that set new benchmarks for excellence, the company's portfolio reflects its unwavering commitment to innovation and customer-centricity. **Collaborative Partnerships and Alliances:** Recognizing the power of collaboration in fueling innovation, ShakarzahiLLC has forged strategic partnerships and alliances with leading organizations across the globe. By leveraging complementary expertise and resources, these alliances have facilitated the co-creation of groundbreaking solutions and propelled ShakarzahiLLC to new heights of success. **Impact on Society and Beyond:** Beyond driving business growth, ShakarzahiLLC's innovative endeavors have had a profound impact on society at large. Whether through [Social Impact Initiative] or [Community Outreach Program], the company remains dedicated to using innovation as a force for positive change, enriching lives, and shaping a brighter future for generations to come. **Adapting to Change:** Innovation is not static; it is a dynamic process that requires constant adaptation to changing circumstances and emerging trends. Recognizing this reality, ShakarzahiLLC remains agile and responsive, continually scanning the horizon for new opportunities and embracing change as a catalyst for innovation and growth. **Looking Towards the Future:** As we gaze into the future, the history of innovation at ShakarzahiLLC appears boundless. With a legacy of pioneering achievements behind it and a relentless spirit of innovation propelling it forward, the company is poised to continue shaping the future of [industry/sector] and inspiring generations to come. **Conclusion:** Innovation lies at the heart of ShakarzahiLLC's remarkable journey, propelling the company from humble beginnings to global prominence. Through a relentless commitment to pushing boundaries, fostering a culture of creativity, and embracing change, ShakarzahiLLC has not only transformed industries but also left an indelible mark on society. As we reflect on the **[history of innovation](https://shakarzahillc.com/history-of-innovation/)** at ShakarzahiLLC, we are reminded that the greatest achievements often begin with a single spark of inspiration—and that the journey towards progress is an ongoing adventure, filled with endless possibilities. #updates
Mbin patch release 1.5.1 is out. Which is an important update for server admins to upgrade as soon as possible in order to fix sending emails (both during registration form as well as contact form). This patch release was created to fix those email issues. More info: https://github.com/MbinOrg/mbin/releases/tag/v1.5.1
Mbin release version 1.5.0 is out today. Official release notes: https://github.com/MbinOrg/mbin/releases/tag/v1.5.0 User notice: https://gehirneimer.de/m/mbinReleases/t/192724
[https://kbin.melroy.org/](url) #updates
### Simply Satisfy & Send Sweets to Canada Craving a taste of sweetness from afar? Sending sweets to Canada is easier than ever with the convenience of online ordering. Whether you want to surprise a loved one, celebrate a special occasion, or simply satisfy your own sweet tooth, indulging in delectable treats has never been simpler. Let's explore the importance to [Send Sweets to Canada](https://egiftsportal.com/sweets-to-canada) and what to consider when selecting the perfect goodies for delivery. **### Send Sweets to Canada** When it comes to sending sweets to Canada, the possibilities are endless. From classic chocolates and candies to gourmet pastries and international delicacies, there's something for every palate. Online platforms make it convenient to browse through a wide selection of delectable treats from the comfort of your home. Sending sweets online allows you to surprise friends and family across borders with a thoughtful gesture that is sure to bring smiles. Whether it's for a birthday, anniversary, holiday, or just because, a sweet treat is always appreciated. Consider the recipient's preferences when choosing the perfect sweet gift – do they have a favorite type of candy or chocolate? Are they more inclined towards savory snacks or decadent desserts? Tailoring your selection to their tastes shows that you've put thought into the gesture. With reliable shipping options and secure payment methods offered by online retailers, sending sweets to Canada has never been more seamless. Take advantage of these services to spread joy and sweetness wherever your loved ones may be. ### **Importance Of Sending Online** In today's fast-paced world, sending sweets to Canada online has become increasingly popular. Whether you want to surprise a loved one on their birthday or simply show appreciation, the convenience of online gifting makes it easier than ever. By sending sweets through online platforms, you can easily browse through a wide variety of options without leaving the comfort of your home. With just a few clicks, you can select the perfect treat and have it delivered directly to your recipient's doorstep. Moreover, sending sweets online allows you to personalize your gift with special messages or notes, adding an extra touch of thoughtfulness to your gesture. It's a simple yet meaningful way to connect with someone across borders and make them feel special. The importance of sending sweets online lies in its ability to bridge distances and create lasting memories. So why wait? Send some sweetness their way today! **### Things to Consider** When sending sweets to Canada, there are a few important things to consider. Ensure that the online store you choose offers a wide selection of sweets that cater to different tastes and preferences. This will give you the opportunity to customize your gift based on the recipient’s likes. Check the shipping policies and delivery times to make sure your package arrives on time. It's essential especially if you're sending sweets for a special occasion or holiday celebration. Additionally, take note of any dietary restrictions or allergies the recipient may have. Opt for options like vegan or gluten-free sweets to accommodate their needs. Consider adding a personal touch with a heartfelt message or card along with the sweet treat to make it even more special for the recipient. By keeping these factors in mind, you can ensure that your gesture of sending sweets to Canada is thoughtful and well-received. Sending sweets to Canada is a delightful way to show your love and appreciation to friends and family across the miles. By utilizing online services, you can easily [Send Cakes to Canada Online](https://egiftsportal.com/cakes-to-canada) without any hassle. Remember to consider factors like shipping costs, delivery times, and dietary restrictions when choosing the perfect sweet gift for your loved ones in Canada. So go ahead, spread sweetness and joy with just a click of a button! #updates
After 1.4.0 release we found some minor issues, it's wise to update your instance to the latest 1.4.1 patch release if you didn't had already. More info at: https://github.com/MbinOrg/mbin/releases/tag/v1.4.1 If you didn't follow the 1.4.0 release notes yet, then BE SURE TO carefully follow the those upgrade instructions as well: https://github.com/MbinOrg/mbin/releases/tag/v1.4.0. From 1.4.0 we changed how the transport messenger (AMQ) is working on bare metal instances. We are planning soon for a new minor release (v1.5.0). Thanks for using Mbin! Personally, I'm also planning to setup mbin.melroy.org which will replace this instance. However, ActivityPub will see that new domain as a totally new instance. Migration is not straightforward too bad.
Has changes to the messenger queue layout, the background worker system. Info: [https://github.com/MbinOrg/mbin/releases/tag/v1.4.0](https://github.com/MbinOrg/mbin/releases/tag/v1.4.0) Docker images also: [https://github.com/MbinOrg/mbin/pkgs/container/mbin](https://github.com/MbinOrg/mbin/pkgs/container/mbin) <details><summary>Full changelog</summary> * Remove the local condition from magazine autocomplete by @BentiGorlich in [#455](https://kbin.melroy.org/tag/455) * Add missing flash on contact form by @melroy89 in [#454](https://kbin.melroy.org/tag/454) * Translations update from Hosted Weblate by @weblate in [#460](https://kbin.melroy.org/tag/460) add user badges to entry and post templates by @e-five256 in [#467](https://kbin.melroy.org/tag/467) * Reread and update as well by @melroy89 in [#462](https://kbin.melroy.org/tag/462) make search recognize [!group](https://kbin.melroy.org/search?q=group@instance.domain) handle format by @asdfzdfj in [#465](https://kbin.melroy.org/tag/465) * fix nodeinfo schema wrong version, add metadata by @asdfzdfj in [#471](https://kbin.melroy.org/tag/471) * load custom css from routes instead of inline by @asdfzdfj in [#472](https://kbin.melroy.org/tag/472) * adding alt text as caption in lightbox by @asdfzdfj in [#473](https://kbin.melroy.org/tag/473) * hotfix: allow custom style while still in 2fa by @asdfzdfj in [#488](https://kbin.melroy.org/tag/488) * Change the messenger queue layout by @BentiGorlich in [#461](https://kbin.melroy.org/tag/461) * Translations update from Hosted Weblate by @weblate in [#474](https://kbin.melroy.org/tag/474) * Using loading lazy on images by @melroy89 in [#491](https://kbin.melroy.org/tag/491) * Preload our logo by @melroy89 in [#493](https://kbin.melroy.org/tag/493) * FAQ: Explain 'all' messages by @melroy89 in [#490](https://kbin.melroy.org/tag/490) * FAQ: Retries three times by @melroy89 in [#489](https://kbin.melroy.org/tag/489) * FAQ: Typical message queue has changed by @melroy89 in [#492](https://kbin.melroy.org/tag/492) * Fix error on entries with an empty body by @BentiGorlich in [#504](https://kbin.melroy.org/tag/504) * move service worker registration into main app bundle by @asdfzdfj in [#507](https://kbin.melroy.org/tag/507) * use title instead of body for federated entry summary by @asdfzdfj in [#506](https://kbin.melroy.org/tag/506) * adjust tag matching to better handle some eastern scripts by @asdfzdfj in [#508](https://kbin.melroy.org/tag/508) * somewhat fix phpunit so it could run functional tests again by @asdfzdfj in [#396](https://kbin.melroy.org/tag/396) * Add column last\_origin\_update to magazine by @BentiGorlich in [#503](https://kbin.melroy.org/tag/503) * Add the correct cascading attribute to Entities by @BentiGorlich in [#500](https://kbin.melroy.org/tag/500) * Update Symfony packages + recipes+ NPM by @melroy89 in [#510](https://kbin.melroy.org/tag/510) * Update remaining composer packages by @melroy89 in [#512](https://kbin.melroy.org/tag/512) * Fix circular message by @BentiGorlich in [#514](https://kbin.melroy.org/tag/514) * Add support for incoming dislikes by @BentiGorlich in [#513](https://kbin.melroy.org/tag/513) * Remove route for down votes and make it a span by @BentiGorlich in [#516](https://kbin.melroy.org/tag/516) * Upgrade all remaining symfony packages by @melroy89 in [#517](https://kbin.melroy.org/tag/517) * Fix imagemanager not having a useful error message by @BentiGorlich in [#523](https://kbin.melroy.org/tag/523) * slightly fix object body extraction on set but empty body by @asdfzdfj in [#525](https://kbin.melroy.org/tag/525) * Update Postmill link by @melroy89 in [#526](https://kbin.melroy.org/tag/526) * Improve handling of images by @BentiGorlich in [#501](https://kbin.melroy.org/tag/501) * Update version number for 1.4 release by @nobodyatroot in [#530](https://kbin.melroy.org/tag/530) more @ [https://github.com/MbinOrg/mbin/compare/v1.3.0...v1.4.0](https://github.com/MbinOrg/mbin/compare/v1.3.0...v1.4.0) </details>
We released version 1.3.0 of Mbin today. More info: https://github.com/MbinOrg/mbin/releases/tag/v1.3.0 We also publish tagged Docker image(s): https://github.com/MbinOrg/mbin/pkgs/container/mbin
A community-focused fork of Kbin, which has tons of improvements, features and bug fixes. Mbin is a federated content aggregator, voting, discussion and microblogging platform. Feel free to host your own instance on the fediverse! If you are already running Kbin; migrating is straightforward towards Mbin and experience the benefits yourself. If you have any questions let us know down below or [join the community matrix chat](https://matrix.to/#/#mbin:melroy.org). Visit the project page: [https://github.com/MbinOrg/mbin](https://github.com/MbinOrg/mbin)
In the past months development of Kbin slowly came to a halt, development was bottlenecked by a single maintainer. I have tried several times to start a discussion about the way of working and trying to address the problems and to come up with a plan to keep development doing and more importantly keep contributors happy! Despite all of this; no response on Matrix and nothing has really changed at Kbin. I saw the project slowly dying over the past months, and I couldn't let this happen. That's why I decided to *fork* the project called [Mbin](https://github.com/MbinOrg/mbin). I wanted to avoid a fork initially, but I didn't saw any way out. [Mbin](https://github.com/MbinOrg/mbin) is community-focused fork, build upon trust and embracing the Collective Code Construction Contract (C4). Despite the fact I'm the creator of Mbin, I am **NOT** the only maintainer, several contributors already have **owner** rights on the GitHub organization as well as on the [Matrix Space](https://matrix.to/#/#mbin:melroy.org) and Weblate. We are all maintainers, we peer-review each other's code and are allowed to merge pull requests from other external contributors and our own. The community of Mbin will now decide what will be picked-up and resolved, what will be merged or not. The community is in charge. And I am "just" another contributor, following the C4 rules. [Mbin](https://github.com/MbinOrg/mbin) development has been accelerated tremendously over just one week time. With tons of improvements in GUI, backend, security and documentation. We have great internal discussions and a friendly community. We work as a team, sharing knowledge and helping each other out. We review and test our code changes together, we all feel responsible. I think all this is the real reason why I created the fork; it's about the people and about empowerment. Various instances already migrated towards Mbin, see: [https://fedidb.org/software/mbin](https://fedidb.org/software/mbin). Mbin is backwards compatible with kbin, so migration should be straight forward and easy. **Success story:** Jerry almost gave up [fedia.io](https://fedia.io/), if it weren't for Mbin, we would already have lost a big federated instance (I genuinely didn't know he was about to give up). Luckily the fork gave him hope. And hopefully I gave everybody hope again.
[@melroy](https://kbin.melroy.org/u/melroy) Because of using some very generic tags on your magazine as featured tags, this microblog gets filled with unrelated things. [\#updates](https://kbin.melroy.org/tag/updates)
The global Vascular Closure Devices (VCD) market size is expected to reach USD 1.67 Billion in 2030 and register a steady revenue CAGR of 7.0% during the forecast period. Growing prevalence of Cardiovascular Diseases (CVD) and obesity is a major factor driving market revenue growth. [https://www.emergenresearch.com/industry-report/vascular-closure-devices-market](https://www.emergenresearch.com/industry-report/vascular-closure-devices-market) [\#updates](https://kbin.melroy.org/tag/updates)
I pushed recently various sql improvements into the `develop` branch: [https://codeberg.org/Kbin/kbin-core/commits/branch/develop](https://codeberg.org/Kbin/kbin-core/commits/branch/develop) I advise all /kbin server owners to update their instance again! I went through all the source code, fixing all possible sql injections once and for all. I have no idea how this all ended up in the code in the first place to be honest. New code needs to be peer reviewed thus verified by another person, unit tested and follow our coding style guide as well.
Yes you heard that right, we are planning for the first /kbin release. Currently most server admins are running directly from the `develop` branch since /kbin is still in very (early) active development. That being said, we are planning for creating the first tagged released of /kbin! We still merge several pull requests, but holding off a bit. At the same time we are looking at all the high priority issues, seeing if some of those can be resolved or mitigated before the first tagged version. I already introduced some basic CI/CD Workflow Actions within Codeberg. Also Ernest setup several development environments. All these preparations are necessary to achieve a better, faster and more stable release cycle in the near future. Thanks to all contributors and of course [@ernest](https://kbin.social/u/ernest) and [@piotrsikora](https://pol.social/@piotrsikora). Thank you all for this wonderful community and becoming part of it. \~Melroy
[See my TIL post](https://kbin.melroy.org/m/til/t/7138/TIL-getting-continuous-integration-working-on-Codeberg)
They mentioned that were blocking all 'bot' user-agent strings, which [unintentionally also blocked /kbin bot](https://kbin.melroy.org/m/updates/t/5590/Lemmy-ml-blocks-KbinBot-UA-again). The issue is finally landed to the devs, thinking there was no such block (but there was). Anyhow, it's now been resolved. Federation should finally work again. See also: [https://lemmy.world/comment/1082149](https://lemmy.world/comment/1082149)
Dear kbin server owners, **upgrade your Kbin instance now**! Ernest just merged a critical hot fix into the `develop` branch. If you don't update, your Kbin instance is vulnerable for HTML/JS injection. Which allows bad actors to do very nasty things on your instance and attack your visitors on your site. Commit: [https://codeberg.org/Kbin/kbin-core/commit/8ee87ba9fbb3192865dfebb054bec3da56b9493e](https://codeberg.org/Kbin/kbin-core/commit/8ee87ba9fbb3192865dfebb054bec3da56b9493e)
In the past weeks lemmy.ml was activity blocking all /kbin instances by looking at the user-agent string "KbinBot" (case-insensitive). Which causes quite a few problems on several /kbin instances, because lemmy.ml didn't want to federate with 'us'. Recently, Lemmy.ml removed this block so it started federating again, at least so we thought. Today it seems that Lemmy.ml is block all /kbin instances again: ``` curl -I --user-agent "kbinbot" https://lemmy.ml HTTP/2 403 server: nginx date: Thu, 06 Jul 2023 20:02:34 GMT content-type: text/html content-length: 146 vary: Accept-Encoding ``` Lemmy developers or the community never responded to any of our questions or request for clarification about this matter. Ps. I know lemmy.ml is not 'whole Lemmy'. However, Lemmy.ml instance is hosted by the official Lemmy developers (Dessalines and nutomic) and considered one of their biggest instances. @lemmy.ml Please, can you be transparent about the reason why? Could we help you maybe?
Currently, the kbin.social instance has planned maintenance. They are busy upgrading the infrastructure to Kubernetes, using Docker containers. They said it shouldn't take much longer than 1 hour downtime in total (if everything goes fine). The migration will help to dynamically scale the instance, to remove the growing pains. And hopefully increase the availability (uptime) as well. Soon additional setup configurations, best server practices and [ansible](https://www.ansible.com/) playbooks will be shared with the community. In the meanwhile you can of course use other instances (I bet you are reading this message right now from another instance).
Today kbin.social is blocking a huge list of domains just to get federation working again. The reason for this temporally block is **not** to defederate, but rather to get the large backlog of 500k messenger queue processed again. Anyway, this does mean that kbin.social is federating again with other instances. This is a temporary measure. Several users / developers are looking into how to better optimize the failed message queue, as we speak. Hopefully Ernest has eventually time to dive into solutions as well instead of workarounds, once his instance is migrated to Kubernets. See my preview thread: [https://kbin.melroy.org/m/updates/t/4257/Kbin-federation-issues-and-infra-upgrade](https://kbin.melroy.org/m/updates/t/4257/Kbin-federation-issues-and-infra-upgrade) List of the domains causing trouble: > > > lemmygrad.ml, eientei.org, vive.im, lemmy.ml, lemmynsfw.com, kbin.lol, lemmy.webgirand.eu, tuna.cat, posta.no, lemmy.atay.dev, sh.itjust.works, kbin.stuffie.club, kbin.dssc.io, bolha.social, dataterm.digital, kbindev.lerman-development.com, test.fedia.io, mer.thekittysays.icu, lemmy.stark-enterprise.net, kbin.rocks, kbin.cocopoops.com, kbin.lgbt, lemmy.deev.io, lemmy.lucaslower.com, lemmy.norbz.org, social.jrruethe.info, digitalgoblin.uk, pwzle.com, lemmy.friheter.com, federated.ninja, lemmy.shtuf.eu, u.fail, arathe.net, lemmy.click, thekittysays.icu, lemmy.ubergeek77.chat, lemmy.maatwo.com, faux.moe, eslemmy.es, seriously.iamincredibly.gay, test.dataharvest.social, programming.dev, kbin.knocknet.net, pawb.social, lucitt.social, longley.ws, kbin.dentora.social, atay.dev, lemmy.kozow.com, ck.altsoshl.com, pawoo.net, techy.news, lemmy.vergaberecht-kanzlei.de, lemmyonline.com, beehaw.org, pouet.chapril.org, kbin.pcft.eu, fl0w.cc, lemmy.sdf.org, lemmy.zip, feddit.dk, fedi.shadowtoot.world, lemmy.noogs.me, lemmy.kemomimi.fans, social.agnitum.co.uk, fediverse.boo, hive.atlanten.se, forkk.me, lemmy.ghostplanet.org, lemmy.mayes.io, lemmy.mats.ooo, lemmy.world, lemmy.sdfeu.org, lemmy.death916.xyz, geddit.social, masto.fediv.eu > >
As you may notice, kbin.social experience several federation issues. @ernest is fixing deleting / editing remote instances problem on the current `develop` branch. Furthermore, 450k messages are still in the queue on kbin.social again, causing those federation issues. Soon kbin.social instance will be moved to the new infrastructure (using Docker on a kubernetes cluster). Which hopefully would fix all of those scalability issues we're currently experiencing. I'll keep you posted! Thank you server admins for your patience. Thank you developers for contributing.
Don't forget you can change the look & feel of kbin. Go to the setting (gear icon) menu. And try out all the options. Adapt the settings to your preferences!