"Upload keeping file names" and "Upload will create random file names".
I have to look into that possibility. I will have to analyze.
One argument for long random names would be to prevent users from guessing the link, but your backup .zips make that possible anyway.
It really makes sense to try to reduce the number of characters. I'll see what I can do about that.
Calm down, I will share this data at the end of the month.
But this month the data will also be a bit inflated because of the image migrations made by users.
directly, I get this:
First of all this image works normally:
https://talkimg.com/images/2023/05/11/TRD-copy2c3b017b31752bf10.png
Then the links of the images placed in this post do not have "https", that's why this error occurs.
Either it was the user who didn't use the link correctly, or for some reason the wrong link was issued. Maybe in server migration, something might have happened.
I have everything set to work on "https" and that's the base it should work on. The proxy doesn't fix links, so if the user types "http" it won't convert to "https". By the way, if you don't put "https" in the link, just put "www" the proxy won't recognize the image.
EDIT:
That said, I'm in doubt: when users create a topic, don't they check if everything is working well?