Cool, thanks for responding mk. One of my ideas was to solve the problem of early adopter issues. You could place TinCan hubs at various hubs (bars, coffee shops, bus stations, airports, etc.) so that you aren't COMPLETELY reliant on the travel of people to spread the messages. I'm thinking these could be as simple as normal phones running special versions of the software that keep the messages alive longer, or even special hardware too something like an embedded linux board running android but with way more storage. I guess some android phones have USB OTG so you could plug a hard drive in.

Is there a more detailed technical description of the protocol TinCan uses? I.E. what happens when two phones which are both using TinCan come into range. Since they're both currently 'hosting' a hotspot how do they talk? Is it using just advertising packets to communicate or something?

Anyway, as for getting it working on lots of phones. I can report it seems to run properly on my Samsung Galaxy S2 (rooted, CM10.2) though I have not exchanged messages with anybody. I did notice something a little annoying, but I'm not sure what you could do about this: If I decide to close TinCan, the hotspot is still active. When I deactivate the hotspot, it leaves my regular WiFi turned off. I could see that annoying people, but I'm not exactly sure how you would fix that. Unfortunately, I do not have any other phones to test on =(

Ah, sorry. I'm a new poster to the hubski community, forgot about the tags. But yeah, we should get some kind of meeting or listserv for people interested in working on it. We could see what kind of skillset we have at our disposal. Would be interesting to see what other backgrounds people have who want to help. I imagine some people on the business/PR end would be helpful as well, not to mention web dev.