Unclear messenger functions #638

New Issue

Iceman · 2023-03-02T12:03:01Z

Iceman commented

2023-03-02 12:03:01 +00:00

Hello, Cwtch guys!
I have some questions about the messenger's functions and I haven't found answers to them on your site or elsewhere, so I have to ask you directly.
First, is it possible to broadcast a message to all your contacts at once? That is, to send a single message to each of your contacts in one click.
Second, is it possible that one of my contacts introduced me to another user which is not in my contacts? This is done greatly in Briar, do you have something similar?
Third, if my contact introduced me to someone else and then this new person writes to me, will I be able to see who introduced me to him?
And finally, is it possible to create some standard message that will be sent to every new contact I accept in my list?

Hello, Cwtch guys! I have some questions about the messenger's functions and I haven't found answers to them on your site or elsewhere, so I have to ask you directly. First, is it possible to broadcast a message to all your contacts at once? That is, to send a single message to each of your contacts in one click. Second, is it possible that one of my contacts introduced me to another user which is not in my contacts? This is done greatly in Briar, do you have something similar? Third, if my contact introduced me to someone else and then this new person writes to me, will I be able to see who introduced me to him? And finally, is it possible to create some standard message that will be sent to every new contact I accept in my list?

sarah commented

2023-03-02 19:03:15 +00:00

Hi.

First, is it possible to broadcast a message to all your contacts at once? That is, to send a single message to each of your contacts in one click.

Not through the standard UI.

We have bot libraries that allow this kind of functionality https://git.openprivacy.ca/sarah/cwtchbot (by iterating through the list of contacts and sending a message to each out).

The underlying p2p libraries also support a broadcast primitive that is used by cwtch-servers to share a message with all connected peers. (https://git.openprivacy.ca/cwtch.im/tapir/src/branch/master/networks/tor/BaseOnionService.go#L314)

Second, is it possible that one of my contacts introduced me to another user which is not in my contacts?

Yes, we have a "send invite" function - which allows a user to share a cwtch address or group invitation with another user.

It seems the p2p documentation for this feature is missing on https://docs.cwtch.im - I will make a note to udpate it. There is a provisional groups entry which is functionally identical (https://docs.cwtch.im/docs/groups/send-invite)

Third, if my contact introduced me to someone else and then this new person writes to me, will I be able to see who introduced me to him?

No. The invite carries no metadata.

And finally, is it possible to create some standard message that will be sent to every new contact I accept in my list?

Not via the standard UI. You can do this using the bot framework above. We have some plans to allow bot integration into the UI, but no work has begun in that direction.

Hi. > First, is it possible to broadcast a message to all your contacts at once? That is, to send a single message to each of your contacts in one click. Not through the standard UI. We have bot libraries that allow this kind of functionality https://git.openprivacy.ca/sarah/cwtchbot (by iterating through the list of contacts and sending a message to each out). The underlying p2p libraries also support a broadcast primitive that is used by cwtch-servers to share a message with all connected peers. (https://git.openprivacy.ca/cwtch.im/tapir/src/branch/master/networks/tor/BaseOnionService.go#L314) > Second, is it possible that one of my contacts introduced me to another user which is not in my contacts? Yes, we have a "send invite" function - which allows a user to share a cwtch address or group invitation with another user. It seems the p2p documentation for this feature is missing on https://docs.cwtch.im - I will make a note to udpate it. There is a provisional groups entry which is functionally identical (https://docs.cwtch.im/docs/groups/send-invite) > Third, if my contact introduced me to someone else and then this new person writes to me, will I be able to see who introduced me to him? No. The invite carries no metadata. > And finally, is it possible to create some standard message that will be sent to every new contact I accept in my list? Not via the standard UI. You can do this using the bot framework above. We have some plans to allow bot integration into the UI, but no work has begun in that direction.

Iceman commented

2023-03-03 09:26:49 +00:00

I see. And how could I use these bots you mentioned? Could I compile them and call from command line or would I have to write my own go code which calls them?
You also said that an invite doesn't indicate the introducer. Then is it possible to combine this invite with a message that contains introducer's ID? If it is, I could take this ID, search for it in my contacts and if present I could let the new person in.

I see. And how could I use these bots you mentioned? Could I compile them and call from command line or would I have to write my own go code which calls them? You also said that an invite doesn't indicate the introducer. Then is it possible to combine this invite with a message that contains introducer's ID? If it is, I could take this ID, search for it in my contacts and if present I could let the new person in.

sarah commented

2023-03-06 20:19:56 +00:00

And how could I use these bots you mentioned? Could I compile them and call from command line or would I have to write my own go code which calls them?

You would have to implement the desired behavior yourself.

You also said that an invite doesn't indicate the introducer. Then is it possible to combine this invite with a message that contains introducer's ID? If it is, I could take this ID, search for it in my contacts and if present I could let the new person in.

We are currently revising the invite flow (#618) - this will likely include some additional information regarding the origin of an invite. Currently the only way to provide this information would be in a follow up message - though there is no nice way of linking this right now.

> And how could I use these bots you mentioned? Could I compile them and call from command line or would I have to write my own go code which calls them? You would have to implement the desired behavior yourself. > You also said that an invite doesn't indicate the introducer. Then is it possible to combine this invite with a message that contains introducer's ID? If it is, I could take this ID, search for it in my contacts and if present I could let the new person in. We are currently revising the invite flow (https://git.openprivacy.ca/cwtch.im/cwtch-ui/issues/618) - this will likely include some additional information regarding the origin of an invite. Currently the only way to provide this information would be in a follow up message - though there is no nice way of linking this right now.

Iceman commented

2023-03-07 10:56:16 +00:00

You would have to implement the desired behavior yourself.

So I'll have to write the code, correct?

We are currently revising the invite flow (#618) - this will likely include some additional information regarding the origin of an invite.

And do you have any expectations of how long this would take approximately?

> You would have to implement the desired behavior yourself. So I'll have to write the code, correct? > We are currently revising the invite flow (#618) - this will likely include some additional information regarding the origin of an invite. And do you have any expectations of how long this would take approximately?

sarah commented

2023-03-07 16:46:49 +00:00

So I'll have to write the code, correct?

Yes

And do you have any expectations of how long this would take approximately?

My hope is to get to it later this month.

For clarity: We are currently working though the cwtch stable roadmap (https://docs.cwtch.im/blog/path-to-cwtch-stable) and all of the remaining items have deadlines towards the end of March. Much of that work has been foundational and is just now making it's way into the UI (#639).

Once that work starts winding down, the next highest priority items are around invitations and other UI-focused functionality.

> So I'll have to write the code, correct? Yes > And do you have any expectations of how long this would take approximately? My hope is to get to it later this month. For clarity: We are currently working though the cwtch stable roadmap (https://docs.cwtch.im/blog/path-to-cwtch-stable) and all of the remaining items have deadlines towards the end of March. Much of that work has been foundational and is just now making it's way into the UI (https://git.openprivacy.ca/cwtch.im/cwtch-ui/pulls/639). Once that work starts winding down, the next highest priority items are around invitations and other UI-focused functionality.

Iceman commented

2023-03-09 07:41:15 +00:00

I see. I'll wait then.

Iceman commented

2023-04-18 13:10:19 +00:00

Hello again!
You said last time you were going to work on invitations after the end of last month. So how is it going?

Hello again! You said last time you were going to work on invitations after the end of last month. So how is it going?

sarah commented

2023-04-20 19:36:02 +00:00

Hi.

We moved some things around at the end of March (https://docs.cwtch.im/blog/cwtch-nightly-1-11 / https://docs.cwtch.im/blog/cwtch-stable-roadmap-update) - and my priority for the last few weeks has been laying some additional ground work for Cwtch Stable.

On the invitation font, @marcia has started UI design work that includes how invites/filesharing should be repositioned in the current interface - that work is going to drive any API changes.

My goal is to get a cut of the new api/ui/functionality out this 1.12 cycle - expecting a 1.12 release candidate to be ready mid-May but could be sooner depending on how quickly some other work comes together.

Hi. We moved some things around at the end of March (https://docs.cwtch.im/blog/cwtch-nightly-1-11 / https://docs.cwtch.im/blog/cwtch-stable-roadmap-update) - and my priority for the last few weeks has been laying some additional ground work for Cwtch Stable. On the invitation font, @marcia has started UI design work that includes how invites/filesharing should be repositioned in the current interface - that work is going to drive any API changes. My goal is to get a cut of the new api/ui/functionality out this 1.12 cycle - expecting a 1.12 release candidate to be ready mid-May but could be sooner depending on how quickly some other work comes together.

Iceman commented

2023-04-25 12:09:35 +00:00

And are you going to add any invitation features in this release that we've talked about which allow to see the invite origin?

By the way, your tor connection is broken. When I visit this site through tor browser, I see an error message at the top which talks something about root url set to onion address, although I'm not using onion address, but a usual one.

And are you going to add any invitation features in this release that we've talked about which allow to see the invite origin? By the way, your tor connection is broken. When I visit this site through tor browser, I see an error message at the top which talks something about root url set to onion address, although I'm not using onion address, but a usual one.

Sign in to join this conversation.