[Freedombox-discuss] Challenges with Tiny Tiny RSS (tt-rss)

[Bob Mottram]

On Tue, Jun 21, 2016 at 11:16:21AM +0100, Bob Mottram wrote:
>teur Radio Emergency Data Network
>> http://www.AREDN.org/
>>
>> They're building a mesh network along the west coast of the
>> U.S.A. starting in San Diego County.
>
>This reminds me of the question of mesh protocol.
>
>Which mesh protocol should we set up with the Freedombox?  It is also a
>question of what community we want the FreedomBox to join?
>
>There are heaps of protocols out there, and it is unclear to me which is
>best and what kind of metrics we should use to decide how good they are.
>One inspiring project is <URL: http://www.servalproject.org/ >, but they
>seem to have made their own mesh protocol.  What are your views on mesh
>protocol?  What is important to consider?  What use case is most
>important for us?

So far I've only experimented with Batman Adv, because that's already
available within Debian.

Important things to consider are things like scalability, ease of
maintenance in Debian and resistance to interference. Batman Adv runs on
network layer 2 and so presumably would be more difficult to block.

Another thing to consider is that on a mesh you need different apps. You
can't just take client/server apps and expect them to run well on a
mesh. So that means using things which are designed to be peer-to-peer,
such as Tox or ZeroNet. P2P apps which also seed content will scale
across a large mesh.

I think it would be a good idea to be protocol agnostic. Choose a
protocol which is easy to maintain in Debian, but also have bridging to
other protocols which can be easily enabled. It is to be expected that
mesh networks could be fairly heterogeneous in their composition.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/freedombox-discuss/attachments/20160621/90207a63/attachment.sig>