Topic: TalkImg.com - Image hosting for BitcoinTalk - page 12. (Read 15544 times)
Event ____________________
I am pleased to announce the launch of the TalkImg Awards - Image of the Year 2023.
Everyone is invited to participate.
I can try asking @theymos to adjust the image proxy to 3MB, which would even give more freedom. 
That doesn't help. I forgot why you increased the limit from 2.5 MB to 3 MB, but this image should have been 1.4 MB so none of this is a solution.For this issue of changing the MB of images, it doesn't solve it. However, it has already been reported and is being analyzed to be resolved.
Regarding requesting a change in size, it was just to align strategies, nothing more. And in reality it provided another form of image management, but it is not something important.
Either way, there will soon be a correction so that only images up to 2.5MB are allowed.
Also these days I guess even 5MB images won’t hurt anyone.
I don't really see the point. The largest image I have posted, is still under 2 MB. There's no point embedding larger images. If you really need a higher resolution, add a link.I wonder what sort of image would need to be 5mb? I mean we dont need to be posting
large files like that, maybe on a photography website where people would be "pixel peeping".
And if accessing the forum through smartphone it enables us to zoom in if required for
more detail.
Essentially extra data means extra costs for storage.
large files like that, maybe on a photography website where people would be "pixel peeping".
And if accessing the forum through smartphone it enables us to zoom in if required for
more detail.
Essentially extra data means extra costs for storage.
You guys won't understand....
What sort of images... ??
Kinda this sort!!!
AI news - static memes are now moving!
There's always another side of the story.
This is our WO stuff... and it's important one.
Also these days I guess even 5MB images won’t hurt anyone.
I don't really see the point. The largest image I have posted, is still under 2 MB. There's no point embedding larger images. If you really need a higher resolution, add a link.Exactly. These days, image files can be made pretty small thanks to compression, so even full HD images don't take up too much space - usually less than 2.5 megs and that's plenty big enough for internet forums when most folks have 1080p screens or less anyway. Bigger files would just eat up bandwidth and slow things down without adding anything useful.
After all, the whole point of this forum is not showing off hi-res photos that nobody can appreciate on their monitors. I mean, unless you've got some specialty community for photographers or graphics work, do we really need massive images that take five minutes to load? Its better to keep file sizes reasonable so everything runs smooth and people can focus on the conversations.
Also these days I guess even 5MB images won’t hurt anyone.
I don't really see the point. The largest image I have posted, is still under 2 MB. There's no point embedding larger images. If you really need a higher resolution, add a link.I can try asking @theymos to adjust the image proxy to 3MB, which would even give more freedom.
That doesn't help. I forgot why you increased the limit from 2.5 MB to 3 MB, but this image should have been 1.4 MB so none of this is a solution.I wonder what sort of image would need to be 5mb? I mean we dont need to be posting
large files like that, maybe on a photography website where people would be "pixel peeping".
And if accessing the forum through smartphone it enables us to zoom in if required for
more detail.
Essentially extra data means extra costs for storage.
Also these days I guess even 5MB images won’t hurt anyone.
I don't really see the point. The largest image I have posted, is still under 2 MB. There's no point embedding larger images. If you really need a higher resolution, add a link.I can try asking @theymos to adjust the image proxy to 3MB, which would even give more freedom.
That doesn't help. I forgot why you increased the limit from 2.5 MB to 3 MB, but this image should have been 1.4 MB so none of this is a solution. You need to remove exif without recompressing the image. Not removing exif is bad, phones store your location by default if you take a picture.
Yes please... you have to remove exif data, either when you are serving the images or at saving... but exif data should be removed.
Yes, I will keep removing Exif from images. I completely agree that this is an important thing.
The problem has already been reported, to be analyzed and corrected.
I also made the request to @Theymos.
At the moment I have TalkImg configured for uploads of up to 3MB, but the forum only accepts up to 2.5MB.
This is already being resolved at the script level, but it could still take a few months to be implemented.
I can try asking @theymos to adjust the image proxy to 3MB, which would even give more freedom.
It doesn't hurt to try.
This is already being resolved at the script level, but it could still take a few months to be implemented.
I can try asking @theymos to adjust the image proxy to 3MB, which would even give more freedom.
It doesn't hurt to try.
Yes, I agree. We will support you. Let’s ask theymos to allow images from TalkImg, supporting up to 3MB. That would be one way to encourage people to use TalkImg.
Also these days I guess even 5MB images won’t hurt anyone. We will ask for full HD images later but let’s go for 3MB first
You need to remove exif without recompressing the image. Not removing exif is bad, phones store your location by default if you take a picture.
Yes please... you have to remove exif data, either when you are serving the images or at saving... but exif data should be removed.
You need to remove exif without recompressing the image. Not removing exif is bad, phones store your location by default if you take a picture.
Try something like exiftool.
Try something like exiftool.
@LoyceV @Apocollapse
Apologize for the double post, but it was important to resolve this issue.
I have already discovered the mystery of this question that arose with this image!
As you know, TalkImg eliminates metadata (Exif data) from images. This means that new images have to be created when they enter the system. So, this can cause some images (especially those that have already been compressed before in some software) to have a different size, as we are creating a new image, which could eliminate some compression elements.
As an immediate solution, TalkImg could stop automatically editing/deleting Exif data. What do you think?
Either way, I will try to resolve this issue at a programming level, but it may take a little longer.
EDIT:
As an informative note. I disabled the Exif removal function and uploaded the image in question. The result was that it maintained the image size. When I reactivated this function, the result was that the image was almost double the size.
Apologize for the double post, but it was important to resolve this issue.
I have already discovered the mystery of this question that arose with this image!
As you know, TalkImg eliminates metadata (Exif data) from images. This means that new images have to be created when they enter the system. So, this can cause some images (especially those that have already been compressed before in some software) to have a different size, as we are creating a new image, which could eliminate some compression elements.
As an immediate solution, TalkImg could stop automatically editing/deleting Exif data. What do you think?
Either way, I will try to resolve this issue at a programming level, but it may take a little longer.
EDIT:
As an informative note. I disabled the Exif removal function and uploaded the image in question. The result was that it maintained the image size. When I reactivated this function, the result was that the image was almost double the size.
It really doesn't make sense, sometimes the way the image was originally compressed can cause this type of problem.
Does that mean you're changing the encoding of images by default? I'd say you shouldn't do anything to the image, unless the user requests for a compression change.In theory there is always a "create ", especially because the system eliminates all metadata from the images. To do this he has to "create" a new image. What shouldn't happen was increasing the size of the image. There may be some byte differences but nothing significant.
That's why I find this case strange.
It really doesn't make sense, sometimes the way the image was originally compressed can cause this type of problem.
Does that mean you're changing the encoding of images by default? I'd say you shouldn't do anything to the image, unless the user requests for a compression change. At the moment I have TalkImg configured for uploads of up to 3MB, but the forum only accepts up to 2.5MB.
The image is 1403233 bytes. Somehow the upload to you server doubles it. Can you check if it's exactly double the size? Something weird is happening during upload.Yes, this is another point that I will have to investigate, it was something that should not be happening.
It really doesn't make sense, sometimes the way the image was originally compressed can cause this type of problem. Either way, it was something that shouldn't happen. But I will investigate and see what I can do.
At the moment I have TalkImg configured for uploads of up to 3MB, but the forum only accepts up to 2.5MB.
The image is 1403233 bytes. Somehow the upload to you server doubles it. Can you check if it's exactly double the size? Something weird is happening during upload. Can I try? I'll also get you a copy at loyce.club/other/tmp/ if you email (alenzuela@gmail) me the image.
I've sent it, the format is zip file in Wetransfer link, I think it's better to not make a copy since I don't need it anymore. 
At the moment I have TalkImg configured for uploads of up to 3MB, but the forum only accepts up to 2.5MB.
This is already being resolved at the script level, but it could still take a few months to be implemented.
I can try asking @theymos to adjust the image proxy to 3MB, which would even give more freedom.
It doesn't hurt to try.
I could upload it to TalkImg without problems. It shows Upload complete with a green tick box. But when I try to post the image, it doesn't work:
That was exactly what I want to say.I can upload it and it's completed, but the image doesn't work since the size turn become 2.8MB, the forum didn't allow such big size.
Can I try? I'll also get you a copy at loyce.club/other/tmp/ if you email (alenzuela@gmail) me the image.
I've sent it, the format is zip file in Wetransfer link, I think it's better to not make a copy since I don't need it anymore. But, tell me one thing: did you use any specific program to compress the image?
Yes, unfortunately I forgot which one I used. I've sent by PM.
Since the contest thread has been locked, so I guess it's fine for me to use alternative hosting image.
But you can use my image to improve your site, maybe someone might face a same problem like me in the future.
I already try to use your image compress, but the result is same.
Since the contest thread has been locked, so I guess it's fine for me to use alternative hosting image.
But you can use my image to improve your site, maybe someone might face a same problem like me in the future.
I already try to use your image compress, but the result is same.
Thank you for the file. I will analyze it carefully.
But, tell me one thing: did you use any specific program to compress the image?
Can I try? I'll also get you a copy at loyce.club/other/tmp/ if you email (alenzuela@gmail) me the image.
I've sent it, the format is zip file in Wetransfer link, I think it's better to not make a copy since I don't need it anymore. Can you put the image inside a zip file and indicate it with a Wetransfer link?
You can put the link here or send it by PM.
I've sent by PM.You can put the link here or send it by PM.
Since the contest thread has been locked, so I guess it's fine for me to use alternative hosting image.
But you can use my image to improve your site, maybe someone might face a same problem like me in the future.
I already try to use your image compress, but the result is same.
Jump to: