From d3684fa8811333c99cd594107843cc58c0bd97c8 Mon Sep 17 00:00:00 2001 From: henri2h Date: Wed, 12 Jan 2022 22:00:10 +0100 Subject: [PATCH] fix: typo --- proposals/MSCZZZZ-matrix-for-the-social-media-use-case.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/proposals/MSCZZZZ-matrix-for-the-social-media-use-case.md b/proposals/MSCZZZZ-matrix-for-the-social-media-use-case.md index eafe6637b..3fec137e3 100644 --- a/proposals/MSCZZZZ-matrix-for-the-social-media-use-case.md +++ b/proposals/MSCZZZZ-matrix-for-the-social-media-use-case.md @@ -97,7 +97,7 @@ We propose two events type to categorize the content of the event. As the room is displayed alongside the user' regular chats rooms we need to make it clear to the user that it's a specific room. -Thus we need to avoid that a user end up "spamming" his room thinking +Thus, we need to avoid that a user end up "spamming" his room thinking the room is a regular chat room. The solution is to separate the regular messaging from the social @@ -117,7 +117,7 @@ be displayed on the user wall / in the group. **Why defining a specific m.social.pictures event ?** -When sending events, we want to be sure that the other users will be +When sending events, we want to be sure that the other users will be able to see our posts. Thus, it might be problematic with image only social media if we send a post with only text and then want to display it in a image only social media or is not able to render @@ -125,9 +125,9 @@ a fraction of the post (like a post with text, video, image). This becomes problematic when the user start making reference to previously sent post. -**=> We define separate types to make sure the app displaying them +> We define separate types to make sure the app displaying them is able to support all the content of this specific event type and -make sure image only and regular feeds don't mix.** +make sure image only and regular feeds don't mix. See the later point for regular room message fallback.