# 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 6
# self = https://watcher.sour.is/conv/twfherq
I don't buy jan6's premise that twts with markdown and image links is hard to read. Markdown came out of how people simulated typeset text in plain text and the URL part of links to images and others resources are also easy for humans to read and parse.
Multi-line is another matter, but I also never used the original client. I guess it could have been implemented in a was that would not break other clients. Using something like -- or just two space at the end of a line like in markdown would also work.
Yeah the argument is pretty flawed when authors can pretty much write whatever content they like including gibberish, XML, HTML or even Binary 😆
Yeah the argument is pretty flawed when authors can pretty much write whatever content they like including gibberish, XML, HTML or even Binary 😆
Yeah the argument is pretty flawed when authors can pretty much write whatever content they like including gibberish, XML, HTML or even Binary 😆
@prologic Also considering the original tagline of twtxt:
> twtxt is a decentralised, minimalist microblogging service for hackers.
if a hacker can't handle some markdown and urls in their microblogging, then user != hacker=
@prologic Also considering the original tagline of twtxt:
> twtxt is a decentralised, minimalist microblogging service for hackers.
So if a hacker can't handle some markdown and urls in their microblogging...