it feels like the strings we are pulling here could be more entangled. (how) does this fold into %ssb-group ?

could be more entangled - @cryptix

I'm reading two features here, both that could probably be implemented independent of each other.

1. Get Scuttlebot running in a webworker in the browser. This would be the holygrail of distributed awesomeness, because it'd make it very easy to distribute fully functional version of Scuttlebot to people who can't or don't want to install Node on their systems. How do we accomplish this?

2. Spec out and implement group private messages.

what do you mean by one-way or two way groups?

my use of the world entangled might have been misleading. I meant it more like this: let's make sure we re-use the work we previously did, if we can. Not this mixes concepts that should be kept seperate. I'm totally with dominic, that to make this really work for the liteclient, we need a full functioning node, not just relaying the rpc over another pub.

I like the :

• inward group = read (and write) permissions
• outward group = write permissions

I think it taps into some spacial intuitions about how meat-space groups behave

@dominic_temp that sounds good. it will still need sbot indexing of the links to the thread root though, right? otherwise the client has to traverse backwards from their add message to the thread root - and they can't traverse forwards

yes, old messages may have to be decrypted. maybe the key add message could also include seqnums of the earliest use of the key by each feed. then you only have to attempt decrypting messages from those feeds since those seqnums.