Skip to content

rpc table with copyable urls #180

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: dev
Choose a base branch
from
Draft

rpc table with copyable urls #180

wants to merge 4 commits into from

Conversation

dariaag
Copy link
Collaborator

@dariaag dariaag commented May 20, 2025

  • made rpc table by network
  • made urls copyable by clicking on them
  • had to make font smaller to fit so not sure about this, hence draft pr

@dariaag dariaag requested review from kkkk666 and web3jenks May 20, 2025 07:26
@kkkk666
Copy link
Collaborator

kkkk666 commented May 20, 2025

image I think there is too much information on the horizontal axis now. It would be better to swap the contents of the horizontal and vertical axes. This way, the presentation would be more user-friendly.

@web3jenks
Copy link
Collaborator

image I think there is too much information on the horizontal axis now. It would be better to swap the contents of the horizontal and vertical axes. This way, the presentation would be more user-friendly.

I also think is a bit hard for developer to select the right endpoints.

Could we consider reducing the dimentions, and have the different types of nodes in side one cell? @dariaag

@web3jenks
Copy link
Collaborator

image I think there is too much information on the horizontal axis now. It would be better to swap the contents of the horizontal and vertical axes. This way, the presentation would be more user-friendly.

I also think is a bit hard for developer to select the right endpoints.

Could we consider reducing the dimentions, and have the different types of nodes in side one cell? @dariaag

How about this?

| Type | Provider URL |
| RPC (Pruned) | Node Guru: https://xxxxxxxxxxx ; Polkachu: https://xxxxxxxxx |

Grouping by type, we have multi-lined entry for provider and their urls.

How will this look?

@dariaag
Copy link
Collaborator Author

dariaag commented May 21, 2025

@web3jenks what about this?
Screenshot 2025-05-21 at 9 03 34 AM

@kkkk666
Copy link
Collaborator

kkkk666 commented May 22, 2025

@web3jenks what about this? Screenshot 2025-05-21 at 9 03 34 AM

Do we have a recommended node? For example, could we mark * on top of a certain recommended node?

@dariaag
Copy link
Collaborator Author

dariaag commented May 22, 2025

@kkkk666 great idea! our preferred ones are node guru? @web3jenks

@web3jenks
Copy link
Collaborator

web3jenks commented Jun 2, 2025

@kkkk666 great idea! our preferred ones are node guru? @web3jenks

Yes preferred ones are node.guru ones.

@web3jenks
Copy link
Collaborator

@web3jenks what about this? Screenshot 2025-05-21 at 9 03 34 AM

Okay, this might be the only way to present it without introducing vertical scrolling.

Let's introduce vertical scrolling and make them a bit wider so we don't see two lines for a node url on a normal width (1200px) if the provider is more than 3.

@web3jenks
Copy link
Collaborator

@dariaag and I have discussed, we will find more examples from other ecosystems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants