nostr-control #453
Closed
nostr-control #453
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
|
Needs rebase |
|
@joelklabo do you still want me to merge this? There are conflicts that need to be resolved. If nostr-control is not being actively maintained, can you remove it from this PR and keep only the part that removes nostrify? If you are unavailable to do this, please let me know so I can do it instead. |
|
Whoops, I forgot we already removed nostrify and @joelklabo stated that he isn't maintaining the newer nostr-control either. Thinking it might be nice to keep everything in an archived list that isn't in the README, even plugins that never made it in here, just so users can search through old code that worked for someone at some point. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding nostr-control and removing Nostrify (now unmaintained, re-implemented as nostr-control)