Can not wait for final release, but why v10.11? Such big changes.. V11 would be better imo 🤔
Anyway thanks to the devs for this great release
this post was submitted on 13 Oct 2025
156 points (98.1% liked)
Selfhosted
52365 readers
805 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
I think the feel from the Devs is that there isn't enough new functionality to justify the major version bump, this primarily being a reimplementation of existing features.
BUT, I agree with you, it should definitely be V11 under the semantic versioning scheme.
Whilst there is a migration path here, the database changes under the hood alone are likely to break backwards compatibility with all plugins (with in-house plugins being upgraded in sync).
Such breakage is kind of the defining characteristic of a MAJOR version.
New funcionality I would like to see would be SSO with OIDC without an exterrnal plugin 😁
Maybe then we get v11
Same dude.... Same
In traditional versioning systems you only jump major versions if you break compatibility with previous versions. For instance Semantic Versioning.
Which they do here. Once you upgrade to 10.11, your database is not 10.10 compatible anymore. So you can't downgrade without restoring a backup.
If an app will work with both without needing to change its API then that counts even if it can’t use the new features.
HEVC support is enabled for Firefox 134
Cool for anyone not using AV1 which I assume is a big chunk of the userbase because not everyone has good AV1 hardware acceleration lol
Unless the media also uses HDR in which case the server will still be required to transcode.
The startup UI is a neat idea