I'm slowly refactoring my infrastructure (including my endpoints).
While gtg.steem.house:8090 is deprecated, it is still running routing to a websocket endpoint, mostly used by cli_wallet users, but I also still see quite a lot of obsolete, deprecated traffic from various clients.
I think that the landscape will largely change after MIRA release.
That makes sense. Do you want the
gtg.steem.house:8090node to still be listed in the public RPC node lists?Yes, you can leave it listed for now, I will make appropriate announcements when it all settles down.
Like for example I have also https://api.steem.house/simple endpoint that routes to consensus node for broadcasting purposes, etc.
Maybe we should establish a standard way of publishing such info, for example using account's JSON metadata? I don't like EOS way by the way, but we can keep it simple:
"endpoints": { "api": "https://api.steem.house", "seed": "gtg.steem.house:2001" }Well, maybe not that simple because there are some more things to consider and we don't want to use napkin grade pseudo-standard that wouldn't cover all cases (multiple nodes, not all nodes are equal (plugins, configs) websocket support or not, etc.).
;-)
Well, it can be off chain for starters. If we came up with a list of criteria that we want to track, we could work on collecting the info from all the node operators.