trees Joined Feb 15, 2017 Messages 48 Jul 27, 2017 Thread Author #1 1. Add F2P/P2P to accounts stored in bot. 2. Add Alias object to API, would have getName(), getF2P/P2P, etc. With ability to rename the alias as well. 3. Environment#getAccountAliases return List<Alias>.
1. Add F2P/P2P to accounts stored in bot. 2. Add Alias object to API, would have getName(), getF2P/P2P, etc. With ability to rename the alias as well. 3. Environment#getAccountAliases return List<Alias>.
party Client Developer Joined Oct 12, 2015 Messages 3,745 Jul 27, 2017 #2 Not sure @Arbiter is comfortable with us holding that data. Over to him I guess.
arbiter Mod Automation Joined Jul 26, 2013 Messages 3,012 Jul 27, 2017 #3 The whole point of aliases is for Bot Authors to be able to operate on accounts without needing any of this sensitive and identifying info. Sent from my iPhone using Tapatalk
The whole point of aliases is for Bot Authors to be able to operate on accounts without needing any of this sensitive and identifying info. Sent from my iPhone using Tapatalk
trees Joined Feb 15, 2017 Messages 48 Jul 27, 2017 Thread Author #4 How is F2P/P2P sensitive and identifying info? Wasn't the whole point of aliases to be able to rotate through accounts? And by getName() I mean the alias name not the account name. (Which you can still get with interfaces anyways lmao)
How is F2P/P2P sensitive and identifying info? Wasn't the whole point of aliases to be able to rotate through accounts? And by getName() I mean the alias name not the account name. (Which you can still get with interfaces anyways lmao)
