Re: Lets get this straight
Posted: Wed Feb 07, 2018 12:28 am
I msg NH earlier i am meaninful in donating 100 bux to advertising. its a start lets get it done. i dont know anything bout that kind of stuff
Folder wrote:Staff can't make items. Summoned monsters can't drop items. Only top level staff can /spy, and Lat told you why he uses it.
I don't see why we would want a log full of warps and refreshes from events. Y'all paranoid.
daedroth wrote:Folder wrote:Staff can't make items. Summoned monsters can't drop items. Only top level staff can /spy, and Lat told you why he uses it.
I don't see why we would want a log full of warps and refreshes from events. Y'all paranoid.
Well you would say that wouldn't you, hmm hmm
killa wrote:I msg NH earlier i am meaninful in donating 100 bux to advertising. its a start lets get it done. i dont know anything bout that kind of stuff
Dan wrote:That is what i am talking about.
We will never know.
Make the player get a notification when anyone who can /spy him.
Like "You are under the eyes of a semi-god" or something like that, but let people know what is going on.
I do however agree that corruption is unlikely as NH does work hard to stamp it out. But I also recognise that Dan's call for increased transparency is a good one for keeping things with a perception of being above board. For example, if NH authorised a certain player to create and test a guild-owned discord bot (which is an exception to the normal TOS) this should have been disclosed to the public for transparency/feedback purposes long before it eventually gets discovered/noticed by the playerbase and becomes a bigger issue and more fuel for the fire. (I admit to being very discouraged by how that whole incident played out).
NiteHawk wrote:
///I do however agree that corruption is unlikely as NH does work hard to stamp it out. But I also recognise that Dan's call for increased transparency is a good one for keeping things with a perception of being above board. For example, if NH authorised a certain player to create and test a guild-owned discord bot (which is an exception to the normal TOS) this should have been disclosed to the public for transparency/feedback purposes long before it eventually gets discovered/noticed by the playerbase and becomes a bigger issue and more fuel for the fire. (I admit to being very discouraged by how that whole incident played out).
Well as I said, in terms of Ry, I didn't give him access to use it as a guild bot for chat though, I told him to stop running it.. I'm not sure where you're getting that the bot was authorized to run as a guild chat bot/etc (on discord I also did state about this.). I gave him the right to try to break the encryption and some other things though. I was aware he was testing the client to try to break the encryption and I'm often fine with it as he relays me what he has done and I patch up stuff and solve it. Ry and I have worked together quite a lot with it going back and forth with stuff he breaks and things I fix. Most security fixes have now been patched because of his tests/breakdowns though.
///