talk-ios
talk-ios copied to clipboard
nextcloud
Add ability to add a caption when sharing media or file through iOS share sheet
Is your feature request related to a problem? Please describe. At the moment if we want to, for example, send an image to a Nextcloud Talk chat with a caption we have to:
- choose the image
- open the share sheet
- choose Nextcloud Talk
- choose the chat
- send the image
- open Nextcloud Talk
- choose the same chat
- send the caption separately
Describe the solution you'd like It would be nice if we could add a caption directly to the image (or file) right before sharing it:
| What iOS Messages does | What Nextcloud Talk could do ("Add a comment..." text field shamelessly stolen by Telegram share sheet) |
|---|---|
 |
 |
This would result in the following steps:
- choose the image
- open the share sheet
- choose Nextcloud Talk
- choose the chat
- add a comment
- send the image
which would eliminate the hassle of having to manually open the app again just to add a comment to the shared media.
The comment can be sent in a separate message following the media file, since I don't think Nextcloud currently supports captions.
Describe alternatives you've considered Not relevant.
Additional context Using Nextcloud Talk iOS 14.0.0.
Hi @e-caste Thank you for your ideas! I remember discussing this in the past and the problem was/is that media and text can’t be combined in a single message, so it would be 2 messages. But it would be possible, basically. Any opinions @Ivansss ? Should we add a text field and send 2 messages?
@SystemKeeper Yes, that was my idea as well:
The comment can be sent in a separate message following the media file, since I don't think Nextcloud currently supports captions.
Interesting idea indeed :) As @SystemKeeper this is currently not possible due to the current API but sending a second message could be a workaround for implementing this feature.
Server ref: https://github.com/nextcloud/spreed/issues/5354
But we also have "metaData" already for shares, e.g. to mark voice messages different. Could also add a comment field on that. However if we simply duck-tape that together into
{file} "Inserted comment"
It would break the rendering currently done by the clients, so that would need a bit coordination
Should we implement this as two messages as a first step? We could chain the sending, first upload and post the file, then post a message directly after. Changes to the gui would be the same as having server support for this, so needs to be done either way.
I think we should wait and then bring and support this properly on all platforms in one cycle.