blackrazor wrote:If there was a player wipe on .org, it would affect me equally as it would everyone else.
You can request your data removal if you're the entity who created them. It would be logical and could be understood. I guess that's why Frost offered you this option - if you insist on data wipe, it's logical to assume you don't want your data to be handled by this team. However, you can't request, say, my data removal. Because you just wrong entity to do such request. You taking too much on yourself. As player I never authorised you to act or speak on my behalf what to do with
my data. I also fail to remember when I assigned exclusive ownership of my data to someone. There was no such agreements accepted by me, ever. So claims of "exclusive" data ownership is just a pure 100% bullsh*t. You can't own what you haven't created. Ha-ha, end of story.
As player I see 2 realistic outcomes:
1) If I'm not happy with someone dealing with my data records -> file complaint and request data removal.
2) If I'm okay with data handling -> no further actions neeeded.
Btw, Platyna proven to be "potentially unfriendly" entity by explicitly refusing to delete data created by requesting entities. Yes, I'm about locking down devs accounts and somesuch. As for me I would qualify such approach as unpleasant and would rather avoid using server where admin is inclined on exclusive ownership of all data.
And IMHO, giving exclusive ownership of all user-generated data to some single person is a really wrong approach for community-based projects.
p.s. also, server-side (eAthena code) devs have inherent access to player data. Either dev can perform his/her duty and then inherently able to access all processed data or it's impossible to put new code, do any debugging and so on, so developent is really screwed up. If someone writes code, this code can do whatever dev wants it to. Say, dumping all player data somewhere, etc. Or whatever. Failure to understand such a basic things is uber-mega-dumb, up to point being laughable.