[FoRK] lazy QR code

Damien Morton dmorton at bitfurnace.com
Tue Jun 19 08:15:13 PDT 2012


For only a dollar you have have your (domain name, geocode) pair signed
using my root certificate, with a guarantee of exclusivity on every cubic
meter signed.

On Tue, Jun 19, 2012 at 11:03 AM, Kevin Marks <kevinmarks at gmail.com> wrote:

> How do you dereference the AP? By connecting to it? If so, there are 2
> existing ideas here:
> Sending a URL in option code 56 for DHCP on connection:
>
> http://www.google.com/patents/US7080132
>
> If you're connected to the API, you can use DNS-SD for nearby webservers
> over mDNS, look for '_http._tcp.'
>
> http://tools.ietf.org/html/draft-cheshire-dnsext-dns-sd-11
>
> (running apache web sharing on MacOS advertises these, Safari will browse
> them - go to Bonjour in the Bookmarks page).
>
> On Mon, Jun 18, 2012 at 2:30 PM, Lucas Gonze <lucas.gonze at gmail.com>
> wrote:
>
> > That's far less of a kludge than my AP name approach, and it's
> > arguably a more secure way of validating that the URL is really
> > related to the place you are in. OTOH, the 20 CM range of NFC is so
> > short that you'd have to put your phone right up to a marker.
> >
> > You couldn't just open your phone and see a short list of URLs that
> > you're likely to want to visit right then and there.
> >
> > Usecase: you're standing outside a store which is closed and want to
> > learn more about it. Ordinarily you would see a domain written on a
> > sticker in the window, open mobile browser, type domain in, visit
> > site. New approach is to open phone, launch dedicated app, see a list
> > of likely pages for this location, open one.
> >
> >
> >
> > On Mon, Jun 18, 2012 at 2:11 PM, Bill Humphries <whump at mac.com> wrote:
> > > Use near-field to advertise to nearby devices the pertinent URLs?
> > >
> > > -- whump
> > >
> > > On Jun 18, 2012, at 13:58, Lucas Gonze <lucas.gonze at gmail.com> wrote:
> > >
> > >> I'd like a mobile app that told me which URLs were intended to be
> > >> fixed in nearby space. For example, HEAD on such a link might have
> > >> lat/long for my GPS to sync up with.  I suppose you could validate
> > >> such URLs by checking whether an open access point named them.
> > > _______________________________________________
> > > FoRK mailing list
> > > http://xent.com/mailman/listinfo/fork
> >
> > _______________________________________________
> > FoRK mailing list
> > http://xent.com/mailman/listinfo/fork
> >
> _______________________________________________
> FoRK mailing list
> http://xent.com/mailman/listinfo/fork
>


More information about the FoRK mailing list