my issue is was mainly
when viewing without js enabled
was less easy to scrape 
… but it seams that might have been
a an older version / long time ago
or some-other svr/instance config option …
because i just tested talk.tw with script-disabled again
pagination appears “?page=2” less obtuse than i recall
though im not such a fan of ‘?u=wiki_user’ (being appened to links could it be user configurable , ie disabled by me !? ;- )
… so i guess
wrt : Can we allow iframes to tiddlytalk content and is there problems doing it? - #8 by wiki_user
that might be possible with " tm-http-request"
though i didnt have much luck
… it appears ( from reading CORS for webserver API to GET tiddler ) cors was the issue and
https://api.allorigins.win/raw?url=
might help …
\procedure store-fetched-output()
<$action-setfield $tiddler=Output status=<<status>> error=<<error>> data=<<data>> headers=<<headers>>/>
\end
\procedure http-get()
<$action-sendmessage
$message="tm-http-request"
url="https://api.allorigins.win/raw?url=https://talk.tiddlywiki.org/t/other-fun-with-iframes/249"
method="GET"
oncompletion=<<store-fetched-output>>
/>
\end
<$button actions=<<http-get>>>send HTTP GET</$button>
well that works … so it appears possible to scrape with tw =]
… i guess i need some xml
(shudders …thinking of “the json saga”) tools / parser
to get a the txt from markup-data