cloud fodder's avatar
cloud fodder
cloudfodder@rogue.earth
npub10npj...tl5h
captain of a sailing vessel building relay.tools electron microscopic time preference capable simplex DM me for all your remotely operated underwater vehicle needs: https://simplex.chat/contact#/?v=1-4&smp=smp%3A%2F%2FSkIkI6EPd2D63F4xFKfHk7I1UGZVNn6k1QWZ5rcyr6w%3D%40smp9.simplex.im%2FP0rE9zB_W1ljpc_Jsaz6K-tbRm2mHqsP%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEAvVLbWdTbqwpdPLLtKG22WDXJUiS1EMVTByd5NuwikWU%253D%26srv%3Djssqzccmrcws6bhmn77vgmhfjmhwlyr3u7puw4erkyoosywgl67slqqd.onion
@Vitor Pamplona do you ever notice with quartz, events come in after the EOSE when they should have arrived before that. It's happening to me fairly consistently which makes me wonder, is quartz detecting this timing right? Is the relay actually sending an EOSE and then the specific event it should have had before the EOSE (like an event id subscription). (in this quartz app I'm building)
/me looks for your relay list. /me realizes you use a client that doesn't have relay lists. /me cries softly.