search

radicle-dev / radicle-bins

Collection of radicle binaries.
Other
21 stars 9 forks source link

seed: show list of peers that track project on project card #44

Open rudolfs opened 3 years ago

rudolfs commented 3 years ago

Can we list the remotes that track a project and show their users? This will help greatly with collaboration as people can get hold of remotes to add in upstream.

cloudhead commented 3 years ago

After some chatting with @xla on IRC and a comment here: https://github.com/radicle-dev/radicle-link/pull/436#issuecomment-732407411, we were thinking it might make sense to make this the primary way to discover peers on the seed node. This would mean getting rid of the peer list to the right, and focusing on the projects and the peers.

One consequence of this would be to sort the project list by online peers, eg. projects that have remotes which are currently connected (online) would show up first in the list.

cc @juliendonck

xla commented 3 years ago

The stats for online peers and seeded projects still make sense.

abbey-titcomb commented 3 years ago

I like this. IMO, an even simpler start would be to have the total number of peers who have tracked the project visible on the project card. This shows how "popular" the project is and visualizes signalling on what view of the project someone should track for the most up to date version. I think this would be a super cool improvement I'd love to see sooner than later.

Listing people will make more sense when you can navigate to user profiles and see lists of projects etc...

xla commented 3 years ago

Listing people will make more sense when you can navigate to user profiles and see lists of projects etc...

Listing remotes also helps to manage remotes locally, something that is a bit tedious at the moment. Flow being: copy Radicle ID -> replicate -> copy Device ID -> add to remotes.

abbey-titcomb commented 3 years ago

Listing people will make more sense when you can navigate to user profiles and see lists of projects etc...

Listing remotes also helps to manage remotes locally, something that is a bit tedious at the moment. Flow being: copy Radicle ID -> replicate -> copy Device ID -> add to remotes.

Sure sure, from a maintainers perspective absolutely — this makes sense. Just wondering how we choose with peers to list....