





erccarp wrote:Why do we need to log in to see if we have/ who has registered?
Can this be changed in the future?



paul wrote:But now you have to log in to know what team you're on!

erccarp wrote:Well first i think logging in is a pain, especially from a mobile device. Secondly I know that prior to a draft I might check out another city's league page and rosters/rankings if I'm trying to figure out if a new-to-town player is worth a late round pick. If that other city's league page block access to rosters i'd be pissed. So why not think about people in some other city searching for a transplanted AFDCer in their draft research.
If membership were voicing concerns about privacy and the public rosters then fine. But if we're fixing a 'problem' that doesn't exist and creating an inconvenience to members and potentially others than maybe consider changing it back.
erccarp wrote:Well first i think logging in is a pain, especially from a mobile device. Secondly I know that prior to a draft I might check out another city's league page and rosters/rankings if I'm trying to figure out if a new-to-town player is worth a late round pick. If that other city's league page block access to rosters i'd be pissed. So why not think about people in some other city searching for a transplanted AFDCer in their draft research.
If membership were voicing concerns about privacy and the public rosters then fine. But if we're fixing a 'problem' that doesn't exist and creating an inconvenience to members and potentially others than maybe consider changing it back.
I cannot think of a single thing you are doing that is so urgent that you simply must see a league participant list right this second where you're standing. It takes all of 30 seconds and while I know that, at least nominatively, I work in the mobile IT sector and I may have an unfair advantage in that regard, I've tried this. It doesn't seem that difficult or onerous.erccarp wrote:Well first i think logging in is a pain, especially from a mobile device.
My obligation is not to random people from other cities who are looking for "rankings" of players new to their leagues. My obligation is to the AFDC and its members. Also, those people from other cities are perfectly capable of creating new accounts to look at participant lists . . . even if it does make them "pissed". (Additionally, if this sort of thing actually gets you that riled up, it might be something to talk about with a professional.)erccarp wrote:Secondly I know that prior to a draft I might check out another city's league page and rosters/rankings if I'm trying to figure out if a new-to-town player is worth a late round pick. If that other city's league page block access to rosters i'd be pissed. So why not think about people in some other city searching for a transplanted AFDCer in their draft research.
As it turns out, "membership" has voiced concerns about the privacy of the AFDC membership and participation lists in far greater numbers than the "membership" that is currently complaining about this issue (by an order of magnitude at minimum). My suspicion is that you've never been in a situation where having your name publicly associated with a time and location that you're going to be somewhere has caused problems for you, but given the size of the AFDC, I'd bet a whole lot of money that some of our members have, and having worked with people in those sorts of situations before, I can tell you unequivocally that a) they appreciate this sort of protection and b) they're not likely to come to the forums here to tell you so (or tell you why). So, yeah, we're not "fixing a problem that doesn't exist"; we're trying to prevent problems before they are created.erccarp wrote:If membership were voicing concerns about privacy and the public rosters then fine. But if we're fixing a 'problem' that doesn't exist and creating an inconvenience to members and potentially others than maybe consider changing it back.

Users browsing this forum: No registered users and 1 guest