In this part of the Meteor microblogging course, I take the profile image we already uploaded and stored on S3 and make it show up in the actual UI. Uploading is cool, but if you can’t display it cleanly, it’s basically useless—so the goal here is simple: when a user has a profile photo, the app should render it reliably and make the profile feel “real”. I focus on wiring the stored image URL into the places people expect to see it (think profile page, avatar spots, and anywhere you reference the user). The big takeaway is treating the profile image like any other piece of user data: store it properly, read it consistently, and always have a sensible fallback when it’s missing. By the end, you’ve got a Meteor app that pulls the profile photo from S3 and displays it for the world to see, without turning your templates/components into a mess.