Mark Dain @sublevel: What happened to the photos feature?

😀 Tom I'm a little curious myself. My guess is that @lucian is just reworking the code. I don't have any pictures right now that I want to share though. Maybe in the future, once I organize my personal files and find a couple. (Organizing my files has been on my to-do list for years, so who knows when I'll actually get to it.)

🏒 Lucian Marin You're right. Photos were an extension of updates so we can have replies and likes. The result was bad and messy because the entire site was getting slower with each new photo -- yeah, that's how Django filtering works for image fields. Now if photos are a different table in the database, the speed will be good, but they will be pretty static -- no way to interact with them. Also, the aspect ratio 16:9 and resolution 480x270@2x were messing with the way text entries looked (too narrow, too much to scroll). For time being I'm rethinking everything related to photos.

Mark Dain Ouch. Yeah I'd rather Sublevel remain fast rather than being slow from all the features. Perhaps there's some way to bypass this in Django? Like flagging "this is not an image, skip image routines"?