feat!: include the sender
ID in static messages
#1172
Merged
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.
In practice, the
severity
of static messages has proven to be meaningless and increases protocol complexity.This PR replacing
severity
withsender
to resolves #1004 (comment)This PR removes the
ps.pub_static()
method and replaces it withps.pub_to()
:Messages with a
kind
that starts with@
indicate they are static messages. Accordingly,ps.sub_remote()
subscribes to static messages using that kind:The
ya pub-static
command has also been removed and replaced withya pub
: