matrix-org / matrix-org/thirdroom

Profile interop: Send avatar and thumbnail as attachments

Open
#379 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Frontend
Dominant language
C
Stars
647
Forks
70
PR merge metrics
No merged PRs in 30d

Description

#70 mentions:
> 3D avatar / thumbnail should be saved in `m.world.profile` room state event

So we can assume it's planned to be state events for now as a primary data point in `profile` type rooms. My only issue with this is **interoperability**:
- one needs to do extra steps to download their backed up model/sprite, as well as to see related thumbnail, from any other client;
- `profile` room will just look empty or have events of which only Third Room client can make sense.

I propose such binary data to be sent as **attachment** instead of room state event.

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 reading this issue alongside #70, then inspect how `m.world.profile` room state events and attachments are currently represented. Define the interoperability requirements and acceptance criteria for sending avatar and thumbnail binary data as attachments rather than state events.

Written by the indexing model from the issue text.

Assessment

Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.