-
Notifications
You must be signed in to change notification settings - Fork 0
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
aggregation only mode #2
Comments
@andrenarchy what do you think about routers not submitting directly to libremap.net database? it can possibly save some headaches down the road. for people who for whatever reason don't setup an instance of db for their network you could still offer separate db at greenhouse.libreamap.net or something else suggesting to grow up 😉 |
That's definitely an interesting thought! I think that it's a good way to point out the decentralized approach from the very beginning. Technically, it's a no-brainer and I'd like to do this for political reasons. @nicoechaniz: what do you think? Any other name suggestions? 😄 |
I would also see it possibly setting us in healthy direction once we want/need to deal with authentication. I still need to check out how replication works in couchdb and if it has some way of keeping track on provenance of data... |
Yes I completely agree with each community setting up their own servers. Big projects (guifi.net, altermundi, freifunk) can host servers for their small communities that cannot host a local instance and still libremap.net would only replicate (pull) from others. |
@nicoechaniz good point! maybe we could also host an instance of couchdb on something like proxy.libremap.net which would use all kind of adapters to only pull-in data from different kinds of databases? (eg. nodeshot) |
yep, exactly. |
where can i find source file for network diagram used in about section? |
how about making instance running on libremap.net agregation only? i see advantages in approach where all the routers post updates to instances of their local communities and libramap.net only replicates from them and doesn't accept any updates directly from routers!
The text was updated successfully, but these errors were encountered: