search

publiclab / wherewebreathe

wherewebreathe.org
2 stars 7 forks source link

On Internet explorer auto generate of user names only works once and gennerates the user name i just used -- zifpoudu #100

Open shapironick opened 9 years ago

shapironick commented 9 years ago

Also the name scanner was picking up lots of parts of words that weren't names and was thinking they were names. After entering in a lot of names for when we were talking to funders the name scan function was a bit annoying as a user. I think maybe we could take that offline for now. we should be warning people enough that they can make an informed decision about using their name or not, and i think scanning for people's first names isn't adding much protection. The other thing we could do is just totally assign people user names--it would cut down on registration time (one less field) and it wouldn't be the false freedom we have now. it could be totally open with the option of random or totally closed. Thoughts?

mmnoo commented 9 years ago

Do you know which version of IE it was you were using? We should decide which version and above for IE we will test for and support.

(Nick, yes we should probably make the site work in at least newer IE versions, but sometimes that requires extra effort and thus expense. These bugs you have found could be easy fixes or difficult. Just a heads up! Good news is less and less users are using IE as time progresses and maybe even one day we will live in a world without IE!)

On Thursday, January 29, 2015, shapironick notifications@github.com wrote:

Assigned #100 https://github.com/publiclab/wherewebreathe/issues/100 to @mmmelissa https://github.com/mmmelissa.

— Reply to this email directly or view it on GitHub https://github.com/publiclab/wherewebreathe/issues/100#event-227196551.

Melissa Nunes Web Developer | Spatial IT Specialist Skype: nunes.melissa.m Email: nunes.melissa.m@gmail.com Linkedin http://ca.linkedin.com/pub/melissa-nunes/74/639/3a5

jywarren commented 9 years ago

For the name scanner issue you've mentioned, can you provide some examples of non name fragments it was incorrectly finding? It'll help with potential debugging. On Jan 29, 2015 7:56 PM, "Melissa" notifications@github.com wrote:

Do you know which version of IE it was you were using? We should decide which version and above for IE we will test for and support.

(Nick, yes we should probably make the site work in at least newer IE versions, but sometimes that requires extra effort and thus expense. These bugs you have found could be easy fixes or difficult. Just a heads up! Good news is less and less users are using IE as time progresses and maybe even one day we will live in a world without IE!)

On Thursday, January 29, 2015, shapironick notifications@github.com wrote:

Assigned #100 https://github.com/publiclab/wherewebreathe/issues/100 to @mmmelissa https://github.com/mmmelissa.

— Reply to this email directly or view it on GitHub https://github.com/publiclab/wherewebreathe/issues/100#event-227196551.

Melissa Nunes Web Developer | Spatial IT Specialist Skype: nunes.melissa.m Email: nunes.melissa.m@gmail.com Linkedin http://ca.linkedin.com/pub/melissa-nunes/74/639/3a5

— Reply to this email directly or view it on GitHub https://github.com/publiclab/wherewebreathe/issues/100#issuecomment-72135539 .

jywarren commented 9 years ago

Also, how are the errors presented? Is it only on submit or continuously as you type? I think it could be less obtrusive if it were as you type; I didn't see that happening on Firefox mobile, though. screenshot_2015-01-30-12-49-13

jywarren commented 9 years ago

Hmm actually perhaps it was just delayed; here the error shows up after a sec:

screenshot_2015-01-30-12-51-39

shapironick commented 9 years ago

Good questions! I just called the public library I was using IE at and they were using IE 11.0.96 it was the Philly library so they may be a bit more up to date than the backwoods rural libraries, but i think we can feel good about just having the most recent IE accounted for. Maybe we can put this as a low priority as maybe people are more likely to use mobile phones that library computers these days.

I think it was upon submit and not continuous, but it seems to be working fine on chrome right now. on IE it was picking up little bits of of words made by the random generator.

on desktop version of chorme right now it does pick up things like "ehr" "truc" "evy" "hoes" "aile" etc so when you try to make up a name of something people might identify with ("chevy" "truck" "shoes" "trailer") it can be a bit frustrating.

A couple options come to mind (but of course are not limited to this):

  1. We could make the scanner a recommendation and not a wall to registration. We could change the warning to say Please consider choose another username if this username could reveal your idenity . (this is an extra step to maintain your anonymity) Maybe this is the easiest option?
  2. We could take out common first names to reduce frustration.
  3. I could go through the list and weed out "names" that look like they are going to cause more trouble then help--this is pretty subjective though and perhaps time intensive.

On Fri, Jan 30, 2015 at 12:52 PM, Jeffrey Warren notifications@github.com wrote:

Hmm actually perhaps it was just delayed; here the error shows up after a sec:

[image: screenshot_2015-01-30-12-51-39] https://cloud.githubusercontent.com/assets/24359/5980489/dc07a866-a87e-11e4-97fa-ff75facf6deb.png

— Reply to this email directly or view it on GitHub https://github.com/publiclab/wherewebreathe/issues/100#issuecomment-72241416 .