EVE Technology Lab

Ah, awesome, this is the new datadump at work.

It is fixed, and the other problem is fixed as well. I do not show specific rat bounties anymore. This data was not in the SDD anyway, and scraping them from the EVE cache with every database update is going to be obnoxious, and even then it will be inaccurate.

Well, the rat bounties were off even when I implemented it, that's why I put the +/- behind the value. It might be that the totals of rat bounties are off too, but I think those are generally correct (unless the API gave me errors).

And I added another feature. You are now able to total your buy and sell orders in the transaction history screen, making for some interesting view of how much you earned on a specific kind of item. It seems PLEXes are one of my major sources of income.

http://www.evemarketeer.com/item/info/coolant

I see there is now a "top 5 regions buy/sell" box.

How is that calculate? Is it dropping regions that are more then 7-14 days out of date?

Both seem fine to me. Are you still experiencing the issue? I really cannot imagine this happening. The row would have to be deleted from my summary table, and I never actually delete stuff from there unless it's replaced right away.

I'll see if there is any reason this could be happening.

As for the calculation. No, it simply takes the regions that have the most orders, though I imagine it would be a good idea to take the top 5 regions that with the most orders that are not out of date. I'll add that to the calculation.

In regards to bounties. If you put it like that, I'm a whole lot more inclined to think something is wrong with the way I retrieve data from my tables, which could cause a problem. I'll still have to export the bounty prices again though (which I will be doing eventually, but for now I'll first look into the correctness of the totals).

The uploader is a bit of problem right now, as my computer has crashed making me lose the source code of the uploader... which means I'll have to rebuild it. Which is good in the sense that it will probably be without errors, but bad in the sense that it's going to take some time. If you were experiencing no issues with a previous version of the uploader and have disabled EVE Central uploading anyway, you could consider downgrading to a previous version.

I am actually using jungledisk and it is making me very happy. It was the reason I couldn't care less that my harddisks suddenly stopped (that, and all my projects being securely in an offsite version control system, which is a backup by default).

The problem was that it didn't backup my downloads folder (which for the sanity of the backup solution, is a good thing) and the uploader source was in that one folder for some reason, so it's vaporized. But don't worry, as long as EVE Marketdata still has their source I can at least start off a decent basis.

Oh, and I also use dropbox, just not for backups ;)

Actually, the minimum for the market call is 3 seconds, which is why it's at that value by default :P you could make it slower, but you can't make it any faster (unless CCP has changed something without my notice).

The new uploader should follow an alltogether different format of entering that data.

I've just noticed that I'm receiving a lot of:

Debug: upload: uploading to http://www.evemarketeer.com/api/upload
Debug: upload: uploader.send = 200, OK
Debug: upload: response=0: The upload cannot come from the future
Error: Upload unknown problem: 0: The upload cannot come from the future
Debug: returned from upload function

I'm definitely not doing anything that allows me to see future market values, but I sure wish that I could. :)

EDIT: BTW, it doesn't happen for all items. There doesn't seem to be a pattern to exactly which items as far as I can tell. Some example item ID's that caused it in the Verge Vendor region, in case it helps:

20843
13239
30078
32108
28471
21238
22577

Maeste, I've just send you an EVE Mail, registration should be working again. It was indeed broken for a few days, but people were very fast to point it out :)

The only reason for the values to come from the future is indeed if your system clock is by some reason ahead of the EVE clock. This has been built in mostly to prevent people from sending illegal data that will always be seen as the most recent. I might relax the requirement a bit so as not to fall over a few seconds difference :)

Likewise, I use NTP so I shouldn't be much more than a second or two different. Unless of course the EVE servers don't and they are drifting. I agree that 10s or so should be sufficient to deter false data but still account for sync issues.

A lot of order filtering is applied. It drops all outrageous orders.

That is, I do not think you would mind the 888.888.888 shuttle being dropped from the results