# 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 15
# self = https://watcher.sour.is/conv/xd7fidq
Thinking about reviving (#xi7nivq) - the idea of managing bashblog comments with twtxt instead of leading people to Twitter.
@marado Oh interestinf! 😳 Did I ever comment on this idea? (I'll search later) 😆
@marado Oh interestinf! 😳 Did I ever comment on this idea? (I'll search later) 😆
@prologic You said it would work nicely, but I'd love to hear more about how you (and others) see this being done...
@prologic You said it would work nicely, but I'd love to hear more about how you (and others) see this being done...
@marado So I did 😅 So the simplest way to do this is to just either use yarnc post or the API or even just write a line to your feed that announces your blog post. Use that as the Yarn/thread to place comments again 😅
The "scope" will blow out when you want to do things like:
- Allow arbitrary internet users to comment, so you'd have to do something around identity and maybe creating ephemeral feds for them.
- Searching for previous comments and displaying them.
Although the 2nd point is probably not so bad, just have to get integrated search into pods now that search.twtxt.net is _mostly_ done 👌 (still needs an API I reckon? 🤔)
@marado So I did 😅 So the simplest way to do this is to just either use yarnc post or the API or even just write a line to your feed that announces your blog post. Use that as the Yarn/thread to place comments again 😅
The "scope" will blow out when you want to do things like:
- Allow arbitrary internet users to comment, so you'd have to do something around identity and maybe creating ephemeral feds for them.
- Searching for previous comments and displaying them.
Although the 2nd point is probably not so bad, just have to get integrated search into pods now that search.twtxt.net is _mostly_ done 👌 (still needs an API I reckon? 🤔)
@prologic I was thinking more on something along the lines of the current twitter "integration", but now that I think more about it, I realize that darch's suggestion has more merit than what I initially realized. The blog comments system can be a twtxt feed, each entry a new twt/hash, each user comment referring to that hash.
@prologic I was thinking more on something along the lines of the current twitter "integration", but now that I think more about it, I realize that darch's suggestion has more merit than what I initially realized. The blog comments system can be a twtxt feed, each entry a new twt/hash, each user comment referring to that hash.
@marado This approach is fine, as long as you're aware that there is no way to _actually_ attribute the authorship of the line in the feed that is essentially being used to let (potentially) anonymous visitors to your site/blog add comments.
I've given this a lot of thought over the months and I _think_ the best way to solve for this in general over time is to a) Build support for micro.Pub into yarnd b) Add support for IndieAuth (as a consumer) and then build out an ecosystem of Javascript and whatever libraries and tools to support this use-case.
This way when someone makes a comment on a blog post or website, they are in fact logging into their feed on some pod (that you choose to use) and they are able to take that with them, or continue using it, etc.
Just my $0.20 worth 😅
@marado This approach is fine, as long as you're aware that there is no way to _actually_ attribute the authorship of the line in the feed that is essentially being used to let (potentially) anonymous visitors to your site/blog add comments.
I've given this a lot of thought over the months and I _think_ the best way to solve for this in general over time is to a) Build support for micro.Pub into yarnd b) Add support for IndieAuth (as a consumer) and then build out an ecosystem of Javascript and whatever libraries and tools to support this use-case.
This way when someone makes a comment on a blog post or website, they are in fact logging into their feed on some pod (that you choose to use) and they are able to take that with them, or continue using it, etc.
Just my $0.20 worth 😅
@prologic tbf, microblogs as comment systems might just be a wrong idea. I was led towards it by the current twitter implementation on bashblog (which I use), but the more I think about it the more I suspect that it just is the wrong tool for the job.
@prologic tbf, microblogs as comment systems might just be a wrong idea. I was led towards it by the current twitter implementation on bashblog (which I use), but the more I think about it the more I suspect that it just is the wrong tool for the job.
@marado I _tend_ to agree with you, I find it quite weird and "wrong" (_for various definitions of_) to let random "people", "bots", "things" post to a feed that absolutely isn't theirs, have no control over and therefore the "Twts" are unauthentic 😢 I of course have strong opinions and a strong opinion on this, I know _some_ do this and _want_ to do this, but like you, it just _feels_ wrong 😅
@marado I _tend_ to agree with you, I find it quite weird and "wrong" (_for various definitions of_) to let random "people", "bots", "things" post to a feed that absolutely isn't theirs, have no control over and therefore the "Twts" are unauthentic 😢 I of course have strong opinions and a strong opinion on this, I know _some_ do this and _want_ to do this, but like you, it just _feels_ wrong 😅