Post has attachment
I've published a few things, using an extended verion of Gary's Thing Tracker template.
https://cscott.github.io/thing-tracker/

The idea is to pull most of the thing.json metadata from the README.md in the github repository, to avoid duplicating this information.

Post has shared content

Post has attachment
I have been working on an implementation of a Thing Tracker Network[1].

The project is far from ready for prime time (I have about 100 items on the ToDo list), but if you want to try it out you can make a new account on the Raspberry Pi that I have running the current version (be gentle on it, it's very slow)[2], or you can get your own by using a Docker container by following these instructions[3], or even set up a development Docker container (but only if you are using Linux)[4].

I was hoping that someone would be a guinea pig and work with me on fixing up the discovery aspect of it so that it doesn't require a public facing IP address and DNS record [5]. This would involve you setting up a (more or less) permanent system (as above) running CouchDB and Deluge with a few published things, that I could access over the next couple of months and get you to update periodically.

[1] https://github.com/derrickoswald/things
[2] http://thingtracker.no-ip.org/
[3] https://github.com/derrickoswald/things/blob/master/markdown/Docker%20Installation%20Instructions.md
[4] https://hub.docker.com/r/derrickoswald/things_dev/
[5] https://github.com/derrickoswald/things/issues/2

Post has shared content
I thought this was an interesting  overview of where bittorrent technology is at the moment.
Amazing presentation.

Javascript... Torrents... and Mad Science!
Mathias Buus Madsen

Enter the ever evolving world of peer to peer using Javascript. In this talk we will push the limits of what is possible today using BitTorrent, streaming, and Javascript.

Post has attachment

Post has attachment
Interesting read on a Content Centric Network, which has similar goas as the TTN.

(via this issue on IPFS which lists some more resources: https://github.com/jbenet/ipfs/issues/28)

Post has attachment
I received an email the other day from Johannes Reinhardt (of BOLTs fame[0]) telling me about his recent work on a ThingTracker application.  CADinet [1] is a python (flask) and mongodb based app which offers a simple API for uploading and browsing Thing information.  He's using openshift [2] for hosting which has a free tier for playing with.  

I spent a couple of hours last night playing with it and got an instance up and running pretty quickly [2.1].  The only issues I had was with my git settings, not with the app itself (I had to unset a GIT_SSH env variable, and my default rebase settings caused problems when pulling from his remote).  It's worth noting that the amount of information that can be pulled in is limited at the moment [2.2] - but the reason is quite interesting - as he has also implemented a FreeCAD macro that uploads models to CADinet directly - and these are the fields that can currently be easily used.

This kind of development really highlights what I was trying to say in the "Ecosystem" [4] part of TTN website - that the power of the network will come from many apps and services working together!  Having a common language, via the specification, opens up a host of possibilities.


[0] http://jreinhardt.github.io/BOLTS/
[1] https://github.com/jreinhardt/CADinet
[2] https://www.openshift.com
[2.1] https://cadinet-garyhodgson.rhcloud.com
[2.2] https://github.com/jreinhardt/CADinet/blob/master/cadinet/specs/thing.json
[3] https://github.com/jreinhardt/CADinet-freecad
[4] http://thingtracker.net/#ecosystem

Post has attachment
This recently opened issue on ipfs relates exactly to the work I am trying to do on relays for TTN, i.e. make content available if the owning node is offline.

Post has attachment
I have some #Keybase .io invitations if anybody wants them. This is used for client side encryption in Javascript, where https://keybase.io/ is the basis of the web of trust. My thinking is that something like this - or google's end to end (https://code.google.com/p/end-to-end/) when they get the key distribution figured out - would be the public key infrastructure (PKI) used to verify the hash chain (http://en.wikipedia.org/wiki/Hash_chain) for proving provenance and temporal ordering of things in the TTN.
Keybase
Keybase
keybase.io

Post has attachment
This looks really interesting, and potentially a superset of requirements to TTN, or perhaps something that would make TTN much easier to realise: "global, versioned, p2p file system"

It's worth checking out the Hacker News discussion too, as they bring up similar issues as what the TTN has to deal with, e.g. how to handle storing potentially illegal data on other peoples machines: https://news.ycombinator.com/item?id=8069836
Wait while more posts are being loaded