-------- Forwarded Message -------- Subject: [Battlemesh] GSoC 2019 announced (Battlemesh Digest, Vol 104, Issue 7) Date: Thu, 15 Nov 2018 16:16:35 +0100 From: Andreas Br?u <ab(a)andi95.de> Reply-To: battlemesh(a)ml.ninux.org To: Battle of the Mesh Mailing List <battlemesh(a)ml.ninux.org> Hi there, on Tuesday Google announce GSoC 2019. Org applications will start on January 15 2019. Until then we have time to update the projects page at https://projects.freifunk.net/#/projects Please add new ideas to the page, update the existing or delete the obsolete ones. Changes to the projects can be made at https://github.com/freifunk/projects.freifunk.net-contents You can find the timeline at https://developers.google.com/open-source/gsoc/timeline If you have any questions, please get in touch with me or write an email to gsoc-org-admins(a)freifunk.net Best regards, Andi _______________________________________________ lime-users mailing list lime-users(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-users

Hi, Just thinking out loud as I'm not going to do it (I don't even know if that is possible), but it would be nice to be able to install a basic Retroshare (to act as a relay) or a ScuttleButt Pub in a Libremesh router, wouldn't it? Ilario Gelmetti: _______________________________________________ lime-users mailing list lime-users(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-users

Both Luandro's answer and yours seem promising news towards network freedom. Software like Scuttlebutt and Retroshare is perfect for community networks. The main problem with these distributed apps is you want to have an always-on friend Retroshare-node/Scuttlebutt-Pub to route and let asynchronous communication happen. That would not be such a problem if the router you connect to is also the always-on friend RS-node/SSB-Pub you need. If those who run community routers, would also run its embedded always-on RS-node/SSB-Pub, that might become into a synergistic boost for both community networks and distributed apps. Gio: too, email _______________________________________________ lime-users mailing list lime-users(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-users

I agree we would get a better performance using different hardware. That is what I would do if I want to optimize performance in my network. But, if you want to accomplish the dizzying difficult mission of spreading Free Networks around the world, it sounds good to me to let people have the opportunity to install -if they want- in their router a piece of software (which otherwise they would probably never install in an always-on dedicated hardware) that would let users feel distributed apps work ok. Marcos: > It sounds interesting, but I think it's a mistake to mix infrastructure and > CDN in the same hardware layer. Let's think about the legal issues, about > the exposed that is the hardware of mesh wifi networks as well as to have > contents. It seems to me that the best thing is not to add points of > failure to the most sensitive point of the network (access points and > backbones) and to think of the devices that are connected as the elements > that really have the contents. At most think of other hardware, that is > easily added to our networks, that uses its advantages of mesh network, and > that fulfills the function of pubs, CDN, etc. > > El mar., 11 dic. 2018 a las 10:48, amuza (<amuza(a)riseup.net>) escribió: > >> Both Luandro's answer and yours seem promising news towards network >> freedom. >> >> Software like Scuttlebutt and Retroshare is perfect for community >> networks. The main problem with these distributed apps is you want to >> have an always-on friend Retroshare-node/Scuttlebutt-Pub to route and >> let asynchronous communication happen. That would not be such a problem >> if the router you connect to is also the always-on friend >> RS-node/SSB-Pub you need. >> >> If those who run community routers, would also run its embedded >> always-on RS-node/SSB-Pub, that might become into a synergistic boost >> for both community networks and distributed apps. >> >> >> >> >> Gio: >>> RetroShare could be probably compiled without much problems for openwrt >> too, >>> what are you thinking to do? >>> >>> On Monday, 10 December 2018 12:48:00 CET amuza wrote: >>>> Hi, >>>> >>>> Just thinking out loud as I'm not going to do it (I don't even know if >>>> that is possible), but it would be nice to be able to install a basic >>>> Retroshare (to act as a relay) or a ScuttleButt Pub in a Libremesh >>>> router, wouldn't it? >>>> >>>> Ilario Gelmetti: >>>>> -------- Forwarded Message -------- >>>>> Subject: [Battlemesh] GSoC 2019 announced (Battlemesh Digest, Vol 104, >>>>> Issue 7) >>>>> Date: Thu, 15 Nov 2018 16:16:35 +0100 >>>>> From: Andreas Br?u <ab(a)andi95.de> >>>>> Reply-To: battlemesh(a)ml.ninux.org >>>>> To: Battle of the Mesh Mailing List <battlemesh(a)ml.ninux.org> >>>>> >>>>> Hi there, >>>>> >>>>> on Tuesday Google announce GSoC 2019. Org applications will start on >>>>> January 15 2019. Until then we have time to update the projects page at >>>>> https://projects.freifunk.net/#/projects >>>>> >>>>> Please add new ideas to the page, update the existing or delete the >>>>> obsolete ones. Changes to the projects can be made at >>>>> https://github.com/freifunk/projects.freifunk.net-contents >>>>> >>>>> You can find the timeline at >>>>> https://developers.google.com/open-source/gsoc/timeline >>>>> >>>>> If you have any questions, please get in touch with me or write an >> email >>>>> to gsoc-org-admins(a)freifunk.net >>>>> >>>>> Best regards, >>>>> >>>>> Andi