On 29 Jul 2014, at 22:51, Adam Roach <[email protected]> wrote: > On 7/29/14 15:40, Jared Wein wrote: >> Here is my mockup: […] >> | go to https://call.mozilla.com/ and enter | >> | in the following pin: 651 24 893 | >> | | >> |-------------------------------------------| >> > > In practice, to prevent abuse by marketers and similar parties, we're going > to need to make this space far more sparse than would be provided by 8 > digits. If we were to provide the same properties as the URL -- and I would > argue that we should -- we would need on the order of 19 or 20. I'm not sure > that's much of an improvement, for the use cases you describe.
The pin solution proposed by Jared works pretty well for other systems and is a great fail-safe / fallback for technically less inclined people - i’d love to see us consider this or drive some usage tests. Is the problem the (missing) sparseness over 30 days, and if so, couldn’t we e.g. restrict the pin validity to a shorter period so 9-12 digits work? Alternatively, how about an alphanumeric subset with no case-sensitivity and problematic letters omitted (I, O, Q)? Do we really need the "#call/“ part in the URL? Georg _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
