# 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 10
# self = https://watcher.sour.is/conv/enmfm3a
I'm not the only twtxt'er that has an bashblog blog... How cool would it be to be able to integrate twtxt comments in it, in replacement to the current twitter comments implementations? With the way threads work in yarn instances, twtxt could even provide way more than just a replacement to twitter...
@marado Yup it would work nicely 😆
@marado Yup it would work nicely 😆
@marado How would you go about implementing this? 🤔 Probably some JS in the browser that collects twts? But how could this collecting work? 🤔
@marado How would you go about implementing this? 🤔 Probably some JS in the browser that collects twts? But how could this collecting work? 🤔
@marado How would you go about implementing this? 🤔 Probably some JS in the browser that collects twts? But how could this collecting work? 🤔
@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.
@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.