# 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 13
# self = https://watcher.sour.is/conv/p2vnraq
prologic
twtxt.net
View Thread
@mckinley Kind of wondering whether you'd contribute your XLST to yarnd so we can use/apply it to all Atom feeds of the Pod's timeline and User feeds (presented as Atom)? 🤔 Could be interesting? 🤔
prologic
twtxt.net
View Thread
@mckinley Kind of wondering whether you'd contribute your XLST to yarnd so we can use/apply it to all Atom feeds of the Pod's timeline and User feeds (presented as Atom)? 🤔 Could be interesting? 🤔
mckinley
twtxt.net
View Thread
@prologic It would definitely be interesting. I don't think there could be any substantial code reuse but I'm open to the idea. I looked into doing it, but there are a few hangups that would probably need to be addressed first:
* Something in the pipeline is adding U+FFFD Replacement Characters to the ends of certain twts
* Markdown isn't rendered to HTML in the Atom feed, but mentions are.
* <summary> elements (which should probably be <contents> instead) are type="html", escaped HTML. It wouldn't be possible to embed twt contents in the generated page on Firefox-based browsers due to my favorite bug
* The other options are either plain text or inline XHTML which means you have to make sure every twt is valid XHTML.
* I don't know how to handle different themes short of JavaScript which can be buggy when used with client-side XSLT or dynamically generated XSLT which is completely and utterly ridiculous.*
mckinley
twtxt.net
View Thread
@prologic It would definitely be interesting. I don't think there could be any substantial code reuse but I'm open to the idea. I looked into doing it, but there are a few hangups that would probably need to be addressed first:
* Something in the pipeline is adding U+FFFD Replacement Characters to the ends of certa*
mckinley
twtxt.net
View Thread
@prologic It would definitely be interesting. I don't think there could be any substantial code reuse but I'm open to the idea. I looked into doing it, but there are a few hangups that would probably need to be addressed first:
* Something in the pipeline is adding U+FFFD Replacement Characters to the ends of certain twts
* Markdown isn't rendered to HTML in the Atom feed, but mentions are.
* <summary> elements (which should probably be <contents> instead) are type="html", escaped HTML. It wouldn't be possible to embed twt contents in the generated page on Firefox-based browsers due to my favorite bug
\t* The other options are either plain text or inline XHTML which means you have to make sure every twt is valid XHTML.
* I don't know how to handle different themes short of JavaScript which can be buggy when used with client-side XSLT or dynamically generated XSLT which is completely and utterly ridiculous.*
mckinley
twtxt.net
View Thread
@prologic It would definitely be interesting. I don't think there could be any substantial code reuse but I'm definitely open to the idea. I looked into doing it, but there are a few hangups that would probably need to be addressed first:
* Something in the pipeline is adding U+FFFD Replacement Characters to the ends of certain twts
* Markdown isn't rendered to HTML in the Atom feed, but mentions are.
* <summary> elements (which should probably be <contents> instead) are type="html", escaped HTML. It wouldn't be possible to embed twt contents in the generated page on Firefox-based browsers due to my favorite bug
\t* The other options are either plain text or inline XHTML which means you have to make sure every twt is valid XHTML.
* I don't know how to handle different themes short of JavaScript which can be buggy when used with client-side XSLT or dynamically generated XSLT which is completely and utterly ridiculous.*
mckinley
twtxt.net
View Thread
These aren't things I could fix myself, and in my opinion it's not worth it.
mckinley
twtxt.net
View Thread
These aren't things I could fix myself, and in my opinion some of them wouldn't be worth it if I could.
prologic
twtxt.net
View Thread
@mckinley Hmmm looks like you've found genuine bugs in our Atom output?
prologic
twtxt.net
View Thread
@mckinley Hmmm looks like you've found genuine bugs in our Atom output?
mckinley
twtxt.net
View Thread
@prologic The first two, definitely. Do you want me to open a couple issues?
prologic
twtxt.net
View Thread
@mckinley Please 🙏 Let's see if we can get them fixed 🤞
prologic
twtxt.net
View Thread
@mckinley Please 🙏 Let's see if we can get them fixed 🤞