8 ms·

I've only just started to dive into it from the documentation side of things. They have ( maybe recently? ) started to create this Gateway Protocol https://docs

by blensor 7mo ago

I've only just started to dive into it from the documentation side of things. They have ( maybe recently? ) started to create this Gateway Protocol https://docs.openclaw.ai/gateway/protocol https://docs.openclaw.ai/gateway/protocol to connect the stuff together. It may be a "we are changing the wheels while driving" thing, but if enough people make nodes for openclaw it will become somewhat of a standard. And then we probably see 100 different claw offshots that all use the same nodes but with a different claw in the center

embedding-shape 7mo ago
> They have ( maybe recently? ) started to create this Gateway Protocol https://docs.openclaw.ai/gateway/protocol https://docs.openclaw.ai/gateway/protocol to connect the stuff together. That's a communication protocol between openclaw server and clients authenticated to that server though, it's not a communication protocol between different openclaw servers, is it? More like defining a HTTP+JSON protocol between a web server and a browser side client application. It's not a "protocol defining how to interact with distributed nodes", again, unless I misunderstand something.
- blensor 7mo ago
  Yes, that's why I compared it to ROS. I didn't mean multiple openclaws communicating with each other but openclaw communicating with nodes ( which are self contained programs running on your desktop or phone providing capabilities like webbrowsing to the claw server )
  - embedding-shape 7mo ago
    Right, I guess that's why I got confused by: > openclaw defines how to interact with distributed nodes When one talks about "distributed nodes" that usually means N nodes talking with each other, and being somewhat homogeneous between each other, unless the protocol temporarly can lift/lower some functionality. You typically don't say "distributed nodes" when you're talking about a server<>client architecture, which seemingly is exactly how openclaw operates, both according to what I saw myself, and what you wrote in this comment.

by blensor 7mo ago

embedding-shape 7mo ago

> They have ( maybe recently? ) started to create this Gateway Protocol https://docs.openclaw.ai/gateway/protocol https://docs.openclaw.ai/gateway/protocol to connect the stuff together. That's a communication protocol between openclaw server and clients authenticated to that server though, it's not a communication protocol between different openclaw servers, is it? More like defining a HTTP+JSON protocol between a web server and a browser side client application. It's not a "protocol defining how to interact with distributed nodes", again, unless I misunderstand something.

blensor 7mo ago
Yes, that's why I compared it to ROS. I didn't mean multiple openclaws communicating with each other but openclaw communicating with nodes ( which are self contained programs running on your desktop or phone providing capabilities like webbrowsing to the claw server )
- embedding-shape 7mo ago
  Right, I guess that's why I got confused by: > openclaw defines how to interact with distributed nodes When one talks about "distributed nodes" that usually means N nodes talking with each other, and being somewhat homogeneous between each other, unless the protocol temporarly can lift/lower some functionality. You typically don't say "distributed nodes" when you're talking about a server<>client architecture, which seemingly is exactly how openclaw operates, both according to what I saw myself, and what you wrote in this comment.