matrix-org / matrix-org/matrix-viewer

Search should return private rooms where the bot is already in or invited to (`world_readable`)

Open
#271 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

T-Other
Dominant language
JavaScript
Stars
84
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I made a private room where I invited the bot (or even have the bot joined in from the past) I expect that room search on the archive site should return this room as it is able to show its chat log.

----
_See below for some background information._

_If I invite the bot to a room that is invite-only but has history visibility set to public, it would be desirable to show the chat log via the web._

_You may ask why this odd combination is beneficial. It's a new proposal against scammers for public groups. Anything else other than invite-only allows for spamming and flooding room state, and we proposed creating a CAPTCHA bot that would let you speak this way, while still retaining readability of the room for outsiders._

https://archive.matrix.org/r/mod-ideas:matrix.org/date/2023/06/22?at=$Y42s_vlxoOy_JRm71sKx09a8gguAgK-fKjRe29FtQXk

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 by tracing the archive site's room-search entry point and the filtering logic for world-readable rooms, then inspect how the viewer determines whether the bot is joined to or invited into a private room. Done means search results include eligible invite-only rooms with public history when the bot is already present or invited, while existing room visibility rules remain intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.