remove followRelay from Follow type #57
Merged
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
The followRelay field in the Follow type has been removed as it's redundant with NIP-65 (RelayListMetadata). Instead of storing relay information with each follow, we now rely on RelayListMetadata events to discover which relays to use for each contact. - Reduces complexity in follow list handling - Removes duplicate relay information storage event ID handling and post notifications - Fix event ID serialization to avoid double quotes in QML - Add missing notifications for post changes - Store events locally before publishing - Fix repost handling in MainContent.qml
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.
The followRelay field in the Follow type has been removed as it's redundant with NIP-65 (RelayListMetadata). Instead of storing relay information with each follow, we now rely on RelayListMetadata events to discover which relays to use for each contact.
event ID handling and post notifications