TalkImg.com - Image hosting for BitcoinTalk

[taufik123]

Thanks @bitmover and @taufik123 for the tips.
Basically, this is what is already done in the zipping tool: https://www.zip.talkimg.com/

Today I dedicated a few more hours and improved the tool, allowing me to convert and compress more types of files: JPG, JPEG, PNG, WebP, BMP, and GIF

I know it's not in the final version yet, on the main platform. But for now, it can be useful for everyone. 

Zip tool, a tool that will be very useful and can be developed with many features.

But why a separate domain with TalkImg?
And there is no link embedded in TalkImg about this Zip Tool?

Is this because the Zip tool is still in beta and needs to be tested before being embedded on the TalkImg front page so that users can access it more easily.

Maybe if it is embedded on the TalkImg front page it will look like this

 

[joker_josue]

But why a separate domain with TalkImg?
And there is no link embedded in TalkImg about this Zip Tool?

Is this because the Zip tool is still in beta and needs to be tested before being embedded on the TalkImg front page so that users can access it more easily.

Exactly. Since it is still in Beta version, I am not highlighting it more than here in the topic.
But, as it is already in an advanced Beta version, perhaps in the next few days, I will add a link to the main page. We'll see.

[DYING_S0UL]

[…]

Hey joker_josue 
I was facing some issue with talkimg. Not every time but I would get this error. Might be worth reporting, so here it is.

 

[joker_josue]

Hey joker_josue 
I was facing some issue with talkimg. Not every time but I would get this error. Might be worth reporting, so here it is.

This error normally occurs when the image being loaded is larger than 2.5MB (3MB).
If you click on "error report" you will see more details. _{(I have to think of a way to improve this information.)}

[DYING_S0UL]

This error normally occurs when the image being loaded is larger than 2.5MB (3MB).
If you click on "error report" you will see more details. _{(I have to think of a way to improve this information.)}

Maybe that was the reason but I am positive that the image was less then 2.5 MB as it was a screenshot from mobile device.

[joker_josue]

Maybe that was the reason but I am positive that the image was less then 2.5 MB as it was a screenshot from mobile device.

Nowadays mobile devices generate very large images, even in a simple screenshot.
If it happens again, click on "error report" to see more details. 

[cygan]

i am already looking forward to the monthly updates (in this case for the month of october) regarding data volume etc. - i hope @joker_josue has not forgotten to post them

[logfiles]

@Joker_josue, apologies if this has been talked about before

I noticed that the images uploaded appear to be larger than the original screenshots. I find myself having to adjust the image height and width most of the time in the posts which is OK but there are some members who don't do this, and you find the entire screen filled up with a screenshot making the post ugly.

Here is part of my desktop showing a side by side comparison of the uploaded image in the browser and original screenshot of the image in the image viewer just for perspective
Is it by design?

[joker_josue]

Here is part of my desktop showing a side by side comparison of the uploaded image in the browser and original screenshot of the image in the image viewer just for perspective
Is it by design?

As a rule, the image size is not changed. (Unless I use the zip tool.)

Comparison using the screenshot is not viable, you have to check the height x width pixels.
Can you check the pixels of both images and share?

[logfiles]

As a rule, the image size is not changed. (Unless I use the zip tool.)

Comparison using the screenshot is not viable, you have to check the height x width pixels.
Can you check the pixels of both images and share?

Thanks, I have actually checked both images and the pixels are the same (1308 × 79 pixels) but what makes me wonder is why the uploaded image always appears larger or more zoomed in than the source from where the screenshot was taken, yet both are displayed on a browser that has the same zoom level at 100%

[joker_josue]

Thanks, I have actually checked both images and the pixels are the same (1308 × 79 pixels) but what makes me wonder is why the uploaded image always appears larger or more zoomed in than the source from where the screenshot was taken, yet both are displayed on a browser that has the same zoom level at 100%

This is often related to the way the browser reads the image. There is usually a way to read the same file, whether via computer or via the web.

[joker_josue]

 
 Statistics  October 2023____________________
The month of October was a calm month in terms of uploads, but it continues to be a service widely used by the community - which I appreciate. I have been studying/working on some changes that have been requested by users. I hope to have news soon.


Here are the numbers for the month and totals:

	Number of uploads in the month:  6.847 (-321 last month)
	Total image disk space:  17GB (+2 last month)
	Number of visits to the talkimg.com website in the month: 5.051 (+861 last month)  Bandwidth in the month: 420GB (+83 last month)

Thank you for using this service.

[joker_josue]

SERVICE STATUS
Maintenance is taking place on the server, which may create instability in the service, causing some interruption.

Our System Operations team will be performing scheduled maintenance on the server. Users will experience a brief service interruption while the routine scheduled maintenance is performed.

We hope that the situation will return to normal as soon as possible.
I appreciate your understanding.

State point: https://talkimg.betteruptime.com/

[joker_josue]

SERVICE STATUS
The situation is now completely normalized. I apologize for any inconvenience caused. Sometimes some maintenance is necessary, which occasionally generates instabilities.

I added the link in the OP to check TalkImg's uptime, so that everyone can always check the status of the service: https://talkimg.betteruptime.com/ 

[promise444c5]

I do encounter  this error while trying  to reupload after a recent  upload  but not all time



 Is it some kind of bug??

[joker_josue]

I do encounter  this error while trying  to reupload after a recent  upload  but not all time

Whenever you finish uploading, you must refresh (F5) the page, or click the "New Upload" button. Otherwise, this error may appear, as the site does not reset the previous process.

[promise444c5]

I do encounter  this error while trying  to reupload after a recent  upload  but not all time

Whenever you finish uploading, you must refresh (F5) the page, or click the "New Upload" button. Otherwise, this error may appear, as the site does not reset the previous process.

But the error  was from the " New upload" as I was able to select new image format but unable to upload, maybe I will just stick to the refreshing of page after an upload

[joker_josue]

But the error  was from the " New upload" as I was able to select new image format but unable to upload, maybe I will just stick to the refreshing of page after an upload

Sometimes, on mobile devices, they may not recognize the click on the "New Upload" button. In this case, it is best to the refreshing the page.

[promise444c5]

But the error  was from the " New upload" as I was able to select new image format but unable to upload, maybe I will just stick to the refreshing of page after an upload

Sometimes, on mobile devices, they may not recognize the click on the "New Upload" button. In this case, it is best to the refreshing the page.

Ohh I get it now, I hardly come across it on PC though it mostly occur on mobile.

[xLays]

Hello JJ, I'm currently experiencing difficulty accessing your website and I'm unable to view any images uploaded to BitcoinTalk using talkimg. I've checked my internet connection and everything seems to be fine on my end. Is there any ongoing maintenance or issue with the site? Thanks!

Edit:  I can access it now and images are also visible.