TornW3B: Bazaars, RW, & Profit Tracking

Issue should be resolved. Seemed to be Cloudflare acting up again. 

I have not. And given his site seems heavily catered towards buymugging I don't recommend using it either. 

Edited. Issue explained. Great site. Thanks.

I just looked and don't see any items right now where the percentage is incorrect. It could just be that someone listed something cheap and then changed the price before my site picked it up, and you bought it in that window. 

Great site. Thanks!

That information helps me to narrow down what exactly is happening.

It's not a bug, it's just the dynamic nature of the item market. The market value of any item is just pulled directly from Torn and only changes once a day based on the average price that item sold for on the previous UTC day. At the time that you had purchased the medieval helmet, the market value was inflated up to 23m, which was artificial inflation. Someone just bought a helmet for really expensive at some point the previous day which caused that one-day spike. 

So the comparison on my site was correct (and looking at both the items you mentioned, it still is). The listed market value of that item was just incorrect. Whenever you are buying an item to flip, you have to know what you're buying first and learn market trends. A good tip is that if you see a bunch of a single item being listed 65% below market value, there's a good chance that it's being listed that cheap for a reason and unlikely to recover.

I occasionally encounter issues with certain bazaar listings not updating for long periods of time, sometimes multiple hours. Worse still, some item types can wind up with multiple "ghost listings" crowding out legitimate listings. 

Literally none of these bazaars actually still have Chamois Plushies. Note several are hours old.

Load image

Is it possible to force the website to update others' bazaar listings using my own API key provided, or would it be possible to add it as a feature?

There's an ongoing issue with my site that I've announced in my discord which is causing this issue. I'll slap it here for reference;

@everyone 

Bug currently affecting the site that is causing several calls to fail as pointed out in bug reports

Site is still working but only at 1/3rd if it's capacity. I'll be home to fix it in about 13 hours

-# why do these bugs only ever occur at the most inopportune times smh my head

Service should be restored to full functionality. Will take some time for it to catch up but the issue is resolved.

Service provider for TornW3B is currently down for security maintenance, but service should have been restored long before now. As soon as it comes back up, TornW3B will automatically reboot. 

Sorry for the inconvenience.

Service is back up

Thank you

is this a known problem

[image: i.gyazo.com]

we broke it

Investigation of what's going on with TornW3B is under way currently. I can't give an ETA on when it will be restored. 

I can't seem to login. Everytime i tried to sign in, create restricted API Key, and then copy the said created api key, it always said "Login Failed, Authentication Failed". Any idea why do this happen? Thank you in advance :)

Thank you for the update.

@everyone <@&1408291391796416702> 

Doing a double role mention with this one to make sure you all see it, because this is very important. So please read. I have some bad news, followed by some good news for TornW3B. 

# **The Bad**

My server got infiltrated by a Russian cryptominer that hijacked every corner of the server. My CPU usage spiked to 100% and database connections were being closed faster than they could be established. This is why the site was behaving so erratically this morning. 

Given this, the server has been shut down entirely and *all* data wiped. Every API key, ranked weapon, bazaar listing - all of it is was wiped clean. The only thing that remains is the shell of the site itself. For some reason I didn't consider storing backups of the database so when I do a relaunch, we will be starting over from scratch.

# **The Good**

Not a lot, if I'm being honest. The site itself is still there and I'll be able to restore the database pretty easily when I get a chance to do so. The culprit was found and removed, and the intrusion did not have anything to do with anyone associated with Torn as far as I can tell. 

# **The Future**

I am going to collaborate with others where needed to ensure any remaining vulnerabilities are patched up before a relaunch to prevent anything like this from happening again (and I will have backups ready should any other failures occur again). I have already made plans to spend tonight and all of tomorrow doing just this.

I can not give an ETA on the relaunch. It might be tomorrow, it might not be. But it won't be tonight. I take the trust all of you have put in me by giving me your keys very seriously and will be prioritizing the security of your data above a speedy relaunch above all else.

In the meantime, there are only two things I would like to ask of all of you:

* Delete any keys you had that were associated with TornW3B. Although there doesn't appear to be any breach from anyone associated with Torn, it's best to not risk it. 

* Check the link below and fill out the form. I will be collecting your keys via Google forms so that when I relaunch, I'm not starting with 0 keys. This will speed things up significantly when the time comes. 

https://docs.google.com/forms/d/e/1FAIpQLSdPbtx7f2yAh_jyqZu8sED4IQ4vEbvByFU62Fk9T76H0TGH5A/viewform?usp=header

If you have any questions or comments, I will be monitoring the discord closely throughout the day.

Damn Russians got nothing better to do #freeweaver