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

Inviting multiple users with PL100 to a story room merges their story into the first user #267

Closed
krille-chan opened this issue Jul 15, 2023 · 2 comments
Labels
Needs upstream fix The issue cannot be fixed in this project and waits for an upstream fix. stale The item is going to be closed soon because of inactivity

Comments

@krille-chan
Copy link
Owner

Description

As I try to not focus my Matrix powers on a single server, I tend to copy-paste a power level event including multiple of trusted accounts on different homeservers. After that and inviting an user, when I post as any of three accounts, they appear as my story instead of the other two being prompted to create their own stories.

I am not sure if it's releated, but all users had their own stories, but I had to leave them due to breaking them by attempting to /upgraderoom 9, which I presume is due to matrix-org/matrix-spec-proposals#3385 .

To Reproduce

  1. Create the first story / room
  2. Give other users power (maybe through Element Web /devtools)
  3. Invite other users to the room
  4. Switch account
  5. Send a story.

Additional information:

  • Device: iPhone SE2020 / A2296
  • OS and OS version: iOS 15.2.1 (19C63)
  • Installed version of FluffyChat: 1.2.0 (7)
  • Which store are you using: Testflight
Copy link

github-actions bot commented Mar 5, 2024

This issue is stale because it has been open for 120 days with no activity.

Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs upstream fix The issue cannot be fixed in this project and waits for an upstream fix. stale The item is going to be closed soon because of inactivity
Projects
None yet
Development

No branches or pull requests

1 participant