I've worked on teams where any observable change is basically a breaking change, just because of how many people were using it (think spacebar heating https://xkcd.com/1172/). If we were being honest with ourselves, we'd bump the major every release.
And I've also dealt with tiny OSS libraries that flatter themselves by releasing 17 major versions in a year, forcing me to comb through their release notes to find they made some tiny innocuous change. There is no perfect way to do semver.
Chirp! is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Chirp! content and data are available under the Creative Commons Attribution 3.0 license.