The Next HOPE is over, and our OpenAMD deployment is packed up in it’s boxes and in storage. Some parts have already been shipped back to their home, and others are still waiting to go out.
If you were at TNH, you may have heard there were some technical issues with the badges that popped up on and off during the event. Yeah, it happens. Our issues came in 2 categories. We had some minor (and trivial to fix) power issues on some badges, and some connectivity confusion with the API and website. That is just part of the game when rolling out a system for 2K users in under 24 hours, on all volunteer effort, with approx. zero budget.
We had a lot of request for more details when we were at The Next HOPE, and below is some more information on what it took to make OpenAMD happen.
For those of you itching to hack your badge and extend GoodFET firmware and host tools, may be interested in the protocol documentation available at the OpenBeacon wiki
With The Next HOPE less than two weeks away, its a great to look back at The Last HOPE and the data that was collected during it. This article will explore what was released to the public and some of the cool data mining that is possible with this data.
Getting the data:
To start we can obtain this data from the Crawdad wireless dataset project. The Last HOPE data can be found at http://crawdad.org/meta.php?name=hope/amd
In browsing the dataset we will concentrate on different files as we need to relate users in different ways. As this data is heavily normalized, we will usually need two or three files to get at the relationships we are interested in.
Some of the more interesting csv files are:
creation.csv – This file records when a user created an account, and which registration code they used.
person.csv – This is the profile record. It contains the user’s handle, their stated age, gender, location, cell provider, etc. None of this data is verified or validated. This is data is useful for labeling and getting beyond user ids. Many of these handles are designed to be recognized. Mining forums for these handles could tell us more about the user.
ping.csv – This file records everybody that pinged somebody else and when they did it. Think of this like Facebook’s “poke” feature.
position_snapshot.csv – This file records what zone each user is twice a minute.
talk_presense.csv – This file joins user locations with where talks were being held to infer which talks a user attended. This can be further used with talks.csv to link users with talk descriptions and interests associated with a talk.
You will see user ids and coordinates. We’re adding more data every day, including the entirety of the HOPE speaker/talks list, so keep checking back as there are updates.
We’ll also be posting updates to the twitter account, so follow @thenexthope
Today we’re officially launching the new OpenAMD website. You can still view the teaser video, and download the public API, which will allow anyone to create their own applications to work with the badge system at HOPE.
However, this new website will have more updates on the project as we get closer to the conference, including both cool things we’re working on, as well as ways you can help.
We have a lot of ideas in the works, some of which will not be revealed until HOPE. In the meantime, please contact amd@hope.net if you’d like to help. One of the biggest pressing needs we have right now is to get PoE switches that will allow us to deploy the system. We’re doing this project on a budget, mostly self-funded, so any resources or leads for materials is extremely helpful and highly appreciated.
Personal privacy will become a thing of the past this July, when hackers unveil technology that could send privacy advocates into a panic mode.
Conference attendees will witness first hand while voluntarily wearing futuristic RFID badges what human tracking capabilities have become.
This system, termed OpenAMD, will both show the fun and reveal the dark side of familiar social networking websites like MySpace.
In addition to making the entire project open source, developers can now create their own software before the conference using the newly released public API.