-
Notifications
You must be signed in to change notification settings - Fork 34
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
Use new muxrpc namespace room.* and soft deprecate tunnel.* #89
Comments
Ideas:
|
|
is this done? |
See #220 (comment). I wasn't sure if those deprecation comments were meant for the JS side. There isn't really a defined way to do deprecation in Go. You usually just remove the APIS from the next major version. |
@cryptix does attendants include the client's ID too? It seems like it doesn't? That's fine if it's the case, it's just different from tunnel.endpoints and I'd need to know (also to update the spec). |
Sorry, I'm not following. Is the client the joining/parting room member or the room or..? |
When Alice connects to the room and calls the |
those were confusion and implied some use beyond just opening tunnel.endpoints/room.attendants (which implicitly does what tunnel.announce does). updates #89
* remove room.announce and room.leave from muxrpc those were confusion and implied some use beyond just opening tunnel.endpoints/room.attendants (which implicitly does what tunnel.announce does). updates #89
spec update: ssbc/rooms2#43 |
room.metadata
rooms.attendants
, an alternative totunnel.endpoints
room.metadata
room.attendants
alternative, Design an alternative to tunnel.endpoints #110tunnel.endpoints
as deprecated but keep it workingtunnel.isRoom
as deprecated but keep it workingroom.announce
androom.leave
The text was updated successfully, but these errors were encountered: