Make Markdown more interoperable #153
No reviewers
Labels
No Label
1000k
100k
10k
200k
20k
500k
50k
5k
75k
backend
blocked:design
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
scope:intl
scope:nip
scope:query_tracing
scope:ux
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Kieran/snort#153
Loading…
Reference in New Issue
No description provided.
Delete Branch "safer-markdown"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
By disallowing the annoying link/image syntax that would cause terrible rendering bugs in other clients.
As result of this change, this note:
Renders like this:
![2023-01-27-183610_699x896_scrot](https://user-images.githubusercontent.com/1653275/215205653-b346da44-8501-4b91-beed-dc41bd6ccc1e.png)
I like the idea but one problem I see with this approach is that
(
and)
are valid URL characters and we end up rendering broken URLs since)
at the end is treated as part of the URL by our regex.That is the point: to discourage people from posting stuff in this syntax. They are rendering broken like that on every other client too.
But sure, let me see if there is a good fallback for this.