https://github.com/ryepdx/pyethrecover does something very similar to what you're asking for, in the context of remembering an ethereum wallet password. In your case, the password-spec file would probably contain something like:
The overall code is not complex: it should be straightforward to strip out the word generation from the wallet testing and re-purpose it for your needs.
regarding the concept... the part I like about it is that it provides a mechanism for property owners to at least have a "say" in what flies over their property (and when). It's perhaps not a big deal now, but if drone delivery, et. al. become commonplace, I see this as the drone equivalent of a do-not-call list.
Agreed, the voluntary participation component is a material differentiator, as opposed to thrusting air traffic over people's homes or property, as is the case with most infrastructure development (railway, pipelines, transmission lines, etc) usually in the form of an eminent domain action.
Pogoseat is building the world's premiere white-labeled platform for live-event upgrades. Want a better seat at the next Giants game? Want to shoot a basket on the court after the game? Pogoseat provides technology that enables teams, venues, promotors, and organizers to offer an endless variety of seat and VIP upgrade possibilities to fans.
We're out to make the world a better place by making live events more memorable. We believe that only the worst seats should be empty, never the best, and we've got a passionate team of diverse, talented people working hard to make sure your next experience at a live event is one you'll never forget.
Join our Santa Monica, CA based team (of 12) and take a leading role in helping us grow.
For anyone interested in learning more about the Open Assets Protocol, the official specification is here [1]. It's relatively short, and really quite readable.
The reference implementation is in Python [2], but I've been working on a JavaScript implementation [3] that's available via npm [4]. It's mostly complete, but I would love help from anyone interested in getting it over the finish line...
This is definitely one of the cleaner implementations I've seen of this idea, but why not allow for traditional (vertical) scrolling? The swipe method is unnatural on a laptop browser.
Not only that. It's pretty much impossible to see where you are in the text. If one is going to get rid of scrolling, it should be replaced by something better. I just find this to be unusable.
Am I alone in this, or are there actual arguments why paging is better than scrolling?
Page information on the bottom may help? Good point. Paging has its pros and cons. One feature that is not obvious is to bookmark or share the URL that has the location within the content. (Though anchor may do the similar thing).
The URL has all the location information if that is of any value. Thanks.
This is amazing. Dead simple, programmable access to absolutely piles of NASA Mars imagery. Everything from the first photos Spirit and Opportunity took on the surface to the latest vistas from the Curiosity rover.
I completely agree with your emphasis on the community as one (if not the) defining attribute of what makes open source special. I think, however, that attitudes towards open source in government are definitely starting to shift. Events like the (3rd annual) Open Source Summit [1], and efforts like XDATA contribute greatly to overall awareness of the importance of understanding and embracing open source in government.
As far as supporting established OSS projects, this is definitely a big part of what XDATA is doing. Several of the projects on this list have well-established communities at the Apache Software Foundation (e.g.: OODT, Spark, Shark, Mesos, Tika) and others have strong ties to university research programs (Stanford, University of Washington, USC, UC Berkeley, etc.)
In a sense, what XDATA is doing is helping to connect these communities and funding them to come up with ways to collaboratively leverage their software and skills to solve data-intensive problems.
The last. It basically acts as a proxy: You type in your query, and IxQuick (aka startpage.com) queries Google on your behalf, thereby shielding you from the associated analytics and tracking. It also claims to not store the IP address associated with an individual query.
Another great take on an HTML5 flocking implementation is Alex Cruikshank's "birds on a line" demo, in which the birds also "land" on wires. I really like how Alex handles 3-dimensionality by adjusting the darkness of the birds so that the further "back" they are, the lighter they appear.
https://github.com/ryepdx/pyethrecover does something very similar to what you're asking for, in the context of remembering an ethereum wallet password. In your case, the password-spec file would probably contain something like:
``` [ ('S','s','5'), ('I','i'), ('M','m'), ('P','p'), ...etc ] ``` See the comments https://github.com/ryepdx/pyethrecover/blob/master/password_... for details.
The overall code is not complex: it should be straightforward to strip out the word generation from the wallet testing and re-purpose it for your needs.