I know much of the work done was being shared on the freenode channel,
but it would be immensely helpful to have everyone post their links to
code and documents here!
That way, when new people want to see what work has been done, we can
put them to this thread!
On Wed, Dec 15, 2010 at 8:16 PM, Jordan Bunker <bunker.jor...@gmail.com> wrote: > That way, when new people want to see what work has been done, we can > put them to this thread!
> On Wed, Dec 15, 2010 at 8:16 PM, Jordan Bunker <bunker.jor...@gmail.com> wrote: >> That way, when new people want to see what work has been done, we can >> put them to this thread!
While not directly related here is an Open Door Switch that was worked out during the event. It's a physical light switch that sends it's status to a remote server. Ajax on the main page of www.hive13.org shows the status of the space. This switch is to show when a member is in the space and the space is considered "Open". We also have our IRC bot reporting state changes to the #hive13 channel. This is to let non-members know there is somebody in the space and they can stop by on non-public hours. It will also be used once the inner-hackerspace passport protocol is established to allow other hackerspaces to gain entry to the space when at least one member is in the space (switch set to Open) with out needing to know the keycode.
> On Wed, Dec 15, 2010 at 8:16 PM, Jordan Bunker <bunker.jor...@gmail.com> > wrote: > > That way, when new people want to see what work has been done, we can > > put them to this thread!
This is the huge interconnect system using a almost defined data standard called odCard (which are beautiful little JSON objects) that has alot of specifications and only some code.
> I know much of the work done was being shared on the freenode channel, > but it would be immensely helpful to have everyone post their links to > code and documents here!
> That way, when new people want to see what work has been done, we can > put them to this thread!
> This is the huge interconnect system using a almost defined data standard > called odCard (which are beautiful little JSON objects) that has alot of > specifications and only some code.
> And Tim's REST authentication server.
> On 12/15/2010 01:16 PM, Jordan Bunker wrote:
>> I know much of the work done was being shared on the freenode channel, >> but it would be immensely helpful to have everyone post their links to >> code and documents here!
>> That way, when new people want to see what work has been done, we can >> put them to this thread!
I would like to put out bounties on some python modules, as I'm not that good at python.
1) Add REST client library. Something probably using urllib2 to interface with Tim's authentication server. It we can use to "open auth server. get user's info. put into odCard." Simple, fun, small.
For that, I think I need to write an init script for Tim's auth server to easily deploy it. Maybe a .deb package.
> This is the huge interconnect system using a almost defined data > standard called odCard (which are beautiful little JSON objects) > that has alot of specifications and only some code.
> And Tim's REST authentication server.
> On 12/15/2010 01:16 PM, Jordan Bunker wrote:
> I know much of the work done was being shared on the freenode > channel, > but it would be immensely helpful to have everyone post their > links to > code and documents here!
> That way, when new people want to see what work has been done, > we can > put them to this thread!
Here is our code for our super simple arduino based RFID shield. I'll be adding a schematic soon, but it is only about 10 parts. It is very, very simple, with an internal database and a serial communication protocol. It isn't directly on topic, as it is missing most stuff needed for cross hackerspace authentication.
On Wed, Dec 15, 2010 at 1:05 PM, Rhys Rhaven <r...@rhavenindustrys.com> wrote: > I would like to put out bounties on some python modules, as I'm not that > good at python.
> 1) Add REST client library. Something probably using urllib2 to interface > with Tim's authentication server. It we can use to "open auth server. get > user's info. put into odCard." Simple, fun, small.
> For that, I think I need to write an init script for Tim's auth server to > easily deploy it. Maybe a .deb package.
> On 12/15/2010 03:00 PM, Craig wrote:
> Ooooohh, that's nice. Good job PS1!
> On Wed, Dec 15, 2010 at 3:45 PM, Rhys Rhaven <r...@rhavenindustrys.com> > wrote:
>> This is the huge interconnect system using a almost defined data standard >> called odCard (which are beautiful little JSON objects) that has alot of >> specifications and only some code.
>> And Tim's REST authentication server.
>> On 12/15/2010 01:16 PM, Jordan Bunker wrote:
>>> I know much of the work done was being shared on the freenode channel, >>> but it would be immensely helpful to have everyone post their links to >>> code and documents here!
>>> That way, when new people want to see what work has been done, we can >>> put them to this thread!
So part of the JSON message, and probably the most important section of the physical key is the pk signature. (meta:sig-all) So I've spent most of tonight trying to find a proper python library to do gpg compatible pk. (Which I -think- is a RSA encrypted hash, as they don't seem so keen on DSA/Elcamal. Still not sure what the hash is on that.)
I think google's keyczar seems to be pretty straight forward and nice code, built ontop of pycrypto. Anyone have experience with keyczar?
> Here is our code for our super simple arduino based RFID shield. I'll > be adding a schematic soon, but it is only about 10 parts. It is > very, very simple, with an internal database and a serial > communication protocol. It isn't directly on topic, as it is missing > most stuff needed for cross hackerspace authentication.
> The PS1 solution looks very interesting - I'll be having fun exploring it!
> Loki
> On Wed, Dec 15, 2010 at 1:05 PM, Rhys Rhaven <r...@rhavenindustrys.com> wrote: >> I would like to put out bounties on some python modules, as I'm not that >> good at python.
>> 1) Add REST client library. Something probably using urllib2 to interface >> with Tim's authentication server. It we can use to "open auth server. get >> user's info. put into odCard." Simple, fun, small.
>> For that, I think I need to write an init script for Tim's auth server to >> easily deploy it. Maybe a .deb package.
>> On 12/15/2010 03:00 PM, Craig wrote:
>> Ooooohh, that's nice. Good job PS1!
>> On Wed, Dec 15, 2010 at 3:45 PM, Rhys Rhaven <r...@rhavenindustrys.com> >> wrote:
>>> This is the huge interconnect system using a almost defined data standard >>> called odCard (which are beautiful little JSON objects) that has alot of >>> specifications and only some code.
>>> And Tim's REST authentication server.
>>> On 12/15/2010 01:16 PM, Jordan Bunker wrote:
>>>> I know much of the work done was being shared on the freenode channel, >>>> but it would be immensely helpful to have everyone post their links to >>>> code and documents here!
>>>> That way, when new people want to see what work has been done, we can >>>> put them to this thread!
> So part of the JSON message, and probably the most important section of > the physical key is the pk signature. (meta:sig-all) So I've spent most > of tonight trying to find a proper python library to do gpg compatible > pk. (Which I -think- is a RSA encrypted hash, as they don't seem so keen > on DSA/Elcamal. Still not sure what the hash is on that.)
> I think google's keyczar seems to be pretty straight forward and nice > code, built ontop of pycrypto. Anyone have experience with keyczar?
> Rhys
> On 12/16/2010 12:31 AM, Lokkju Brennr wrote: > > Here is our code for our super simple arduino based RFID shield. I'll > > be adding a schematic soon, but it is only about 10 parts. It is > > very, very simple, with an internal database and a serial > > communication protocol. It isn't directly on topic, as it is missing > > most stuff needed for cross hackerspace authentication.
> > The PS1 solution looks very interesting - I'll be having fun exploring > it!
> > Loki
> > On Wed, Dec 15, 2010 at 1:05 PM, Rhys Rhaven <r...@rhavenindustrys.com> > wrote: > >> I would like to put out bounties on some python modules, as I'm not that > >> good at python.
> >> 1) Add REST client library. Something probably using urllib2 to > interface > >> with Tim's authentication server. It we can use to "open auth server. > get > >> user's info. put into odCard." Simple, fun, small.
> >> For that, I think I need to write an init script for Tim's auth server > to > >> easily deploy it. Maybe a .deb package.
> >> On 12/15/2010 03:00 PM, Craig wrote:
> >> Ooooohh, that's nice. Good job PS1!
> >> On Wed, Dec 15, 2010 at 3:45 PM, Rhys Rhaven <r...@rhavenindustrys.com> > >> wrote:
> >>> This is the huge interconnect system using a almost defined data > standard > >>> called odCard (which are beautiful little JSON objects) that has alot > of > >>> specifications and only some code.
> >>> And Tim's REST authentication server.
> >>> On 12/15/2010 01:16 PM, Jordan Bunker wrote:
> >>>> I know much of the work done was being shared on the freenode channel, > >>>> but it would be immensely helpful to have everyone post their links to > >>>> code and documents here!
> >>>> That way, when new people want to see what work has been done, we can > >>>> put them to this thread!
> >>>> Post away!
-- The real problem is not whether machines think but whether men do. B. F. Skinner
We know there was some debate as to our use of OpenID. In the next
few weeks several of us plan on rounding out some of the code and
adding some more documentation to explain the system a little better.
If you have any questions, I would be glad to discuss our ideas and
thoughts behind the implementation with anyone.
We had a blast working on this, thanks for finally kicking us into
gear and giving us a great group project to hack on.
I notice that the hyperlink doesn't have "http://" and for some reason clicking it doesn't work (error 404).
-- Jigsaw Renaissance is a learning and making community, a collaborative community dedicated to collective education and creation. Our mission is to create an environment in which success, failure, and most of all discovery are celebrated. Our vision is that this environment will foster an enduring sense of wonder and a drive to effect change in ourselves, our communities, and the world.
