Mbin Blog Updates

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 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 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

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

Docker images also: https://github.com/MbinOrg/mbin/pkgs/container/mbin

• Remove the local condition from magazine autocomplete by @BentiGorlich in #455
• Add missing flash on contact form by @melroy89 in #454
• Translations update from Hosted Weblate by @weblate in #460
  add user badges to entry and post templates by @e-five256 in #467
• Reread and update as well by @melroy89 in #462
  make search recognize !group handle format by @asdfzdfj in #465
• fix nodeinfo schema wrong version, add metadata by @asdfzdfj in #471
• load custom css from routes instead of inline by @asdfzdfj in #472
• adding alt text as caption in lightbox by @asdfzdfj in #473
• hotfix: allow custom style while still in 2fa by @asdfzdfj in #488
• Change the messenger queue layout by @BentiGorlich in #461
• Translations update from Hosted Weblate by @weblate in #474
• Using loading lazy on images by @melroy89 in #491
• Preload our logo by @melroy89 in #493
• FAQ: Explain 'all' messages by @melroy89 in #490
• FAQ: Retries three times by @melroy89 in #489
• FAQ: Typical message queue has changed by @melroy89 in #492
• Fix error on entries with an empty body by @BentiGorlich in #504
• move service worker registration into main app bundle by @asdfzdfj in #507
• use title instead of body for federated entry summary by @asdfzdfj in #506
• adjust tag matching to better handle some eastern scripts by @asdfzdfj in #508
• somewhat fix phpunit so it could run functional tests again by @asdfzdfj in #396
• Add column last_origin_update to magazine by @BentiGorlich in #503
• Add the correct cascading attribute to Entities by @BentiGorlich in #500
• Update Symfony packages + recipes+ NPM by @melroy89 in #510
• Update remaining composer packages by @melroy89 in #512
• Fix circular message by @BentiGorlich in #514
• Add support for incoming dislikes by @BentiGorlich in #513
• Remove route for down votes and make it a span by @BentiGorlich in #516
• Upgrade all remaining symfony packages by @melroy89 in #517
• Fix imagemanager not having a useful error message by @BentiGorlich in #523
• slightly fix object body extraction on set but empty body by @asdfzdfj in #525
• Update Postmill link by @melroy89 in #526
• Improve handling of images by @BentiGorlich in #501
• Update version number for 1.4 release by @nobodyatroot in #530
  more @ https://github.com/MbinOrg/mbin/compare/v1.3.0...v1.4.0

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.

Visit the project page: 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. I wanted to avoid a fork initially, but I didn't saw any way out.

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 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 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. Mbin is backwards compatible with kbin, so migration should be straight forward and easy.

Success story: Jerry almost gave up 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 Because of using some very generic tags on your magazine as featured tags, this microblog gets filled with unrelated things.

#updates

I pushed recently various sql improvements into the develop branch: 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 and @piotrsikora. Thank you all for this wonderful community and becoming part of it.

~Melroy

See my TIL post

They mentioned that were blocking all 'bot' user-agent strings, which unintentionally also blocked /kbin bot.

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

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

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 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

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!