feat: real time Guardian status #358
Open
Conversation
This file contains hidden or 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
m1sterc001guy
force-pushed
the
peer_status2
branch
from
1fde50a to
5669c88
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It always bothered me that in order to determine if a peer is online or offline we needed to wait 30 seconds and manually refresh the UI. With the new API in
v0.10.0, we no longer need to do this.This PR:
PeerStatus. If the user hasn't joined the federation yet, it is a stream with a single event.Below is small video of what it looks like to manually kill guardians in a devimint federation.
Kooha-2026-01-28-14-13-41.webm