element-hq / element-hq/element-web
The language around published addresses makes it sound like you can bypass join rules
- Dominant language
- TypeScript
- Stars
- 13.5k
- Forks
- 2.8k
- PR merge metrics
- PR metrics pending
Description
### Your use case
#### What would you like to do?
I would like to not get confused as to what the impact of setting a published address for a room does.
#### Why would you like to do it?
So I don't have to spend 30 minutes each time figuring it out
#### How would you like to achieve it?
By rewording the following
> Published addresses can be used by anyone on any server to join your room. To publish an address, it needs to be set as a local address first.
The "by anyone on any server" makes it sound a bit like it can be used somehow to bypass join rules. That's not the case, but it would be nice to have something in there like "by anyone knowing the published address and as permitted by the room's access permissions"
### Have you considered any alternatives?
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Locate the interface text containing “Published addresses can be used by anyone on any server to join your room.” Read the surrounding copy and any related documentation, then revise the wording so it does not imply that published addresses bypass the room’s access permissions; confirm the updated text is clear in the relevant room settings view.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100