The feature to sort by random is partially functional: if /library/browse?order=random is added to the URL, it does show a random assortment of photos. However, when one is clicked on, instead of opening the intended photo, it opens a different, random one instead. From what I understand, this is only an issue with large libraries. If a non-empty search query is added to the URL as well, the random sort does function as intended (Note that a wildcard search, i.e. adding &q=* or similar to the URL was considered, but the random sort does not work when done in that way). I would like to request that a workaround be implemented that enables the sort by random feature to work on large libraries. It should, if possible, open the image or video the user clicked on rather than another, random image or video.
The feature to sort by random is partially functional: if /library/browse?order=random is added to the URL, it does show a random assortment of photos. However, when one is clicked on, instead of opening the intended photo, it opens a different, random one instead. From what I understand, this is only an issue with large libraries. If a non-empty search query is added to the URL as well, the random sort does function as intended (Note that a wildcard search, i.e. adding &q=* or similar to the URL was considered, but the random sort does not work when done in that way). I would like to request that a workaround be implemented that enables the sort by random feature to work on large libraries. It should, if possible, open the image or video the user clicked on rather than another, random image or video.