You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To take a few steps towards understanding Threads in Android before a full implementation
Why would you like to do it?
To ensure maximum backwards compatibility and continuity in conversations when threads will be available to the masses.
How would you like to achieve it?
MSC3440 recommends two things for clients that do not fully support threads yet
To treat m.thread the same way that they treat m.in_reply_to
To change the event references from m.in_reply_to to m.thread when replying to an event that has an m.thread relation (to ensure that the message will be displayed correctly in the thread when viewed on thread's ready clients)
Have you considered any alternatives?
No response
Additional context
Threads might be using a m.thread relation over m.in_reply_to
The text was updated successfully, but these errors were encountered:
bmarty
added
A-Threads
An issue for the Threads project
and removed
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
labels
Oct 14, 2021
Your use case
What would you like to do?
To take a few steps towards understanding Threads in Android before a full implementation
Why would you like to do it?
To ensure maximum backwards compatibility and continuity in conversations when threads will be available to the masses.
How would you like to achieve it?
MSC3440 recommends two things for clients that do not fully support threads yet
m.thread
the same way that they treatm.in_reply_to
m.in_reply_to
tom.thread
when replying to an event that has anm.thread
relation (to ensure that the message will be displayed correctly in the thread when viewed on thread's ready clients)Have you considered any alternatives?
No response
Additional context
Threads might be using a
m.thread
relation overm.in_reply_to
The text was updated successfully, but these errors were encountered: