Implementing authorized_keys function for non-NIP-42 supported clients #8
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.
I expected to start Bostr Relay, which only accepts my public key for reading and writing.
However, I've discovered most iOS clients do not support NIP-42, so I could not make my personal Bostr relay as expected.
Instead, I've added some code in this program to achieve similar goals by checking their public key when they've made writing requests to the Bostr Relay.
Please accept my merge request if you like my idea. Please let me know if you have any suggestions so I can change the code accordingly. If you don't like my idea, please don't hesitate to close this pull request.