PS
I had to post reply in proper topic that is related with TalkImg, to avoid going off-topic in Ninjatsic topic.
It was the Bitcointalk forum that inspired us to create Bitcointalksearch.org - Bitcointalk is an excellent site that should be the default page for anybody dealing in cryptocurrency, since it is a virtual gold-mine of data. However, our experience and user feedback led us create our site; Bitcointalk's search is slow, and difficult to get the results you need, because you need to log in first to find anything useful - furthermore, there are rate limiters for their search functionality.
The aim of our project is to create a faster website that yields more results and faster without having to create an account and eliminate the need to log in - your personal data, therefore, will never be in jeopardy since we are not asking for any of your data and you don't need to provide them to use our site with all of its capabilities.
We created this website with the sole purpose of users being able to search quickly and efficiently in the field of cryptocurrency so they will have access to the latest and most accurate information and thereby assisting the crypto-community at large.
Number of uploads in the month: 5 548 (-1 186 that in the last month) | |
Total disk space in the month: 1.48GB (-0.66 that in the last month) | |
Number of visits to the talkimg.com website in the month: 5 836 (-710 that in the last month) Estimated number of times images were viewed on the forum in the month (hits): 2 205 947 (-1 255k that in the last month) Bandwidth in the month: 340GB (-266 that in the last month) |
1017 hits
There is an incident code there so I'm not sure if you can check that? Perhaps the security system has been increased a little, which may make it difficult to upload in this way. I will send you a PM with an API, so you can try to do this via the API. Nah, it was just the mimetype thing. I'll have a look at the API. There is an incident code there so I'm not sure if you can check that? Perhaps the security system has been increased a little, which may make it difficult to upload in this way. I will send you a PM with an API, so you can try to do this via the API.
Looks like it just needed the mimetype added.
Obviously, nothing changed at my end but as I'm using Curl, it's possible that something changed under the covers that I need to account for. But I'm looking at the network traffic for a successful upload and I'm not seeing anything different than what I am doing (but I'm only digging surface level so far). Successful upload through browser: I assemble the form like so: Code: my $form = WWW::Curl::Form->new(); $form->formaddfile("$filename",'source', 'image/png' ); $form->formadd('type','file'); $form->formadd('action','upload'); $form->formadd('timestamp',time()); $form->formadd('auth_token',$auth); $form->formadd('expiration',''); $form->formadd('nsfw','0'); $i->setopt( CURLOPT_HTTPPOST(), $form ); But the error I am now getting is: Code: {"status_code":500,"error":{"message":"\u2b55\ufe0f Something went wrong \u2022 Incident ID:663132d5a78cf","type":"Chevere\\Throwable\\Exceptions\\ErrorException","time":"2024-04-30T18:05:09+00:00","code":0,"id":"663132d5a78cf"},"status_txt":"Internal Server Error"} There is an incident code there so I'm not sure if you can check that? [/s] Let me show why I was facing the problem. I discovered that two things have changed which I have been using to upload images from www.talkimg.com. Number one. Whenever I am uploading an image I first click the bbcode/width on the forum tool bar which showing on the image below. The way TalkImg works has not changed at all. The BBCode code has always been available first in embed codes. If you just copy the image link, then yes, you have to manually add the [img] code. If you copy the entire BBCode code, it already includes the code necessary for the image to appear on the forum. I remember that from the first day of this project, it was to facilitate the use of images on the forum. Therefore, it is prepared from the beginning so that there is no need to manually write the code [img]. Either way, the situation is clarified. Good use of this service by everyone, and any suggestions are welcome. Last time, you suspected me that I am posting here just to meet my signature quota when you're the one doing that. Lol Your explanations are not indepth but on the shallow surface. You only check my bbcode and said all is right when I was facing difficulty to upload images on my posts. There are some comments you will like to make and it needs practical. You can just upload any picture as you did to show the service is okay and probably the way I did my was not properly done then if possible you direct the person how to do it. Let me show why I was facing the problem. I discovered that two things have changed which I have been using to upload images from www.talkimg.com. Number one. Whenever I am uploading an image I first click the bbcode/width on the forum tool bar which showing on the image below. But now we don't have to click on the bbcode/width again on the forum and it is already in the link on the website. And you can also see it. . And also the second thing I discovered is, before when I was uploading any images from the website, I normally clicked on the send link and not the first link and now it is the first link. And because of all this I came here to find out the issue and you gave me a shallow contribution that didn't solve my problem. Well I am okay now because it has been resolved. Thanks to the Op and PX-Z for there resolution. Quote ChartBuddy I'm getting 500 internal service errors. Were you using any API? It's just that at the moment all services are ON. Just Curl in Perl. Maybe you changed the way the auth token was passed in the first page. I'll take a look at it tomorrow. Jump to:
|