# 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 61083 # self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=27191 # next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=27291 # prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=27091
!(s) from _things_ that look like they _should_ be URL(s) doesn't mean they're correct. Just because _you_ happen to have an opinion that English punctuation _should_ override the URI specifications doesn't mean you are correct.! π
! π
standards
standards
regexp based parser, but in practise we found that it was hard to do some things using ordinary regular expressions so we dropped it for a proper lexer/parser.lextwt parser anyway π€
regexp based parser, but in practise we found that it was hard to do some things using ordinary regular expressions so we dropped it for a proper lexer/parser.lextwt parser anyway π€
yarnd did something about these broken links, I will not π
yarnd did something about these broken links, I will not π
yarnd's codebase I'm fine with your choice/preference π
Try not to do it too often eh? I mean clicking on broken links is kind of annoying at best π
yarnd's codebase I'm fine with your choice/preference π
Try not to do it too often eh? I mean clicking on broken links is kind of annoying at best π
netbros.com and twtxt.net -- Both have different Cache Size and TTL configurations. I actually use the defaults mostly.netbros.com and twtxt.net -- Both have different Cache Size and TTL configurations. I actually use the defaults mostly.yarnd uses for parsing. If we split this out into a library (_actually you can already import it_) then both twet and yarnd can share the same parser - thus reducing efforts and sharing the same behaviour and bug fixes π -- I _believe_ even @lyse has managed to import lextwt via a C-extension with his Python written tt client too π
yarnd uses for parsing. If we split this out into a library (_actually you can already import it_) then both twet and yarnd can share the same parser - thus reducing efforts and sharing the same behaviour and bug fixes π -- I _believe_ even @lyse has managed to import lextwt via a C-extension with his Python written tt client too π
! in them, that's fine, just understand that is a totally valid URI.
! in them, that's fine, just understand that is a totally valid URI.
! on the end of your URL(s) π You frequently do this and ruin many URLs you link to (_I'm sure not on purpose_) π€£ -- Remember that many characters are actually valid in URL(s) π
! on the end of your URL(s) π You frequently do this and ruin many URLs you link to (_I'm sure not on purpose_) π€£ -- Remember that many characters are actually valid in URL(s) π
<!doctype html>
<head>
<title>fortune</title>
</head>
<body>
<h1>fortune</h1>
<pre><code>{{ /usr/games/fortune }}</code></pre>
</body>
</html>
<!doctype html>
<head>
<title>fortune</title>
</head>
<body>
<h1>fortune</h1>
<pre><code>{{ /usr/games/fortune }}</code></pre>
</body>
</html>
zs or mkws or some other static site generator (SSg)? π€
zs or mkws or some other static site generator (SSg)? π€
