Michael Paine wrote: > > Has anyone used the dynip service with their wearable? If so, are there > alternatives for non-static IP connections out there? If you want to make people to be able finding your current IP, you might display it in a prominent static place: your home page, for instance. When serving 24/7 content from your home box, this is usually done with a redirection URL stored at your home page stored at your ISP, which is refreshed when the address changes (if you're on a flat rate, you can bruteforce it by crontabbing a script which uploads the redirection anchor via ftp). There are more advanced methods, using distributed querying in dynamic sparse random connectivity clouds, which work via small number of degrees of separation (if you know about the current state of just ten other entities, each subsequent fanning out of the query means an additional, order of magnitude, and of course you can store information about several k IDs with very little costs to you -- with that scheme can query a billion IDs in just three easy steps). But these methods require a certain criticality in their use. Meaning, they're useless as long not a nonnegligable fraction of people out there are already running it. A typical technological chicken & egg dilemma. We're stuck untless we can zero-cost bundle it with some other piece of usable software, perhaps with an instant messenger, or an anonymous distributed file sharing software (MojoNation et al.). -- Subscription/unsubscription/info requests: send e-mail with subject of "subscribe", "unsubscribe", or "info" toWear-Hard Mailing List Archive (searchable): http://wearables.blu.org please, Please, *PLEASE* don't subscribe through a forward/false domain
From Wear-Hard Mailing list Archive (WH)
Maintained by R. Paul McCarty
Archive created with babymail