You could (but not necessarily should) combine them by making the trunkver the "patch" part of semver.
In our work, the semver is kept separate from the build version. We use a build versioning of vYYYY-MM-DD[.hhh] where hhh is for a "hotfix" of a previously released version.
The version of the "next" release can be set (either in advance, or based on a sprint or just the current date).
from semver spec:
4) Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
But it's 200x.
Right?
I can't see any world where chat gets standardized that doesn't involve throwing out everything except the most basic sms-style semantics which is basically what RCS is.
(One should also note that mortage rate here in Sweden are still surprisingly low. My 3 month fixed rate right now is 3.65% of which I get back 30% via taxes. Hence I am effectivly borrowing at 2.5%)
Or use Belize dollars. They’re worth $0.50 by law and have no instability issues.