yeah but its typical double speak

Why do you think so?

all “current” features. further down its asked about the future and they arent always clear but the fo state there wont be feature parity moving forward

Yup. All CURRENT, these will start to diverge…

I kinda thought the paid plan already had extra features no? Like silly ones but I swear it isn’t just donations right?

It had cloud storage, built in TOTP with autofill, and some had features like organizations and sharing

Still, this fucking sucks. Bitwarden was literally created as a ln answer to this shit happening to LastPass and Dashlane.

I get it because minio dying burned me hard but so long as it keeps operating as it does now do we need more features? I would be fine with a continuously secure version of exactly what it does now. I kinda hate feature bloat

If it’s not getting security updates and it’s not ona completely airgapped sysyem it’s a huge liability. Especially something that lives at the storage level.

Aren’t there forks being maintained? I was looking at implementing it right before it went enshitty, and I could have sworn there were alternatives…

I meant features on Bitwarden etc. meaning maintenance to me on an app like this is fine. Minio happened too quickly for good alternatives to exist but yes people jumped on getting some together pretty quickly.

It was, if anything, lesson in treating a single FOSS as a solved problem.

Unfortunately, there is no historical example where this hasn’t turned predatory. It’s a tale as old as venture capital has been in software development:

• get free contributions from altruistic people donating their time and expertise to your FOSS project that you’re selling
• make a closed-source set of extensions as optional dependencies
• slowly diverge the closed source feature set to include developer and user “must-haves” you do not contribute upstream
• slow or functionally halt open source contributions

It is an oft-repeated long con to pull off a mass heist of donated skill and time while imposing vendor lock-in on your users through a back door.

"As the poison spread through his body, the frog cried out, “Why did you sting me? You have killed us both!”

The scorpion replied, “I couldn’t help it. It’s my nature.”

• Embrace
• Extend
• Extinguish

I swear most of Grafana’s new features are enterprise only now

Good take. I trust you on this, if you mind me asking: What is now the alternative? A system of setting up once, let it work until hardware dies etc.

If there is no intention to put the screws to the user base, then why do it on the first place?

We all know how this game ends when venture capital gets involved.

@flop_leash_973 Where are the screws here?

Split versions is usually the first step. Many projects have done so before. Next year there will be some technical reason they can’t keep feature parity with the commercial repository, and it will drift from the OSS repository. Oops, we broke compatibility, sowwy guys. A couple of years later the OSS repository will be closed because it is a security risk. By that point the company and management would’ve drifted so far from the initial values of the project that people won’t notice. Those who cared will have jumped ship to alternatives sooner, those who noticed later will be already too deep into depending on the software that they will keep paying the subscription.

I have no evidence, but I also don’t have any doubts this is the plan.