[Noisebridge-discuss] [RFC] Noisegate Web app prototype

Jake jake at spaz.org
Sun Apr 7 19:04:56 UTC 2013

Ken M. Haggerty wrote:
> Hi Josh: Would it be possible to see whether a code entered was 
> successful?

Hi Ken.  The reason why an app can't give you that kind of information is 
because the information is not given by the API.  We intentionally 
withhold that information because the only reason you might need it is if 
you're trying to hack the door code system by brute force.

Since the door code system uses just a few digits of numbers, someone 
might be tempted to wardial all the numbers from an API.  So the only way 
to know whether a code is successful or not is by seeing/hearing the door 
buzz open for you.

Does that sound reasonable?


On Sun, Apr 7, 2013 at 3:26 AM, Josh Juran <jjuran at gmail.com> wrote:

> [RFC == Request For Comments]
> In the interest of supporting Noisebridgers not running Android, I'm
> developing an implementation of Noisegate in DHTML (which might be 
> known by its marketing name "HTML5", although Noisegate doesn't use any
> features introduced by HTML version 5).
> So far, I have a user interface that works in (at least some) desktop
> browsers.
> Noisegate for Web prototype
> While the Enter key doesn't do anything yet (except clear the entered
> code), the UI is mostly there -- you can click the keys, and typing 
> also.  (The text animation is missing, but this will be easy enough to
> add.)  However, the app doesn't behave as desired (and in my experience 
> not usable) in the Android 2.3 mobile browser, and I suspect similar 
> may affect Mobile Safari on iOS (which I don't have to test).  My CSS 
> JS knowledge doesn't include the details of mobile/touchscreen Web app
> development; let me know if you're interested in helping out here.  CSS
> experience in general would also be useful.
> All comments are welcome.
> Josh

More information about the Noisebridge-discuss mailing list