Published on: 2014-06-01T09:56:52+00:00
In a recent Github discussion, the topic of dependency on centralized resources in applications is emphasized. The conversation highlights the importance of addressing issues related to broken and insecure applications caused by DNS seeds being down. It is argued that instead of solely relying on DNS seeds, fallbacks such as hardcoded node lists and manual peer entry should be implemented, particularly during the initial startup phase. This approach ensures that the application remains functional even when DNS seeds are unavailable.However, it is important to note that this solution still relies on a centralized resource. To make the application more resilient, it is suggested that either the application needs to be made more resilient or there needs to be a more robust DNS system in place. This would prevent downtime and ensure that the application can continue to function even when there are issues with DNS seeds.To explore the details of this discussion further, you can refer to the provided link. Additionally, the conversation ends with a mention of automated cross-browser testing and an invitation to join a mailing list.
Updated on: 2023-08-01T09:23:08.001242+00:00