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
> 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@tnode.com> wrote:
>
>> Hi!
>>
>>> 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
>>
>> Yes. So providing your own interface to the same API is probably
>> reasonable. But I got a feeling that Marc was arguing for doing some
>> other API and another directory?
>>
>> Of course another idea could be that we just translate freifunk.net
>> webpage, point meshtheplanet.net to that site and make so that when it
>> is visited through meshtheplanet.net, an English version (with whatever
>> logo) appears. And if we want some additional feature, we extend current
>> website with it and both freifunk.net and meshtheplanet.net then have
>> it. This is open source as well. Don't fork if not necessary. Have you
>> tried to contribute to freifunk.net? Was it proven to be impossible?
>> That they didn't accept your contributions with your translations and
>> visualizations? If not, why fork?
>>
>>
>> Mitar
>>
>>>
>>> --mark B.
>>> On Sep 24, 2013 6:47 PM, "Mitar" <mitar@tnode.com> wrote:
>>>
>>>> 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
>>>>
>>>
>>
>> --
>> http://mitar.tnode.com/
>> https://twitter.com/mitar_m
>> _______________________________________________
>> mesh mailing list
>> mesh@lists.sudoroom.org
>> http://lists.sudoroom.org/listinfo/mesh
>>
>
--
http://mitar.tnode.com/
https://twitter.com/mitar_m