and then we are thinking about using meshtheplanet.net (and meshthepla.net) as a campaign to get more people involved or a map of all community networks (like hackerspaces.org)

Cool, but do they have an actual site like hackerspaces.org or just the code for the map and api?

If they only have code and a freifunk-specific site,

That site is completely freifunk-specific.

Site appears to be in german only.

No easy way to add your own community to the mesh (need to use an api).

No info on the different meshes except for a link.

This does not even seem to be an attempt at a global community site.

Yeah, but maybe forking hackerspaces.org would be better.

As far as global directories, I don't see any reason for freifunk to be the only front end for all this open data - in part because "freifunk" is a much better name for german speakers than for everyone else. As long as we are dealing with open data and open source, it shouldn't be a problem for motivated folks to throw up their own translated/localized version, experiment with visualizations, etc. if they want to

--mark B. On Sep 24, 2013 6:47 PM, "Mitar" <mitar(a)tnode.com> wrote:

Mitar and all, The idea with meshthepla.net is to create a campaign site that is agnostic toward any particular network. Freifunk.net by and large points to and promotes itself, which is really all the argument needed. Also, I'm intending to use the site for documenting the workshop I'll be leading at the wireless summit, one output of which is a global community asset map of free networks and a communications framework for continuing the conversation. :) I do like the Freifunk site a lot and am hoping I can grok more of it after spending a few weeks immersed in German! On Sep 25, 2013 6:53 AM, "Mitar" <mitar(a)tnode.com> wrote:

Hi! So, maybe you should talk with people behind the freifunk.net site and see what is their vision is? Probably they are just around the corner. :-) As I said, there could be two domain names pointing to the same page, meshthepla.net having different theme and different (English) locale. Mitar agnostic and be community continuing after to be is a long as problem for it whatever current have you and a nice just https://github.com/freifunk/api.freifunk.net/blob/master/directory/director… https://github.com/freifunk/api.freifunk.net/blob/master/specs/0.1.json site. eager this on because I https://en.wikipedia.org/wiki/List_of_wireless_community_networks_by_region site But who >>>> will maintain that directory. >>>> >>>> >>>> Mitar >>>> >>>> -- >>>> http://mitar.tnode.com/ >>>> https://twitter.com/mitar_m >>>> _______________________________________________ >>>> mesh mailing list >>>> mesh(a)lists.sudoroom.org >>>> http://lists.sudoroom.org/listinfo/mesh >>>> >>> >> >> -- >> http://mitar.tnode.com/ >> https://twitter.com/mitar_m >> _______________________________________________ >> mesh mailing list >> mesh(a)lists.sudoroom.org >> http://lists.sudoroom.org/listinfo/mesh >> >

Marc Juul <juul(a)labitat.dk> wrote: Would you be willing to work with the Free Network Foundation and our guifi.us effort for the mapping? Also look at guifi.net (they are working closely with global mesh networks to map everything). -- Charles Wyble (818) 280-7059 charles(a)knownelement.com CTO Free Network Foundation (thefnf.org) _______________________________________________ mesh mailing list mesh(a)lists.sudoroom.org http://lists.sudoroom.org/listinfo/mesh

Jenny Ryan <tunabananas(a)gmail.com> wrote: I would browse the site and also talk to Roje/Pau at the summit. They know the site far better than I. Guifi.us is a 2.0 version of that site/concept and also more US centric.

Hi! What's wrong with JSON? That is really just a question how API is defined. From what I see, API is defined in a collaborative fashion through GitHub. So if one particular network needs something special, you can add this to the schema. And then everybody else benefits as well. I don't see how this is "one size fits all", but more "let's find/make the one size which fits all". And we are not so differently shaped that this would be impossible. Mitar

> Instead of defining a shared database efforts should be focused on > defining a shared data structure.

This data structure can be (and IMO should be) JSON and would contain a list of common attributes, not an all-inclusive list of attributes. Each organization can define their own database and need only write a script to export common attributes into the JSON shared data structure.

freifunk's api is re: a directory of networks not nodes. The json would basically be a url we maintain about our network that provides metadata such as name of our network, number of nodes, access policy, URLs for more info, etc. The json just represents our entry in a directory (or multiple directories) of mesh networks. I'm pretty sure no one is suggesting using json as a database, that doesn't make any sense... --mark Traditionally JSON is the way you'd interface with a database through a web app and not the database itself. The real problem is that JSON is a *data structure* and not a *database*. All the awesome tools one might want to use for sorting data sets are written for relational databases and not JSON objects. Using anything but a relational database doesn't make much sense to me if we are to prepare for the beautiful future of 100k+ node meshes. Writing a relational database to JSON object script is trivial, I'd put money on multiple libraries existing in all popular languages for just this. Not all mesh networks are created equal, for example some route on layer 2 while others route on layer 3. Should every entry in the JSON "database" contain both a MAC and IP address because of this? There are thousands of other variations which would each require their own JSON attribute even though 95% of the nodes may leave it undefined. Instead of defining a shared database efforts should be focused on defining a shared data structure. This data structure can be (and IMO should be) JSON and would contain a list of common attributes, not an all-inclusive list of attributes. Each organization can define their own database and need only write a script to export common attributes into the JSON shared data structure. -- rhodey On 09/25/2013 02:57 PM, Mitar wrote: _______________________________________________ mesh mailing list mesh(a)lists.sudoroom.org <mailto:mesh@lists.sudoroom.org> http://lists.sudoroom.org/listinfo/mesh