Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make public conversations persistent #1816

Closed
pmarini-nc opened this issue Feb 15, 2022 · 9 comments
Closed

Make public conversations persistent #1816

pmarini-nc opened this issue Feb 15, 2022 · 9 comments
Labels

Comments

@pmarini-nc
Copy link

Is your feature request related to a problem? Please describe.
When participating in public conversations, leaving the conversation window makes the conversation disappear from the conversation list so that you need to rejoin the conversation again with the conversation public link.

Describe the solution you'd like
It would be great that public conversation were "first-class citizens" and be persistent by default. The user can decide whenever he/she wants to leave the conversation.

Describe alternatives you've considered
Rejoin the conversation

Additional context
This feature is useful for users that communicate from two or more separate Nextcloud instances and need to establish a persistent communication channel.

@pmarini-nc pmarini-nc added 0. Needs triage enhancement New feature or request labels Feb 15, 2022
@mahibi
Copy link
Collaborator

mahibi commented Feb 16, 2022

Hi Pietro

i cannot reproduce this.
find my successful test in the video.
I first created a conversation in web and opened it to registered users. Then i copied the link which is then used in the video..

please describe at which point you did something different or discovered a different behaviour.

file.mp4

@mahibi mahibi added feature: 🗨️ chat needs info Not enough information provided and removed 0. Needs triage labels Feb 16, 2022
@pmarini-nc
Copy link
Author

That's strange.. I did the same as you, I would say, but the conversation is not persistent
Peek 2022-02-16 13-33

I'm using Talk v13.0.0

@no-response no-response bot removed the needs info Not enough information provided label Feb 16, 2022
@mahibi
Copy link
Collaborator

mahibi commented Feb 16, 2022

okay that's strange. also can't reproduce with 13.0.0
did you discover this also on other nextcloud instances or only on your local test instance?

additionally it's strange that the messages in the chat seem to be duplicated..
grafik

@pmarini-nc
Copy link
Author

It is also reproducible on c.nc.com.

I don't if this is relevant, but I'm running talk-android as downloaded from here and my device runs /e/OS

In any case, if you cannot reproduce, I would say that something is wrong with my setup and happy to hear that the feature is already implemented.

@pmarini-nc
Copy link
Author

Now, in Talk Android 17.1.2 against Nextcloud server 17 I cannot even enter the conversation once ("Something went wrong")

@mahibi
Copy link
Collaborator

mahibi commented Oct 24, 2023

Now, in Talk Android 17.1.2 against Nextcloud server 17 I cannot even enter the conversation once ("Something went wrong")

can you enter the conversation in webUI?

@pmarini-nc
Copy link
Author

pmarini-nc commented Oct 25, 2023 via email

@mahibi
Copy link
Collaborator

mahibi commented Nov 3, 2023

Is it an instance that i could access with a test account?

@mahibi
Copy link
Collaborator

mahibi commented Nov 29, 2023

Having a closer look, i think i oversaw that you asking for this to be from a seperate instance.
Unfortunately, this feature had to be dismissed as experimental.
While modernizing the codebase (conductor migration), it was even removed for the upcoming v18 to join other instances via conversation link. So for now conversation can only be joined on the same instance.
Communicating between different instances will come back again, and then also for all platforms!

@mahibi mahibi closed this as completed Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants