You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the service only supports displaying the first image/video in a post
The most likely best fix for this would be what VxTwitter does, which is to take all of the images in a post, and merge them into one single image in a grid:
This could be achieved using the Pillow library for Python, or another image handling library.
This would require that the embed images are actually served by the application instead of directly linking to them, which may require use of the privex-helpers cache system (via redis or memcached adapter in production) to speed up requests and avoid constantly rendering images unnecessarily.
NOTE: This shouldn't be done for videos, only images. For videos it's best that we continue to display just the first video, as it would be difficult to merge videos into one video, especially due to audio tracks. Videos should probably take priority over images, if a post contains a video, then we display just the video, or possibly we base it off of the first media, i.e. if the first media is an image, we display only the images, if the first media is a video, we display just the first video
The text was updated successfully, but these errors were encountered:
Some Fediverse applications allow more than 4 images, so if #3 gets implemented this would need to be extended
I think limiting it to 4 is fair though, as this seems to be the general limit on most platforms. I think combining more then 4 images to a single image will just not be practical, at that point you may as well open the whole post.
At the moment, the service only supports displaying the first image/video in a post
The most likely best fix for this would be what VxTwitter does, which is to take all of the images in a post, and merge them into one single image in a grid:
This could be achieved using the Pillow library for Python, or another image handling library.
This would require that the embed images are actually served by the application instead of directly linking to them, which may require use of the privex-helpers cache system (via redis or memcached adapter in production) to speed up requests and avoid constantly rendering images unnecessarily.
NOTE: This shouldn't be done for videos, only images. For videos it's best that we continue to display just the first video, as it would be difficult to merge videos into one video, especially due to audio tracks. Videos should probably take priority over images, if a post contains a video, then we display just the video, or possibly we base it off of the first media, i.e. if the first media is an image, we display only the images, if the first media is a video, we display just the first video
The text was updated successfully, but these errors were encountered: