nextcloud / nextcloud/richdocuments
Properly set the username for federated editing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
If NextcloudServer1 user "jon" jon@nc.tld1 opens document via other server running Collabora, then a different guy named "jon" on NextcloudServer2 jon@nc.tld2 opens a document, the Collabora admin panel counts these both as 1 user in the "Users online" tab. It says correctly in large letters, that there are 2 users, but the "Users online" Collabora Admin tab @loleaflet/dist/admin/admin.html combines any users with the same name even though they are different people.
I'm wondering if there's anyway to include the domain in the username that gets sent to collabora server or if this has another workaround, or is this a Collabora bug or perhaps there's a loolwsd admin setting I can't find. I deem this NOT good for the purpose of monitoring usage for 2 NextCloud instances sharing a Collabora server.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with loleaflet/dist/admin/admin.html and trace how the Users online tab identifies and combines users. Then inspect how the username is sent to the Collabora server and whether the federated domain is available there. Done means users with the same name from different Nextcloud domains are counted separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100