Don't allow incoming calls if "debug calls" is disabled

[hpk42]

It's currently not possible to have a chat profile that does not do calls, even though we declare it "opt-in" officially.

With "debug calls" disabled, incoming calls core should only print a (system) message, and leave the profile alone. See also https://misskey.sangeunahna.com/notes/ah4ub6qwfsjo0178 for user-context.

[adhisimon]

Yes, it's a blocker for me to share my public deltachat link. My current sollution is to use two separate apps, one official deltachat, and one arcanechat.

[link2xt]

Core does not have a "debug calls" option, so it is an UI issue or we need to add some option to the core that will result in not emitting events.

[hpk42]

we probably need some UX guidance from @r10s for options around calls, also in light of recent work on iOS native calls. But i would expect that a core-managed per-profile calls-option, with a clear definition of what it causes in the UIs would be useful.

[adhisimon]

I think it should be handled by UI. Should be simple just to ignore incoming call and not raising any notification if calls is disabled. No need to bloat core. But that was my opinion.

[link2xt]

Related forum post: https://support.delta.chat/t/who-can-call-me-setting/4303
We currently don't have a well-managed contact list (https://support.delta.chat/t/separate-collected-contacts-from-the-contact-list/4485) and contact requests already should not cause calls.
For now we can add to the core an option "who can call me" with two options: "Everybody" and "Nobody". "Everybody" is like it is now, "Nobody" means there are no call notifications at all. Third option "My contacts" can be added when/if we have a better contact list that is significantly different from "Everybody".

[link2xt]

I think it should be handled by UI. Should be simple just to ignore incoming call and not raising any notification if calls is disabled. No need to bloat core. But that was my opinion.

We usually try to put as much logic as possible into the core to avoid different behaviors in different clients.

[r10s]

contact requests already should not cause calls.

this was the reason to postpone the discussion about an option that time. also to have one potential issue less to check if things do not work

however, it is indeed questionable when sharing invite links publicly (which, however, is discouraged), so some option makes sense

[r10s]

ftr, thinking it over, iirc, there are also ideas around to let "old" publicly shared invite links result in a contact request only, without "verification" flag set then.

not saying that this will completely make an option superfluous, but this seems to be the issue at hand

[link2xt]

ftr, thinking it over, iirc, there are also ideas around to let "old" publicly shared invite links result in a contact request only, without "verification" flag set then.

I also checked, members of the group that you wrote to still result in a contact request when they try to create a 1:1 chat with you. So the problem of strangers you never approved manually calling you seems to be only possible with a public QR invites.

Still, for a public profile you may want to have a lot of 1:1 chats with strangers, but disable calls completely, so #7682 is still useful for the "Nobody" option.