Site Development Notification and Feedback Thread

@evan555alpha  
The change from moving the sorting in the database (which does collation) to doing the sorting in the application (which doesn’t, and sorts by codepoint values) caused the change.

>>828677 Also, why are the comments on this locked? As far as I’m aware, there was no hate, which I thought was the sole reason that happened. What’s wrong with an image simply having a lot of comments?

@reversalmushroom  
It hit the max amount of comments an image could have, so that’s why it got locked.
 
It literally could not take any more comment.

@icey wicey 1517  
Then we should up that so it can move onward to infinity.
 
Why would it have a maximum number built in? I’m guessing a comment section would normally just allow infinite commenters, so someone had to actually go in and make it stop at 200035. I don’t think it would crash the site or cause problems in the display because it only ever shows a small number of comments and pages at 1 time.

The image comment and thread post limits are sanity checks for the database to avoid it using a lot of memory while sorting.

@reversalmushroom  
Someone did have to go in and lock that particular picture, the comment limits have been introduced afterwards (and IIRC are a lot smaller today than 200k).

@reversalmushroom  
Good times….

@ЅℰℒᎯℙℋℐℰℒ  
I remember that it broke comment pagination (the comment fetching would always return the first page)

How come we can’t put the tag “drama in the comments” anymore? I saw an image I wanted to put that on.

@reversalmushroom  
I’m assuming that the mods don’t want to formally recognize comment drama as something notable, and don’t want to enable the sort of person who would actively search for “drama in the comments”.

@reversalmushroom  
It was banned four years ago (Oct 2016 to be specific) for the reason BP described.

site’s upload file size limit has been increased

@Luna  
Increased to how much now?

@Luna  
How many gigs?

@evan555alpha  
100MB (100,000,000 bytes exactly)

@Luna  
Such a weird random number.
 
Why not use a nice round number, like 104857600?

@JP  
Computers are weird.

@Luna  
@JP  
@Officer Hotpants  
1024 > 1000 when it comes to describing computer storage and speeds.
 
Even if I think that the term “mebibytes” is fucking stupid and the “mega” prefix (and others used in computer terms) should just change based on context.

@Luna  
100MB  
That sounds kinda dangerous for mobile users, are WEBM and GIF thumbnails still throttled to a maximum size?

@TexasUberAlles  
all >25MB thumbnails are throttled to the variants they would’ve had if they were <25MB (e.g. medium)

@TexasUberAlles  
Browsers download video files progressively, using byte-range requests instead of downloading the whole thing at once.

@byte[]  
With my connection, I am very much aware! Apparently Hughesnet is bouncing this signal off the Andromeda Galaxy or something, WEBM loads like GIFs on AOL dialup.
 
Android Firefox tends to just start crying and give up partway through a large video file unless the data signal is at maximum bars.

@TexasUberAlles  
My point was that throttling the thumbnail size for slower connections isn’t needed for videos because browsers won’t download that much at once to begin with.

@reversalmushroom  
There are still “argument in the comments” and “discussion in the comments”

From upstream Philomena: Animated uploads (including GIF, APNG, and WebM video) now display the duration of the animation in the metabar.
 
To do: add search UX to be able to filter and sort by duration.