Topic: TalkImg.com - Image hosting for BitcoinTalk - page 25. (Read 20808 times)

We invite everyone to vote for entries in the TalkImg Awards - Image of the Year 2023 event.

 
 Statistics  December 2023____________________
This month's statistics took a little longer, because I was preparing an adjustment to them. From this month onwards, data on occupied disk space will now indicate the space that was occupied during the month of statistics, similar to what happens with the number of uploads. I believe that this way, we can have a more real perspective on what happened throughout the month. In the OP, the total data for the entire service will continue to be updated.

I also added a new element to the statistics - hits. Hits are basically each time a file is accessed. The number indicated refers to hits coming from outside the site (forum, robots, and similar). Therefore, the number indicated is only an estimate of how many times the images hosted were viewed on the forum. I hope you enjoy these new statistical data.


Here are the numbers for the month:

	Number of uploads in the month:  7.197 (-2.459 that in the last month)
	Total disk space in the month:  2.4GB (+0 that in the last month)
	Number of visits to the talkimg.com website in the month: 4.919 (+75 that in the last month)  Estimated number of times images were viewed on the forum in the month (hits): 3.478.270 (+562k that in the last month)  Bandwidth in the month: 667GB (+126 that in the last month)

 2023 Overview
Having reached the end of 2023, I would like to make a small general summary of the statistical data from the "first year" ^{(or almost a year)} of TalkImg. The service started on April 28, 2023, and since then it has been a success, with 77,505 images uploaded. Which represents more than 21GB of images. The site received more than 32,000 visits throughout 2023, and generated a bandwidth of 3.18TB. And it is estimated that the images hosted on TalkImg have been viewed more than 18,000,000 times on the forum. Not forgetting to thank everyone who donated a total of 0.05BTC to the project. Thank you all for these fantastic numbers!

And your won amount of 0.25 and 1.50 mBTC (from your 1st and 3rd price here) as well.  

+1
Your service is of great helpfulness, many thanks for inventing and maintaining it!  

To be more precise it's a bundle of donations from different raffles and a bunch of participants.
The transaction contains:
0,25mBTC from @o_solo_miner from this raffle of 1miau.
0,75mBTC from @mikeywith and 0,15mBTC from @bct_ail from my raffle here.
0,5mBTC from me as a bounty for my 1.000 merit screenshot.
0,35mBTC from me because it was left and you deserve it for your service (regard it as a tip)

I inform you that I have made a change to the event prizes. So, don't forget to participate. 

Thank you very much for your support of this project. I will continue to work to make it better and better.

Some people from our German section have won a small amount of BTC in my recent giveaways and wanted to donate their prizes to TalkImg.com (Turbartuluk and o_solo_miner), so don't be surprised where the valuable BTC arriving on your address comes from (transaction). 

 
 Event  ____________________
I am pleased to announce the launch of the TalkImg Awards - Image of the Year 2023.
Everyone is invited to participate.

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.

You guys won't understand....

What sort of images... ??

Kinda this sort!!!


This is our WO stuff...  and it's important one.

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.

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.

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.

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.

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. 

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



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.

@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.

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.

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.

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.