proposal: use inscription_id instead of inscription_number for /num/*.png

[jokie88]

trafficstars

Hi!

I think it may be more robust to issues to use the inscription_id instead of the inscription_number as the "key reference" for orc-721.

Reason:

1. Inscription number could shift since it is a manually constructed ID depending on what is included/excluded from the ordinalds standard.
2. InscriptionID will not change and is unique to each inscription

(this is for num/*.png specifically but may be a good standard to use across the project)

[geraldb]

summary - let''s make it a requirement / policy to upload / commit / save the image indexed by inscribe id AND num here - i will rewrite the README shortly.

thanks for all your support - i personally prefer numbers because they are more human and easier to use and remember for humans and promote the idea of the "long count" going from 0 to infinity - and bonus - easy to sort / order by date - 0,1,2... .... i see your point about bitcoin / inscribe tx ids ... here's the promise (and suggestion) ... let's always upload both ... indexed by num & id (git itself is content-addressed storage e.g. indexed by content hash and not file name/dir hierarchy - so the image is in the blog store only once and gets referenced in the "commit tree" - that is my understanding of the git internals). note: the only oonstraint is the image size ... i run here on a (personal) free plan (with space limits)