MeshCore is a new routing protocol designed for low-power, wireless mesh networks using packet radio. It combines proactive and reactive routing strategies in a hybrid approach for increased efficiency. Proactive routing builds a minimal spanning tree for reliable connectivity, while reactive routing dynamically discovers routes on demand, reducing overhead when network topology changes. This hybrid design aims to minimize power consumption and latency while maintaining robustness in challenging RF environments, particularly useful for applications like IoT sensor networks and remote monitoring. MeshCore is implemented in C and focuses on simplicity and portability.
The blog post "An early social un-network" details the creation and demise of a hyperlocal, anonymous social network called "Dodgeball" in the early 2000s. Unlike friend-based platforms like Friendster, Dodgeball centered around broadcasting one's location via SMS to nearby users, fostering spontaneous real-world interactions. Its simple design and focus on proximity aimed to connect people in the same physical space, facilitating serendipitous meetings and shared experiences. However, its reliance on SMS proved costly and cumbersome, while its anonymity attracted unwanted attention and hindered the formation of meaningful connections. Despite its innovative approach to social networking, Dodgeball ultimately failed to gain widespread traction and was eventually acquired and shut down.
Hacker News users discussed the impracticality of the "social un-network" described in the linked article, particularly its reliance on physical proximity and limitations on content sharing. Some found the idea nostalgic and reminiscent of earlier, smaller online communities like Usenet or BBSs. Others expressed concerns about scalability and the potential for abuse and harassment without robust moderation tools. Several commenters questioned the overall utility of such a system, arguing that existing social networks already address the desire for smaller, more focused communities through features like groups or subreddits. The lack of searchability and portability of conversations was also a recurring criticism. While some appreciated the author's intention to foster deeper connections, the general consensus was that the proposed system was too restrictive and ultimately unworkable in its current form.
Summary of Comments ( 4 )
https://news.ycombinator.com/item?id=43693406
Hacker News users discussed MeshCore's potential advantages, like its hybrid approach combining proactive and reactive routing and its lightweight nature. Some questioned the practicality of LoRa for mesh networking due to its limitations and suggested alternative protocols like Bluetooth mesh. Others expressed interest in the project's potential for emergency communication and off-grid applications. Several commenters inquired about specific technical details, like the handling of hidden node problems and scalability. A few users also compared MeshCore to other mesh networking projects and protocols, discussing the trade-offs between different approaches. Overall, the comments show a cautious optimism towards MeshCore, with interest in its potential but also a desire for more information and real-world testing.
The Hacker News post about MeshCore, a lightweight, hybrid routing mesh protocol for packet radios, has generated a moderate amount of discussion with a mix of curious questions, expressions of interest, and some skeptical observations.
One commenter highlights the challenge of dynamic mesh networking, especially concerning the maintenance of routing tables and efficient data transmission in unstable network conditions. They question how MeshCore addresses these complexities, particularly in scenarios with frequent node joins and departures or fluctuating link quality. This comment reflects a common concern within mesh networking: balancing the need for accurate routing information with the overhead of constant updates.
Another comment focuses on the "hybrid" nature of MeshCore, inquiring about the specific blend of proactive and reactive routing mechanisms employed. They express interest in understanding the trade-offs MeshCore makes between the overhead of proactive routing and the latency associated with reactive routing. This highlights a key aspect of the protocol's design and a point of potential differentiation from existing mesh networking solutions.
Several commenters draw comparisons to other established mesh networking protocols like Babel and BATMAN-adv, questioning MeshCore's advantages and potential improvements. They ask about specific performance metrics, scalability, and resilience to network partitions. These comparisons demonstrate a desire to understand MeshCore's place within the existing landscape of mesh networking technologies and to evaluate its potential benefits over established solutions.
One commenter raises a point about the limited information available in the provided GitHub repository, particularly concerning practical implementation details and performance benchmarks. They express a desire for more concrete evidence of the protocol's claimed efficiency and performance improvements. This echoes a common sentiment among Hacker News users who value practical demonstrations and data-driven comparisons.
A comment also expresses skepticism about the feasibility of achieving significantly improved performance in mesh networking given the inherent constraints of wireless communication. This highlights a more general skepticism about disruptive claims in a well-established field.
Finally, there are comments expressing general interest in the project and requesting further details or expressing their intention to explore the codebase further. This indicates a general interest from the community in exploring new mesh networking technologies and a willingness to engage with promising projects.