|
|
|
|
@ -48,9 +48,8 @@ We propose three room types.
|
|
|
|
|
|
|
|
|
|
* m.social.feed
|
|
|
|
|
* m.social.group
|
|
|
|
|
* m.social.event
|
|
|
|
|
|
|
|
|
|
Those three rooms will act as a container for events of different
|
|
|
|
|
Those two rooms will act as a container for events of different
|
|
|
|
|
types, which will be displayed only on a specific client.
|
|
|
|
|
|
|
|
|
|
The type is used to set the general purpose of the room.
|
|
|
|
|
@ -97,32 +96,6 @@ m.social.group
|
|
|
|
|
Group is just a regular profile room `m.social.feed` but with a
|
|
|
|
|
slightly different UI as there is no single owner of the room.
|
|
|
|
|
|
|
|
|
|
#### Social media : Events (TODO)
|
|
|
|
|
|
|
|
|
|
This type is only an idea yet and should be defined more clearly.
|
|
|
|
|
|
|
|
|
|
Maybe the topic of another MSC.
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
m.social.event
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
This room type could be reserved for the event use case. i.e. for a
|
|
|
|
|
single event, invite people and let each user say if he will be present.
|
|
|
|
|
|
|
|
|
|
Idea:
|
|
|
|
|
|
|
|
|
|
What should be defined for the event
|
|
|
|
|
* name : [regular event] : room name
|
|
|
|
|
* main picture : [regular event] : room avatar
|
|
|
|
|
* topic : [regular event] : room topic
|
|
|
|
|
* event location
|
|
|
|
|
* event time start
|
|
|
|
|
* event time end
|
|
|
|
|
* add a way to say if we will come (maybe use regular polls)
|
|
|
|
|
|
|
|
|
|
Regular events : the actual event is already defined in matrix,
|
|
|
|
|
no need to reimplement.
|
|
|
|
|
|
|
|
|
|
### Room content
|
|
|
|
|
|
|
|
|
|
|