It's not feasible to do any of this on a single client because another client can just ruin your day. You can implement compression and resizing just fine, but people can just share a link and it renders, or upload through another client.

You also can't really block large images because by the time you see it it already loaded. In some cases HTTP headers will solve this for you but in many instances you won't have this info at all.

You are right that you can cache things, and it's not an issue then, but this is an issue particularly on mobile connections and particularly on slow ones.

For slow connections though we can disable automatic loading of all media (as some clients have done).

Reply to this note

Please Login to reply.

Discussion

No replies yet.