Thank you for the reply!
On the first point that’s good to hear. On the second point, I totally get that there can’t be unlimited threading and that eventually you’d run into overflow issues. I think my ideal solution if you’re looking for feedback is a “See More Replies” link after 2 threads? It’s something that’s hard to say for sure without testing and seeing, but on gut feel that seems right.
On the last point about image resizing, I’ve done a lot of investigating on my end. The issue I thought I had with it was a 2k x 3k image being resized to 500px tall. This was either a server distribution error at the time or user error due to me trying to save the thumbnail that appears on the feed.
It was then that I delved into the CSS and code to find out exactly how you’re serving up images. Even knowing exactly how it works now, in my opinion there’s still a lot of room for confusion and I’d like to offer additional feedback.
On image uploads there is no download button. Being that the entire point of an image post is a file, this seems like a missed opportunity and potential cause for confusion considering the feed image is resized.
Even on click the image is constrained to 90vh. That’s understandable because large images shouldn’t necessarily be made illegible by falling off screen, but it’s the enlarge function that’s especially frustrating. The enlarge button constraints to 1000px width. This means the user has absolutely zero user friendly ways of viewing a full size image in the browser. It could also lead a user to believe that the image itself is no larger than 1000px. Without a download or opening with a right click there is no way to know.
(By my math it also means that on 4k the enlarge button does nothing, which is more amusing than it is a problem)
If you could give me a way to serve the full sized images to my patrons I’d be really excited.