Talk knows status "in a meeting/call" only from calendar event, doesn't talk know status from itself and changes on call end??

[Kasperx]

Hi

thank you for this awesome program and environment.
Sry, the title should have one ?, not two.

Description

We use nextcloud talk (windows local program, mostly) with teams in company, hopefully one of latest versions (details later nextc days ;) ). So while in an active call in talk resulting from a calendar event, talk shows status of all members "in a call (or meeting? using german)". Well, right, invited by an event. I think that talk knows the status by itself because, well, it is used ;)

Situation

If one leaves the call the status of the member in talk will not be changed. Right, due to calendar event, but isn't it a personal choice?

Expected

If one leaves the call the status of the member in talk should be changed to the previous status. It should not only be resulted by calendar event.

[Antreesy]

Both are automated statuses:

• In a call - persists for the whole time user being joined to a call (higher priority)
• In a meeting - persists for the whole time event is scheduled in Calendar (e.g. from 10:00 to 11:00)
  Both could be overwritten manually, if user wants to. So we respect preferences, but that still helps others to understand your 'current occupation'

[Kasperx]

Thx for answer. I understand.
What I don't understand is that talk does not change status if the user as member of a meeting leaves that meeting before calendar event "officially" ends, your 2. point. Because if user does leave meeting early (naughty, I know) the logical status of the user is not "in a meeting / call" any more, it should be the previous status before joining the meeting.

[Antreesy]

The thing is, there is no way to know if you left for good, or coming back in 5-10 minutes, right?
So we decided that user is booked till the end of a meeting, with an option to reset status manually

[Kasperx]

Well, program talk knows the current status of "itself", right? Independent of the users behavior or if user wants to return in some minutes (or not). So why not use the current (logical and technical) status of talk? With a calendar you would plan events and meetings, but its only plans, not what user does recently. I see a misunderstanding of environment / program usage there, kind of derived from real life. Or doesn't talk know its status, independent of other progs?
Maybe there should be another status like "occupied for meeting" or "don't disturb" (oh wait ... :D ) for planned, but not joined.

Compared to a smartphone maybe, smartphones use the status of current events like calls. If you are (with smartphone) in an active call, it will signal others (trying to call you) that you are occupied and not ready to react with an accustic and optical signal. Once you end the call and others try again, you are (theoretical) free and ready to react, no occupied signal from your phone to others.

In my opinion program should use the technical status, not what user thinks or not thinks to do in near future like 10 minutes, independent of other plans (calendar?). That would be very near derived to real life, not to things that could happen (or not).