You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PNG files allow for blocks of bytes marked as "ignore" which we can use to embed metadata information about the image.
The contents of all the settings used to generate the image would not inflate the size by much, but it would allow us to recreate the image from a sample of code. A user could upload an image to carbon.now.sh that was generated by the same tool and be able to make slight edits and tweaks to the original image.
Upsides
You can "copy" code from a carbon.now.sh file - you wouldn't need an OCR to get the code contents.
You can make quick corrections to code samples (an API is updated, name change, bug fix) without needing to recreate the entire image from scratch.
Impact on image size would be minimal.
Quick to generate in the browser.
Actual issues
A standard for serializing carbon settings.
We're compressing to bits. We could store settings pretty efficiently if we wanted to.
This could also be rolled out without including settings meta-data. The contents of the image is more important than the surround settings.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
PNG files allow for blocks of bytes marked as "ignore" which we can use to embed metadata information about the image.
The contents of all the settings used to generate the image would not inflate the size by much, but it would allow us to recreate the image from a sample of code. A user could upload an image to carbon.now.sh that was generated by the same tool and be able to make slight edits and tweaks to the original image.
Upsides
Actual issues
Beta Was this translation helpful? Give feedback.
All reactions