# 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 12
# self = https://watcher.sour.is/conv/uebsf7a
quark
ferengi.one
View Thread
@movq going a little sideways on this, "*If twtxt/Yarn was to grow bigger, then this would become a concern again. *But even Mastodon allows editing*, so how much of a problem can it really be? 😅*", wouldn't it preparing for a potential (even if very, very, veeeeery remote) growth be a good thing? Mastodon signs all messages, keeps a history of edits, and it doesn't break threads. It isn't a problem there.😉 It is here.

I think keeping hashes is a must. If anything for that "feels good" feeling.
quark
ferengi.one
View Thread
@movq going a little sideways on this, "*If twtxt/Yarn was to grow bigger, then this would become a concern again. *But even Mastodon allows editing*, so how much of a problem can it really be? 😅*", wouldn't it preparing for a potential (even if very, very, veeeeery remote) growth be a good thing? Mastodon signs all messages, keeps a history of edits, and it doesn't break threads. It isn't a problem there.😉 It is here.

I think keeping hashes is a must. If anything for that "feels good" feeling.
quark
ferengi.one
View Thread
@prologic, there is a parser bug on parent. Specifically on this portion:


"*If twtxt/Yarn was to grow bigger, then this would become a concern again. *But even Mastodon allows editing*, so how
+much of a problem can it really be? 😅*"

quark
ferengi.one
View Thread
@prologic, there is a parser bug on parent. Specifically on this portion:


"*If twtxt/Yarn was to grow bigger, then this would become a concern again. *But even Mastodon allows editing*, so how
+much of a problem can it really be? 😅*"

prologic
twtxt.net
View Thread
@quark i'm guessing the quotas text should've been emphasized?
prologic
twtxt.net
View Thread
@quark i'm guessing the quotas text should've been emphasized?
bender
twtxt.net
View Thread
@prologic yes, like they show here: https://ferengi.one/#uebsf7a
prologic
twtxt.net
View Thread
@bender This is the different Markdown parsers being used. Goldmark vs. gomarkdown. We need to switch to Goldmark 😅
prologic
twtxt.net
View Thread
@bender This is the different Markdown parsers being used. Goldmark vs. gomarkdown. We need to switch to Goldmark 😅
xuu
txt.sour.is
View Thread
i feel like we should isolate a subset of markdown that makes sense and built it into lextwt. it already has support for links and images. maybe basic formatting bold, italic. possibly block quote and bullet lists. no tables or footnotes
prologic
twtxt.net
View Thread
@xuu I don't think this is a lextwt problem tbh. Just the Markdown aprser that yarnd currently uses. twtxt2html uses Goldmark and appears to behave better 🤣
prologic
twtxt.net
View Thread
@xuu I don't think this is a lextwt problem tbh. Just the Markdown aprser that yarnd currently uses. twtxt2html uses Goldmark and appears to behave better 🤣