# 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 4
# self = https://watcher.sour.is/conv/xi7nivq
@movq I have thought of different approaches, each have strengths and weaknesses. Mostly, I'd like to know what others think :-) In any case, I suppose I'd like to "extend" the hashtag generation API, so each blog post can have its own thread hash tag (like twts do). Then, "listing" the comments could be via querying a registry, and the "leave a comment" link could link to https://preconfigured-yarn.pod/?newtwt=@blogowner%20(#hashtag) or whatever link that would open that pod ready to create that new post if you're logged in. Bonus points if you can configure more than one pod and it displays a dropdown; more bonus if we decide to implement twt:// uris letting twt clients listen to those (including a browser plug-in letting you say 'open twt:// uris on https://my.pod').
Yes, I might be overengineering.
@marado That's a great idea, and I don't think you're overengineering too badly. There's already a Gitea issue with ideas for a potential browser extension. I put the idea in that thread. Feel free to comment on it if you have something to add.
Interestingly Yarn pods used to have a built-in "full blogging" feature that used to take advantage of very similar mechanisms. It would let you write a full blog post, with URI(s) like /blogs/<username>/<yyyy>/<mm>/<dd>.html (rendered from Markdown) and would automatically "announce" the blog post as a Twt itself. That Twt would become the "Root Hash" of all "comments" on _that_ blog post.
We removed the feature as the community at the time "felt" it was out-of-scope and had a bunch of other missing features you'd typically find in a full-blogging engine.
Interestingly Yarn pods used to have a built-in "full blogging" feature that used to take advantage of very similar mechanisms. It would let you write a full blog post, with URI(s) like /blogs/<username>/<yyyy>/<mm>/<dd>.html (rendered from Markdown) and would automatically "announce" the blog post as a Twt itself. That Twt would become the "Root Hash" of all "comments" on _that_ blog post.
We removed the feature as the community at the time "felt" it was out-of-scope and had a bunch of other missing features you'd typically find in a full-blogging engine.