# 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 14
# self = https://watcher.sour.is/conv/xrtbbhq
Hi twt.social / yarn.social :)
Been a while since I've been here.
I just read @jlj recent blog entry and noticed for the users with their own instance, the link to their blogs is only visible from their side. Is this by design at this stage? Only users on the same instance can reply comment on a blog?
@jlj @lazarus No you should be able to reply to blog posts like any other post.
@jlj @lazarus No you should be able to reply to blog posts like any other post.
@lazarus What you _may_ be referring to is this:\n\n 
\n\nWhere yes, if you randomly came across someone's blog post entry, you'd have to login to a valid pod somewhere to reply. But just replying with the subject hash of the blog post's announcement itself will add comments associated with that blog. Make sense?
@lazarus What you _may_ be referring to is this:
Where yes, if you randomly came across someone's blog post entry, you'd have to login to a valid pod somewhere to reply. But just replying with the subject hash of the blog post's announcement itself will add comments associated with that blog. Make sense?
@lazarus What you _may_ be referring to is this:
Where yes, if you randomly came across someone's blog post entry, you'd have to login to a valid pod somewhere to reply. But just replying with the subject hash of the blog post's announcement itself will add comments associated with that blog. Make sense?
Also... I _think_ the "display" of "comments" as such is _actually_ broken now. This is the reason I needed to build this Yarns (https://search.twtxt.net) search engine! 🤣 To illustrate; here is where @jlj 's pod announced the publication of his new blog entry and here are all the replies and conversation in response! 🙃 -- So we just need to tie the two things together (working on it!) 🤞
Also... I _think_ the "display" of "comments" as such is _actually_ broken now. This is the reason I needed to build this Yarns (https://search.twtxt.net) search engine! 🤣 To illustrate; here is where @jlj 's pod announced the publication of his new blog entry and here are all the replies and conversation in response! 🙃 -- So we just need to tie the two things together (working on it!) 🤞
@prologic @jlj Yeah, as jlj shared the direct link to the blog, not the twt about the blog, the reader has to go looking to see if there is a twt to reply to.\n\nThe twt propagates across pods but the user profile of a different pod doesn't show the link to blog entries on a different pod.\n\nIf I saw the twt at his page, I could copy the 'conv/qc5b6ba' and manually add it to twtxt.net to reply. Maybe for now, if pod owners wanted to make it easier to reply, they could copy the link and edit their blog entry to include it.
@prologic @jlj Yeah, as jlj shared the direct link to the blog, not the twt about the blog, the reader has to go looking to see if there is a twt to reply to.
The twt propagates across pods but the user profile of a different pod doesn't show the link to blog entries on a different pod.
If I saw the twt at his page, I could copy the 'conv/qc5b6ba' and manually add it to twtxt.net to reply. Maybe for now, if pod owners wanted to make it easier to reply, they could copy the link and edit their blog entry to include it.
@lazarus @jlj Hmmm 🤔 We _should_ just improve the experience here I think. I'm open to ideas, better all-round integration and UX is what I'd love to see here 👌
@lazarus @jlj Hmmm 🤔 We _should_ just improve the experience here I think. I'm open to ideas, better all-round integration and UX is what I'd love to see here 👌
Interesting -- I had no idea that blogs were any different; thanks for the heads-up, @lazarus! Good to see you too. :-)
Looks like GNU social is now advocating a Docker based deployment; might opt for that instead, actually. That's the route I went down, hosting vaultwarden on my Pi 3A, and I'm pretty happy with the results, to date.