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
{{ message }}
This repository has been archived by the owner on Mar 15, 2020. It is now read-only.
I've just realised a fatal flaw in j - anyone can post a blog in a room, even if they're not a moderator. Permission to post messages needs to be handled by the server, not by j (as it is now). This would be a simple matter of putting a power level required to send m.room.messages into room, but comments are also messages.
So comments and blogs need different event types, which can have their own custom power levels individually. Neither should be messages at this point, and messages could be reserved for general discussion about the blog as is intended by in-site messaging: #37.
I'd probably go with
j.blog.comment
j.blog.post
The text was updated successfully, but these errors were encountered:
This removes compatibility with Riot and other matrix clients supporting m.text using org.matrix.custom.html. The motivation behind this is to introduce different power levels for comments vs. blogs, which can only be done by using different event types. The room can still be used as a general chat room surrounding the blog and this might see some kind of UI in journal in the future.
See #46
I've just realised a fatal flaw in j - anyone can post a blog in a room, even if they're not a moderator. Permission to post messages needs to be handled by the server, not by j (as it is now). This would be a simple matter of putting a power level required to send
m.room.message
s into room, but comments are also messages.So comments and blogs need different event types, which can have their own custom power levels individually. Neither should be messages at this point, and messages could be reserved for general discussion about the blog as is intended by in-site messaging: #37.
I'd probably go with
j.blog.comment
j.blog.post
The text was updated successfully, but these errors were encountered: