| github | neilalexander |
| web | https://neilalexander.dev |
@ufm We're planning to rethink link costing in v0.6 so that we have better multi-hop awareness of latencies rather than just next-hop awareness.
At the moment what we do is optimistic at best, but in the worst cases it can pick a very fast next-hop but then the rest of the onward path is worse than the direct peer would have been. Then people complain that the direct peering shouldn't have been ignored.
In an ideal world, people would fix their peerings too. In reality, that doesn't happen.
First Yggdrasil Network release candidate in a while, will likely aim for a general release later this week.
https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.13-RC.1
#yggdrasil #yggdrasilnetwork #meshnet #meshnetworking #meshnetworks #e2ee #decentralized
Philips Hue is such a good example of how good the smart home could be:
1. Their ecosystem uses industry-standard ZigBee and is interoperable with non-Hue bulbs;
2. Their v2 hub is 10 years old now and yet still gets regular updates and support for new products and is just as reliable as ever;
3. It works just fine on your local LAN, even without internet access;
4. It has a well-documented and complete API that is accessible locally.
This is what all smart home manufacturers should aspire to.
🌳 Yggdrasil Network 0.5.9 was released a couple days ago!
https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.9
This is a notable release due to the addition of new link costing based on the average RTT of each peering, which should help to bring latency down by selecting better links in the vast majority of cases.
If you are running Yggdrasil, please upgrade your nodes, and if you know anyone else who is running Yggdrasil, please pass on the message to them too!
JA Westenberg