Neat, we should implement freifunk's api. We probably want to automatically update the json file so the number of nodes and unix timestamp of last activity is correct.
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.
Hi!
> That site is completely freifunk-specific.
Because it is starting from there.
I am probably biased though. :-) But in the past they had already a nice
planet (blog aggregator) and I know few networks (including wlan
slovenija) who were part of that. So I don't have a feeling it is just
freifunk specific.
> Site appears to be in german only.
Currently. This is called international diversity. :-)
> No easy way to add your own community to the mesh (need to use an
> api).
Pull request against:
https://github.com/freifunk/api.freifunk.net/blob/master/directory/directory.json
What is easier?
> No info on the different meshes except for a link.
Have you checked the schema?
https://github.com/freifunk/api.freifunk.net/blob/master/specs/0.1.json
And of course, schema can be worked on by communities.
> This does not even seem to be an attempt at a global community site.
Interesting, I got a feeling that they are trying to be. They were eager
to translate into English the GitHub README, once I told them that this
would help others. :-)
> Yeah, but maybe forking hackerspaces.org would be better.
As you want. I am just saying that some people are already working on
that and that it is really hard to maintain such lists. I know because I
tried one:
http://interop.wlan-si.net/
There is then simply:
https://en.wikipedia.org/wiki/List_of_wireless_community_networks_by_region
Which was viewed by many as good enough.
And now freifunk is trying to improve on situation. So making a site
which uses the same API and same directory is probably reasonable. But
doing one new directory is probably not. Because the question is who
will maintain that directory.
Mitar
--
http://mitar.tnode.com/
https://twitter.com/mitar_m
_______________________________________________
mesh mailing list
mesh@lists.sudoroom.org
http://lists.sudoroom.org/listinfo/mesh