Post
Topic
Board Meta
Re: TalkImg.com - Image hosting for BitcoinTalk
by
Synchronice
on 09/09/2023, 09:45:27 UTC
 
 Statistics August 2023____________________
The month of August was a little calmer compared to the previous ones - but at a good pace, perhaps because many people usually go on vacation at this time.
Also this month there has been no wave of new entries, with users uploading large batches of images to the service. I therefore take this opportunity to remind you that you can have access to all the images that each user posts, using the database provided by @LoyceV here... Or use the script created by @TryNinja to transfer your photos to TalkImg.


Here are the numbers for the month and totals:
               
 
 Number of uploads in the month:
 5.732 (-6.291 last month)
 
 Total disk space occupied:
 13GB (+2 last month)
 
 Number of visits to the talkimg.com website in the month: 3.874 (-572 last month)
 Bandwidth in the month: 336GB (= last month)


Thanks for your support.
Wow, this is amazing. I think that around 4K visits on your website means that your website is very popular, I would say these are good numbers, congrats! Bandwidth is pretty high, just wondering, is your website used outside of bitcointalk? Is it allowed or do you block it?

As LoyceV commented, the most efficient systems that exist are native to PHP, which is GD or ImageMagick. They do their job well, but for those who like to see images always with quality - like me, I'm always a little reluctant to use these tools. Not to mention, that security is more exposed.

But I'm going to study the possibility of having an additional platform that performs these conversions and then sends the image to TalkImg. Wink
Lossless image compression is not a bad option to be honest. It will significantly decrease the size and quality won't be significantly affected. I think you can add it as an optional service and some people like me will use that option when they have to upload a screenshot or snap. I can do it manually and do sometimes but built-in compression is a better idea.