Atoki/discussion
4
5
Fork 1
Code Issues 32 Pull requests 2 Projects Wiki Activity

have spoilers be handled better #20

New issue
Open
opened 2023-08-03 16:00:45 +02:00 by theotheroracle · 1 comment
theotheroracle commented 2023-08-03 16:00:45 +02:00
Copy link

ckie (they/them): because what it does is send a HTML tag and put the user's proceeding message into it w/o any escaping whatsoever

ckie (they/them): so that meshes well with the Message AST idea that's in the backlog

Sorunome ⚡️ Lucky Skies: /spoiler is the wrong syntax to go about spoilers anyways. spoilers were designed to be able to put inline, e.g. via ||reason|spoilerd text||
or just ||spoiler||, if no reason is specified

joepie91 🏳️‍🌈: I think we probably need an issue about input format more generally, because the inconsistency around this between clients is often a source of confusion, and "just use CommonMark" has turned out not to be the solution

> ckie (they/them): because what it does is send a HTML tag and put the user's proceeding message into it w/o any escaping whatsoever > ckie (they/them): so that meshes well with the Message AST idea that's in the backlog > Sorunome ⚡️ Lucky Skies: /spoiler is the wrong syntax to go about spoilers anyways. spoilers were designed to be able to put inline, e.g. via ||reason|spoilerd text|| or just ||spoiler||, if no reason is specified > joepie91 🏳️‍🌈: I think we probably need an issue about input format more generally, because the inconsistency around this between clients is often a source of confusion, and "just use CommonMark" has turned out not to be the solution
👍 1
zocker.net commented 2023-08-15 11:35:06 +02:00
Copy link

maybe it makes even sense to define a minimal CommonMark subset (+ Matrix specific additions), which all clients SHOULD support (at least optionally)? (“SHOULD” as per RFC 2119)

maybe it makes even sense to define a minimal CommonMark subset (+ Matrix specific additions), which all clients SHOULD support (at least optionally)? (“SHOULD” as per [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119))
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Atoki/discussion#20
No description provided.