-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check Primary Relays Before Project Submission #116
Comments
I agree, this is probably very important. |
The relays can change for each user, we don't have control over that. |
However, we must check that if there is no active relay, the project should not be registered at all |
We first create the profile on nostr when you click next, than we add the project details and only on the last step we publish to the blockchain. |
Also if you want to have a project using a relay that whitelists users other users won't be able to see the project info.. |
I think this is ok, it is as designed if you get a project from indexer but don't have the relay we don't show it.
This is already the case now no? |
Before we submit a project to the indexer, we need to make sure it is published in the primary relays listed in Angor. If a project isn't in these relays, it might show up in the display but won’t be accessible or have any information available.
Steps to Reproduce:
Expected Outcome:
The project should be published in all primary relays before it gets submitted to the indexer, so it’s accessible and information is available.
Current Problem:
Projects not in the primary relays might show up but won’t be accessible or have any information.
Proposed Fix:
Add a check to make sure the project is published in all primary relays before submitting it to the indexer. This will help avoid issues with accessibility and missing information.
The text was updated successfully, but these errors were encountered: