Maybe....but despite it being unprecedented, is there really any technical reason Ken couldn't just roll into 3 digits for the final "octet"?
IE: 5.9.9.100 , etc.
I actually think it is likely he can continue up to
5.9.9.255. I had been saying for a while that I think 99 is the highest possible version number in Ken's system based on the insane way he makes people encode the version number in his web server JSON API for remotely installing a BI software update. Here's the help file documentation for that:
“version, flags” install current software update. version is the HEX formatted number, for example 0x05030906
(5.3.9.6), converted to decimal (84084998 for this example). flags should be 0.
But I was wrong. The help file description does not make this clear due to a poor choice of example, but the hex formatted number does in fact use base-16 encoding, so this scheme supports version numbers up to 255 in each segment (not 99).
Version
5.9.9.100 would literally encode as
0x05090964 ->
84478308, and nothing breaks due to this.
This isn't to say that
nothing will break if he releases
5.9.9.100, but it won't be this part that breaks at least.
Blue Iris update files as downloaded by Blue Iris are also named poorly, like this one is the current version:
The only way that naming scheme works is if the first 3 segments are a single digit long. That is probably why we never got a 5.9.10.0 or 5.10.0.0. Granted, this is a really silly reason that he could have eliminated a long time ago if he wanted to badly enough. He didn't do it though.
The fact remains, Ken has a tendency to code himself into arbitrary limits when it comes to numbers/sizes so there may be other reasons in less visible parts of Blue Iris's code base that would prevent the last segment from growing to 3 digits. We may find out soon enough
