Add support for rooms

[boreq]

Rooms need to supported before using scuttlego in Planetary as we just added basic room support to the app.

The scope of the required work needs to be further investigated and documented.

Alias management:

• connect to a room and list aliases using an RPC command
• connect to a room and revoke an alias using an RPC command
• connect to a room and register an alias using an RPC command
• return a predefined error when an alias is already taken when registering it (requires changes to the RPC layer, related to Properly handle error cases when redeeming invites #62)
• test commands and queries, confirm how EndOrErr is set for async requests

Connection management:

• accept tunnel.connect
• when connecting to the room we must be able to dial people using that room
• persist information about rooms advertised on feeds
• stay connected to our own rooms so that people can talk to us?
• use rooms in connection management (randomly dial known rooms and talk to the online peers should be fine for now)

[decentral1se]

I was asking about room functionality to cryptix at some point and got the following tips:

(hopefully fine to share!)

so to add allow connections to the room you need to

sbotcli call conn.replicate @roomID.ed25519

since a room doesnt have a feed it wont sync anything. then you can

sbotcli cal conn.connect "net:1.2.3.4:8008~shs:roomID"

just like with a normal pub.. afterwards you should start seeing join and leave messages for the room members in the go-sbot output. finally, if room members dont connect to a go-sbot, you can use conn.dialViaRoom to initiate a connection the other way around. the address follows what manyverse does.. the syntax is tunnel:@roomID.ed25519:@target.ed25519~target

Maybe helpful!

[rabble]

Could be moved to review, question: how large can rooms get.

Need connection manager when we get LOTS of people online. Right now we don't have any logic around who to connect to so it tries everybody.

[boreq]

Closing and replacing with a bunch of smaller issues:

• Accept tunnel.connect  #93
• Properly handle error cases when registering aliases #94
• Test alias-related commands and queries #95