[QA] federated ids are not "wellformed" email-addresses
Open
Nobody has claimed this yet.
QA:team
- Dominant language
- PHP
- Stars
- 8.8k
- Forks
- 2.1k
- Avg merge
- 20h 7m
- Merged PRs (30d)
- 41
Description
Seen on server 10.7.0RC2
- usernames can have whitespace
- serverurls can have a path component
- both are incorporated into the federation id
Ducktyping breaks here.
A federation id looks like an email address, but it is not an email address.
Maybe showing it urlencoded would help with worries about whitespace?
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 by reproducing the federated ID behavior described on server 10.7.0RC2, then trace where usernames and server URLs are combined and validated. The issue does not name files or tests; done should mean IDs containing whitespace or server URL paths are handled consistently without treating them as ordinary email addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100