Thread

Ya that is another way of doing it, and the client (in this case DEGA) would read and filter them, then have a different kind event to have a list of 'selected' submitters, then the game dev would update the playtest page to add that list event id to it, where users would then be able to see if they're in the test or not, and if they're in then they'd receive an envolved encryption (sent via a nother kind event) locked to their pubkey that they can open to decrypt the test build file. i guess the only issue here is for devs to whip up this type of relay that they'd control to handle all these requests, and perhaps to have a super fast relay structure to handle said potential scale. I'd imagine x% of devs would grab whatever public relay and slap it in there, resulting in an unreliable result even a small scale (1k? 10k?). I'd imagine the best that can be done in this situation is to build such a decent relay, write/record a great guide, and plaster a few warnings to advise not to use random public relays and showcase the unreliability of the experience of doing so.