# 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 12
# self = https://watcher.sour.is/conv/feq2ekq
@justamoment The _troulbe_ with a website and trying to support some kind of "comment system" or "guestbook" type thing is that Twtxt was designed to be a text format with a 1:N mapping of author to twt(s). In essence a single feed is owned by one author that can contain zero or more twts. It is not really possible (_although @darch is trying and finding various ways to break the spec 😅_) to have a "centralised" feed that lets N users add to it.

To really support this kind of thing, you'd really have to "dynamically" create a new feed for every user, uniquely identify them in some way so you can do this (e.g: with OAuth, IndieAuth, etc), then have an API or Form that they can enter content to and it write to "their" feed._
@justamoment The _troulbe_ with a website and trying to support some kind of "comment system" or "guestbook" type thing is that Twtxt was designed to be a text format with a 1:N mapping of author to twt(s). In essence a single feed is owned by one author that can contain zero or more twts. It is not really possible (_although @darch is trying and finding various ways to break the spec 😅_) to have a "centralised" feed that lets N users add to it.

To really support this kind of thing, you'd really have to "dynamically" create a new feed for every user, uniquely identify them in some way so you can do this (e.g: with OAuth, IndieAuth, etc), then have an API or Form that they can enter content to and it write to "their" feed._
@prologic, @darch isn't breaking the spec. Here's another multi-user feed. :)
@prologic, @darch isn't breaking the spec. Here's another multi-user feed. :)
Oops, it warned me that it was longer than 140 characters and I accidentally reloaded the query page so it posted twice.
Oops, it warned me that it was longer than 140 characters and I accidentally reloaded the query page so it posted twice. You get the point, though.
Wait what?! 😳
Wait what?! 😳
@prologic It's a feed that anyone can post to with a Gopher query. Where does the spec say that one feed *must* represent a single person?
@mckinley I _think_ I've misspoken. I can't even access that feed either, it's "connection refused". If we're talking about an API (of some kind) that lets me post some text, that's totally fine. I _assume_ at that point the feed is basically a feed that anyone can post to but the "authorship" of the feed id still just one entity (although I note this feed in particular has no metadata about it so 🤷‍♂️) What gets a bit weird IMO is when you start to do things like:


<timestamp>\\tPost by prologic: Hello World!


I mean sure its a hack but no client will recognize this Twt in some random feed as a post by me.
@mckinley I _think_ I've misspoken. I can't even access that feed either, it's "connection refused". If we're talking about an API (of some kind) that lets me post some text, that's totally fine. I _assume_ at that point the feed is basically a feed that anyone can post to but the "authorship" of the feed id still just one entity (although I note this feed in particular has no metadata about it so 🤷‍♂️) What gets a bit weird IMO is when you start to do things like:


<timestamp>\tPost by prologic: Hello World!


I mean sure its a hack but no client will recognize this Twt in some random feed as a post by me.
@mckinley I _think_ I've misspoken. I can't even access that feed either, it's "connection refused". If we're talking about an API (of some kind) that lets me post some text, that's totally fine. I _assume_ at that point the feed is basically a feed that anyone can post to but the "authorship" of the feed id still just one entity (although I note this feed in particular has no metadata about it so 🤷‍♂️) What gets a bit weird IMO is when you start to do things like:


<timestamp>\tPost by prologic: Hello World!


I mean sure its a hack but no client will recognize this Twt in some random feed as a post by me.