cough cough
From the instructions that FFAC linked 
Maybe I’m missing something technically.
With „my“ community, I can put the contact details on the node’s web interface - but I don’t have to. So far I assumed that they’d only be available exactly there - maybe that’s simply wrong and the data shows up in some API somewhere.
The web interface of the nodes „for us“ is only accessible from within the Freifunk network - but as far as I know - not visible to outsiders. So my enthusiasm for publishing contact details „for everyone“ in the Federated Map is pretty limited.
Maybe I’ve also misjudged the technical situation, and the security I assumed could be called security-by-not-membership: Whoever isn’t in the internal Freifunk network can’t access my data.
All in all: cool project, but I find publishing my contact details in that context kind of meh!
As long as your firmware — Braunschweig AFAICS — doesn’t filter the field, it’s included in the public data. Braunschweig seems to filter it:
According to the map, FFBS uses 2001:bf7:381::/48 addresses, which are neither registered with IN-Berlin nor listed in global routing. In that sense, „only from within the Freifunk network“ is probably correct — IPv6 access from within the FFBS network would then have to be rewritten to routed addresses at the network boundaries (gateways), e.g. via prefix translation — „IPv6-NAT.“
Subjunctive; your community did this before, as we’re now doing too: protecting contact data by replacing it with a descriptive placeholder in data usable by third parties. Precisely because publishing this data is something different from publishing the raw node statistics.
What does a „fetch failed“ actually mean? For example, if all the URLs mentioned are reachable from here and other data sources from the same server are also OK („active“) in the debug.html?
Really cool project! Would it maybe be possible to somehow export your efforts regarding fixing the Freifunk API feeds again?
I’m wondering if that could maybe also be used for the Census exporter. So that the data would then mostly come through the Freifunk API unchanged, apart from a few small manual fixes. That way maybe you could save yourself the hassle of maintaining this extra list here: census-exporter/communities.json at main · freifunk-gluon/census-exporter · GitHub