Comments (9)
i wouldn't worry about breaking stuff to much.. TOMESH map and some stuff i built.. thats about it.
Early on not to worried about the havoc it will cause
from node-list.
Should there be a seperate services json?
from node-list.
Maybe add also what type of mesh its running?
from node-list.
I like the array option as it can be expanded upon in the future in a nice way that doesn't break things and is semantically neat. How much stuff breaks if we do it that way?
from node-list.
We should do this instead, because these protocols are complex and often require more than one field to work with (e.g. cjdns past a certain version is not backward compatible):
{
"protocols": [
{
"name": "cjdns",
"attributes": {
"version": "v16",
"ipv6": "fcc5:480e:20d6:dd89:12e1:19f8:23b9:f6ab"
}
},
{
"name": "yggdrasil",
"attributes": {
"version": "v12.2",
"ipv6": "fcc5:480e:20d6:dd89:12e1:19f8:23b9:f6ab",
"peering": true
}
},
{
"name": "ipfs",
"attributes": {
"version": "v13.5",
"id": "ipfs-id",
"public-key": "ipfs-public-key"
}
}
]
}
The keys within each protocol is just an example, but name
and attributes
should be there. We can incorporate this into schema-v8.
from node-list.
I think that would be good for actual mesh services like sites or DNS, etc. I'm not sure if Yggdrasil/CJDNS falls under that or not though. IPFS would imo, so why not those too.
from node-list.
Should there be a seperate services json?
@darkdrgn2k I am not opposed to that. Do you think cjdns, yggdrasil, and ipfs should all be in that services json?
We also need a unique key to map between the two.
As @makeworld-the-better-one showed, it's hard to decide which goes to which json. In my mind, these are all in the services json. Whether we wanna stick that in here or another file, I am kinda split, because single file does have its advantages of being easy to parse in business logic :)
from node-list.
We also need a unique key to map between the two.
Currently the NODE NAME
is planned to be unique across the network.
I am kinda split, because single file does have its advantages of being easy to parse in business logic :)
I fear that as the network grows it may become to big.
Also what about "multicast" services, services that exist on multiple nodes (like DNS)
from node-list.
I fear that as the network grows it may become to big.
I agree, I think that having a separate services file is fine.
Also what about "multicast" services, services that exist on multiple nodes (like DNS)
Not sure exactly what you mean, but the file could be organized by service anyway, with potentially multiple nodes offering it.
{
"DNS": [
"1.1.1.1:123",
"1.2.3.4:321"
]
}
from node-list.
Related Issues (8)
- Create schema and sample node list HOT 8
- Add CONTRIBUTING file HOT 2
- Free Geek Node - Information Sheet/Screen HOT 5
- New Map Submission (mesh-bridlewood) HOT 1
- New Map Submission (LibreMesh-59bf) HOT 1
- Define Schema for integration with monitoring (Stage 2) HOT 5
- Switch to json object vs. array in node list HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-list.