Investigate ssb clients and how they interact with sbot

[benhylau]

• [x] Over plain http, https, or websocket?
• [x] Does an "app" need to be installed on client?
• [ ] How to pass identities?
• [ ] How to share a sbot instance among multiple identities?
• [ ] How do invites work with IPs over LAN? How about a cjdns address?
• [x] Do nodes run a pub?
• [x] How does LAN discovery work?

[darkdrgn2k]

Cycle 1 update

Proof of concept SBOT interface was created that could answer some of the questions.

My proof of concept stores the SBOT Private/Public keys on the "server" (or your private pi) allowing a Login/Password to use make use of those credentials. This would allow a simple web browser to interact with the pi and the pi does all the ScuttleBot heavy lifting (databasing, indexing etc)

• Over plain http, https, or websocket?

Would work over plain HTTP/HTTPS

• Does an "app" need to be installed on client?

No

• How to share a sbot instance among multiple identities?

Yes

• How to pass identities?

Login/Password you create

• Do nodes run a pub?

Maybe not a full pub but defiantly sbot. It would deal with all the collection of data as time goes on so when you login you have all the information ready to go (no more waiting to sync)

• How does LAN discovery work?

IPV4 Broadcast packet with Identity and "call back" ip address is sent out

Issues found and details can be found at https://github.com/benhylau/ssbc-grants-scuttlemesh/issues/5

• How do invites work with IPs over LAN? How about a cjdns address?

Broadcasts only work on IPV4, We could however craft unicast addresses to each device we are cjdns peered with however currently it looks like it only listens on an ipv4 socket.

Two Options

• Best option - SBOT ipv6 support for Invites (but since ipv6 doesnt do broadcasts i dont know if they will implement that)
• Possible quick option - SOCAT hack to move ipv6 packets to IPV4 port (will it screw up the packet content with the : in ipv6?)