This system will take images and store them in an appropriate folder. There will be the option to create a compressed "web version," but the original will always be kept as well.
Images that I'd want to store include images that I upload as posts, profile pictures linked to h-cards, and images that other people post in reply to mine.
There will be a table of images, each with its own ID. The table will remember the location of the original photo as well as the location of the web-friendly one, should it exist.
Web-friendly versions will be created by default, and preferred when serving. This is important not only because I want to decrease bandwidth when possible, but also because I want to serve predictable and well-supported filetypes/encodings. The originals will be kept for a similar reason: I'd like to be able to re-encode all of my assets in the future if I like, without losing any quality.
Another feature I'll likely add is a thumbnail for each photo. This is an image scaled down to a relatively small size for previews or other small situations. A use case I have in mind for this is the facepile of people who've liked a given post: those will be small images, and I don't want to be serving full-size ones.
This issue will probably be broken into sub-issues in the future.
This system will take images and store them in an appropriate folder. There will be the option to create a compressed "web version," but the original will always be kept as well.
Images that I'd want to store include images that I upload as posts, profile pictures linked to h-cards, and images that other people post in reply to mine.
There will be a table of images, each with its own ID. The table will remember the location of the original photo as well as the location of the web-friendly one, should it exist.
Web-friendly versions will be created by default, and preferred when serving. This is important not only because I want to decrease bandwidth when possible, but also because I want to serve predictable and well-supported filetypes/encodings. The originals will be kept for a similar reason: I'd like to be able to re-encode all of my assets in the future if I like, without losing any quality.
Another feature I'll likely add is a thumbnail for each photo. This is an image scaled down to a relatively small size for previews or other small situations. A use case I have in mind for this is the facepile of people who've liked a given post: those will be small images, and I don't want to be serving full-size ones.
This issue will probably be broken into sub-issues in the future.