nextcloud / nextcloud/spreed

Shares in federated conversation broken for public conversations

Open
#18,650 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: api 🛠️ feature: federation 🌐 feature: upload & shares & voice 📤🎙️ regression
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

[!TIP]

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Instance A: Have a conversation that is public (!)
  2. Instance A: Post a picture
  3. Instance A: Invite participant from instance B
  4. Instance B: Accept invite and open conversation
Expected behaviour
Image
Actual behaviour
Image

From what I can see it's a regression from conversation folders, namely https://github.com/nextcloud/spreed/commit/bb1a36d830255f046e96cbbeac324b4595e8aeac.

https://github.com/nextcloud/spreed/blob/c22c37107ae58d690ddae86065c011579e2851fc/lib/Chat/Parser/SystemMessage.php#L544-L550

Since this is not throwing anymore, we don't end up at https://github.com/nextcloud/spreed/blob/c22c37107ae58d690ddae86065c011579e2851fc/lib/Chat/Parser/SystemMessage.php#L575-L577

Talk app

Talk app version: Tested stable34 -> main

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in lib/Chat/Parser/SystemMessage.php at the cited lines 544-550 and 575-577, then compare the behavior with the conversation-folders regression commit bb1a36d. Reproduce the public federated conversation flow with an image between two instances and verify that the shared image reaches the expected state shown in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.