Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mesh SSIDs #15

Open
rubo77 opened this issue Oct 11, 2016 · 3 comments
Open

Mesh SSIDs #15

rubo77 opened this issue Oct 11, 2016 · 3 comments

Comments

@rubo77
Copy link
Contributor

rubo77 commented Oct 11, 2016

It would come handy to select each mesh-SSID for each community as well

Discussion: https://forum.freifunk.net/t/jede-community-eigene-ad-hoc-ssid/13663

@rubo77 rubo77 changed the title Mesh SSIDS Mesh SSIDs Oct 11, 2016
@WIStudent
Copy link
Owner

I don't think that collecting the mesh-SSIDs in this repository would be a good idea. This repository was primarily created to make updating the SSID list in the Freifunk Auto Connect App easier. To check for new SSIDs the app downloads the latest ssid.json file form the freifunk_auto_connect_production branch. This is done whenever the app is started and more than 24 hours have passed since the last check. This means that users who use the app on a daily basis will download the ssid.json file quite a lot. Therefore the size of that file should be kept as small as possible. Seeing that the Münsterland community alone uses 65 different mesh-SSIDs I fear that adding all mesh-SSIDs of every community would cause the file size to explode.

But you could still fork this repository and add the mesh-SSIDs there if you want.

@WIStudent
Copy link
Owner

Another alternative would be to collect the mesh-SSIDs in this repository but in a separate file.

@rubo77
Copy link
Contributor Author

rubo77 commented Oct 11, 2016

yes, a separate file would be fine. so you don't have to download it in your app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants