im not exactly sure how many images i will end up having to share for the project(As i havent even started taking screenshots of the actual full project document and the Project has surpassed 700+ Pages in Pageless format in Google Docs, i still have not finished the writing process because i still need to work on adding more clarity and improving immersion for storyboard images which will result in increasing the length of the document even more(More pages and ultimately resulting in having to take more screenshots and Get it uploaded on the discourse community which i have planned to share)).
lets assume if the end result is 1500 images which needs to be added as screenshots(Entire document shared as screenshots), Will discourse be able to handle the load ?, i ask this because sites like Google can handle the load, for example, while you search for “car images” and switch to the images tab, You can find Google displaying 500+ images at 1st and then “See more results” button where once clicked, Another batch of 500+ images will be loaded, So in Essence, Google servers can handle the load but asks for user input/consent to decide whether they want to see more images? so once users wishes to see it, more images gets loaded, is there any way to Get that behavior implemented?
Need more clarity ? See here
This is Speed up Version, 48 Seconds
Original Video, 90 Seconds
In the video, You can see the site only loads more images while “More” Button is clicked, Also, its important to note that the user needs to click more button only for the 1st two times, after you click more for 2 times, Site Server Seems to understand, user is interested in this Profile, So More Memes Gets loaded automatically(similar to infy scroll or uautopagerize extension in chrome store where paginated web sites will turn into infinite scroll) but after like 300+ images gets autoscrolled Server asks for confirmation(See 01:15 in the 2nd Video) and once clicked ~500+ images/videos will be auto scrolled before the “More” Button Shows up again.
Also you did not answer the question “how many images can discourse handle per topic ?” as your reply only says image loading behavior and discourse is not meant for conducting experiments which im fine as i can make the project look good even without testing(as now i know more ways to improve immersion), So thats not a problem But it would certainly feel Relieving if discourse says there are no limits and can also implement the same kind of behavior as seen in the video which i personally feel more Robust and yes its satisfying to know if the discourse systems are perfect, reliable and will succeed in handling/showcasing the 1500+ images to people who reads my topic exactly as i meant to be seen.
For Example, if there are 1500 images, it wouldn’t feel good if the discourse loads
1 to 360 images correctly
361, 362 missing
363 to 508 images correctly
508, 509 missing
Hope you’re grasping what i am trying to illustrate, Leaving some timeframe before the images gets loaded will be good, for Example discourse can load 1st 50 images as soon as the topic is opened, Load the Next 50 images in cache, RAM and display it only while the user reaches the end of 50th image would improve the experience. You say images not gets loaded all at once but there should be a limit on what’s considered as “on demand” by you, idk whats that default limit…
Overall, I will be happy if discourse can handled unlimited number of images , Sure Not everyone will scroll walls of text but for people who enjoy reading long topics/Like seeing a lot of new images will be happy to check them. I think having the “See more” Button will assure only people who are actually interested in having the topic to be checked will have more images getting loaded.
Why this is important ?
- Reduce Stress on Discourse Servers
If 1500+ images Gets loaded for Everyone who opens the topic and if more people opens the 1500+ image Loaded topic all at once, it will stress the servers and will slow down down the Performance of the Website.
- First Impression
Most of the Population have Limited Attention Span and will Lose interest/motivation to check the topics if they detect Massive “Walls of text” because most of the people checks the length 1st before investing to read and current Load behavior Get this task accomplished for the public who sees the topic so as a creator of the topic, it would be great to know only few part of the topic(1st 50 images) Gets Autoscroll support initially and the rest of the entire topic will Get loaded based upon consent(See more) which result in adding extra effort where this extra effort assures only people who Likes the topic will click the button so the other users who dont find the topic interesting wont load any more images and Exit the topic.
Here is a illustration
Discourse Servers detects My topic has 1500+ images
Server Loads 1st 50 images with Auto Scroll function
{user Reaches End of 50th image}
“See More” Button
User Clicks See More Button
Next 150+ images Gets Loaded
{user Reaches End of 200th image}
“See More” Button
User Clicks See More Button
Next 350+ images Gets Loaded
{user Reaches End of 550th image}
“See More” Button
User Clicks See More Button
Entire topic will Get Loaded as user scrolls, No More “See More” Button.
Hope you’re grasping the concept.
