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

kingdom Valley Lahore payment plan

In the bustling metropolis of Lahore, where history mingles with modernity, there lies a haven of tranquility and luxury: Kingdom Valley Lahore. Nestled amidst lush greenery and serene landscapes, this residential marvel offers not just homes, but a lifestyle epitomizing elegance and comfort. As you embark on your journey to secure your slice of paradise, navigating through the** Kingdom Valley Lahore payment plan** becomes imperative. Let's delve deep into the intricacies of this plan and explore the various choices available to make your dream a reality.

Understanding Kingdom Valley Lahore: A Beacon of Luxury

Before we dive into the realm of payment plans, let's acquaint ourselves with the jewel of Lahore – Kingdom Valley. Situated in the heart of the city, Kingdom Valley Lahore redefines luxury living with its meticulously crafted architecture, world-class amenities, and a commitment to excellence in every aspect. Boasting a range of residential options, from opulent villas to chic apartments, Kingdom Valley caters to the diverse needs and preferences of its discerning clientele.

Decoding the Kingdom Valley Lahore Payment Plan: Your Pathway to Ownership

Embarking on the journey to homeownership entails careful consideration of financial aspects, and the Kingdom Valley Lahore payment plan offers a range of options to suit every budget and requirement. Whether you seek flexibility, affordability, or premium offerings, Kingdom Valley has tailored payment choices designed to accommodate your aspirations.

1. Flexible Installment Plans: Tailored to Your Convenience

For those seeking flexibility in managing their finances without compromising on their dream home, Kingdom Valley Lahore presents a range of flexible installment plans. These plans allow buyers to spread their payments over a predefined period, easing the burden of a lump-sum payment. With flexible installment plans, homeowners can embark on their journey to Kingdom Valley with confidence, knowing that their financial commitments align with their capabilities and preferences.

2. Deferred Payment Options: Paving the Way for Future Investments

In a world where financial planning plays a pivotal role in shaping our future, Kingdom Valley Lahore offers deferred payment options that empower buyers to invest in their dream home without immediate financial strain. With deferred payment plans, buyers can secure their slice of paradise today while deferring a portion of the payment to a later date, thereby unlocking opportunities for future investments and financial growth.

3. Special Incentives and Discounts: Maximizing Value for Discerning Buyers

Recognizing the significance of value-driven investments, Kingdom Valley Lahore extends special incentives and discounts to its discerning buyers. From early bird offers to exclusive promotions, these incentives add an extra layer of value to your investment, ensuring that you not only secure your dream home but also maximize returns on your investment.

4. Customized Payment Solutions: Empowering Your Journey to Homeownership

At Kingdom Valley Lahore, customization is key, and the payment solutions offered reflect this ethos. Whether you seek a personalized payment plan tailored to your specific requirements or wish to explore alternative financing options, Kingdom Valley's dedicated team is committed to empowering your journey to homeownership. From mortgage assistance to bespoke payment structures, the possibilities are endless, ensuring that your pathway to Kingdom Valley is as seamless as it is rewarding.

Navigating the Kingdom Valley Lahore Payment Portal: A User-Friendly Experience

In an era dominated by digital innovation, Kingdom Valley Lahore leverages technology to enhance the homebuying experience for its clientele. With an intuitive payment portal designed to streamline the payment process, buyers can effortlessly manage their payments, track transaction history, and stay updated on upcoming deadlines. The Kingdom Valley Lahore payment portal is more than just a platform—it's a gateway to convenience and peace of mind.

#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

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

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

#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

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!