# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 17
# self = https://watcher.sour.is/conv/zogehjq
@prologic I don't know if a metadata field is strictly necessary. I think there ought to be a defined set of syntax that all clients with Markdown support can be expected to handle in the same way. CommonMark maybe? It looks like Yarn supports most of CommonMark already, though I've never seen a horizontal rule. Let's try it:
***
Some text here
---***
Nope, no horizontal rule. What about referenced links?

[My website][My website=][My website][My website=][My website][My website=][My website][My website=][1][1=][1][1=][1][1=][1][1=]
![An image on my website][2]

[1][1=][1][1=][1][1=][1][1=]: https://mckinley.cc/
[2][2=][2][2=][2][2=][2][2=]: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
Nope, no horizontal rule. What about referenced links?

[My website][My website=][1][1=]
![An image on my website][2]

[1][1=]: https://mckinley.cc/
[2][2=]: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
Nope, no horizontal rule. What about referenced links?

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
![An image on my website][2]

\n\n\n\n\n\n\n\n: https://mckinley.cc/
\n\n\n\n\n\n\n\n: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
Nope, no horizontal rule. What about referenced links?

\n\n\n\n\n\n\n\n
![An image on my website][2]

\n\n\n\n: https://mckinley.cc/
\n\n\n\n: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
Nope, no horizontal rule. What about referenced links?

\n\n\n\n
![An image on my website][2]

\n\n: https://mckinley.cc/
\n\n: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
Nope, no horizontal rule. What about referenced links?

[My website]\n[My website]\n[My website]\n[My website]\n[1]\n[1]\n[1]\n[1]\n
![An image on my website][2]

[1]\n[1]\n[1]\n[1]\n: https://mckinley.cc/
[2]\n[2]\n[2]\n[2]\n: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
Nope, no horizontal rule. What about referenced links?

[My website][My website][My website][My website][My website][My website][My website][My website][1][1][1][1][1][1][1][1]
![An image on my website][2]

[1][1][1][1][1][1][1][1]: https://mckinley.cc/
[2][2][2][2][2][2][2][2]: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
Nope, no horizontal rule. What about referenced links?

[My website][1]
![An image on my website][2]

[1]: https://mckinley.cc/
[2]: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
@mckinley It actually did work in the mobile app Goryon
@mckinley It actually did work in the mobile app Goryon
Probably yhe sanitizer doesn't allow it 🤔 (for web)
Probably yhe sanitizer doesn't allow it 🤔 (for web)
@prologic Referenced links also work on the Web client, but I tried both CommonMark syntax options for the horizontal rule and only one worked on Goryon.

This is exactly what I'm talking about. We should have a concrete specification so Markdown can be rendered consistently between client implementations.
Neither horizontal rule worked on the Web client, I failed to mention that.
@mckinley In that case maybe we should adopt the GoldMark library which I think implements CommonMark?
@mckinley In that case maybe we should adopt the GoldMark library which I think implements CommonMark?