@dmytri has emphasized again the need for a distributed, p2p practice for Thimbl (not just underlying architecture) and how it should be present in our priorities and communication. I agree with this, it's what sets Thimbl apart. It's not easy though. There are a lot of obstacles, some technical - such as difficulty in running daemons behind NATs and firewalls, of people not having the resources (like always-on servers) or knowledge to set it up by themselves. I think these obstacles need to be dealt with separately. With regards to the telecoms getting in the middle of communication and in our way and generally ripping the end-to-end principle to shreds, there's some code for setting up tunnels automatically that may be of help here: http://pagekite.net/. Maybe we can include it, maybe with mammatus, @dmytri? As to the other aspects, documentation on how to DIY will help and is needed. But still, there is much variety out there and to drive adoption some straight forward way of sharing the load of setting things up would help too. In the process, maybe more people will group and get and control domain names and servers and email... I'm rambling now. My thinking was that encouraging groups of users grab control of their communication resources and sharing the burden of administration would be good. (cc @all)