| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Glengrant
TOHA Heavy Industries
|
Posted - 2009.09.10 11:20:00 -
[1]
Account hijacking is terrible for both the players affected and CCP - who are likely to loose frustrated customers in the process if too much got lost before the account gets restored.
I assume that it is relatively easy to reverse money transfers.
But that still leaves the big problem of rare and expensive ships getting reprocessed and the resulting minerals being sold of for lowish prices.
We can't expect CCP to keep records of everything all the time - just so they can reverse complex changes. But the damage could be limited.
When an account gets hijacked there's a big difference between random junk lying around - a lot of which never gets used anyway (or is quickly replaced by a few buy orders) and that specially fitted very expensive ship.
Under normal circumstances people hardly ever reprocess named BS or T2 ships. The mineral value is far below market value.
So if it's a navy issue ship, or valuable T2 or just above a to be determined value threshold - delay reprocessing for - say - 1 day.
I understand that there are legitimate reasons for reprocessing even valuable ships - firesale when alliance leaves a region for example. But overall the recycling of such ships is rare.
More importantly - log that data for a few weeks (to cover typical holiday periods).
Value limits and delay period have to be based on analysis of what's typically going on. A 1 day delay is not going to help somebody coming back from a 1 week vacation - but the saved data snapshot will allow a GM to restore that rare and hard to replace ship (while subtracting a percentage of the reversed isk of course).
To be clear - I don't expect CCP to log all data for weeks - just a defined subset under suspect circumstances. Recycled navy issue ravens or Tengus should be a very very tiny percentage of all recycling actions - while beig a large percentage of cases where that's happening with a hijacked account.
And this should anyway be part of a set of triggers I expect CCP to follow already to look for hijackers and RMTers. --- Save the forum: Think before you post. ISK BUYER = LOSER EVE TV- Bring it back! Laptop, NVidia7900GS, Ubuntu 8.04, WINE |

David Grogan
Gallente Final Conflict UK
|
Posted - 2009.09.10 11:27:00 -
[2]
no
ccp can track any change in game by simply accessing their database system and using queries to retrieve the info they need SIG: if my message has spelling errors its cos i fail at typing properly :P |

Glengrant
TOHA Heavy Industries
|
Posted - 2009.09.10 11:34:00 -
[3]
Originally by: David Grogan no
ccp can track any change in game by simply accessing their database system and using queries to retrieve the info they need
We can all see that money transactions get journaled (for a few weeks at least) and money transactions only need a few bytes of data.
But I would be surprised if all other changes get the same treatment. That would generate insane amounts of data per day. And for speed reasons alone that would make the database much less efficient.
Also this fits with reports from those who hd their accounts hijacked. When all goes well money is returned - but I don't remember stories about assets being restored also.
I'm speculating based on limited data of course and could easily be wrong about this.
Do you have specific information about this or are you just assuming that CCP logs everything all the time? --- Save the forum: Think before you post. ISK BUYER = LOSER EVE TV- Bring it back! Laptop, NVidia7900GS, Ubuntu 8.04, WINE |

Rakshasa Taisab
Caldari Sane Industries Inc. Ethereal Dawn
|
Posted - 2009.09.10 13:59:00 -
[4]
Originally by: Glengrant But I would be surprised if all other changes get the same treatment. That would generate insane amounts of data per day. And for speed reasons alone that would make the database much less efficient.
What does the database have to do with logging? Hell... Any coder that even considers using the database for logging deserves to be fired immediately.
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |