I challenge nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 and nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr to use Iris, Snort and Nostrudel with the same set of "read" relays I'm using and see how much they can survive with threads that don't load, root events that show up only in notifications but not in the actual event view, parents that don't show up or replies that have no indication that they are replies and publishing of events without any visual feedback that the event has actually been published.
once I am ready with some more alpha tests, I will ask you to use wss://nostr. ivmanto.dev as reading relay
Nice event to plan and visit …
hey :), be careful what you wish. That idea is easy to still and it’s great and it’s feasible … 👍
nostr:npub1zach44xjpc4yyhx6pgse2cj2pf98838kja03dv2e8ly8lfr094vqvm5dy5 I just made an announcement on flcokstr and it posted it as a note on other clients. For some people it might be not clear what’s going on.
for testing purposes you can include as well wss://nostr.ivmanto.dev 😃
but it is in early alpha …