# 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 7
# self = https://watcher.sour.is/conv/vvbyfxa
TIL: There appear to be different whitespace collapsing rules in XML that – at least some of the parsers we used – don’t agree on. Some appear to expect that <a> </a> results in an empty string, others don’t. Well, .trim() it is, I guess.
(I didn’t research any specs on this.)
TIL: There appear to be different whitespace collapsing rules in XML that – at least some of the parsers we used – don’t agree on. Some appear to expect that <a> </a> results in an empty string, others don’t. Well, .trim() it is, I guess.
(I didn’t research any specs on this.)
TIL: There appear to be different whitespace collapsing rules in XML that – at least some of the parsers we used – don’t agree on. Some appear to expect that <a> </a> results in an empty string, others don’t. Well, .trim() it is, I guess.
(I didn’t research any specs on this.)
Or maybe it’s just bugs, of course.
Or maybe it’s just bugs, of course.
Or maybe it’s just bugs, of course.
@movq Yeah, when I had to do XML back in the days, I also stumbled across this. I might mix things up, but when I looked it up (results are long forgotten, though), there were different rules for XML and HTML. And the behavior also changed with whitespace-only content vs. whitespace pre- and suffixes. Some were kept, others weren't.