Firmware updates still scare me.
| homepage | https://hil-de.de |
| pixelfed | https://pixelfed.de/biggerchipmunk |
| android apps | https://play.google.com/store/apps/developer?id=Denny+Hildenbrandt |
| homepage | https://hil-de.de |
| pixelfed | https://pixelfed.de/biggerchipmunk |
| android apps | https://play.google.com/store/apps/developer?id=Denny+Hildenbrandt |
Firmware updates still scare me.
I just started to publish my photos on @pixelfedde
You can find me here: https://pixelfed.de/biggerchipmunk
This is my first step to getting away from Instagram.
38 Posts, 26 Following, 25 Followers · Fotografieren als Hobby, hauptsächlich #Natur, #Tiere, #Makro oder #Landschaft---Photography as a hobby, mainly #nature, #animals, #macro or #landscape#CanonR7 #CanonLens #Sigma #SigmaLens
Had a lot of fun with this years #AdventOfCode https://adventofcode.com/2025.
Thank you @ericwastl for making these puzzles!
@normplum This will not work as soon as parts of the version have more than one digit. I.e. 11.0.0 (1100) will have the same version as 1.10.0 (1100).
Also later versions will have lower version codes. I.e. 10.0.0 (1000) vs. 2.0.15 (2015).
To solve this I'm using the following formula to calculate a unique, order-able version code: Given major.minor.fix use ((major*100 + minor)*100 + fix).
For the examples above this will be 110000 (11.0.0) and 11000 (1.10.0), or 100000 (10.0.0) and 20015 (2.0.15)
If you expect three digit parts of the version code you have to use a factor of 1000 instead of 100 in the formula.