-
Notifications
You must be signed in to change notification settings - Fork 8
Description
Incident
I attempted to mitigate slowdowns caused by connecting to multiple relays simultaneously and fetching all their events by making the kitchen relay the default relay. However, when the kitchen.zap.cooking relay went down, the website stopped functioning. I promptly added another default relay, b6031c7, but it was ineffective. While the profiles loaded and you could view those recipes, nothing on the recents page or any of the categories loaded, but the profiles did. Notably, if I removed the offline relay, the website would suddenly start working again.
Initial Assumptions
My initial assumption is that there is a bug in the NDK that is causing this issue. I will open an issue to report it.
Mitigation
For now, I have implemented a temporary fix by filtering out the kitchen.zap.cooking relay from the relay list on load in the commit 710dab3.