search

freifunk / api.freifunk.net

Freifunk Community API
http://freifunk.net/api-generator/
47 stars 24 forks source link

English README file #11

Closed mitar closed 11 years ago

mitar commented 11 years ago

Could README file be in English? It would be much easier for global communities to contribute and understand.

andibraeu commented 11 years ago

i tried my very best, maybe someone can read the history section

mitar commented 11 years ago

Thanks! I have a question. You are talking about "community map". But there are no nodes or maps really involved. I think this is confusing because at some point we will also have a "community map" where we would like to put all nodes of all networks on, no?

andibraeu commented 11 years ago

I think it's a wording issue, and in my opinion there's a map involved to give an overview about all communities. An example you'll find here: http://weimarnetz.de/ffmap/map.html

that's why we call it "freifunk community map", telling also it's not a node map or a node db

may someone has a better idea naming that map?

And: the API is not only for drawing a map, the map is a use case, it's more to provide a way of connecting communities from all over the world without maintaining the list of communities on a central place.

Another use case I implemented yesterday is to merge community feeds into one global feed

mitar commented 11 years ago

I think it's a wording issue, and in my opinion there's a map involved to give an overview about all communities.

BTW. Why we can specify only one location of the network? What if the network is spread around bigger area? For example, wlan slovenija covers whole country. What should we put then into our JSON? And then wlan slovenija will have only one dot on the map?

may someone has a better idea naming that map?

"freifunk community list" :-)

And then map is only one use case. :-) Why name everything a map if map is only a use case?

But in reality. I started thinking about very similar thing as you are doing here some time ago. I found the name "network commons" (and have domain name networkcommons.net) to be the most suitable for all this. So to have and combine a list of all networks together, globally, have a special page for that. So a reiteration of interop wiki (http://interop.wlan-si.net/). And then next step would be also to interconnect all those networks. And make it legally valid as well (with a licensing/peering agreement). So one idea is that all this is moved to "network commons" name? Because it is a bit strange that it is "freifujnk community map" if has all networks all around the world in.

Do you know about these two lists:

BTW, do you have in schema also things we are collecting on the latter wiki? Like DNS TLDs used by networks? Services a network provides? Licenses/peering agreements? Because at some point it would be useful to start working on a way for finding compatible licenses.

Another use case I implemented yesterday is to merge community feeds into one global feed

Great! This is really nice.

We have also such feeds (GeoRSS):

andibraeu commented 11 years ago

BTW. Why we can specify only one location of the network? What if the network is spread around bigger area? For example, wlan slovenija covers whole country. What should we put then into our JSON? And then wlan slovenija will have only one dot on the map?

no, every local community could create their own directory entry. By using the "metacommunity" field, it's possible to show these communities belong together.

    may someone has a better idea naming that map?

"freifunk community list" :-)

hmm.. maybe we misunderstood. Only the map part is called map, because it draws a map. the whole project we call "freifunk API", the list you mentioned is called "directory"

And then map is only one use case. :-) Why name everything a map if map is only a use case?

because we only named this use case a map :-)

But in reality. I started thinking about very similar thing as you are doing here some time ago. I found the name "network commons" (and have domain name networkcommons.net) to be the most suitable for all this. So to have and combine a list of all networks together, globally, have a special page for that. So a reiteration of interop wiki (http://interop.wlan-si.net/). And then next step would be also to interconnect all those networks. And make it legally valid as well (with a licensing/peering agreement). So one idea is that all this is moved to "network commons" name? Because it is a bit strange that it is "freifujnk community map" if has all networks all around the world in.

let's talk about it on IS4WCN in berlin, if you're there...

Do you know about these two lists:

  * https://en.wikipedia.org/wiki/List_of_wireless_community_networks_by_region
  * http://interop.wlan-si.net/wiki/IPAddressing/List

now I know about :-) our approach was not to have a central place, every community should be enabled to do it on their own. the freifunk wiki also has several list, but the data is always outdated, there's no well defined common format and so on...

BTW, do you have in schema also things we are collecting on the latter wiki? Like DNS TLDs used by networks? Services a network provides? Licenses/peering agreements? Because at some point it would be useful to start working on a way for finding compatible licenses.

there's a section "techDetails" in our api specs. Some things we already listed, based on lists on our freifunk.net wiki. At the moment, it's only a stub and subject to rework. Our focus was to collect metadata of communities to provide summarized information on a web page. We didn't need so much tech detail until now. But the API is open to enhancements.

mitar commented 11 years ago

no, every local community could create their own directory entry. By using the "metacommunity" field, it's possible to show these communities belong together.

wlan slovenija is in our case a local community. We do not have smaller communities.

hmm.. maybe we misunderstood. Only the map part is called map,

Oh, I read your commit a bit too diagonally. :-( Sorry. Yes. I understand now. My mistake.

let's talk about it on IS4WCN in berlin, if you're there...

Sadly it seems I will not be this time. But we can connect on some other audio/video chat if you want.

now I know about :-) our approach was not to have a central place, every community should be enabled to do it on their own. the freifunk wiki also has several list, but the data is always outdated, there's no well defined common format and so on...

Yes. This is why I am saying that this was an old version. And I really like your approach. We should work more on the concept of feeds and aggregators. It is a beautiful concept.

there's a section "techDetails" in our api specs. Some things we already listed, based on lists on our freifunk.net wiki. At the moment, it's only a stub and subject to rework. Our focus was to collect metadata of communities to provide summarized information on a web page. We didn't need so much tech detail until now. But the API is open to enhancements.

Just ideas. I understand there will be more work needed. And thank you for your efforts!

andibraeu commented 11 years ago

back to the issue... is there enough information in english now? may I close this issue?

mitar commented 11 years ago

It is perfect! Thanks!