What happens if it's a really tall image, will it take up a huge amount of the timeline or is there a limit?
Top-level
What happens if it's a really tall image, will it take up a huge amount of the timeline or is there a limit? 27 comments
That's what concerns me :/ I can see why people want to move outside 16:9 but you'd think there would be some kind of limit? Limit is on home feed and other feeds, but not within threads. Works for me, as I don't have trust issues with image height in the threads I'm opening. 😁 What bothers me is that many clients do not follow the focus point on images which have it set via Mastodon web interface. It cuts off the image to 16:9 aspect ratio in the wrong position, when viewed through other clients. 🤔 You already have your answer, but I'll confirm with another detail. I use the advanced desktop UI (the one with the columns) and it not only takes up a large space in the feed, but when I expand it, it is expanded but super narrow with no way to zoom to 100% on a click, so it's illegible on both the timeline and on the click. @ericheiken @feditips @Gargron Lack of zoom makes detalized photo and, especially, art sharing here a lost cause, IMO. Hopefully the steps we're taking to provide feedback is all it takes to improve the experience. It's a relatively young software, so don't lose hope. @ericheiken @feditips @Gargron Yeah! Definitely need to remind myself to search through the issue tracker or file a feature request. @feditips @Gargron I thought this would be a more convenient way of viewing this remarkable graphic. https://www.youtube.com/watch?v=got07wxkOoM Yeah, this is more what I expected to happen. Otherwise trolls could sabotage timelines quite easily if there's really no limit at all? @feditips@mstdn.social @Gargron@mastodon.social I kind of like what misskey/firefish do (displaying images in a 16:9 box, but scaling instead of cropping) |
@feditips @Gargron Takes up a huge amount of space right now, check out this GitHub comment: https://github.com/mastodon/mastodon/pull/26132#issuecomment-1649263201