Gluon v2020.2 emits primary_domainy_code

ffnord / mesh-announce

Discussion at #mesh-announce:irc.hackint.org and (separately) at

https://matrix.to/#/!MjLIHcALOcENXZWQlH:irc.hackint.org/$1547640760901FmKaD:matrix.eclabs.de

13 stars 45 forks source link

Gluon v2020.2 emits primary_domainy_code #61

Closed mweinelt closed 3 years ago

mweinelt commented 4 years ago

See https://github.com/freifunk-gluon/gluon/pull/2027/files#diff-6174b1a86ab3714de32ec046179b4ecbR133.

For gateways it is probably more feasible to emit a primary_domain_code instead of a domain_code, since they don't really belong to any pretty domain name, but to the primary physical domain.

This is a step to fix up the relationship between pretty multidomain names and the underlying physical domain, that is currently not decernible from e.g. meshviewer.

AiyionPrime commented 3 years ago

I think primary_domain_code should become a provided option, but not instead of a domain_code. Considering a community, that got its stuff well enough together, to even have supernodes on-site of a domain. Same scenario applies if some organisation in a community wants to run dedicated supernodes for testing, or just their own guests. I think emitting both would be sensible, which would furthermore not introduce breaking changes.