This repository has been archived by the owner on Sep 24, 2023. It is now read-only.
Broadcast Coordinators to Nostr #397
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benthecarman
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was done during a live coding session at TAB conf.
Scalastr is still being published to maven: https://issues.sonatype.org/browse/OSSRH-85124
Some things should still be handled. We are using a
mutable.Bufferfor theextraCoordinatorsnow. This is not ideal and we should be able to handle receiving a nostr announcement while running.We can also have the coordinator check if they have already sent their address with the relay.