Is there a nostr sign-up system, one that guarantees the collection of submited npubs and not have them lost in relays?
Like adding your email to a newsletter on some websites.
I'm assuming there isn't, so I might have to figure out a way to do it (shouldn't be too hard, but it'd be a hassle for the end-user that sets up the form).
#asknostr #nostr
Login to reply
Replies (8)
By the way, by guarantee, I mean sign-ups of 1 million, or 10 million, maybe 100 million too.
I don't think there is one?
Guess I'll have to think of a solution here.
(For playtests on dega)
Ya... It seems like a specialized relay with a traditional db structure is required here, a GUI for its management and sending operations. Open source of course so game devs can set this up if they want bigger limits / unlimited on sign ups
I kind of figured things out; however, this kind of workload is too big to be part of the launch of DEGA, so initially, there'd only be support for 'open playtests', so just a simple add to library/download, with closed ones to be implemented later in the future.
Use your own relay, use a custom event kind, and don't delete them ever, then from your relay push outward.
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.
I'll use what these guys did https://formstr.app/
with two more kinds to handle other things.
i think this can be done on launch as well (launch of the playtest system, not the launch of the store).
it'll be unreliable at a certain percentage of course, that's just the nature of nostr, however, down the line an aggregator events db (like on deg mods) would be developed/setup to mitigate this.