makeworld

> I dont like the "opt in" model. Then let's make it the default. I've confirmed with Arceliar that it is a stable feature and will not effect link-local auto-peering.

As [said](https://matrix.to/#/!yzLpKcnymfPsdJyjnB:tomesh.net/$15437895294616BBFjd:tomesh.net) by @benhylau in our chats: > Yes I commented on there yesterday and my position still stands, that I think making custom configurations is (a) arbitrary and (b)...

"Opens" meaning what? In the firewall?

Maybe something similar to nodeinfo, where modules can add a file to some folder that will add output to `status`? It should still be there though, at best in addition...

Yggdrasil currently doesn't have a spec for nodeinfo. The CJDNS spec is [here](https://github.com/hyperboria/docs/blob/master/cjdns/nodeinfo-json.md), and we need to figure out a way to combine Ygg info with that already existing spec....

Whatever is worked out here, possibly with @neilalexander's help, should be served over http and possibly through the Yggdrasil config file as well. At the moment, we have a `name`...

My idea for a spec: ```json { "hostname": "your.node", "name": "your.node", // for ygg "contact": { "name": "Your name, handle, nick, whatever", "email": "[email protected]", "xmpp": "[email protected]", "other cool communication service":...

To address each of your concerns @neilalexander: ### `"software"` The software section is tomesh specific, we use it to identify what version, branch, etc of our stack that our nodes...

@darkdrgn2k I mean it really depends how much we expose. Having a location setting is still a good idea, but it's always optional of course. Having basic services and software...

@Arceliar Personally, `"hostname"` makes more sense to me, so I would like it if Yggdrasil checked for both. What are your opinions on the spec overall though, and @neilalexander's comments...